architecture-compliance

Enforce architectural layer boundaries by validating dependencies across Views, Components, Services, API, and Core layers to prevent cross-layer violations and detect circular dependencies during module addition or refactoring.

Detect circular dependencies by running a validation workflow that audits dependency rules across your codebase layers, returning a detailed report of violations and graph-based analysis to pinpoint unwanted circular references.

Dependency-cruiser integrates with validation workflows to enforce service-layer design patterns, applying strict architectural compliance rules to maintain code quality and prevent unwanted cross-layer dependency violations.

Generate dependency graphs by running the architecture compliance workflow, which analyzes your codebase structure, identifies layer boundary violations, and produces visual graph outputs for architectural analysis and refactoring guidance.

Validate architectural layer boundaries during refactoring by applying dependency rule enforcement checks that ensure correct layer usage and detect violations before they break existing module dependencies or introduce circular references.

Architecture compliance checks are needed when adding new modules to ensure correct layer usage, prevent unwanted cross-layer dependencies, and maintain service-layer design patterns that keep the codebase maintainable and free of circular dependencies.