Search docs
Docs searchValidation rule
Back to Rule CatalogAP-DEP-007DependencyPotential orphan module detected
Flags modules with no declared or actual inbound/outbound module dependencies.
warningviolationAuto-fix available
How to fix
- Decide whether the isolation is intentional.
- Connect the module through legitimate dependencies or document the intentional isolation.
- Remove stale modules that are no longer part of the architecture.
What the rule validates
A registered module is isolated from the module graph.
Why it matters
An isolated module may be intentional, but it can also mean stale architecture metadata or unused code.
Common causes
- The module is intentionally standalone.
- The module is registered before it is used.
- The module is obsolete and should be removed.
Typical violation example
A registered health module has no inbound or outbound dependencies and no ADR explaining the isolation.Typical compliant example
The module is either connected through valid dependencies or documented as intentionally isolated.Related rules
AP-DEP-001 - Circular module dependency detectedAP-DEP-002 - Forbidden cross-module dependency detectedAP-DEP-003 - Non-public cross-module import detectedAP-DEP-004 - Cross-module dependency missing from module contract
Adjacent categories
Related files/config
.archpilot/architecture.json.archpilot/contracts/*.json
Related CLI commands
archpilot fix AP-DEP-007archpilot validatearchpilot validate --ci