After several weeks of fixing bugs, refining edge cases, and rolling out new features based on direct feedback from early users, both the Drupal Site Audit module and the DruScan dashboard can now be considered stable.
What's new in the dashboard
Two significant additions have landed during this period:
A charts system that visualizes how scores evolve over time across categories. Until now, the dashboard only showed current scores. It now also shows the history, so trends are visible at a glance and improvements (or regressions) over weeks and months can be spotted.
An email notifications system that fires when a project's score drops, when a security update is detected on any connected project, or when a regression appears between environments. The frequency depends on the plan tier (monthly, weekly, or daily). The point is the same in all cases: no need to keep checking the dashboard manually to find out when something needs attention.
Both features have been running on real projects for several days without surprises. That's the threshold that justified declaring this version stable.
Thanks to the early users
The version that's stable today is not the version that was published a month ago. Several people who installed the module and tested the dashboard during the past month sent feedback about things that didn't work as expected, things that were confusing, or things they expected to find and couldn't. Conversations with some of them led directly to changes that made it into this version, including parts of the notifications system, which was shaped by what users said they actually wanted to be alerted about.
If you're one of the people who took the time to write in: thank you. Real people running this on real projects is what makes the difference between something that works in a controlled environment and something that holds up across the variety of configurations the world throws at it.
What stable means (and what it doesn't)
Calling something stable doesn't mean done. It means there's no longer a backlog of known bugs that would block anyone from using it confidently. New scenarios will still come up. Some hosting configurations are unusual. Some Drupal projects do things in ways nobody expected. Those cases will get handled as they appear.
What stable does mean is that anyone installing the module today, or signing up for the dashboard today, can expect it to work as advertised. That's a different thing from "early access" or "beta", and the distinction is worth making.
Feedback is still welcome
The module and the dashboard are stable, but they aren't finished. There's a roadmap of features still to build, integrations still to add, and refinements still to make based on how people actually use the tool.
If something doesn't work, if a metric is missing or off, or if there's a way a workflow could be smoother: write to [email protected] or open an issue in the module's queue on drupal.org.
Feedback at this stage still has a direct impact on what gets built next.