What problem does it solve?
Domain-driven design codebases gradually erode as developers accidentally import across bounded contexts or bypass aggregate invariants, and these boundary leaks are hard to spot in manual code review.
Core Features & Use Cases
- Boundary Violation Detection: Scans TypeScript files to flag imports that reach directly into another bounded context's domain layer instead of its public application interface.
- Invariant and Event Auditing: Checks aggregate roots for public setters that bypass validation, verifies domain events are past-tense named and immutable, and confirms repository interfaces live in the domain layer.
- Use Case: Before merging a cross-cutting pull request, run the validation to produce a categorized report of BOUNDARY, INVARIANT, EVENT, and REPOSITORY violations with file paths, line numbers, and suggested fixes, then store the summary as a CI gate record.
Quick Start
Audit my DDD codebase for cross-context import violations and aggregate invariant issues, then report all boundary violations by category.