Evyweb/simple-ddd-toolkit

The Aggregate base class now supports asynchronous, non-blocking dispatch of domain events via a new \dispatchEventsAsync\ method, which uses \setImmediate\ to avoid blocking the main thread. The synchronous \dispatchEvents\ method has been updated to be \async\ and now accepts an \EventBusPort\ interface instead of a concrete \EventBus\ class, improving testability. Additionally, a \getEvents\ method has been added to retrieve a snapshot of pending domain events.

src/aggregate · medium confidence

The base ValueObject now uses a recursive deep-freeze mechanism to ensure all nested data structures are immutable, and equality checks are performed via a new reflective comparison method. For UUIDs, the API is simplified: the static create method now accepts an explicit value and isNew flag, removing the previous separation between create (auto-generate) and createFrom (manual) methods, and the dependency on Node's crypto module is removed.

src/valueObject · high confidence

The event bus now supports a middleware chain, allowing cross-cutting concerns like logging to be applied around event handling. The \EventBus\ class now uses a \use\ method to register \IEventMiddleware\ implementations, such as the new \EventLoggingMiddleware\ which logs event details. Additionally, the bus now provides \dispatchEvents\ for synchronous batch processing and \dispatchEventsAsync\ for fire-and-forget asynchronous processing, improving consistency and performance for multiple events.

src/eventBus · high confidence

The separate CommandBus and QueryBus implementations have been removed, consolidating the two into a single, unified bus. This change simplifies the registration of commands and queries, removing the previous separation between command and query handling mechanisms.

src/commandBus · high confidence

The project has migrated its code quality and formatting tooling from ESLint/other formatters to Biome, introducing a new biome.json configuration file that enforces import organization, linting, and formatting rules (including a 120-character line width). Additionally, the TypeScript configuration (tsconfig.json) has been updated to target ES2022, enable declaration generation, and adjust module resolution and strictness settings to align with the new tooling and modern standards.

(repo-wide) · high confidence

The error handling classes in the src/errors directory have been refactored. The abstract property errorName on CustomError has been replaced with \_\_TAG, and the isDomainError and isTechnicalError methods have been implemented in the DomainError and TechnicalError subclasses to distinguish between domain and technical errors. Additionally, the code formatting has been updated to use 4-space indentation.

src/errors · medium confidence

The domain event system has been refactored to use an abstract \DomainEvent\ class that implements a \Message\ interface, replacing the previous interface-based approach. This change introduces dedicated \Payload\ and \Metadata\ types, allowing domain events to carry structured data and arbitrary metadata. The \DomainEvent\ class now encapsulates \eventId\, \occurredOn\, \payload\, and \metadata\ properties, providing a more robust foundation for event handling and metadata autocompletion.

src/domainEvent · medium confidence

The \ICommand\ and \ICommandHandler\ interfaces have been removed from the codebase. This eliminates the optional response pattern for commands, simplifying the command structure by removing these specific interface definitions.

src/command · high confidence

The command and query middleware interfaces (CommandMiddleware, QueryMiddleware) and the CommandLoggingMiddleware implementation have been removed from the codebase. This eliminates the previous middleware execution chain for commands and queries, meaning logging and potential side-effects from these middleware layers will no longer occur.

src/middleware · high confidence

The generic interfaces IQuery, IQueryHandler, and IResponse have been removed from the codebase. This eliminates the shared abstractions for query types, handlers, and responses, likely as part of a broader simplification of the command/query pattern implementation.

src/query · high confidence

The set method on the Entity class is now protected, meaning it can only be called from within the class or its subclasses, preventing external code from directly modifying entity state via the set method.

src/entity · high confidence

The public API surface has been reorganized: command and query buses are now exported from the new 'bus' directory, with separate exports for commands, queries, and their respective handlers. Middleware and logging utilities have been consolidated under the 'bus' and 'domainEvent' paths. Additionally, the IUseCase interface's execute method now explicitly returns a Promise\<void\>, clarifying its asynchronous nature.

src · medium confidence

The message bus has been refactored to support both commands and queries through a single, unified Bus class. This change introduces a shared Message type with a \_\_TAG identifier, allowing the bus to route messages to their respective handlers. Additionally, the architecture now supports a middleware pipeline, enabling cross-cutting concerns like logging to be applied to both command and query execution flows.

src/bus · high confidence

The Result class now uses a discriminated union (success/failure) with a \\_tag\ property to track state, replacing the previous approach of storing separate \\_value\ and \\_error\ fields. This change introduces explicit \getValue()\ and \getError()\ methods to safely access the result's content, ensuring that accessing the wrong state (e.g., getting a value from a failure) throws an error rather than returning undefined. The \isOk()\ and \isFail()\ type guards have also been updated to check the \\_tag\ property.

src/result · high confidence

Added comprehensive test coverage for the command and query bus implementations; Added tests for value object equality and immutability; Removed obsolete test files for the command bus; Removed test infrastructure for command handlers; Update error class tests to use \_\_TAG property; Updated Result spec to use new getter methods; Updated aggregate and UUID test suite; Updated entity test suite with new imports and formatting; Updated use case test to use new command structure.

The project's package manifests have been updated to version 0.21.1, with the lock file reflecting upgrades to TypeScript (5.3.3→5.8.3), Vitest (1.3.1→3.1.2), @changesets/cli, and @types/node. A new dev dependency, @biomejs/biome, has been added alongside @vitest/coverage-v8 and rimraf, while the configuration now specifies 'dist/' as the published files and sets the npm registry access to public.

(dependencies) · medium confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 62 → 65 (+2.9)
• Rubric changed (rubric-2026.08.18 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 99 → 97 (-1.8)
• Architecture 69 → 69 (+0.0)
• Maturity 54 → 57 (+2.8)
• Readiness 61 → 71 (+10.3)
• Security 73 → 74 (+1.5)

• Coverage not included — suite not readable by the collector
• Critical CVE: [GHSA redacted] (package-lock.json)
• Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• Low CVE: [GHSA redacted] (package-lock.json)
• No exposed public API
• Test reliability not included
• The document begins with a two-line warning about unreleased production readiness, then an installation block, and features as checkboxes before any content on Value Object or Entity appears. The outlined sections 'Value Object' and 'Entity' are present in the Features outline but not yet shown. (README.md)
• no production source files with tracked history to analyse
• …and 1 more

• Critical CVE: [GHSA redacted] (package-lock.json)
• Dependency hygiene PARTLY measured — npm pinning read, dependency currency not (the committed lockfile resolved no direct production dependency)
• Documentation: no installation or build instructions (README.md)
• Documentation: no usage examples (README.md)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High CVE: [GHSA redacted] (package-lock.json)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• Low CVE: [GHSA redacted] (package-lock.json)
• …and 5 more

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

Evyweb/simple-ddd-toolkit was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.