>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3567304. --> Reported by: [trebormc](https://www.drupal.org/user/1750828) >>> <p>## Summary</p> <p>The `drupal/audit` Composer namespace is incorrectly occupied by a submodule from the<br> abandoned project `audit_custom`. This blocks the legitimate project at<br> <a href="https://www.drupal.org/project/audit">https://www.drupal.org/project/audit</a> from using its expected namespace.</p> <p>## Current situation</p> <p>When running: composer show drupal/audit --all<br> name : drupal/audit<br> descrip. : &#23457;&#25209;&#27169;&#22411;<br> keywords :<br> versions : 1.x-dev, dev-1.x<br> type : metapackage<br> license : GNU General Public License v2.0 or later (GPL-2.0-or-later) (OSI approved) <a href="https://spdx.org/licenses/GPL-2.0-or-later.html#licenseText">https://spdx.org/licenses/GPL-2.0-or-later.html#licenseText</a><br> homepage : <a href="https://www.drupal.org/project/audit_custom">https://www.drupal.org/project/audit_custom</a><br> source : []<br> dist : []<br> names : drupal/audit</p> <p>The namespace points to a submodule inside `audit_custom`, not to the actual<br> `drupal.org/project/audit` project.</p> <p>## Why this namespace should be released</p> <p>### 1. I am the active maintainer of drupal.org/project/audit</p> <p>I recently took over maintainership of the `audit` project and I'm actively developing it.<br> I'm pivoting the module from its original purpose (content auditing) to a comprehensive<br> **Drupal site health auditing framework** that includes:</p> <p>- Site configuration analysis<br> - Code quality checks (PHPStan, PHPCS integration)<br> - Performance audits<br> - Security configuration reviews<br> - Module update tracking<br> - Multiple specialized submodules (audit_status, audit_cron, audit_modules, etc.)</p> <p>A new release is coming soon with these improvements.</p> <p>### 2. The blocking project (audit_custom) is abandoned</p> <p>The `audit_custom` project (<a href="https://www.drupal.org/project/audit_custom">https://www.drupal.org/project/audit_custom</a>):</p> <p>- Is marked as **"Seeking new maintainer"** (abandoned)<br> - Has **0 reported site installations**<br> - Is **not covered by Drupal's security advisory policy**<br> - Was created in 2017 with no meaningful recent activity<br> - Its own description says "please rename audit_custom to audit" - acknowledging<br> the naming issue</p> <p>### 3. Drupal standards support this request</p> <p>Per Drupal's Composer package naming conventions:<br> &gt; "In the case naming conflicts cannot be resolved, Drupal Projects shall take<br> &gt; precedence over (sub-)modules"</p> <p>The project `drupal.org/project/audit` should have priority over a submodule<br> named `audit` inside another project.</p> <p>## Requested action</p> <p>Please reassign the `drupal/audit` namespace to point to <a href="https://www.drupal.org/project/audit">https://www.drupal.org/project/audit</a><br> instead of the audit_custom submodule.</p> <p>The audit_custom project maintainer should be notified to rename their submodule<br> (e.g., to `audit_custom_core` or similar) to avoid this collision.</p> <p>## References</p> <p>- Active project: <a href="https://www.drupal.org/project/audit">https://www.drupal.org/project/audit</a><br> - Blocking project: <a href="https://www.drupal.org/project/audit_custom">https://www.drupal.org/project/audit_custom</a></p> <p>Thank you for your help resolving this namespace conflict.</p>