sarj/graph/disallowed-code-dependency Follow the code dependency matrix
Production code dependencies follow the closed component-kind matrix.
error
Examples
migration set --source-import--> contractmigration set --package-dependency--> shared libraryWhy it matters
The closed matrix keeps reusable and deployable layers independently releasable.
How detection works
A code dependency targets a component kind not allowed for its source kind.
What is inspected
- source and target kinds plus declared code dependency
How to fix it
Replace implementation coupling with an owned library or runtime contract.
- Target an allowed library, contract, or generated-client kind.
Verify
- Run repo-lint again and confirm the rule passes.