clean-architecture-validator

Clean architecture violations are detected by mapping source code into domain, application, infrastructure, and presentation layers, then analyzing imports to enforce dependency rules. This process flags broken boundaries, direct infrastructure links, and misplaced repository or port interfaces.

The dependency rule dictates that domain and application layers must never depend on infrastructure or presentation layers. Proper interface placement requires repository and port interfaces to reside in inner layers, ensuring dependencies always flow inward toward the domain.

Review code for layer boundary violations by running an architecture compliance audit that maps dependencies across domain, application, infrastructure, and presentation layers. This returns a focused list of issues and refactoring guidance indicating where misplaced code should move.

Yes, architecture compliance checks validate interface placement and flag misplaced repository and port interfaces. The validation identifies ports living in the wrong layer and provides short refactoring fixes explaining exactly where the code should move.

Clean architecture validation works without external dependencies. It relies solely on source code import analysis and layer mapping to audit dependency flow across domain, application, infrastructure, and presentation areas without requiring additional tools.