dependency-boundary-check

To detect architecture boundary violations, analyze source trees and module import graphs to surface forbidden layer directions, cyclic coupling, and infrastructure leakage into domain or UI layers. This produces a structured report of observed dependencies and coupling risks.

Cyclic coupling and infrastructure leakage occur when modules bypass intended layering constraints, allowing forbidden dependency directions or shared-abstraction misuse. Analyzing change diffs and import graphs identifies these inappropriate shared code usages before architecture erodes.

Yes, you can run a dependency boundary analysis against a pull request to identify newly introduced boundary violations, UI or delivery code carrying domain decisions, and recommended corrective actions prior to merge.

The best way to find forbidden layer directions is by analyzing the module import graph to enumerate package and layer-level dependencies, flagging implicit coupling and inappropriate shared code usage that violate architectural boundaries.

To get prioritized recommendations for fixing coupling risks, run a dependency boundary analysis on the target repository, which outputs a structured report including observed dependencies, identified violations, and minimal immediate actions for architects and reviewers.