Executive summary
nestjs/cqrs falls short of our standard for production, held back most by its Domain Modelling lens, the way the code models the business it serves. It scores 56 out of 100 and is rated Adequate, and 15 of its 17 critical findings are security problems.
Domain Modelling, at 51, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step for the work it takes is rebalancing the test suite towards unit tests, worth about 2 points. Validating new business objects would lift Domain Modelling itself, worth about 3 points.
Ten passwords or keys in the code's history and one in the code are open to anyone who can read the repository. Three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Replacing each exposed password or key and pinning each tool to an exact version would close both risks. Updating the vulnerable packages would fix the package with a known security hole. The two loops of files that import each other need breaking.
The product code is 2,208 lines, about €6,100 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 2 findings
- Dependency Vulnerabilities · REDACTED
- Large Files · src/event-bus.ts: 420 lines of code src/event-bus.ts
Fixed since the last survey: 5 findings
- Code Duplication · Duplicated block (15 lines × 2 locations) src/event-bus.ts
- Code Duplication · Duplicated block with local edits (9 matched lines × 2 locations) src/interfaces/aggregate-root.interface.ts
- Code Duplication · Duplicated block (6 lines × 2 locations) src/command-bus.ts
- Large Files · src/event-bus.ts: 416 lines of code src/event-bus.ts
- Documentation (README) · README may be stale
Rebuild cost: about €6,100 · Estimate
| Cost to rebuild | €2,000 to €10,000, for 34 to 108 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 56. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 2,208 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 aggregate-root | 2 exceptions.command-not-found_exception | 3 exceptions.invalid-command-handler_exception | 4 exceptions.invalid-events-handler_exception | 5 exceptions.invalid-query-handler_exception | 6 interfaces.aggregate-root_interface | 7 interfaces.commands.command-publisher_interface | 8 interfaces.commands.command_interface | 9 interfaces.events.event-handler_interface | 10 interfaces.events.event-id-provider_interface | 11 interfaces.events.message-source_interface | 12 interfaces.exceptions.unhandled-exception-info_interface | 13 interfaces.providers-introspection-result_interface | 14 interfaces.queries.query-publisher_interface | 15 interfaces.queries.query_interface | 16 scopes.async_context | 17 utils.observable-bus | 18 classes.command | 19 classes.query | 20 decorators | 21 helpers.default-command-pubsub | 22 helpers.default-event-id-provider | 23 helpers.default-query-pubsub | 24 interfaces.events.event-bus_interface | 25 interfaces.events.event-publisher_interface | 26 interfaces.exceptions.unhandled-exception-publisher_interface | 27 mixins.with-aggregate-root_mixin | 28 services.explorer_service | 29 helpers.default-pubsub | 30 helpers.default-unhandled-exception-pubsub | 31 interfaces.commands.command-bus_interface | 32 interfaces.cqrs-module-options_interface | 33 interfaces.queries.query-bus_interface | 34 command-bus | 35 query-bus | 36 unhandled-exception-bus | 37 event-bus | 38 cqrs_module | 39 event-publisher | 40 storages.aggregate-root_storage |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 aggregate-root | ||||||||||||||||||||||||||||||||||||||||
| 2 exceptions.command-not-found_exception | ||||||||||||||||||||||||||||||||||||||||
| 3 exceptions.invalid-command-handler_exception | ||||||||||||||||||||||||||||||||||||||||
| 4 exceptions.invalid-events-handler_exception | ||||||||||||||||||||||||||||||||||||||||
| 5 exceptions.invalid-query-handler_exception | ||||||||||||||||||||||||||||||||||||||||
| 6 interfaces.aggregate-root_interface | ||||||||||||||||||||||||||||||||||||||||
| 7 interfaces.commands.command-publisher_interface | ||||||||||||||||||||||||||||||||||||||||
| 8 interfaces.commands.command_interface | ||||||||||||||||||||||||||||||||||||||||
| 9 interfaces.events.event-handler_interface | ||||||||||||||||||||||||||||||||||||||||
| 10 interfaces.events.event-id-provider_interface | ||||||||||||||||||||||||||||||||||||||||
| 11 interfaces.events.message-source_interface | ||||||||||||||||||||||||||||||||||||||||
| 12 interfaces.exceptions.unhandled-exception-info_interface | ||||||||||||||||||||||||||||||||||||||||
| 13 interfaces.providers-introspection-result_interface | ||||||||||||||||||||||||||||||||||||||||
| 14 interfaces.queries.query-publisher_interface | ||||||||||||||||||||||||||||||||||||||||
| 15 interfaces.queries.query_interface | ||||||||||||||||||||||||||||||||||||||||
| 16 scopes.async_context | ||||||||||||||||||||||||||||||||||||||||
| 17 utils.observable-bus | ||||||||||||||||||||||||||||||||||||||||
| 18 classes.command | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 classes.query | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 decorators | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 helpers.default-command-pubsub | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 helpers.default-event-id-provider | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 helpers.default-query-pubsub | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 interfaces.events.event-bus_interface | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 interfaces.events.event-publisher_interface | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 interfaces.exceptions.unhandled-exception-publisher_interface | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 mixins.with-aggregate-root_mixin | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 services.explorer_service | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 helpers.default-pubsub | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 helpers.default-unhandled-exception-pubsub | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 interfaces.commands.command-bus_interface | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 interfaces.cqrs-module-options_interface | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 33 interfaces.queries.query-bus_interface | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 command-bus | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 35 query-bus | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 36 unhandled-exception-bus | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 event-bus | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 38 cqrs_module | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 event-publisher | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 storages.aggregate-root_storage | 1 | 1 |
18→8 classes.command uses interfaces.commands.command_interface✕
- Connections
- 1 pair of types, where a type in classes.command uses a type in interfaces.commands.command_interface.
- The types involved
src.classes.command.Command→src.interfaces.commands.command_interface.ICommand
- Direction
- classes.command uses interfaces.commands.command_interface, so a change to interfaces.commands.command_interface can break classes.command, while a change to classes.command can't break interfaces.commands.command_interface.
- Position
- Below the diagonal: classes.command uses a module listed above it, which is the healthy direction.
19→15 classes.query uses interfaces.queries.query_interface✕
- Connections
- 1 pair of types, where a type in classes.query uses a type in interfaces.queries.query_interface.
- The types involved
src.classes.query.Query→src.interfaces.queries.query_interface.IQuery
- Direction
- classes.query uses interfaces.queries.query_interface, so a change to interfaces.queries.query_interface can break classes.query, while a change to classes.query can't break interfaces.queries.query_interface.
- Position
- Below the diagonal: classes.query uses a module listed above it, which is the healthy direction.
20→15 decorators uses interfaces.queries.query_interface✕
- Connections
- 1 pair of types, where a type in decorators uses a type in interfaces.queries.query_interface.
- The types involved
src.decorators.query-handler.decorator→src.interfaces.queries.query_interface.IQuery
- Direction
- decorators uses interfaces.queries.query_interface, so a change to interfaces.queries.query_interface can break decorators, while a change to decorators can't break interfaces.queries.query_interface.
- Position
- Below the diagonal: decorators uses a module listed above it, which is the healthy direction.
21→7 helpers.default-command-pubsub uses interfaces.commands.command-publisher_interface✕
- Connections
- 1 pair of types, where a type in helpers.default-command-pubsub uses a type in interfaces.commands.command-publisher_interface.
- The types involved
src.helpers.default-command-pubsub.DefaultCommandPubSub→src.interfaces.commands.command-publisher_interface.ICommandPublisher
- Direction
- helpers.default-command-pubsub uses interfaces.commands.command-publisher_interface, so a change to interfaces.commands.command-publisher_interface can break helpers.default-command-pubsub, while a change to helpers.default-command-pubsub can't break interfaces.commands.command-publisher_interface.
- Position
- Below the diagonal: helpers.default-command-pubsub uses a module listed above it, which is the healthy direction.
22→10 helpers.default-event-id-provider uses interfaces.events.event-id-provider_interface✕
- Connections
- 1 pair of types, where a type in helpers.default-event-id-provider uses a type in interfaces.events.event-id-provider_interface.
- The types involved
src.helpers.default-event-id-provider.DefaultEventIdProvider→src.interfaces.events.event-id-provider_interface.EventIdProvider
- Direction
- helpers.default-event-id-provider uses interfaces.events.event-id-provider_interface, so a change to interfaces.events.event-id-provider_interface can break helpers.default-event-id-provider, while a change to helpers.default-event-id-provider can't break interfaces.events.event-id-provider_interface.
- Position
- Below the diagonal: helpers.default-event-id-provider uses a module listed above it, which is the healthy direction.
23→14 helpers.default-query-pubsub uses interfaces.queries.query-publisher_interface✕
- Connections
- 1 pair of types, where a type in helpers.default-query-pubsub uses a type in interfaces.queries.query-publisher_interface.
- The types involved
src.helpers.default-query-pubsub.DefaultQueryPubSub→src.interfaces.queries.query-publisher_interface.IQueryPublisher
- Direction
- helpers.default-query-pubsub uses interfaces.queries.query-publisher_interface, so a change to interfaces.queries.query-publisher_interface can break helpers.default-query-pubsub, while a change to helpers.default-query-pubsub can't break interfaces.queries.query-publisher_interface.
- Position
- Below the diagonal: helpers.default-query-pubsub uses a module listed above it, which is the healthy direction.
24→16 interfaces.events.event-bus_interface uses scopes.async_context✕
- Connections
- 1 pair of types, where a type in interfaces.events.event-bus_interface uses a type in scopes.async_context.
- The types involved
src.interfaces.events.event-bus_interface.IEventBus→src.scopes.async_context.AsyncContext
- Direction
- interfaces.events.event-bus_interface uses scopes.async_context, so a change to scopes.async_context can break interfaces.events.event-bus_interface, while a change to interfaces.events.event-bus_interface can't break scopes.async_context.
- Position
- Below the diagonal: interfaces.events.event-bus_interface uses a module listed above it, which is the healthy direction.
25→16 interfaces.events.event-publisher_interface uses scopes.async_context✕
- Connections
- 1 pair of types, where a type in interfaces.events.event-publisher_interface uses a type in scopes.async_context.
- The types involved
src.interfaces.events.event-publisher_interface.IEventPublisher→src.scopes.async_context.AsyncContext
- Direction
- interfaces.events.event-publisher_interface uses scopes.async_context, so a change to scopes.async_context can break interfaces.events.event-publisher_interface, while a change to interfaces.events.event-publisher_interface can't break scopes.async_context.
- Position
- Below the diagonal: interfaces.events.event-publisher_interface uses a module listed above it, which is the healthy direction.
26→12 interfaces.exceptions.unhandled-exception-publisher_interface uses interfaces.exceptions.unhandled-exception-info_interface✕
- Connections
- 1 pair of types, where a type in interfaces.exceptions.unhandled-exception-publisher_interface uses a type in interfaces.exceptions.unhandled-exception-info_interface.
- The types involved
src.interfaces.exceptions.unhandled-exception-publisher_interface.IUnhandledExceptionPublisher→src.interfaces.exceptions.unhandled-exception-info_interface.UnhandledExceptionInfo
- Direction
- interfaces.exceptions.unhandled-exception-publisher_interface uses interfaces.exceptions.unhandled-exception-info_interface, so a change to interfaces.exceptions.unhandled-exception-info_interface can break interfaces.exceptions.unhandled-exception-publisher_interface, while a change to interfaces.exceptions.unhandled-exception-publisher_interface can't break interfaces.exceptions.unhandled-exception-info_interface.
- Position
- Below the diagonal: interfaces.exceptions.unhandled-exception-publisher_interface uses a module listed above it, which is the healthy direction.
27→6 mixins.with-aggregate-root_mixin uses interfaces.aggregate-root_interface✕
- Connections
- 1 pair of types, where a type in mixins.with-aggregate-root_mixin uses a type in interfaces.aggregate-root_interface.
- The types involved
src.mixins.with-aggregate-root_mixin.AggregateRoot→src.interfaces.aggregate-root_interface.IAggregateRoot
- Direction
- mixins.with-aggregate-root_mixin uses interfaces.aggregate-root_interface, so a change to interfaces.aggregate-root_interface can break mixins.with-aggregate-root_mixin, while a change to mixins.with-aggregate-root_mixin can't break interfaces.aggregate-root_interface.
- Position
- Below the diagonal: mixins.with-aggregate-root_mixin uses a module listed above it, which is the healthy direction.
28→13 services.explorer_service uses interfaces.providers-introspection-result_interface✕
- Connections
- 1 pair of types, where a type in services.explorer_service uses a type in interfaces.providers-introspection-result_interface.
- The types involved
src.services.explorer_service.ExplorerService→src.interfaces.providers-introspection-result_interface.ProvidersIntrospectionResult
- Direction
- services.explorer_service uses interfaces.providers-introspection-result_interface, so a change to interfaces.providers-introspection-result_interface can break services.explorer_service, while a change to services.explorer_service can't break interfaces.providers-introspection-result_interface.
- Position
- Below the diagonal: services.explorer_service uses a module listed above it, which is the healthy direction.
29→11 helpers.default-pubsub uses interfaces.events.message-source_interface✕
- Connections
- 1 pair of types, where a type in helpers.default-pubsub uses a type in interfaces.events.message-source_interface.
- The types involved
src.helpers.default-pubsub.DefaultPubSub→src.interfaces.events.message-source_interface.IMessageSource
- Direction
- helpers.default-pubsub uses interfaces.events.message-source_interface, so a change to interfaces.events.message-source_interface can break helpers.default-pubsub, while a change to helpers.default-pubsub can't break interfaces.events.message-source_interface.
- Position
- Below the diagonal: helpers.default-pubsub uses a module listed above it, which is the healthy direction.
29→25 helpers.default-pubsub uses interfaces.events.event-publisher_interface✕
- Connections
- 1 pair of types, where a type in helpers.default-pubsub uses a type in interfaces.events.event-publisher_interface.
- The types involved
src.helpers.default-pubsub.DefaultPubSub→src.interfaces.events.event-publisher_interface.IEventPublisher
- Direction
- helpers.default-pubsub uses interfaces.events.event-publisher_interface, so a change to interfaces.events.event-publisher_interface can break helpers.default-pubsub, while a change to helpers.default-pubsub can't break interfaces.events.event-publisher_interface.
- Position
- Below the diagonal: helpers.default-pubsub uses a module listed above it, which is the healthy direction.
30→12 helpers.default-unhandled-exception-pubsub uses interfaces.exceptions.unhandled-exception-info_interface✕
- Connections
- 1 pair of types, where a type in helpers.default-unhandled-exception-pubsub uses a type in interfaces.exceptions.unhandled-exception-info_interface.
- The types involved
src.helpers.default-unhandled-exception-pubsub.DefaultUnhandledExceptionPubSub→src.interfaces.exceptions.unhandled-exception-info_interface.UnhandledExceptionInfo
- Direction
- helpers.default-unhandled-exception-pubsub uses interfaces.exceptions.unhandled-exception-info_interface, so a change to interfaces.exceptions.unhandled-exception-info_interface can break helpers.default-unhandled-exception-pubsub, while a change to helpers.default-unhandled-exception-pubsub can't break interfaces.exceptions.unhandled-exception-info_interface.
- Position
- Below the diagonal: helpers.default-unhandled-exception-pubsub uses a module listed above it, which is the healthy direction.
30→26 helpers.default-unhandled-exception-pubsub uses interfaces.exceptions.unhandled-exception-publisher_interface✕
- Connections
- 1 pair of types, where a type in helpers.default-unhandled-exception-pubsub uses a type in interfaces.exceptions.unhandled-exception-publisher_interface.
- The types involved
src.helpers.default-unhandled-exception-pubsub.DefaultUnhandledExceptionPubSub→src.interfaces.exceptions.unhandled-exception-publisher_interface.IUnhandledExceptionPublisher
- Direction
- helpers.default-unhandled-exception-pubsub uses interfaces.exceptions.unhandled-exception-publisher_interface, so a change to interfaces.exceptions.unhandled-exception-publisher_interface can break helpers.default-unhandled-exception-pubsub, while a change to helpers.default-unhandled-exception-pubsub can't break interfaces.exceptions.unhandled-exception-publisher_interface.
- Position
- Below the diagonal: helpers.default-unhandled-exception-pubsub uses a module listed above it, which is the healthy direction.
31→16 interfaces.commands.command-bus_interface uses scopes.async_context✕
- Connections
- 1 pair of types, where a type in interfaces.commands.command-bus_interface uses a type in scopes.async_context.
- The types involved
src.interfaces.commands.command-bus_interface.ICommandBus→src.scopes.async_context.AsyncContext
- Direction
- interfaces.commands.command-bus_interface uses scopes.async_context, so a change to scopes.async_context can break interfaces.commands.command-bus_interface, while a change to interfaces.commands.command-bus_interface can't break scopes.async_context.
- Position
- Below the diagonal: interfaces.commands.command-bus_interface uses a module listed above it, which is the healthy direction.
31→18 interfaces.commands.command-bus_interface uses classes.command✕
- Connections
- 1 pair of types, where a type in interfaces.commands.command-bus_interface uses a type in classes.command.
- The types involved
src.interfaces.commands.command-bus_interface.ICommandBus→src.classes.command.Command
- Direction
- interfaces.commands.command-bus_interface uses classes.command, so a change to classes.command can break interfaces.commands.command-bus_interface, while a change to interfaces.commands.command-bus_interface can't break classes.command.
- Position
- Below the diagonal: interfaces.commands.command-bus_interface uses a module listed above it, which is the healthy direction.
32→7 interfaces.cqrs-module-options_interface uses interfaces.commands.command-publisher_interface✕
- Connections
- 1 pair of types, where a type in interfaces.cqrs-module-options_interface uses a type in interfaces.commands.command-publisher_interface.
- The types involved
src.interfaces.cqrs-module-options_interface.CqrsModuleOptions→src.interfaces.commands.command-publisher_interface.ICommandPublisher
- Direction
- interfaces.cqrs-module-options_interface uses interfaces.commands.command-publisher_interface, so a change to interfaces.commands.command-publisher_interface can break interfaces.cqrs-module-options_interface, while a change to interfaces.cqrs-module-options_interface can't break interfaces.commands.command-publisher_interface.
- Position
- Below the diagonal: interfaces.cqrs-module-options_interface uses a module listed above it, which is the healthy direction.
32→10 interfaces.cqrs-module-options_interface uses interfaces.events.event-id-provider_interface✕
- Connections
- 1 pair of types, where a type in interfaces.cqrs-module-options_interface uses a type in interfaces.events.event-id-provider_interface.
- The types involved
src.interfaces.cqrs-module-options_interface.CqrsModuleOptions→src.interfaces.events.event-id-provider_interface.EventIdProvider
- Direction
- interfaces.cqrs-module-options_interface uses interfaces.events.event-id-provider_interface, so a change to interfaces.events.event-id-provider_interface can break interfaces.cqrs-module-options_interface, while a change to interfaces.cqrs-module-options_interface can't break interfaces.events.event-id-provider_interface.
- Position
- Below the diagonal: interfaces.cqrs-module-options_interface uses a module listed above it, which is the healthy direction.
32→14 interfaces.cqrs-module-options_interface uses interfaces.queries.query-publisher_interface✕
- Connections
- 1 pair of types, where a type in interfaces.cqrs-module-options_interface uses a type in interfaces.queries.query-publisher_interface.
- The types involved
src.interfaces.cqrs-module-options_interface.CqrsModuleOptions→src.interfaces.queries.query-publisher_interface.IQueryPublisher
- Direction
- interfaces.cqrs-module-options_interface uses interfaces.queries.query-publisher_interface, so a change to interfaces.queries.query-publisher_interface can break interfaces.cqrs-module-options_interface, while a change to interfaces.cqrs-module-options_interface can't break interfaces.queries.query-publisher_interface.
- Position
- Below the diagonal: interfaces.cqrs-module-options_interface uses a module listed above it, which is the healthy direction.
32→25 interfaces.cqrs-module-options_interface uses interfaces.events.event-publisher_interface✕
- Connections
- 1 pair of types, where a type in interfaces.cqrs-module-options_interface uses a type in interfaces.events.event-publisher_interface.
- The types involved
src.interfaces.cqrs-module-options_interface.CqrsModuleOptions→src.interfaces.events.event-publisher_interface.IEventPublisher
- Direction
- interfaces.cqrs-module-options_interface uses interfaces.events.event-publisher_interface, so a change to interfaces.events.event-publisher_interface can break interfaces.cqrs-module-options_interface, while a change to interfaces.cqrs-module-options_interface can't break interfaces.events.event-publisher_interface.
- Position
- Below the diagonal: interfaces.cqrs-module-options_interface uses a module listed above it, which is the healthy direction.
32→26 interfaces.cqrs-module-options_interface uses interfaces.exceptions.unhandled-exception-publisher_interface✕
- Connections
- 1 pair of types, where a type in interfaces.cqrs-module-options_interface uses a type in interfaces.exceptions.unhandled-exception-publisher_interface.
- The types involved
src.interfaces.cqrs-module-options_interface.CqrsModuleOptions→src.interfaces.exceptions.unhandled-exception-publisher_interface.IUnhandledExceptionPublisher
- Direction
- interfaces.cqrs-module-options_interface uses interfaces.exceptions.unhandled-exception-publisher_interface, so a change to interfaces.exceptions.unhandled-exception-publisher_interface can break interfaces.cqrs-module-options_interface, while a change to interfaces.cqrs-module-options_interface can't break interfaces.exceptions.unhandled-exception-publisher_interface.
- Position
- Below the diagonal: interfaces.cqrs-module-options_interface uses a module listed above it, which is the healthy direction.
33→16 interfaces.queries.query-bus_interface uses scopes.async_context✕
- Connections
- 1 pair of types, where a type in interfaces.queries.query-bus_interface uses a type in scopes.async_context.
- The types involved
src.interfaces.queries.query-bus_interface.IQueryBus→src.scopes.async_context.AsyncContext
- Direction
- interfaces.queries.query-bus_interface uses scopes.async_context, so a change to scopes.async_context can break interfaces.queries.query-bus_interface, while a change to interfaces.queries.query-bus_interface can't break scopes.async_context.
- Position
- Below the diagonal: interfaces.queries.query-bus_interface uses a module listed above it, which is the healthy direction.
33→19 interfaces.queries.query-bus_interface uses classes.query✕
- Connections
- 1 pair of types, where a type in interfaces.queries.query-bus_interface uses a type in classes.query.
- The types involved
src.interfaces.queries.query-bus_interface.IQueryBus→src.classes.query.Query
- Direction
- interfaces.queries.query-bus_interface uses classes.query, so a change to classes.query can break interfaces.queries.query-bus_interface, while a change to interfaces.queries.query-bus_interface can't break classes.query.
- Position
- Below the diagonal: interfaces.queries.query-bus_interface uses a module listed above it, which is the healthy direction.
34→7 command-bus uses interfaces.commands.command-publisher_interface✕
- Connections
- 1 pair of types, where a type in command-bus uses a type in interfaces.commands.command-publisher_interface.
- The types involved
src.command-bus.CommandBus→src.interfaces.commands.command-publisher_interface.ICommandPublisher
- Direction
- command-bus uses interfaces.commands.command-publisher_interface, so a change to interfaces.commands.command-publisher_interface can break command-bus, while a change to command-bus can't break interfaces.commands.command-publisher_interface.
- Position
- Below the diagonal: command-bus uses a module listed above it, which is the healthy direction.
34→16 command-bus uses scopes.async_context✕
- Connections
- 1 pair of types, where a type in command-bus uses a type in scopes.async_context.
- The types involved
src.command-bus.CommandBus→src.scopes.async_context.AsyncContext
- Direction
- command-bus uses scopes.async_context, so a change to scopes.async_context can break command-bus, while a change to command-bus can't break scopes.async_context.
- Position
- Below the diagonal: command-bus uses a module listed above it, which is the healthy direction.
34→17 command-bus uses utils.observable-bus✕
- Connections
- 1 pair of types, where a type in command-bus uses a type in utils.observable-bus.
- The types involved
src.command-bus.CommandBus→src.utils.observable-bus.ObservableBus
- Direction
- command-bus uses utils.observable-bus, so a change to utils.observable-bus can break command-bus, while a change to command-bus can't break utils.observable-bus.
- Position
- Below the diagonal: command-bus uses a module listed above it, which is the healthy direction.
34→18 command-bus uses classes.command✕
- Connections
- 1 pair of types, where a type in command-bus uses a type in classes.command.
- The types involved
src.command-bus.CommandBus→src.classes.command.Command
- Direction
- command-bus uses classes.command, so a change to classes.command can break command-bus, while a change to command-bus can't break classes.command.
- Position
- Below the diagonal: command-bus uses a module listed above it, which is the healthy direction.
34→31 command-bus uses interfaces.commands.command-bus_interface✕
- Connections
- 1 pair of types, where a type in command-bus uses a type in interfaces.commands.command-bus_interface.
- The types involved
src.command-bus.CommandBus→src.interfaces.commands.command-bus_interface.ICommandBus
- Direction
- command-bus uses interfaces.commands.command-bus_interface, so a change to interfaces.commands.command-bus_interface can break command-bus, while a change to command-bus can't break interfaces.commands.command-bus_interface.
- Position
- Below the diagonal: command-bus uses a module listed above it, which is the healthy direction.
34→32 command-bus uses interfaces.cqrs-module-options_interface✕
- Connections
- 1 pair of types, where a type in command-bus uses a type in interfaces.cqrs-module-options_interface.
- The types involved
src.command-bus.CommandBus→src.interfaces.cqrs-module-options_interface.CqrsModuleOptions
- Direction
- command-bus uses interfaces.cqrs-module-options_interface, so a change to interfaces.cqrs-module-options_interface can break command-bus, while a change to command-bus can't break interfaces.cqrs-module-options_interface.
- Position
- Below the diagonal: command-bus uses a module listed above it, which is the healthy direction.
35→14 query-bus uses interfaces.queries.query-publisher_interface✕
- Connections
- 1 pair of types, where a type in query-bus uses a type in interfaces.queries.query-publisher_interface.
- The types involved
src.query-bus.QueryBus→src.interfaces.queries.query-publisher_interface.IQueryPublisher
- Direction
- query-bus uses interfaces.queries.query-publisher_interface, so a change to interfaces.queries.query-publisher_interface can break query-bus, while a change to query-bus can't break interfaces.queries.query-publisher_interface.
- Position
- Below the diagonal: query-bus uses a module listed above it, which is the healthy direction.
35→16 query-bus uses scopes.async_context✕
- Connections
- 1 pair of types, where a type in query-bus uses a type in scopes.async_context.
- The types involved
src.query-bus.QueryBus→src.scopes.async_context.AsyncContext
- Direction
- query-bus uses scopes.async_context, so a change to scopes.async_context can break query-bus, while a change to query-bus can't break scopes.async_context.
- Position
- Below the diagonal: query-bus uses a module listed above it, which is the healthy direction.
35→17 query-bus uses utils.observable-bus✕
- Connections
- 1 pair of types, where a type in query-bus uses a type in utils.observable-bus.
- The types involved
src.query-bus.QueryBus→src.utils.observable-bus.ObservableBus
- Direction
- query-bus uses utils.observable-bus, so a change to utils.observable-bus can break query-bus, while a change to query-bus can't break utils.observable-bus.
- Position
- Below the diagonal: query-bus uses a module listed above it, which is the healthy direction.
35→19 query-bus uses classes.query✕
- Connections
- 1 pair of types, where a type in query-bus uses a type in classes.query.
- The types involved
src.query-bus.QueryBus→src.classes.query.Query
- Direction
- query-bus uses classes.query, so a change to classes.query can break query-bus, while a change to query-bus can't break classes.query.
- Position
- Below the diagonal: query-bus uses a module listed above it, which is the healthy direction.
35→32 query-bus uses interfaces.cqrs-module-options_interface✕
- Connections
- 1 pair of types, where a type in query-bus uses a type in interfaces.cqrs-module-options_interface.
- The types involved
src.query-bus.QueryBus→src.interfaces.cqrs-module-options_interface.CqrsModuleOptions
- Direction
- query-bus uses interfaces.cqrs-module-options_interface, so a change to interfaces.cqrs-module-options_interface can break query-bus, while a change to query-bus can't break interfaces.cqrs-module-options_interface.
- Position
- Below the diagonal: query-bus uses a module listed above it, which is the healthy direction.
35→33 query-bus uses interfaces.queries.query-bus_interface✕
- Connections
- 1 pair of types, where a type in query-bus uses a type in interfaces.queries.query-bus_interface.
- The types involved
src.query-bus.QueryBus→src.interfaces.queries.query-bus_interface.IQueryBus
- Direction
- query-bus uses interfaces.queries.query-bus_interface, so a change to interfaces.queries.query-bus_interface can break query-bus, while a change to query-bus can't break interfaces.queries.query-bus_interface.
- Position
- Below the diagonal: query-bus uses a module listed above it, which is the healthy direction.
36→12 unhandled-exception-bus uses interfaces.exceptions.unhandled-exception-info_interface✕
- Connections
- 1 pair of types, where a type in unhandled-exception-bus uses a type in interfaces.exceptions.unhandled-exception-info_interface.
- The types involved
src.unhandled-exception-bus.UnhandledExceptionBus→src.interfaces.exceptions.unhandled-exception-info_interface.UnhandledExceptionInfo
- Direction
- unhandled-exception-bus uses interfaces.exceptions.unhandled-exception-info_interface, so a change to interfaces.exceptions.unhandled-exception-info_interface can break unhandled-exception-bus, while a change to unhandled-exception-bus can't break interfaces.exceptions.unhandled-exception-info_interface.
- Position
- Below the diagonal: unhandled-exception-bus uses a module listed above it, which is the healthy direction.
36→17 unhandled-exception-bus uses utils.observable-bus✕
- Connections
- 1 pair of types, where a type in unhandled-exception-bus uses a type in utils.observable-bus.
- The types involved
src.unhandled-exception-bus.UnhandledExceptionBus→src.utils.observable-bus.ObservableBus
- Direction
- unhandled-exception-bus uses utils.observable-bus, so a change to utils.observable-bus can break unhandled-exception-bus, while a change to unhandled-exception-bus can't break utils.observable-bus.
- Position
- Below the diagonal: unhandled-exception-bus uses a module listed above it, which is the healthy direction.
36→26 unhandled-exception-bus uses interfaces.exceptions.unhandled-exception-publisher_interface✕
- Connections
- 1 pair of types, where a type in unhandled-exception-bus uses a type in interfaces.exceptions.unhandled-exception-publisher_interface.
- The types involved
src.unhandled-exception-bus.UnhandledExceptionBus→src.interfaces.exceptions.unhandled-exception-publisher_interface.IUnhandledExceptionPublisher
- Direction
- unhandled-exception-bus uses interfaces.exceptions.unhandled-exception-publisher_interface, so a change to interfaces.exceptions.unhandled-exception-publisher_interface can break unhandled-exception-bus, while a change to unhandled-exception-bus can't break interfaces.exceptions.unhandled-exception-publisher_interface.
- Position
- Below the diagonal: unhandled-exception-bus uses a module listed above it, which is the healthy direction.
36→32 unhandled-exception-bus uses interfaces.cqrs-module-options_interface✕
- Connections
- 1 pair of types, where a type in unhandled-exception-bus uses a type in interfaces.cqrs-module-options_interface.
- The types involved
src.unhandled-exception-bus.UnhandledExceptionBus→src.interfaces.cqrs-module-options_interface.CqrsModuleOptions
- Direction
- unhandled-exception-bus uses interfaces.cqrs-module-options_interface, so a change to interfaces.cqrs-module-options_interface can break unhandled-exception-bus, while a change to unhandled-exception-bus can't break interfaces.cqrs-module-options_interface.
- Position
- Below the diagonal: unhandled-exception-bus uses a module listed above it, which is the healthy direction.
37→9 event-bus uses interfaces.events.event-handler_interface✕
- Connections
- 1 pair of types, where a type in event-bus uses a type in interfaces.events.event-handler_interface.
- The types involved
src.event-bus.EventBus→src.interfaces.events.event-handler_interface.IEventHandler
- Direction
- event-bus uses interfaces.events.event-handler_interface, so a change to interfaces.events.event-handler_interface can break event-bus, while a change to event-bus can't break interfaces.events.event-handler_interface.
- Position
- Below the diagonal: event-bus uses a module listed above it, which is the healthy direction.
37→10 event-bus uses interfaces.events.event-id-provider_interface✕
- Connections
- 1 pair of types, where a type in event-bus uses a type in interfaces.events.event-id-provider_interface.
- The types involved
src.event-bus.EventBus→src.interfaces.events.event-id-provider_interface.EventIdProvider
- Direction
- event-bus uses interfaces.events.event-id-provider_interface, so a change to interfaces.events.event-id-provider_interface can break event-bus, while a change to event-bus can't break interfaces.events.event-id-provider_interface.
- Position
- Below the diagonal: event-bus uses a module listed above it, which is the healthy direction.
37→12 event-bus uses interfaces.exceptions.unhandled-exception-info_interface✕
- Connections
- 1 pair of types, where a type in event-bus uses a type in interfaces.exceptions.unhandled-exception-info_interface.
- The types involved
src.event-bus.EventBus→src.interfaces.exceptions.unhandled-exception-info_interface.UnhandledExceptionInfo
- Direction
- event-bus uses interfaces.exceptions.unhandled-exception-info_interface, so a change to interfaces.exceptions.unhandled-exception-info_interface can break event-bus, while a change to event-bus can't break interfaces.exceptions.unhandled-exception-info_interface.
- Position
- Below the diagonal: event-bus uses a module listed above it, which is the healthy direction.
37→16 event-bus uses scopes.async_context✕
- Connections
- 1 pair of types, where a type in event-bus uses a type in scopes.async_context.
- The types involved
src.event-bus.EventBus→src.scopes.async_context.AsyncContext
- Direction
- event-bus uses scopes.async_context, so a change to scopes.async_context can break event-bus, while a change to event-bus can't break scopes.async_context.
- Position
- Below the diagonal: event-bus uses a module listed above it, which is the healthy direction.
37→17 event-bus uses utils.observable-bus✕
- Connections
- 1 pair of types, where a type in event-bus uses a type in utils.observable-bus.
- The types involved
src.event-bus.EventBus→src.utils.observable-bus.ObservableBus
- Direction
- event-bus uses utils.observable-bus, so a change to utils.observable-bus can break event-bus, while a change to event-bus can't break utils.observable-bus.
- Position
- Below the diagonal: event-bus uses a module listed above it, which is the healthy direction.
37→24 event-bus uses interfaces.events.event-bus_interface✕
- Connections
- 1 pair of types, where a type in event-bus uses a type in interfaces.events.event-bus_interface.
- The types involved
src.event-bus.EventBus→src.interfaces.events.event-bus_interface.IEventBus
- Direction
- event-bus uses interfaces.events.event-bus_interface, so a change to interfaces.events.event-bus_interface can break event-bus, while a change to event-bus can't break interfaces.events.event-bus_interface.
- Position
- Below the diagonal: event-bus uses a module listed above it, which is the healthy direction.
37→25 event-bus uses interfaces.events.event-publisher_interface✕
- Connections
- 1 pair of types, where a type in event-bus uses a type in interfaces.events.event-publisher_interface.
- The types involved
src.event-bus.EventBus→src.interfaces.events.event-publisher_interface.IEventPublisher
- Direction
- event-bus uses interfaces.events.event-publisher_interface, so a change to interfaces.events.event-publisher_interface can break event-bus, while a change to event-bus can't break interfaces.events.event-publisher_interface.
- Position
- Below the diagonal: event-bus uses a module listed above it, which is the healthy direction.
37→32 event-bus uses interfaces.cqrs-module-options_interface✕
- Connections
- 1 pair of types, where a type in event-bus uses a type in interfaces.cqrs-module-options_interface.
- The types involved
src.event-bus.EventBus→src.interfaces.cqrs-module-options_interface.CqrsModuleOptions
- Direction
- event-bus uses interfaces.cqrs-module-options_interface, so a change to interfaces.cqrs-module-options_interface can break event-bus, while a change to event-bus can't break interfaces.cqrs-module-options_interface.
- Position
- Below the diagonal: event-bus uses a module listed above it, which is the healthy direction.
37→34 event-bus uses command-bus✕
- Connections
- 1 pair of types, where a type in event-bus uses a type in command-bus.
- The types involved
src.event-bus.EventBus→src.command-bus.CommandBus
- Direction
- event-bus uses command-bus, so a change to command-bus can break event-bus, while a change to event-bus can't break command-bus.
- Position
- Below the diagonal: event-bus uses a module listed above it, which is the healthy direction.
37→36 event-bus uses unhandled-exception-bus✕
- Connections
- 1 pair of types, where a type in event-bus uses a type in unhandled-exception-bus.
- The types involved
src.event-bus.EventBus→src.unhandled-exception-bus.UnhandledExceptionBus
- Direction
- event-bus uses unhandled-exception-bus, so a change to unhandled-exception-bus can break event-bus, while a change to event-bus can't break unhandled-exception-bus.
- Position
- Below the diagonal: event-bus uses a module listed above it, which is the healthy direction.
38→28 cqrs_module uses services.explorer_service✕
- Connections
- 1 pair of types, where a type in cqrs_module uses a type in services.explorer_service.
- The types involved
src.cqrs_module.CqrsModule→src.services.explorer_service.ExplorerService
- Direction
- cqrs_module uses services.explorer_service, so a change to services.explorer_service can break cqrs_module, while a change to cqrs_module can't break services.explorer_service.
- Position
- Below the diagonal: cqrs_module uses a module listed above it, which is the healthy direction.
38→32 cqrs_module uses interfaces.cqrs-module-options_interface✕
- Connections
- 2 pairs of types, where a type in cqrs_module uses a type in interfaces.cqrs-module-options_interface.
- The types involved
src.cqrs_module.CqrsModule→src.interfaces.cqrs-module-options_interface.CqrsModuleAsyncOptionssrc.cqrs_module.CqrsModule→src.interfaces.cqrs-module-options_interface.CqrsModuleOptions
- Direction
- cqrs_module uses interfaces.cqrs-module-options_interface, so a change to interfaces.cqrs-module-options_interface can break cqrs_module, while a change to cqrs_module can't break interfaces.cqrs-module-options_interface.
- Position
- Below the diagonal: cqrs_module uses a module listed above it, which is the healthy direction.
38→34 cqrs_module uses command-bus✕
- Connections
- 1 pair of types, where a type in cqrs_module uses a type in command-bus.
- The types involved
src.cqrs_module.CqrsModule→src.command-bus.CommandBus
- Direction
- cqrs_module uses command-bus, so a change to command-bus can break cqrs_module, while a change to cqrs_module can't break command-bus.
- Position
- Below the diagonal: cqrs_module uses a module listed above it, which is the healthy direction.
38→35 cqrs_module uses query-bus✕
- Connections
- 1 pair of types, where a type in cqrs_module uses a type in query-bus.
- The types involved
src.cqrs_module.CqrsModule→src.query-bus.QueryBus
- Direction
- cqrs_module uses query-bus, so a change to query-bus can break cqrs_module, while a change to cqrs_module can't break query-bus.
- Position
- Below the diagonal: cqrs_module uses a module listed above it, which is the healthy direction.
38→37 cqrs_module uses event-bus✕
- Connections
- 1 pair of types, where a type in cqrs_module uses a type in event-bus.
- The types involved
src.cqrs_module.CqrsModule→src.event-bus.EventBus
- Direction
- cqrs_module uses event-bus, so a change to event-bus can break cqrs_module, while a change to cqrs_module can't break event-bus.
- Position
- Below the diagonal: cqrs_module uses a module listed above it, which is the healthy direction.
39→16 event-publisher uses scopes.async_context✕
- Connections
- 1 pair of types, where a type in event-publisher uses a type in scopes.async_context.
- The types involved
src.event-publisher.EventPublisher→src.scopes.async_context.AsyncContext
- Direction
- event-publisher uses scopes.async_context, so a change to scopes.async_context can break event-publisher, while a change to event-publisher can't break scopes.async_context.
- Position
- Below the diagonal: event-publisher uses a module listed above it, which is the healthy direction.
39→37 event-publisher uses event-bus✕
- Connections
- 1 pair of types, where a type in event-publisher uses a type in event-bus.
- The types involved
src.event-publisher.EventPublisher→src.event-bus.EventBus
- Direction
- event-publisher uses event-bus, so a change to event-bus can break event-publisher, while a change to event-publisher can't break event-bus.
- Position
- Below the diagonal: event-publisher uses a module listed above it, which is the healthy direction.
40→6 storages.aggregate-root_storage uses interfaces.aggregate-root_interface✕
- Connections
- 1 pair of types, where a type in storages.aggregate-root_storage uses a type in interfaces.aggregate-root_interface.
- The types involved
src.storages.aggregate-root_storage.AggregateRootStorage→src.interfaces.aggregate-root_interface.IAggregateRoot
- Direction
- storages.aggregate-root_storage uses interfaces.aggregate-root_interface, so a change to interfaces.aggregate-root_interface can break storages.aggregate-root_storage, while a change to storages.aggregate-root_storage can't break interfaces.aggregate-root_interface.
- Position
- Below the diagonal: storages.aggregate-root_storage uses a module listed above it, which is the healthy direction.
40→37 storages.aggregate-root_storage uses event-bus✕
- Connections
- 1 pair of types, where a type in storages.aggregate-root_storage uses a type in event-bus.
- The types involved
src.storages.aggregate-root_storage.AggregateRootStorage→src.event-bus.EventBus
- Direction
- storages.aggregate-root_storage uses event-bus, so a change to event-bus can break storages.aggregate-root_storage, while a change to storages.aggregate-root_storage can't break event-bus.
- Position
- Below the diagonal: storages.aggregate-root_storage uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Event-Driven
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A07:2025 — Authentication Failures | 12 | High / Critical |
| A05:2025 — Injection | 3 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 3 | High / Critical |
Roadmap
Top priorities: Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure; Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters); Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Inverted test pyramid finding(s) in Test Distribution. | +1.9 pts | Low | Test Distribution |
| Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. | +1.8 pts | Low | Secret Scanning |
| Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure. | +3.3 pts | Medium | Constructible invalid state |
| Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters). | +2.9 pts | Medium | Encapsulated state |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). | +1.4 pts | Low | Static Analysis (SAST) |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +2.6 pts | Medium | Architecture documentation |
| Resolve the 10 High secret finding(s) in Secrets (history) — start with REDACTED (10). | +2.2 pts | Medium | Secrets (history) |
| Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. | +0.8 pts | Low | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| test/e2e/unhandled-exceptions.spec.ts | 7.8 | Mixed | Test Quality: No assertions: should keep reacting to events after the saga has thrown |
| src/operators/of-type.spec.ts | 7.8 | Mixed | Test Quality: No assertions: should infer return types of similar unions unions |
| test/e2e/sync-event-handlers-app.spec.ts | 9.0 | Near-clean | Test Quality: Mock-dominated test: should wait for the event handlers to complete |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 72 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 72 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 38 of 49 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D12 Dependency Hygiene — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's 1 package.json manifest(s) and its 1 committed lockfile(s) WERE read; what went unanswered is the currency half, because it grades the production `dependencies` a lockfile resolves and these manifests declare none — only 16 devDependencies, which D12 does not grade. So registry.npmjs.org was never asked, and there was nothing here for it to grade. This is a true statement about the repository and NOT a gap on our side: the lockfile was resolved, and no reader we could write would find a production dependency in it.
- D19 Documentation Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a web-server dependency ('@nestjs/core') — a service to boot even with no user interface. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and none applies: this repository publishes a library and deploys nothing (no container, IaC or deployment manifest), so it holds no runtime state of its own. Any data-access dependency it declares is the store it is a CLIENT for, not one it operates. The DR control belongs to whoever runs that data.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 67 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D6 · Cohesion (LCOM4)
0 of 8 classes have LCOM4 above 3.
D9 · Test Distribution
73 test methods: 35 unit, 0 integration, 0 BDD, 38 e2e. The JavaScript/TypeScript suite contributes 73 `it`/`test` case(s) across 10 test file(s) declaring at least one; its tier split is read from package names and paths only.
What to do
- Resolve the 1 Inverted test pyramid finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
D10 · Test Quality
0 skipped, 3 zero-assertion, 1 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 73 tests.
What to do
- Resolve the 5 Mock-dominated test finding(s) in Test Quality — start with sync-event-handlers-app.spec.ts (5). — One of this dimension's main actionable groups (5 recommendation-level).
- Resolve the 3 No assertions finding(s) in Test Quality — start with of-type.spec.ts (2), unhandled-exceptions.spec.ts. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Fixed-sleep synchronisation finding(s) in Test Quality — start with unhandled-exceptions.spec.ts. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `npm ci --ignore-scripts` in the repository root (61 tests)): measured (0 flaky).
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 4 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 4 package(s) this repository's committed lockfile installs for a consumer — its 4 production, optional and peer dependency(ies), across 1 product package.json manifest(s), and everything those install in turn. Its 16 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: src/event-bus.ts (5 of 6 changes were fixes)
What to do
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with event-bus.ts. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
No source file's living knowledge is concentrated in a single author. Counted over 9 of the 68 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
0 deducted task-comment markers across 2208 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D26 · Project Cohesion
0 of 1 build units (npm) flagged as possibly oversized/incoherent.
D27 · Navigability
65 % of calls cross a namespace and 16 % go through an interface, but 30 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
10 finding(s): 0 critical, 10 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 10 High secret finding(s) in Secrets (history) — start with REDACTED (10). — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
D30 · Dependency Vulnerabilities
3 finding(s): 0 critical, 1 high, 2 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 9 of the 68 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
AX9 · CQS / query purity
DM1 · Aggregate boundaries
DM11 · Constructible invalid state
- `Hero`'s public constructor takes `id` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was checked for any branch (`if`, ternary, `switch`) or any call — it has neither, only assignments; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Hero` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. (×2) — test/src/heroes/models/hero.model.ts:6, test/src/scoped/models/hero.model.ts:6
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM5 · Encapsulated state
- `AggregateRoot` exposes publicly writable state ([IS_AUTO_COMMIT_ENABLED], autoCommit). — src/mixins/with-aggregate-root.mixin.ts:26
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM9 · Scattered domain decisions
ED3 · Event naming
- `NoopEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — test/src/noop/events/impl/noop.event.ts:1
What to do
- Name events in the past tense — they record facts that already happened.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
- CONTRIBUTING.md links to `docs/DEVELOPER.md#clang-format`, but `docs/DEVELOPER.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:156
What to do
- Reconcile the README with reality: CONTRIBUTING.md links to `docs/DEVELOPER.md#clang-format`, but `docs/DEVELOPER.md` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 1427 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- src/command-bus.ts:27 · src/query-bus.ts:29 — the two spans are one implementation copied and then locally edited — 751 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/command-bus.ts:27
- src/event-publisher.ts:25 · src/event-publisher.ts:56 — the two spans are one implementation copied and then locally edited — 85 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/event-publisher.ts:25
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
R3 · Large Files
- src/event-bus.ts has 420 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/event-bus.ts:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
R7 · Dead Code
- Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect. — src/mixins/with-aggregate-root.mixin.ts:31
R8 · Dependency Hygiene
R9 · Circular Imports
- src/classes/command.ts → src/interfaces/index.ts → src/interfaces/commands/command-bus.interface.ts → src/classes/index.ts → src/classes/command.ts (one verified cycle inside a mutually-dependent group of 8 files) — src/classes/command.ts:1
- src/command-bus.ts → src/index.ts → src/command-bus.ts (one verified cycle inside a mutually-dependent group of 10 files) — src/command-bus.ts:13
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- ~2.0 `!` null assertions per 1k TypeScript source lines — 5 assertion(s) across the 2474 source line(s) of the 67 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: src/event-bus.ts (3), src/command-bus.ts (1), src/query-bus.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 92% | Exemplary | Solid. |
| Architecture | 85% | Strong | Solid. |
| Maturity | 55% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 62% | Adequate — gated by D9, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 53% | Adequate — gated by D28 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 51% | Adequate — gated by DM11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 67 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: NestJS makes a provider that injects a request-scoped one request-scoped itself (scope bubbles up the injection chain), and gives every consumer its own transient instance by contract.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D12 Dependency Hygiene — Dependency currency not established — this repository declares no production dependency to grade
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — D19 withholds "Documentation: generator boilerplate left in place": 1 candidate(s) were measured and not published.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (629 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (mixins), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — Too few judgeable comments (18 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D4 Code Duplication — This repository's production source (.ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM6 Domain ↔ infrastructure boundary — this TypeScript/JavaScript repository maps no type to a persistence framework (TypeORM/Prisma/MikroORM/Sequelize/Mongoose), so DM6's domain↔infrastructure fusion read has no population to be taken over
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- ED5 Idempotency — 15 mutating command handler(s)/consumer(s) detected and 18 handler method(s) walked, but no persistent write was recognised in any of them — idempotency not assessed
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage --coverage.reporter=lcovonly`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- S1 Web-Security Posture — Not assessed: 67 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 17 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Import cycle (4 files) src/classes/command.ts:1
- Import cycle (2 files) src/command-bus.ts:13
Serious — 15 finding(s)
- No assertions: should keep reacting to events after the saga has thrown test/e2e/unhandled-exceptions.spec.ts:130
- No assertions: should infer return types of similar unions unions src/operators/of-type.spec.ts:58
- No assertions: should infer return types of disparate unions src/operators/of-type.spec.ts:72
- REDACTED
- REDACTED
- Constructible in an invalid state: Hero test/src/heroes/models/hero.model.ts:6
- Constructible in an invalid state: Hero test/src/scoped/models/hero.model.ts:6
- Fixed-sleep synchronisation: should keep reacting to events after the saga has thrown test/e2e/unhandled-exceptions.spec.ts:130
- Repeated repair: src/event-bus.ts src/event-bus.ts:223
- REDACTED
- Coverage not measured — JavaScript/TypeScript suite
- Mutable entity: AggregateRoot src/mixins/with-aggregate-root.mixin.ts:26
- Duplicated block with local edits (122 matched lines × 2 locations) src/command-bus.ts:27
- Duplicated block with local edits (18 matched lines × 2 locations) src/event-publisher.ts:25
- src/event-bus.ts: 420 lines of code src/event-bus.ts:1
Minor — 16 finding(s)
- Mock-dominated test: should wait for the event handlers to complete test/e2e/sync-event-handlers-app.spec.ts:45
- Mock-dominated test: should wait for the event handlers to complete test/e2e/sync-event-handlers-app.spec.ts:57
- Mock-dominated test: should wait for the event handlers to complete test/e2e/sync-event-handlers-app.spec.ts:86
- Mock-dominated test: should wait for the event handlers to complete test/e2e/sync-event-handlers-app.spec.ts:98
- Mock-dominated test: should return directly test/e2e/sync-event-handlers-app.spec.ts:110
- Scattered collaborators
- REDACTED
- Inverted test pyramid
- Event not named in past tense: NoopEvent test/src/noop/events/impl/noop.event.ts:1
- No ADRs
- No architecture diagram/doc
- README/code drift CONTRIBUTING.md:156
- No SAST
- No changelog
- Unused private field 'readonly' src/mixins/with-aggregate-root.mixin.ts:31
- Null assertions (`!`) reduce the strict null checking score
Minor — 1 finding(s)
- Dependency hygiene PARTLY measured — npm pinning read, dependency currency not (the committed lockfile resolved no direct production dependency)
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ad2ac5df8e8043ff9dc2d160f9e7582e/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ad2ac5df8e8043ff9dc2d160f9e7582e/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 3 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 3 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |