As repositories grow, modular boundaries erode. What began as a clean layered architecture degrades into spaghetti dependencies, undocumented cross-package imports, and configuration fragmentation. Catalayer Code scans directory trees to map architectural drift.
Directory topology mirrors system architecture.
Circular dependencies between sibling packages indicate leaky abstractions.
Monorepos require centralized dependency governance and workspace lockfile coordination.
Detecting structural decay early prevents painful multi-month architectural rewrites.
Specific verifiable repository conditions evaluated by Catalayer Code.
| SIGNAL NAME | VERIFIED REPOSITORY CONDITION | CONFIDENCE | TARGET RISK MITIGATED |
|---|---|---|---|
| Workspace Boundary Enforcement | Validates pnpm-workspace.yaml, lerna.json, or npm workspaces definitions | HIGH | Orphaned packages and uncoordinated dependency versions |
| Deep Nesting Topology Risk | Flags directory nesting exceeding 6 levels deep | MEDIUM | Excessive coupling and fragile import paths |
Structural rot presents concrete symptoms: duplicated utility modules across sibling folders, inconsistent tsconfig.json configurations, and root-level script bloat. Catalayer Code highlights these signals to maintain clean separation of concerns.
What this inspection method does not and cannot evaluate.
Run deterministic checks against any public repository without granting OAuth permissions. Review structural gaps, untested changes, and reviewability findings with evidence.
Yes. It recognizes package workspaces across JavaScript/TypeScript, Go workspaces, Cargo workspaces, and Python poetry/uv monorepos.