architecture-lint

You can detect clean architecture violations by running static analysis across Events, Facades, Services, and Repository layers to find cross-layer access, transaction misuse, and DB connection violations, producing a structured remediation report.

A cross-layer dependency violation is an unauthorized direct call bypassing intended boundaries, such as Events calling Services or Repositories directly, or Facades accessing Repositories. Static analysis identifies these calls to enforce proper layering.

Enforce transaction boundaries in the Facade layer by validating that begin, commit, and rollback operations reside exclusively there. The linter detects transaction misuse outside this layer and reports it for remediation.

Yes, you can check for DB connection violations by scanning layers to prevent individual components from creating their own connections. The linter enforces shared access from AppState and flags unauthorized connection creation.

Beyond dependency direction, a static analysis linter checks architectural rules including transaction boundary placement and database connection usage. It detects transaction misuse and prevents layers from creating independent DB connections.

Yes, the architecture linter works without external dependencies or components. It applies a step-by-step methodology directly to your codebase to identify, analyze, and report violations across your architectural layers.