Just published a contributed module on drupal.org for auditing Drupal projects:
https://www.drupal.org/project/audit
It analyzes your installation and gives you scored reports across different categories: module updates, security, cache, performance, SEO, fields, Views... with concrete recommendations in each one. It's built around independent submodules so you only enable what makes sense for each project.
The idea is that you install it, run the audit, and get a clear picture of what's wrong and where to focus. It works on any hosting, everything stays on your server, and most submodules are fine to run on production. The only exceptions are audit_phpstan and audit_phpcs, which do static code analysis and require dev dependencies so those are better suited for development or staging environments.
Curious how you currently handle audits across your Drupal projects and whether something like this would fit into your workflow or not. Any feedback is welcome.
submitted by
/u/rmenetray [link] [comments]