Custom Integration Auditor

Custom Integration Auditor helps teams keep custom code maintainable by scanning enabled extensions (typically under modules/custom/) for integration problems: empty hook implementations, broken service definitions, event subscriber wiring mistakes, and overlapping hook plus subscriber logic. It provides an admin report, a Drush command for CI, and optional demonstration mode with clearly labeled sample findings for training—not real site errors.

Features
When you maintain custom modules or themes, it is easy to leave behind empty hooks, duplicate entity presave logic, or YAML that references missing classes. This module runs a static audit and lists findings with severity, category, file, and line where possible.

Configurable scan scope (enabled extensions, custom module path, optional custom themes, additional machine names).
Detects empty procedural and attribute-based (#[Hook]) hook implementations.
Validates *.services.yml class references and event subscriber method wiring.
Flags plugin classes under src/Plugin that appear to lack plugin discovery metadata.
Warns when the same extension implements both a procedural hook and a related event subscriber (for example hook_entity_presave() and a presave subscriber).
Administrative audit report with paging and severity summary.
Drush cia-audit with configurable exit codes for deployment pipelines.
Demonstration mode: administrators can click Run demonstration audit on the report page to preview sample rows. The Type column shows Demonstration, messages include [DEMO — not a real issue], and demo rows do not count toward Drush failure unless real scan findings meet your severity threshold.
Use it during code review, after onboarding developers, before releases, or in CI to catch regressions in custom code hygiene.

Post-Installation
After installation, grant or confirm permissions, configure scan scope, and open the report.

Enable the module (for example drush en custom_integration_auditor -y) and rebuild caches.
Permissions: Administer custom integration auditor (settings) and View custom integration auditor report (report). Both are granted to the Administrator role on install.
Settings: Configuration → Development → Custom integration auditor (/admin/config/development/custom-integration-auditor).
Report: Configuration → Development → Integration audit report (/admin/config/development/custom-integration-auditor/report).
Optional demo: on the report page, click Run demonstration audit, review sample rows, then Clear demonstration.
Automation: drush cia-audit (options such as --severity=error and --demo are documented in the README).
No new content types or fields are added. The module reads extension files and service definitions only; it does not modify your custom code.

Additional Requirements
Drupal core 10.3+ or 11+.
PHP 8.1+.
Core User module (permissions and Administrator role on install).
Drush is optional but recommended for CI.
Recommended modules/libraries
None required. PHPStan or PHPCS can complement this module; Custom Integration Auditor focuses on Drupal integration patterns (hooks, services, subscribers, plugins), not general PHP analysis.

Similar projects
Devel supports runtime debugging but does not offer this scan-only hygiene report for custom extensions. PHPStan and PHPCS address types and coding standards; this module adds Drupal-specific integration checks and labeled demonstration mode for training.

Supporting this Module
Report issues and feature requests in the project issue queue on Drupal.org. Contributions via the official Git repository are welcome.

Community Documentation
See the bundled README.txt and README.md for permissions, Drush options, demonstration mode, and limitations (static analysis only).

Short summary for “Edit summary” (max 200 characters): Scans custom modules and themes for empty hooks, wiring errors, and redundant integrations. Admin report, Drush CI audit, and optional demo mode with labeled samples.