ddd-validator

Layer separation validation checks that your Presentation, Application, Domain, and Infrastructure layers follow DDD rules—ensuring the Domain layer has zero external dependencies, Application layer uses @injectable() decorators correctly, and repositories use token-based injection. Run the validator against your codebase to identify violations and get actionable recommendations.

The validator enforces domain pattern compliance including private constructors, create/reconstitute factory methods, and getter-only property access on entities and value objects. It also validates that @injectable() is used properly in the Application layer and that repositories are injected via tokens, not direct instantiation.

Yes. The validator performs non-destructive, non-invasive analysis that identifies DDD architecture violations without altering code. It reports critical issues, warnings, and suggestions, making it suitable for automated pre-commit hooks and integration into code review workflows.

The validator flags this as a violation. DDD requires the Domain layer to remain free of framework dependencies to ensure business logic stays decoupled and portable. The validator identifies these unauthorized imports and reports them as critical issues.

This validator works with existing codebases implementing Domain-Driven Design across multiple layers. It analyzes your current architecture without modifying code, identifies where patterns diverge from DDD principles, and enables refactoring validation to progressively improve compliance.