ddd-evaluator

To evaluate source code for Domain-Driven Design conformance, you provide a codebase path to the evaluator, which then analyzes it to detect tactical DDD patterns, anti-patterns, and ubiquitous language gaps. It generates a report with health metrics.

Common Domain-Driven Design anti-patterns identified during code review include missing invariants enforcement in entities, improper aggregate boundaries, and ubiquitous language gaps between code naming and domain language. The evaluator flags these modeling quality issues.

Yes, you can use a DDD evaluator to check ubiquitous language consistency by evaluating naming conventions against the domain language across the codebase. It identifies gaps where code structure diverges from domain terminology.

You validate aggregate and repository implementations by running a pattern analysis on the codebase, which classifies code structures against expected DDD tactical patterns and flags modeling quality issues. It produces actionable findings for architects.

Yes, DDD code analysis is applicable to codebases across different domains. It validates entities, value objects, aggregates, and repositories by reading the code before classifying, ensuring domain-agnostic conformance evaluation.