Magebean Logo Magebean
← Back to Baseline

MB-0808

Partially automated Consistent static Magento module identity

MB-C20 Module Integrity & Compatibility Medium

Literal module registrations and module.xml names agree for selected module roots, and a literal registration name has a unique installed root.

Overview

Compare literal registration.php names, etc/module.xml and installed roots. Duplicate roots can make ownership and deployment resolution ambiguous.

Why it Matters

Conflicting module identities can cause the wrong component to be resolved or deployed.

Interpret the reported resource and collection scope before making changes. Unsupported source, unresolved symbols and bounded collection gaps cannot establish a clean result.

Verification Steps

Manual Verification

  1. Compare literal registration.php names, etc/module.xml and installed roots. Duplicate roots can make ownership and deployment resolution ambiguous.
  2. Inspect the reported file, declaration, package or evidence record in the same selected release. Keep source observations separate from effective runtime behavior.
  3. Apply the rule-specific remediation below, validate the affected behavior in staging, and rerun the same selection.

Command / Review Sample

php magebean.phar audit --path=/var/www/magento --profile=module-integrity --rules=MB-0808 --modules=Vendor_Module

Use the assessed Magento project and the appropriate application or read-only review account. Replace example hosts, paths and identifiers with the assessment scope; configuration and source fragments are illustrative.

Remediation / Fix Guidance

  1. Fix inconsistent component names or remove the duplicate installation.
  2. Verify the corrected behavior in an authorized staging environment.
  3. Rerun MB-0808 with the same module selection.

Examples

Illustrative declaration/review examples, not recorded scan output. A pass example concerns only the stated predicate and supported collected scope.

Fail Example

registration.php: Vendor_Old
module.xml: Vendor_Module

Pass Example

registration.php: Vendor_Module
module.xml: Vendor_Module
One installed root for this identity.

Scope and Evidence Limits

Rule revision: 1. Target modes: LOCAL.

Literal module registrations and module.xml names agree for selected module roots, and a literal registration name has a unique installed root.

Dynamic registration, absent metadata, and incomplete discovery require a collection diagnostic.

Catalog coverage describes implementation capability, not a scan outcome. An incomplete manual review cannot establish that the criterion is satisfied.

References