Executive summary
snatalenko/node-cqrs is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because we found no automated security scanning of the code, its secrets or its dependencies. It scores 68 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 58, is the weakest lens and counts most in the score. The best first step is adding automated security scanning, worth about 7 points. Making the two tests that check nothing check their results comes next, worth about 2 points. Raising Production Readiness to 70 would lift the score to about 72.
Eleven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Eight known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version and updating the vulnerable packages would close both risks. The two tests that check nothing need to check the result they produce.
The product code is 8,773 lines, about €29,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Production Readiness rose from 58 to 70, the lowest score rated Strong, the score would rise from 68 to about 72.
New since the last survey: 1 finding
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 3 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Code Duplication · Duplicated block with local edits (7 matched lines × 2 locations) src/sqlite-workers/SqliteWorkerRunner.ts
Rebuild cost: about €29,000 · Estimate
| Cost to rebuild | €9,500 to €48,000, for 158 to 501 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, 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.9 at a score of 68. 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: 8,773 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 interfaces | 2 interfaces.IDispatchPipelineProcessor | 3 interfaces.IEventSet | 4 interfaces.IEventStream | 5 interfaces.IIdentifierProvider | 6 interfaces.ILogger | 7 interfaces.IMessageMeta | 8 interfaces.IObservable | 9 interfaces.IViewLocker | 10 interfaces.Identifier | 11 rabbitmq.utils.resolveProvider | 12 interfaces.ICommandBus | 13 interfaces.IEventBus | 14 interfaces.IEventLocker | 15 interfaces.IEventStorageReader | 16 interfaces.IEventStore | 17 interfaces.IObjectStorage | 18 rabbitmq.RabbitMqGateway | 19 AggregateCommandHandler | 20 SagaEventHandler | 21 in-memory.InMemoryMessageBus | 22 interfaces.IEventDispatcher | 23 interfaces.IProjection | 24 mongodb.AbstractMongoView | 25 redis.RedisView | 26 workers.WorkerProxyProjection | 27 AbstractAggregate | 28 AbstractProjection | 29 AbstractSaga | 30 CqrsContainerBuilder | 31 interfaces.IContainer | 32 EventStore | 33 in-memory.InMemoryEventStorage | 34 in-memory.InMemorySnapshotStorage | 35 mongodb.MongoEventStorage | 36 rabbitmq.RabbitMqCommandBus | 37 rabbitmq.RabbitMqEventBus | 38 sqlite.AbstractSqliteAccessor | 39 sqlite.AbstractSqliteView | 40 sqlite.SqliteEventStorage |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 interfaces | ||||||||||||||||||||||||||||||||||||||||
| 2 interfaces.IDispatchPipelineProcessor | ||||||||||||||||||||||||||||||||||||||||
| 3 interfaces.IEventSet | ||||||||||||||||||||||||||||||||||||||||
| 4 interfaces.IEventStream | ||||||||||||||||||||||||||||||||||||||||
| 5 interfaces.IIdentifierProvider | ||||||||||||||||||||||||||||||||||||||||
| 6 interfaces.ILogger | ||||||||||||||||||||||||||||||||||||||||
| 7 interfaces.IMessageMeta | ||||||||||||||||||||||||||||||||||||||||
| 8 interfaces.IObservable | ||||||||||||||||||||||||||||||||||||||||
| 9 interfaces.IViewLocker | ||||||||||||||||||||||||||||||||||||||||
| 10 interfaces.Identifier | ||||||||||||||||||||||||||||||||||||||||
| 11 rabbitmq.utils.resolveProvider | ||||||||||||||||||||||||||||||||||||||||
| 12 interfaces.ICommandBus | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 interfaces.IEventBus | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 interfaces.IEventLocker | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 interfaces.IEventStorageReader | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 interfaces.IEventStore | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 interfaces.IObjectStorage | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 rabbitmq.RabbitMqGateway | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 AggregateCommandHandler | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 20 SagaEventHandler | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 21 in-memory.InMemoryMessageBus | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 22 interfaces.IEventDispatcher | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 interfaces.IProjection | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 mongodb.AbstractMongoView | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 redis.RedisView | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 26 workers.WorkerProxyProjection | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 27 AbstractAggregate | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 28 AbstractProjection | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 29 AbstractSaga | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 30 CqrsContainerBuilder | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 interfaces.IContainer | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 32 EventStore | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||
| 33 in-memory.InMemoryEventStorage | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 34 in-memory.InMemorySnapshotStorage | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 mongodb.MongoEventStorage | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 36 rabbitmq.RabbitMqCommandBus | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 37 rabbitmq.RabbitMqEventBus | 1 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 38 sqlite.AbstractSqliteAccessor | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 sqlite.AbstractSqliteView | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 sqlite.SqliteEventStorage | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
12→7 interfaces.ICommandBus uses interfaces.IMessageMeta✕
- Connections
- 1 pair of types, where a type in interfaces.ICommandBus uses a type in interfaces.IMessageMeta.
- The types involved
src.interfaces.ICommandBus.ICommandBus→src.interfaces.IMessageMeta.IMessageMeta
- Direction
- interfaces.ICommandBus uses interfaces.IMessageMeta, so a change to interfaces.IMessageMeta can break interfaces.ICommandBus, while a change to interfaces.ICommandBus can't break interfaces.IMessageMeta.
- Position
- Below the diagonal: interfaces.ICommandBus uses a module listed above it, which is the healthy direction.
13→1 interfaces.IEventBus uses interfaces✕
- Connections
- 1 pair of types, where a type in interfaces.IEventBus uses a type in interfaces.
- The types involved
src.interfaces.IEventBus.IEventBus→src.interfaces.IEvent
- Direction
- interfaces.IEventBus uses interfaces, so a change to interfaces can break interfaces.IEventBus, while a change to interfaces.IEventBus can't break interfaces.
- Position
- Below the diagonal: interfaces.IEventBus uses a module listed above it, which is the healthy direction.
14→1 interfaces.IEventLocker uses interfaces✕
- Connections
- 1 pair of types, where a type in interfaces.IEventLocker uses a type in interfaces.
- The types involved
src.interfaces.IEventLocker.IEventLocker→src.interfaces.IEvent
- Direction
- interfaces.IEventLocker uses interfaces, so a change to interfaces can break interfaces.IEventLocker, while a change to interfaces.IEventLocker can't break interfaces.
- Position
- Below the diagonal: interfaces.IEventLocker uses a module listed above it, which is the healthy direction.
15→4 interfaces.IEventStorageReader uses interfaces.IEventStream✕
- Connections
- 1 pair of types, where a type in interfaces.IEventStorageReader uses a type in interfaces.IEventStream.
- The types involved
src.interfaces.IEventStorageReader.IEventStorageReader→src.interfaces.IEventStream.IEventStream
- Direction
- interfaces.IEventStorageReader uses interfaces.IEventStream, so a change to interfaces.IEventStream can break interfaces.IEventStorageReader, while a change to interfaces.IEventStorageReader can't break interfaces.IEventStream.
- Position
- Below the diagonal: interfaces.IEventStorageReader uses a module listed above it, which is the healthy direction.
15→10 interfaces.IEventStorageReader uses interfaces.Identifier✕
- Connections
- 1 pair of types, where a type in interfaces.IEventStorageReader uses a type in interfaces.Identifier.
- The types involved
src.interfaces.IEventStorageReader.IEventStorageReader→src.interfaces.Identifier.Identifier
- Direction
- interfaces.IEventStorageReader uses interfaces.Identifier, so a change to interfaces.Identifier can break interfaces.IEventStorageReader, while a change to interfaces.IEventStorageReader can't break interfaces.Identifier.
- Position
- Below the diagonal: interfaces.IEventStorageReader uses a module listed above it, which is the healthy direction.
16→1 interfaces.IEventStore uses interfaces✕
- Connections
- 1 pair of types, where a type in interfaces.IEventStore uses a type in interfaces.
- The types involved
src.interfaces.IEventStore.IEventStore→src.interfaces.IEvent
- Direction
- interfaces.IEventStore uses interfaces, so a change to interfaces can break interfaces.IEventStore, while a change to interfaces.IEventStore can't break interfaces.
- Position
- Below the diagonal: interfaces.IEventStore uses a module listed above it, which is the healthy direction.
16→8 interfaces.IEventStore uses interfaces.IObservable✕
- Connections
- 1 pair of types, where a type in interfaces.IEventStore uses a type in interfaces.IObservable.
- The types involved
src.interfaces.IEventStore.IEventStore→src.interfaces.IObservable.IMessageHandler
- Direction
- interfaces.IEventStore uses interfaces.IObservable, so a change to interfaces.IObservable can break interfaces.IEventStore, while a change to interfaces.IEventStore can't break interfaces.IObservable.
- Position
- Below the diagonal: interfaces.IEventStore uses a module listed above it, which is the healthy direction.
17→10 interfaces.IObjectStorage uses interfaces.Identifier✕
- Connections
- 1 pair of types, where a type in interfaces.IObjectStorage uses a type in interfaces.Identifier.
- The types involved
src.interfaces.IObjectStorage.IObjectStorage→src.interfaces.Identifier.Identifier
- Direction
- interfaces.IObjectStorage uses interfaces.Identifier, so a change to interfaces.Identifier can break interfaces.IObjectStorage, while a change to interfaces.IObjectStorage can't break interfaces.Identifier.
- Position
- Below the diagonal: interfaces.IObjectStorage uses a module listed above it, which is the healthy direction.
18→7 rabbitmq.RabbitMqGateway uses interfaces.IMessageMeta✕
- Connections
- 1 pair of types, where a type in rabbitmq.RabbitMqGateway uses a type in interfaces.IMessageMeta.
- The types involved
src.rabbitmq.RabbitMqGateway.RabbitMqGateway→src.interfaces.IMessageMeta.IMessageMeta
- Direction
- rabbitmq.RabbitMqGateway uses interfaces.IMessageMeta, so a change to interfaces.IMessageMeta can break rabbitmq.RabbitMqGateway, while a change to rabbitmq.RabbitMqGateway can't break interfaces.IMessageMeta.
- Position
- Below the diagonal: rabbitmq.RabbitMqGateway uses a module listed above it, which is the healthy direction.
18→11 rabbitmq.RabbitMqGateway uses rabbitmq.utils.resolveProvider✕
- Connections
- 1 pair of types, where a type in rabbitmq.RabbitMqGateway uses a type in rabbitmq.utils.resolveProvider.
- The types involved
src.rabbitmq.RabbitMqGateway.RabbitMqGateway→src.rabbitmq.utils.resolveProvider.ConfigProvider
- Direction
- rabbitmq.RabbitMqGateway uses rabbitmq.utils.resolveProvider, so a change to rabbitmq.utils.resolveProvider can break rabbitmq.RabbitMqGateway, while a change to rabbitmq.RabbitMqGateway can't break rabbitmq.utils.resolveProvider.
- Position
- Below the diagonal: rabbitmq.RabbitMqGateway uses a module listed above it, which is the healthy direction.
19→3 AggregateCommandHandler uses interfaces.IEventSet✕
- Connections
- 1 pair of types, where a type in AggregateCommandHandler uses a type in interfaces.IEventSet.
- The types involved
src.AggregateCommandHandler.AggregateCommandHandler→src.interfaces.IEventSet.IEventSet
- Direction
- AggregateCommandHandler uses interfaces.IEventSet, so a change to interfaces.IEventSet can break AggregateCommandHandler, while a change to AggregateCommandHandler can't break interfaces.IEventSet.
- Position
- Below the diagonal: AggregateCommandHandler uses a module listed above it, which is the healthy direction.
19→6 AggregateCommandHandler uses interfaces.ILogger✕
- Connections
- 1 pair of types, where a type in AggregateCommandHandler uses a type in interfaces.ILogger.
- The types involved
src.AggregateCommandHandler.AggregateCommandHandler→src.interfaces.ILogger.ILogger
- Direction
- AggregateCommandHandler uses interfaces.ILogger, so a change to interfaces.ILogger can break AggregateCommandHandler, while a change to AggregateCommandHandler can't break interfaces.ILogger.
- Position
- Below the diagonal: AggregateCommandHandler uses a module listed above it, which is the healthy direction.
19→7 AggregateCommandHandler uses interfaces.IMessageMeta✕
- Connections
- 1 pair of types, where a type in AggregateCommandHandler uses a type in interfaces.IMessageMeta.
- The types involved
src.AggregateCommandHandler.AggregateCommandHandler→src.interfaces.IMessageMeta.IMessageMeta
- Direction
- AggregateCommandHandler uses interfaces.IMessageMeta, so a change to interfaces.IMessageMeta can break AggregateCommandHandler, while a change to AggregateCommandHandler can't break interfaces.IMessageMeta.
- Position
- Below the diagonal: AggregateCommandHandler uses a module listed above it, which is the healthy direction.
19→8 AggregateCommandHandler uses interfaces.IObservable✕
- Connections
- 1 pair of types, where a type in AggregateCommandHandler uses a type in interfaces.IObservable.
- The types involved
src.AggregateCommandHandler.AggregateCommandHandler→src.interfaces.IObservable.IObservable
- Direction
- AggregateCommandHandler uses interfaces.IObservable, so a change to interfaces.IObservable can break AggregateCommandHandler, while a change to AggregateCommandHandler can't break interfaces.IObservable.
- Position
- Below the diagonal: AggregateCommandHandler uses a module listed above it, which is the healthy direction.
19→10 AggregateCommandHandler uses interfaces.Identifier✕
- Connections
- 1 pair of types, where a type in AggregateCommandHandler uses a type in interfaces.Identifier.
- The types involved
src.AggregateCommandHandler.AggregateCommandHandler→src.interfaces.Identifier.Identifier
- Direction
- AggregateCommandHandler uses interfaces.Identifier, so a change to interfaces.Identifier can break AggregateCommandHandler, while a change to AggregateCommandHandler can't break interfaces.Identifier.
- Position
- Below the diagonal: AggregateCommandHandler uses a module listed above it, which is the healthy direction.
19→12 AggregateCommandHandler uses interfaces.ICommandBus✕
- Connections
- 1 pair of types, where a type in AggregateCommandHandler uses a type in interfaces.ICommandBus.
- The types involved
src.AggregateCommandHandler.AggregateCommandHandler→src.interfaces.ICommandBus.ICommandHandler
- Direction
- AggregateCommandHandler uses interfaces.ICommandBus, so a change to interfaces.ICommandBus can break AggregateCommandHandler, while a change to AggregateCommandHandler can't break interfaces.ICommandBus.
- Position
- Below the diagonal: AggregateCommandHandler uses a module listed above it, which is the healthy direction.
19→16 AggregateCommandHandler uses interfaces.IEventStore✕
- Connections
- 1 pair of types, where a type in AggregateCommandHandler uses a type in interfaces.IEventStore.
- The types involved
src.AggregateCommandHandler.AggregateCommandHandler→src.interfaces.IEventStore.IEventStore
- Direction
- AggregateCommandHandler uses interfaces.IEventStore, so a change to interfaces.IEventStore can break AggregateCommandHandler, while a change to AggregateCommandHandler can't break interfaces.IEventStore.
- Position
- Below the diagonal: AggregateCommandHandler uses a module listed above it, which is the healthy direction.
20→1 SagaEventHandler uses interfaces✕
- Connections
- 1 pair of types, where a type in SagaEventHandler uses a type in interfaces.
- The types involved
src.SagaEventHandler.SagaEventHandler→src.interfaces.IEvent
- Direction
- SagaEventHandler uses interfaces, so a change to interfaces can break SagaEventHandler, while a change to SagaEventHandler can't break interfaces.
- Position
- Below the diagonal: SagaEventHandler uses a module listed above it, which is the healthy direction.
20→6 SagaEventHandler uses interfaces.ILogger✕
- Connections
- 1 pair of types, where a type in SagaEventHandler uses a type in interfaces.ILogger.
- The types involved
src.SagaEventHandler.SagaEventHandler→src.interfaces.ILogger.ILogger
- Direction
- SagaEventHandler uses interfaces.ILogger, so a change to interfaces.ILogger can break SagaEventHandler, while a change to SagaEventHandler can't break interfaces.ILogger.
- Position
- Below the diagonal: SagaEventHandler uses a module listed above it, which is the healthy direction.
20→7 SagaEventHandler uses interfaces.IMessageMeta✕
- Connections
- 1 pair of types, where a type in SagaEventHandler uses a type in interfaces.IMessageMeta.
- The types involved
src.SagaEventHandler.SagaEventHandler→src.interfaces.IMessageMeta.IMessageMeta
- Direction
- SagaEventHandler uses interfaces.IMessageMeta, so a change to interfaces.IMessageMeta can break SagaEventHandler, while a change to SagaEventHandler can't break interfaces.IMessageMeta.
- Position
- Below the diagonal: SagaEventHandler uses a module listed above it, which is the healthy direction.
20→8 SagaEventHandler uses interfaces.IObservable✕
- Connections
- 1 pair of types, where a type in SagaEventHandler uses a type in interfaces.IObservable.
- The types involved
src.SagaEventHandler.SagaEventHandler→src.interfaces.IObservable.IObservable
- Direction
- SagaEventHandler uses interfaces.IObservable, so a change to interfaces.IObservable can break SagaEventHandler, while a change to SagaEventHandler can't break interfaces.IObservable.
- Position
- Below the diagonal: SagaEventHandler uses a module listed above it, which is the healthy direction.
20→10 SagaEventHandler uses interfaces.Identifier✕
- Connections
- 1 pair of types, where a type in SagaEventHandler uses a type in interfaces.Identifier.
- The types involved
src.SagaEventHandler.SagaEventHandler→src.interfaces.Identifier.Identifier
- Direction
- SagaEventHandler uses interfaces.Identifier, so a change to interfaces.Identifier can break SagaEventHandler, while a change to SagaEventHandler can't break interfaces.Identifier.
- Position
- Below the diagonal: SagaEventHandler uses a module listed above it, which is the healthy direction.
20→12 SagaEventHandler uses interfaces.ICommandBus✕
- Connections
- 1 pair of types, where a type in SagaEventHandler uses a type in interfaces.ICommandBus.
- The types involved
src.SagaEventHandler.SagaEventHandler→src.interfaces.ICommandBus.ICommandBus
- Direction
- SagaEventHandler uses interfaces.ICommandBus, so a change to interfaces.ICommandBus can break SagaEventHandler, while a change to SagaEventHandler can't break interfaces.ICommandBus.
- Position
- Below the diagonal: SagaEventHandler uses a module listed above it, which is the healthy direction.
20→16 SagaEventHandler uses interfaces.IEventStore✕
- Connections
- 1 pair of types, where a type in SagaEventHandler uses a type in interfaces.IEventStore.
- The types involved
src.SagaEventHandler.SagaEventHandler→src.interfaces.IEventStore.IEventStore
- Direction
- SagaEventHandler uses interfaces.IEventStore, so a change to interfaces.IEventStore can break SagaEventHandler, while a change to SagaEventHandler can't break interfaces.IEventStore.
- Position
- Below the diagonal: SagaEventHandler uses a module listed above it, which is the healthy direction.
21→1 in-memory.InMemoryMessageBus uses interfaces✕
- Connections
- 1 pair of types, where a type in in-memory.InMemoryMessageBus uses a type in interfaces.
- The types involved
src.in-memory.InMemoryMessageBus.InMemoryMessageBus→src.interfaces.IEvent
- Direction
- in-memory.InMemoryMessageBus uses interfaces, so a change to interfaces can break in-memory.InMemoryMessageBus, while a change to in-memory.InMemoryMessageBus can't break interfaces.
- Position
- Below the diagonal: in-memory.InMemoryMessageBus uses a module listed above it, which is the healthy direction.
21→7 in-memory.InMemoryMessageBus uses interfaces.IMessageMeta✕
- Connections
- 1 pair of types, where a type in in-memory.InMemoryMessageBus uses a type in interfaces.IMessageMeta.
- The types involved
src.in-memory.InMemoryMessageBus.InMemoryMessageBus→src.interfaces.IMessageMeta.IMessageMeta
- Direction
- in-memory.InMemoryMessageBus uses interfaces.IMessageMeta, so a change to interfaces.IMessageMeta can break in-memory.InMemoryMessageBus, while a change to in-memory.InMemoryMessageBus can't break interfaces.IMessageMeta.
- Position
- Below the diagonal: in-memory.InMemoryMessageBus uses a module listed above it, which is the healthy direction.
21→8 in-memory.InMemoryMessageBus uses interfaces.IObservable✕
- Connections
- 2 pairs of types, where a type in in-memory.InMemoryMessageBus uses a type in interfaces.IObservable.
- The types involved
src.in-memory.InMemoryMessageBus.InMemoryMessageBus→src.interfaces.IObservable.IMessageHandlersrc.in-memory.InMemoryMessageBus.InMemoryMessageBus→src.interfaces.IObservable.IObservable
- Direction
- in-memory.InMemoryMessageBus uses interfaces.IObservable, so a change to interfaces.IObservable can break in-memory.InMemoryMessageBus, while a change to in-memory.InMemoryMessageBus can't break interfaces.IObservable.
- Position
- Below the diagonal: in-memory.InMemoryMessageBus uses a module listed above it, which is the healthy direction.
21→12 in-memory.InMemoryMessageBus uses interfaces.ICommandBus✕
- Connections
- 1 pair of types, where a type in in-memory.InMemoryMessageBus uses a type in interfaces.ICommandBus.
- The types involved
src.in-memory.InMemoryMessageBus.InMemoryMessageBus→src.interfaces.ICommandBus.ICommandBus
- Direction
- in-memory.InMemoryMessageBus uses interfaces.ICommandBus, so a change to interfaces.ICommandBus can break in-memory.InMemoryMessageBus, while a change to in-memory.InMemoryMessageBus can't break interfaces.ICommandBus.
- Position
- Below the diagonal: in-memory.InMemoryMessageBus uses a module listed above it, which is the healthy direction.
21→13 in-memory.InMemoryMessageBus uses interfaces.IEventBus✕
- Connections
- 1 pair of types, where a type in in-memory.InMemoryMessageBus uses a type in interfaces.IEventBus.
- The types involved
src.in-memory.InMemoryMessageBus.InMemoryMessageBus→src.interfaces.IEventBus.IEventBus
- Direction
- in-memory.InMemoryMessageBus uses interfaces.IEventBus, so a change to interfaces.IEventBus can break in-memory.InMemoryMessageBus, while a change to in-memory.InMemoryMessageBus can't break interfaces.IEventBus.
- Position
- Below the diagonal: in-memory.InMemoryMessageBus uses a module listed above it, which is the healthy direction.
22→3 interfaces.IEventDispatcher uses interfaces.IEventSet✕
- Connections
- 1 pair of types, where a type in interfaces.IEventDispatcher uses a type in interfaces.IEventSet.
- The types involved
src.interfaces.IEventDispatcher.IEventDispatcher→src.interfaces.IEventSet.IEventSet
- Direction
- interfaces.IEventDispatcher uses interfaces.IEventSet, so a change to interfaces.IEventSet can break interfaces.IEventDispatcher, while a change to interfaces.IEventDispatcher can't break interfaces.IEventSet.
- Position
- Below the diagonal: interfaces.IEventDispatcher uses a module listed above it, which is the healthy direction.
22→13 interfaces.IEventDispatcher uses interfaces.IEventBus✕
- Connections
- 1 pair of types, where a type in interfaces.IEventDispatcher uses a type in interfaces.IEventBus.
- The types involved
src.interfaces.IEventDispatcher.IEventDispatcher→src.interfaces.IEventBus.IEventBus
- Direction
- interfaces.IEventDispatcher uses interfaces.IEventBus, so a change to interfaces.IEventBus can break interfaces.IEventDispatcher, while a change to interfaces.IEventDispatcher can't break interfaces.IEventBus.
- Position
- Below the diagonal: interfaces.IEventDispatcher uses a module listed above it, which is the healthy direction.
23→1 interfaces.IProjection uses interfaces✕
- Connections
- 1 pair of types, where a type in interfaces.IProjection uses a type in interfaces.
- The types involved
src.interfaces.IProjection.IProjection→src.interfaces.IEvent
- Direction
- interfaces.IProjection uses interfaces, so a change to interfaces can break interfaces.IProjection, while a change to interfaces.IProjection can't break interfaces.
- Position
- Below the diagonal: interfaces.IProjection uses a module listed above it, which is the healthy direction.
23→8 interfaces.IProjection uses interfaces.IObservable✕
- Connections
- 1 pair of types, where a type in interfaces.IProjection uses a type in interfaces.IObservable.
- The types involved
src.interfaces.IProjection.IProjection→src.interfaces.IObservable.IObservable
- Direction
- interfaces.IProjection uses interfaces.IObservable, so a change to interfaces.IObservable can break interfaces.IProjection, while a change to interfaces.IProjection can't break interfaces.IObservable.
- Position
- Below the diagonal: interfaces.IProjection uses a module listed above it, which is the healthy direction.
23→15 interfaces.IProjection uses interfaces.IEventStorageReader✕
- Connections
- 1 pair of types, where a type in interfaces.IProjection uses a type in interfaces.IEventStorageReader.
- The types involved
src.interfaces.IProjection.IProjection→src.interfaces.IEventStorageReader.IEventStorageReader
- Direction
- interfaces.IProjection uses interfaces.IEventStorageReader, so a change to interfaces.IEventStorageReader can break interfaces.IProjection, while a change to interfaces.IProjection can't break interfaces.IEventStorageReader.
- Position
- Below the diagonal: interfaces.IProjection uses a module listed above it, which is the healthy direction.
24→1 mongodb.AbstractMongoView uses interfaces✕
- Connections
- 1 pair of types, where a type in mongodb.AbstractMongoView uses a type in interfaces.
- The types involved
src.mongodb.AbstractMongoView.AbstractMongoView→src.interfaces.IEvent
- Direction
- mongodb.AbstractMongoView uses interfaces, so a change to interfaces can break mongodb.AbstractMongoView, while a change to mongodb.AbstractMongoView can't break interfaces.
- Position
- Below the diagonal: mongodb.AbstractMongoView uses a module listed above it, which is the healthy direction.
24→9 mongodb.AbstractMongoView uses interfaces.IViewLocker✕
- Connections
- 1 pair of types, where a type in mongodb.AbstractMongoView uses a type in interfaces.IViewLocker.
- The types involved
src.mongodb.AbstractMongoView.AbstractMongoView→src.interfaces.IViewLocker.IViewLocker
- Direction
- mongodb.AbstractMongoView uses interfaces.IViewLocker, so a change to interfaces.IViewLocker can break mongodb.AbstractMongoView, while a change to mongodb.AbstractMongoView can't break interfaces.IViewLocker.
- Position
- Below the diagonal: mongodb.AbstractMongoView uses a module listed above it, which is the healthy direction.
24→14 mongodb.AbstractMongoView uses interfaces.IEventLocker✕
- Connections
- 1 pair of types, where a type in mongodb.AbstractMongoView uses a type in interfaces.IEventLocker.
- The types involved
src.mongodb.AbstractMongoView.AbstractMongoView→src.interfaces.IEventLocker.IEventLocker
- Direction
- mongodb.AbstractMongoView uses interfaces.IEventLocker, so a change to interfaces.IEventLocker can break mongodb.AbstractMongoView, while a change to mongodb.AbstractMongoView can't break interfaces.IEventLocker.
- Position
- Below the diagonal: mongodb.AbstractMongoView uses a module listed above it, which is the healthy direction.
25→1 redis.RedisView uses interfaces✕
- Connections
- 1 pair of types, where a type in redis.RedisView uses a type in interfaces.
- The types involved
src.redis.RedisView.RedisView→src.interfaces.IEvent
- Direction
- redis.RedisView uses interfaces, so a change to interfaces can break redis.RedisView, while a change to redis.RedisView can't break interfaces.
- Position
- Below the diagonal: redis.RedisView uses a module listed above it, which is the healthy direction.
25→9 redis.RedisView uses interfaces.IViewLocker✕
- Connections
- 1 pair of types, where a type in redis.RedisView uses a type in interfaces.IViewLocker.
- The types involved
src.redis.RedisView.RedisView→src.interfaces.IViewLocker.IViewLocker
- Direction
- redis.RedisView uses interfaces.IViewLocker, so a change to interfaces.IViewLocker can break redis.RedisView, while a change to redis.RedisView can't break interfaces.IViewLocker.
- Position
- Below the diagonal: redis.RedisView uses a module listed above it, which is the healthy direction.
25→10 redis.RedisView uses interfaces.Identifier✕
- Connections
- 1 pair of types, where a type in redis.RedisView uses a type in interfaces.Identifier.
- The types involved
src.redis.RedisView.RedisView→src.interfaces.Identifier.Identifier
- Direction
- redis.RedisView uses interfaces.Identifier, so a change to interfaces.Identifier can break redis.RedisView, while a change to redis.RedisView can't break interfaces.Identifier.
- Position
- Below the diagonal: redis.RedisView uses a module listed above it, which is the healthy direction.
25→14 redis.RedisView uses interfaces.IEventLocker✕
- Connections
- 1 pair of types, where a type in redis.RedisView uses a type in interfaces.IEventLocker.
- The types involved
src.redis.RedisView.RedisView→src.interfaces.IEventLocker.IEventLocker
- Direction
- redis.RedisView uses interfaces.IEventLocker, so a change to interfaces.IEventLocker can break redis.RedisView, while a change to redis.RedisView can't break interfaces.IEventLocker.
- Position
- Below the diagonal: redis.RedisView uses a module listed above it, which is the healthy direction.
25→17 redis.RedisView uses interfaces.IObjectStorage✕
- Connections
- 1 pair of types, where a type in redis.RedisView uses a type in interfaces.IObjectStorage.
- The types involved
src.redis.RedisView.RedisView→src.interfaces.IObjectStorage.IObjectStorage
- Direction
- redis.RedisView uses interfaces.IObjectStorage, so a change to interfaces.IObjectStorage can break redis.RedisView, while a change to redis.RedisView can't break interfaces.IObjectStorage.
- Position
- Below the diagonal: redis.RedisView uses a module listed above it, which is the healthy direction.
26→1 workers.WorkerProxyProjection uses interfaces✕
- Connections
- 1 pair of types, where a type in workers.WorkerProxyProjection uses a type in interfaces.
- The types involved
src.workers.WorkerProxyProjection.WorkerProxyProjection→src.interfaces.IEvent
- Direction
- workers.WorkerProxyProjection uses interfaces, so a change to interfaces can break workers.WorkerProxyProjection, while a change to workers.WorkerProxyProjection can't break interfaces.
- Position
- Below the diagonal: workers.WorkerProxyProjection uses a module listed above it, which is the healthy direction.
26→3 workers.WorkerProxyProjection uses interfaces.IEventSet✕
- Connections
- 1 pair of types, where a type in workers.WorkerProxyProjection uses a type in interfaces.IEventSet.
- The types involved
src.workers.WorkerProxyProjection.WorkerProxyProjection→src.interfaces.IEventSet.IEventSet
- Direction
- workers.WorkerProxyProjection uses interfaces.IEventSet, so a change to interfaces.IEventSet can break workers.WorkerProxyProjection, while a change to workers.WorkerProxyProjection can't break interfaces.IEventSet.
- Position
- Below the diagonal: workers.WorkerProxyProjection uses a module listed above it, which is the healthy direction.
26→6 workers.WorkerProxyProjection uses interfaces.ILogger✕
- Connections
- 1 pair of types, where a type in workers.WorkerProxyProjection uses a type in interfaces.ILogger.
- The types involved
src.workers.WorkerProxyProjection.WorkerProxyProjection→src.interfaces.ILogger.ILogger
- Direction
- workers.WorkerProxyProjection uses interfaces.ILogger, so a change to interfaces.ILogger can break workers.WorkerProxyProjection, while a change to workers.WorkerProxyProjection can't break interfaces.ILogger.
- Position
- Below the diagonal: workers.WorkerProxyProjection uses a module listed above it, which is the healthy direction.
26→9 workers.WorkerProxyProjection uses interfaces.IViewLocker✕
- Connections
- 1 pair of types, where a type in workers.WorkerProxyProjection uses a type in interfaces.IViewLocker.
- The types involved
src.workers.WorkerProxyProjection.WorkerProxyProjection→src.interfaces.IViewLocker.IViewLocker
- Direction
- workers.WorkerProxyProjection uses interfaces.IViewLocker, so a change to interfaces.IViewLocker can break workers.WorkerProxyProjection, while a change to workers.WorkerProxyProjection can't break interfaces.IViewLocker.
- Position
- Below the diagonal: workers.WorkerProxyProjection uses a module listed above it, which is the healthy direction.
26→15 workers.WorkerProxyProjection uses interfaces.IEventStorageReader✕
- Connections
- 1 pair of types, where a type in workers.WorkerProxyProjection uses a type in interfaces.IEventStorageReader.
- The types involved
src.workers.WorkerProxyProjection.WorkerProxyProjection→src.interfaces.IEventStorageReader.IEventStorageReader
- Direction
- workers.WorkerProxyProjection uses interfaces.IEventStorageReader, so a change to interfaces.IEventStorageReader can break workers.WorkerProxyProjection, while a change to workers.WorkerProxyProjection can't break interfaces.IEventStorageReader.
- Position
- Below the diagonal: workers.WorkerProxyProjection uses a module listed above it, which is the healthy direction.
26→16 workers.WorkerProxyProjection uses interfaces.IEventStore✕
- Connections
- 1 pair of types, where a type in workers.WorkerProxyProjection uses a type in interfaces.IEventStore.
- The types involved
src.workers.WorkerProxyProjection.WorkerProxyProjection→src.interfaces.IEventStore.IEventStore
- Direction
- workers.WorkerProxyProjection uses interfaces.IEventStore, so a change to interfaces.IEventStore can break workers.WorkerProxyProjection, while a change to workers.WorkerProxyProjection can't break interfaces.IEventStore.
- Position
- Below the diagonal: workers.WorkerProxyProjection uses a module listed above it, which is the healthy direction.
27→1 AbstractAggregate uses interfaces✕
- Connections
- 1 pair of types, where a type in AbstractAggregate uses a type in interfaces.
- The types involved
src.AbstractAggregate.AbstractAggregate→src.interfaces.IEvent
- Direction
- AbstractAggregate uses interfaces, so a change to interfaces can break AbstractAggregate, while a change to AbstractAggregate can't break interfaces.
- Position
- Below the diagonal: AbstractAggregate uses a module listed above it, which is the healthy direction.
27→3 AbstractAggregate uses interfaces.IEventSet✕
- Connections
- 1 pair of types, where a type in AbstractAggregate uses a type in interfaces.IEventSet.
- The types involved
src.AbstractAggregate.AbstractAggregate→src.interfaces.IEventSet.IEventSet
- Direction
- AbstractAggregate uses interfaces.IEventSet, so a change to interfaces.IEventSet can break AbstractAggregate, while a change to AbstractAggregate can't break interfaces.IEventSet.
- Position
- Below the diagonal: AbstractAggregate uses a module listed above it, which is the healthy direction.
27→10 AbstractAggregate uses interfaces.Identifier✕
- Connections
- 1 pair of types, where a type in AbstractAggregate uses a type in interfaces.Identifier.
- The types involved
src.AbstractAggregate.AbstractAggregate→src.interfaces.Identifier.Identifier
- Direction
- AbstractAggregate uses interfaces.Identifier, so a change to interfaces.Identifier can break AbstractAggregate, while a change to AbstractAggregate can't break interfaces.Identifier.
- Position
- Below the diagonal: AbstractAggregate uses a module listed above it, which is the healthy direction.
27→12 AbstractAggregate uses interfaces.ICommandBus✕
- Connections
- 1 pair of types, where a type in AbstractAggregate uses a type in interfaces.ICommandBus.
- The types involved
src.AbstractAggregate.AbstractAggregate→src.interfaces.ICommandBus.ICommandBus
- Direction
- AbstractAggregate uses interfaces.ICommandBus, so a change to interfaces.ICommandBus can break AbstractAggregate, while a change to AbstractAggregate can't break interfaces.ICommandBus.
- Position
- Below the diagonal: AbstractAggregate uses a module listed above it, which is the healthy direction.
27→16 AbstractAggregate uses interfaces.IEventStore✕
- Connections
- 1 pair of types, where a type in AbstractAggregate uses a type in interfaces.IEventStore.
- The types involved
src.AbstractAggregate.AbstractAggregate→src.interfaces.IEventStore.IEventStore
- Direction
- AbstractAggregate uses interfaces.IEventStore, so a change to interfaces.IEventStore can break AbstractAggregate, while a change to AbstractAggregate can't break interfaces.IEventStore.
- Position
- Below the diagonal: AbstractAggregate uses a module listed above it, which is the healthy direction.
27→19 AbstractAggregate uses AggregateCommandHandler✕
- Connections
- 1 pair of types, where a type in AbstractAggregate uses a type in AggregateCommandHandler.
- The types involved
src.AbstractAggregate.AbstractAggregate→src.AggregateCommandHandler.AggregateCommandHandler
- Direction
- AbstractAggregate uses AggregateCommandHandler, so a change to AggregateCommandHandler can break AbstractAggregate, while a change to AbstractAggregate can't break AggregateCommandHandler.
- Position
- Below the diagonal: AbstractAggregate uses a module listed above it, which is the healthy direction.
28→1 AbstractProjection uses interfaces✕
- Connections
- 1 pair of types, where a type in AbstractProjection uses a type in interfaces.
- The types involved
src.AbstractProjection.AbstractProjection→src.interfaces.IEvent
- Direction
- AbstractProjection uses interfaces, so a change to interfaces can break AbstractProjection, while a change to AbstractProjection can't break interfaces.
- Position
- Below the diagonal: AbstractProjection uses a module listed above it, which is the healthy direction.
28→6 AbstractProjection uses interfaces.ILogger✕
- Connections
- 1 pair of types, where a type in AbstractProjection uses a type in interfaces.ILogger.
- The types involved
src.AbstractProjection.AbstractProjection→src.interfaces.ILogger.ILogger
- Direction
- AbstractProjection uses interfaces.ILogger, so a change to interfaces.ILogger can break AbstractProjection, while a change to AbstractProjection can't break interfaces.ILogger.
- Position
- Below the diagonal: AbstractProjection uses a module listed above it, which is the healthy direction.
28→8 AbstractProjection uses interfaces.IObservable✕
- Connections
- 1 pair of types, where a type in AbstractProjection uses a type in interfaces.IObservable.
- The types involved
src.AbstractProjection.AbstractProjection→src.interfaces.IObservable.IObservable
- Direction
- AbstractProjection uses interfaces.IObservable, so a change to interfaces.IObservable can break AbstractProjection, while a change to AbstractProjection can't break interfaces.IObservable.
- Position
- Below the diagonal: AbstractProjection uses a module listed above it, which is the healthy direction.
28→15 AbstractProjection uses interfaces.IEventStorageReader✕
- Connections
- 1 pair of types, where a type in AbstractProjection uses a type in interfaces.IEventStorageReader.
- The types involved
src.AbstractProjection.AbstractProjection→src.interfaces.IEventStorageReader.IEventStorageReader
- Direction
- AbstractProjection uses interfaces.IEventStorageReader, so a change to interfaces.IEventStorageReader can break AbstractProjection, while a change to AbstractProjection can't break interfaces.IEventStorageReader.
- Position
- Below the diagonal: AbstractProjection uses a module listed above it, which is the healthy direction.
28→23 AbstractProjection uses interfaces.IProjection✕
- Connections
- 1 pair of types, where a type in AbstractProjection uses a type in interfaces.IProjection.
- The types involved
src.AbstractProjection.AbstractProjection→src.interfaces.IProjection.IProjection
- Direction
- AbstractProjection uses interfaces.IProjection, so a change to interfaces.IProjection can break AbstractProjection, while a change to AbstractProjection can't break interfaces.IProjection.
- Position
- Below the diagonal: AbstractProjection uses a module listed above it, which is the healthy direction.
29→1 AbstractSaga uses interfaces✕
- Connections
- 1 pair of types, where a type in AbstractSaga uses a type in interfaces.
- The types involved
src.AbstractSaga.AbstractSaga→src.interfaces.IEvent
- Direction
- AbstractSaga uses interfaces, so a change to interfaces can break AbstractSaga, while a change to AbstractSaga can't break interfaces.
- Position
- Below the diagonal: AbstractSaga uses a module listed above it, which is the healthy direction.
29→10 AbstractSaga uses interfaces.Identifier✕
- Connections
- 1 pair of types, where a type in AbstractSaga uses a type in interfaces.Identifier.
- The types involved
src.AbstractSaga.AbstractSaga→src.interfaces.Identifier.Identifier
- Direction
- AbstractSaga uses interfaces.Identifier, so a change to interfaces.Identifier can break AbstractSaga, while a change to AbstractSaga can't break interfaces.Identifier.
- Position
- Below the diagonal: AbstractSaga uses a module listed above it, which is the healthy direction.
29→12 AbstractSaga uses interfaces.ICommandBus✕
- Connections
- 1 pair of types, where a type in AbstractSaga uses a type in interfaces.ICommandBus.
- The types involved
src.AbstractSaga.AbstractSaga→src.interfaces.ICommandBus.ICommandBus
- Direction
- AbstractSaga uses interfaces.ICommandBus, so a change to interfaces.ICommandBus can break AbstractSaga, while a change to AbstractSaga can't break interfaces.ICommandBus.
- Position
- Below the diagonal: AbstractSaga uses a module listed above it, which is the healthy direction.
29→16 AbstractSaga uses interfaces.IEventStore✕
- Connections
- 1 pair of types, where a type in AbstractSaga uses a type in interfaces.IEventStore.
- The types involved
src.AbstractSaga.AbstractSaga→src.interfaces.IEventStore.IEventStore
- Direction
- AbstractSaga uses interfaces.IEventStore, so a change to interfaces.IEventStore can break AbstractSaga, while a change to AbstractSaga can't break interfaces.IEventStore.
- Position
- Below the diagonal: AbstractSaga uses a module listed above it, which is the healthy direction.
29→20 AbstractSaga uses SagaEventHandler✕
- Connections
- 1 pair of types, where a type in AbstractSaga uses a type in SagaEventHandler.
- The types involved
src.AbstractSaga.AbstractSaga→src.SagaEventHandler.SagaEventHandler
- Direction
- AbstractSaga uses SagaEventHandler, so a change to SagaEventHandler can break AbstractSaga, while a change to AbstractSaga can't break SagaEventHandler.
- Position
- Below the diagonal: AbstractSaga uses a module listed above it, which is the healthy direction.
30→12 CqrsContainerBuilder uses interfaces.ICommandBus✕
- Connections
- 1 pair of types, where a type in CqrsContainerBuilder uses a type in interfaces.ICommandBus.
- The types involved
src.CqrsContainerBuilder.CqrsContainerBuilder→src.interfaces.ICommandBus.ICommandHandler
- Direction
- CqrsContainerBuilder uses interfaces.ICommandBus, so a change to interfaces.ICommandBus can break CqrsContainerBuilder, while a change to CqrsContainerBuilder can't break interfaces.ICommandBus.
- Position
- Below the diagonal: CqrsContainerBuilder uses a module listed above it, which is the healthy direction.
30→23 CqrsContainerBuilder uses interfaces.IProjection✕
- Connections
- 1 pair of types, where a type in CqrsContainerBuilder uses a type in interfaces.IProjection.
- The types involved
src.CqrsContainerBuilder.CqrsContainerBuilder→src.interfaces.IProjection.IProjection
- Direction
- CqrsContainerBuilder uses interfaces.IProjection, so a change to interfaces.IProjection can break CqrsContainerBuilder, while a change to CqrsContainerBuilder can't break interfaces.IProjection.
- Position
- Below the diagonal: CqrsContainerBuilder uses a module listed above it, which is the healthy direction.
31→2 interfaces.IContainer uses interfaces.IDispatchPipelineProcessor✕
- Connections
- 1 pair of types, where a type in interfaces.IContainer uses a type in interfaces.IDispatchPipelineProcessor.
- The types involved
src.interfaces.IContainer.IContainer→src.interfaces.IDispatchPipelineProcessor.IDispatchPipelineProcessor
- Direction
- interfaces.IContainer uses interfaces.IDispatchPipelineProcessor, so a change to interfaces.IDispatchPipelineProcessor can break interfaces.IContainer, while a change to interfaces.IContainer can't break interfaces.IDispatchPipelineProcessor.
- Position
- Below the diagonal: interfaces.IContainer uses a module listed above it, which is the healthy direction.
31→5 interfaces.IContainer uses interfaces.IIdentifierProvider✕
- Connections
- 1 pair of types, where a type in interfaces.IContainer uses a type in interfaces.IIdentifierProvider.
- The types involved
src.interfaces.IContainer.IContainer→src.interfaces.IIdentifierProvider.IIdentifierProvider
- Direction
- interfaces.IContainer uses interfaces.IIdentifierProvider, so a change to interfaces.IIdentifierProvider can break interfaces.IContainer, while a change to interfaces.IContainer can't break interfaces.IIdentifierProvider.
- Position
- Below the diagonal: interfaces.IContainer uses a module listed above it, which is the healthy direction.
31→12 interfaces.IContainer uses interfaces.ICommandBus✕
- Connections
- 1 pair of types, where a type in interfaces.IContainer uses a type in interfaces.ICommandBus.
- The types involved
src.interfaces.IContainer.IContainer→src.interfaces.ICommandBus.ICommandBus
- Direction
- interfaces.IContainer uses interfaces.ICommandBus, so a change to interfaces.ICommandBus can break interfaces.IContainer, while a change to interfaces.IContainer can't break interfaces.ICommandBus.
- Position
- Below the diagonal: interfaces.IContainer uses a module listed above it, which is the healthy direction.
31→13 interfaces.IContainer uses interfaces.IEventBus✕
- Connections
- 1 pair of types, where a type in interfaces.IContainer uses a type in interfaces.IEventBus.
- The types involved
src.interfaces.IContainer.IContainer→src.interfaces.IEventBus.IEventBus
- Direction
- interfaces.IContainer uses interfaces.IEventBus, so a change to interfaces.IEventBus can break interfaces.IContainer, while a change to interfaces.IContainer can't break interfaces.IEventBus.
- Position
- Below the diagonal: interfaces.IContainer uses a module listed above it, which is the healthy direction.
31→15 interfaces.IContainer uses interfaces.IEventStorageReader✕
- Connections
- 1 pair of types, where a type in interfaces.IContainer uses a type in interfaces.IEventStorageReader.
- The types involved
src.interfaces.IContainer.IContainer→src.interfaces.IEventStorageReader.IEventStorageReader
- Direction
- interfaces.IContainer uses interfaces.IEventStorageReader, so a change to interfaces.IEventStorageReader can break interfaces.IContainer, while a change to interfaces.IContainer can't break interfaces.IEventStorageReader.
- Position
- Below the diagonal: interfaces.IContainer uses a module listed above it, which is the healthy direction.
31→16 interfaces.IContainer uses interfaces.IEventStore✕
- Connections
- 1 pair of types, where a type in interfaces.IContainer uses a type in interfaces.IEventStore.
- The types involved
src.interfaces.IContainer.IContainer→src.interfaces.IEventStore.IEventStore
- Direction
- interfaces.IContainer uses interfaces.IEventStore, so a change to interfaces.IEventStore can break interfaces.IContainer, while a change to interfaces.IContainer can't break interfaces.IEventStore.
- Position
- Below the diagonal: interfaces.IContainer uses a module listed above it, which is the healthy direction.
31→22 interfaces.IContainer uses interfaces.IEventDispatcher✕
- Connections
- 1 pair of types, where a type in interfaces.IContainer uses a type in interfaces.IEventDispatcher.
- The types involved
src.interfaces.IContainer.IContainer→src.interfaces.IEventDispatcher.IEventDispatcher
- Direction
- interfaces.IContainer uses interfaces.IEventDispatcher, so a change to interfaces.IEventDispatcher can break interfaces.IContainer, while a change to interfaces.IContainer can't break interfaces.IEventDispatcher.
- Position
- Below the diagonal: interfaces.IContainer uses a module listed above it, which is the healthy direction.
32→1 EventStore uses interfaces✕
- Connections
- 1 pair of types, where a type in EventStore uses a type in interfaces.
- The types involved
src.EventStore.EventStore→src.interfaces.IEvent
- Direction
- EventStore uses interfaces, so a change to interfaces can break EventStore, while a change to EventStore can't break interfaces.
- Position
- Below the diagonal: EventStore uses a module listed above it, which is the healthy direction.
32→3 EventStore uses interfaces.IEventSet✕
- Connections
- 1 pair of types, where a type in EventStore uses a type in interfaces.IEventSet.
- The types involved
src.EventStore.EventStore→src.interfaces.IEventSet.IEventSet
- Direction
- EventStore uses interfaces.IEventSet, so a change to interfaces.IEventSet can break EventStore, while a change to EventStore can't break interfaces.IEventSet.
- Position
- Below the diagonal: EventStore uses a module listed above it, which is the healthy direction.
32→4 EventStore uses interfaces.IEventStream✕
- Connections
- 1 pair of types, where a type in EventStore uses a type in interfaces.IEventStream.
- The types involved
src.EventStore.EventStore→src.interfaces.IEventStream.IEventStream
- Direction
- EventStore uses interfaces.IEventStream, so a change to interfaces.IEventStream can break EventStore, while a change to EventStore can't break interfaces.IEventStream.
- Position
- Below the diagonal: EventStore uses a module listed above it, which is the healthy direction.
32→5 EventStore uses interfaces.IIdentifierProvider✕
- Connections
- 1 pair of types, where a type in EventStore uses a type in interfaces.IIdentifierProvider.
- The types involved
src.EventStore.EventStore→src.interfaces.IIdentifierProvider.IIdentifierProvider
- Direction
- EventStore uses interfaces.IIdentifierProvider, so a change to interfaces.IIdentifierProvider can break EventStore, while a change to EventStore can't break interfaces.IIdentifierProvider.
- Position
- Below the diagonal: EventStore uses a module listed above it, which is the healthy direction.
32→6 EventStore uses interfaces.ILogger✕
- Connections
- 1 pair of types, where a type in EventStore uses a type in interfaces.ILogger.
- The types involved
src.EventStore.EventStore→src.interfaces.ILogger.ILogger
- Direction
- EventStore uses interfaces.ILogger, so a change to interfaces.ILogger can break EventStore, while a change to EventStore can't break interfaces.ILogger.
- Position
- Below the diagonal: EventStore uses a module listed above it, which is the healthy direction.
32→8 EventStore uses interfaces.IObservable✕
- Connections
- 2 pairs of types, where a type in EventStore uses a type in interfaces.IObservable.
- The types involved
src.EventStore.EventStore→src.interfaces.IObservable.IMessageHandlersrc.EventStore.EventStore→src.interfaces.IObservable.IObservable
- Direction
- EventStore uses interfaces.IObservable, so a change to interfaces.IObservable can break EventStore, while a change to EventStore can't break interfaces.IObservable.
- Position
- Below the diagonal: EventStore uses a module listed above it, which is the healthy direction.
32→10 EventStore uses interfaces.Identifier✕
- Connections
- 1 pair of types, where a type in EventStore uses a type in interfaces.Identifier.
- The types involved
src.EventStore.EventStore→src.interfaces.Identifier.Identifier
- Direction
- EventStore uses interfaces.Identifier, so a change to interfaces.Identifier can break EventStore, while a change to EventStore can't break interfaces.Identifier.
- Position
- Below the diagonal: EventStore uses a module listed above it, which is the healthy direction.
32→13 EventStore uses interfaces.IEventBus✕
- Connections
- 1 pair of types, where a type in EventStore uses a type in interfaces.IEventBus.
- The types involved
src.EventStore.EventStore→src.interfaces.IEventBus.IEventBus
- Direction
- EventStore uses interfaces.IEventBus, so a change to interfaces.IEventBus can break EventStore, while a change to EventStore can't break interfaces.IEventBus.
- Position
- Below the diagonal: EventStore uses a module listed above it, which is the healthy direction.
32→15 EventStore uses interfaces.IEventStorageReader✕
- Connections
- 1 pair of types, where a type in EventStore uses a type in interfaces.IEventStorageReader.
- The types involved
src.EventStore.EventStore→src.interfaces.IEventStorageReader.IEventStorageReader
- Direction
- EventStore uses interfaces.IEventStorageReader, so a change to interfaces.IEventStorageReader can break EventStore, while a change to EventStore can't break interfaces.IEventStorageReader.
- Position
- Below the diagonal: EventStore uses a module listed above it, which is the healthy direction.
32→16 EventStore uses interfaces.IEventStore✕
- Connections
- 1 pair of types, where a type in EventStore uses a type in interfaces.IEventStore.
- The types involved
src.EventStore.EventStore→src.interfaces.IEventStore.IEventStore
- Direction
- EventStore uses interfaces.IEventStore, so a change to interfaces.IEventStore can break EventStore, while a change to EventStore can't break interfaces.IEventStore.
- Position
- Below the diagonal: EventStore uses a module listed above it, which is the healthy direction.
32→22 EventStore uses interfaces.IEventDispatcher✕
- Connections
- 1 pair of types, where a type in EventStore uses a type in interfaces.IEventDispatcher.
- The types involved
src.EventStore.EventStore→src.interfaces.IEventDispatcher.IEventDispatcher
- Direction
- EventStore uses interfaces.IEventDispatcher, so a change to interfaces.IEventDispatcher can break EventStore, while a change to EventStore can't break interfaces.IEventDispatcher.
- Position
- Below the diagonal: EventStore uses a module listed above it, which is the healthy direction.
32→31 EventStore uses interfaces.IContainer✕
- Connections
- 1 pair of types, where a type in EventStore uses a type in interfaces.IContainer.
- The types involved
src.EventStore.EventStore→src.interfaces.IContainer.IContainer
- Direction
- EventStore uses interfaces.IContainer, so a change to interfaces.IContainer can break EventStore, while a change to EventStore can't break interfaces.IContainer.
- Position
- Below the diagonal: EventStore uses a module listed above it, which is the healthy direction.
33→2 in-memory.InMemoryEventStorage uses interfaces.IDispatchPipelineProcessor✕
- Connections
- 1 pair of types, where a type in in-memory.InMemoryEventStorage uses a type in interfaces.IDispatchPipelineProcessor.
- The types involved
src.in-memory.InMemoryEventStorage.InMemoryEventStorage→src.interfaces.IDispatchPipelineProcessor.IDispatchPipelineProcessor
- Direction
- in-memory.InMemoryEventStorage uses interfaces.IDispatchPipelineProcessor, so a change to interfaces.IDispatchPipelineProcessor can break in-memory.InMemoryEventStorage, while a change to in-memory.InMemoryEventStorage can't break interfaces.IDispatchPipelineProcessor.
- Position
- Below the diagonal: in-memory.InMemoryEventStorage uses a module listed above it, which is the healthy direction.
33→3 in-memory.InMemoryEventStorage uses interfaces.IEventSet✕
- Connections
- 1 pair of types, where a type in in-memory.InMemoryEventStorage uses a type in interfaces.IEventSet.
- The types involved
src.in-memory.InMemoryEventStorage.InMemoryEventStorage→src.interfaces.IEventSet.IEventSet
- Direction
- in-memory.InMemoryEventStorage uses interfaces.IEventSet, so a change to interfaces.IEventSet can break in-memory.InMemoryEventStorage, while a change to in-memory.InMemoryEventStorage can't break interfaces.IEventSet.
- Position
- Below the diagonal: in-memory.InMemoryEventStorage uses a module listed above it, which is the healthy direction.
33→4 in-memory.InMemoryEventStorage uses interfaces.IEventStream✕
- Connections
- 1 pair of types, where a type in in-memory.InMemoryEventStorage uses a type in interfaces.IEventStream.
- The types involved
src.in-memory.InMemoryEventStorage.InMemoryEventStorage→src.interfaces.IEventStream.IEventStream
- Direction
- in-memory.InMemoryEventStorage uses interfaces.IEventStream, so a change to interfaces.IEventStream can break in-memory.InMemoryEventStorage, while a change to in-memory.InMemoryEventStorage can't break interfaces.IEventStream.
- Position
- Below the diagonal: in-memory.InMemoryEventStorage uses a module listed above it, which is the healthy direction.
33→5 in-memory.InMemoryEventStorage uses interfaces.IIdentifierProvider✕
- Connections
- 1 pair of types, where a type in in-memory.InMemoryEventStorage uses a type in interfaces.IIdentifierProvider.
- The types involved
src.in-memory.InMemoryEventStorage.InMemoryEventStorage→src.interfaces.IIdentifierProvider.IIdentifierProvider
- Direction
- in-memory.InMemoryEventStorage uses interfaces.IIdentifierProvider, so a change to interfaces.IIdentifierProvider can break in-memory.InMemoryEventStorage, while a change to in-memory.InMemoryEventStorage can't break interfaces.IIdentifierProvider.
- Position
- Below the diagonal: in-memory.InMemoryEventStorage uses a module listed above it, which is the healthy direction.
33→10 in-memory.InMemoryEventStorage uses interfaces.Identifier✕
- Connections
- 1 pair of types, where a type in in-memory.InMemoryEventStorage uses a type in interfaces.Identifier.
- The types involved
src.in-memory.InMemoryEventStorage.InMemoryEventStorage→src.interfaces.Identifier.Identifier
- Direction
- in-memory.InMemoryEventStorage uses interfaces.Identifier, so a change to interfaces.Identifier can break in-memory.InMemoryEventStorage, while a change to in-memory.InMemoryEventStorage can't break interfaces.Identifier.
- Position
- Below the diagonal: in-memory.InMemoryEventStorage uses a module listed above it, which is the healthy direction.
33→15 in-memory.InMemoryEventStorage uses interfaces.IEventStorageReader✕
- Connections
- 1 pair of types, where a type in in-memory.InMemoryEventStorage uses a type in interfaces.IEventStorageReader.
- The types involved
src.in-memory.InMemoryEventStorage.InMemoryEventStorage→src.interfaces.IEventStorageReader.IEventStorageReader
- Direction
- in-memory.InMemoryEventStorage uses interfaces.IEventStorageReader, so a change to interfaces.IEventStorageReader can break in-memory.InMemoryEventStorage, while a change to in-memory.InMemoryEventStorage can't break interfaces.IEventStorageReader.
- Position
- Below the diagonal: in-memory.InMemoryEventStorage uses a module listed above it, which is the healthy direction.
33→31 in-memory.InMemoryEventStorage uses interfaces.IContainer✕
- Connections
- 1 pair of types, where a type in in-memory.InMemoryEventStorage uses a type in interfaces.IContainer.
- The types involved
src.in-memory.InMemoryEventStorage.InMemoryEventStorage→src.interfaces.IContainer.IContainer
- Direction
- in-memory.InMemoryEventStorage uses interfaces.IContainer, so a change to interfaces.IContainer can break in-memory.InMemoryEventStorage, while a change to in-memory.InMemoryEventStorage can't break interfaces.IContainer.
- Position
- Below the diagonal: in-memory.InMemoryEventStorage uses a module listed above it, which is the healthy direction.
34→2 in-memory.InMemorySnapshotStorage uses interfaces.IDispatchPipelineProcessor✕
- Connections
- 1 pair of types, where a type in in-memory.InMemorySnapshotStorage uses a type in interfaces.IDispatchPipelineProcessor.
- The types involved
src.in-memory.InMemorySnapshotStorage.InMemorySnapshotStorage→src.interfaces.IDispatchPipelineProcessor.IDispatchPipelineProcessor
- Direction
- in-memory.InMemorySnapshotStorage uses interfaces.IDispatchPipelineProcessor, so a change to interfaces.IDispatchPipelineProcessor can break in-memory.InMemorySnapshotStorage, while a change to in-memory.InMemorySnapshotStorage can't break interfaces.IDispatchPipelineProcessor.
- Position
- Below the diagonal: in-memory.InMemorySnapshotStorage uses a module listed above it, which is the healthy direction.
34→10 in-memory.InMemorySnapshotStorage uses interfaces.Identifier✕
- Connections
- 1 pair of types, where a type in in-memory.InMemorySnapshotStorage uses a type in interfaces.Identifier.
- The types involved
src.in-memory.InMemorySnapshotStorage.InMemorySnapshotStorage→src.interfaces.Identifier.Identifier
- Direction
- in-memory.InMemorySnapshotStorage uses interfaces.Identifier, so a change to interfaces.Identifier can break in-memory.InMemorySnapshotStorage, while a change to in-memory.InMemorySnapshotStorage can't break interfaces.Identifier.
- Position
- Below the diagonal: in-memory.InMemorySnapshotStorage uses a module listed above it, which is the healthy direction.
34→31 in-memory.InMemorySnapshotStorage uses interfaces.IContainer✕
- Connections
- 1 pair of types, where a type in in-memory.InMemorySnapshotStorage uses a type in interfaces.IContainer.
- The types involved
src.in-memory.InMemorySnapshotStorage.InMemorySnapshotStorage→src.interfaces.IContainer.IContainer
- Direction
- in-memory.InMemorySnapshotStorage uses interfaces.IContainer, so a change to interfaces.IContainer can break in-memory.InMemorySnapshotStorage, while a change to in-memory.InMemorySnapshotStorage can't break interfaces.IContainer.
- Position
- Below the diagonal: in-memory.InMemorySnapshotStorage uses a module listed above it, which is the healthy direction.
35→2 mongodb.MongoEventStorage uses interfaces.IDispatchPipelineProcessor✕
- Connections
- 1 pair of types, where a type in mongodb.MongoEventStorage uses a type in interfaces.IDispatchPipelineProcessor.
- The types involved
src.mongodb.MongoEventStorage.MongoEventStorage→src.interfaces.IDispatchPipelineProcessor.IDispatchPipelineProcessor
- Direction
- mongodb.MongoEventStorage uses interfaces.IDispatchPipelineProcessor, so a change to interfaces.IDispatchPipelineProcessor can break mongodb.MongoEventStorage, while a change to mongodb.MongoEventStorage can't break interfaces.IDispatchPipelineProcessor.
- Position
- Below the diagonal: mongodb.MongoEventStorage uses a module listed above it, which is the healthy direction.
35→3 mongodb.MongoEventStorage uses interfaces.IEventSet✕
- Connections
- 1 pair of types, where a type in mongodb.MongoEventStorage uses a type in interfaces.IEventSet.
- The types involved
src.mongodb.MongoEventStorage.MongoEventStorage→src.interfaces.IEventSet.IEventSet
- Direction
- mongodb.MongoEventStorage uses interfaces.IEventSet, so a change to interfaces.IEventSet can break mongodb.MongoEventStorage, while a change to mongodb.MongoEventStorage can't break interfaces.IEventSet.
- Position
- Below the diagonal: mongodb.MongoEventStorage uses a module listed above it, which is the healthy direction.
35→4 mongodb.MongoEventStorage uses interfaces.IEventStream✕
- Connections
- 1 pair of types, where a type in mongodb.MongoEventStorage uses a type in interfaces.IEventStream.
- The types involved
src.mongodb.MongoEventStorage.MongoEventStorage→src.interfaces.IEventStream.IEventStream
- Direction
- mongodb.MongoEventStorage uses interfaces.IEventStream, so a change to interfaces.IEventStream can break mongodb.MongoEventStorage, while a change to mongodb.MongoEventStorage can't break interfaces.IEventStream.
- Position
- Below the diagonal: mongodb.MongoEventStorage uses a module listed above it, which is the healthy direction.
35→5 mongodb.MongoEventStorage uses interfaces.IIdentifierProvider✕
- Connections
- 1 pair of types, where a type in mongodb.MongoEventStorage uses a type in interfaces.IIdentifierProvider.
- The types involved
src.mongodb.MongoEventStorage.MongoEventStorage→src.interfaces.IIdentifierProvider.IIdentifierProvider
- Direction
- mongodb.MongoEventStorage uses interfaces.IIdentifierProvider, so a change to interfaces.IIdentifierProvider can break mongodb.MongoEventStorage, while a change to mongodb.MongoEventStorage can't break interfaces.IIdentifierProvider.
- Position
- Below the diagonal: mongodb.MongoEventStorage uses a module listed above it, which is the healthy direction.
35→10 mongodb.MongoEventStorage uses interfaces.Identifier✕
- Connections
- 1 pair of types, where a type in mongodb.MongoEventStorage uses a type in interfaces.Identifier.
- The types involved
src.mongodb.MongoEventStorage.MongoEventStorage→src.interfaces.Identifier.Identifier
- Direction
- mongodb.MongoEventStorage uses interfaces.Identifier, so a change to interfaces.Identifier can break mongodb.MongoEventStorage, while a change to mongodb.MongoEventStorage can't break interfaces.Identifier.
- Position
- Below the diagonal: mongodb.MongoEventStorage uses a module listed above it, which is the healthy direction.
35→15 mongodb.MongoEventStorage uses interfaces.IEventStorageReader✕
- Connections
- 1 pair of types, where a type in mongodb.MongoEventStorage uses a type in interfaces.IEventStorageReader.
- The types involved
src.mongodb.MongoEventStorage.MongoEventStorage→src.interfaces.IEventStorageReader.IEventStorageReader
- Direction
- mongodb.MongoEventStorage uses interfaces.IEventStorageReader, so a change to interfaces.IEventStorageReader can break mongodb.MongoEventStorage, while a change to mongodb.MongoEventStorage can't break interfaces.IEventStorageReader.
- Position
- Below the diagonal: mongodb.MongoEventStorage uses a module listed above it, which is the healthy direction.
35→31 mongodb.MongoEventStorage uses interfaces.IContainer✕
- Connections
- 1 pair of types, where a type in mongodb.MongoEventStorage uses a type in interfaces.IContainer.
- The types involved
src.mongodb.MongoEventStorage.MongoEventStorage→src.interfaces.IContainer.IContainer
- Direction
- mongodb.MongoEventStorage uses interfaces.IContainer, so a change to interfaces.IContainer can break mongodb.MongoEventStorage, while a change to mongodb.MongoEventStorage can't break interfaces.IContainer.
- Position
- Below the diagonal: mongodb.MongoEventStorage uses a module listed above it, which is the healthy direction.
36→7 rabbitmq.RabbitMqCommandBus uses interfaces.IMessageMeta✕
- Connections
- 1 pair of types, where a type in rabbitmq.RabbitMqCommandBus uses a type in interfaces.IMessageMeta.
- The types involved
src.rabbitmq.RabbitMqCommandBus.RabbitMqCommandBus→src.interfaces.IMessageMeta.IMessageMeta
- Direction
- rabbitmq.RabbitMqCommandBus uses interfaces.IMessageMeta, so a change to interfaces.IMessageMeta can break rabbitmq.RabbitMqCommandBus, while a change to rabbitmq.RabbitMqCommandBus can't break interfaces.IMessageMeta.
- Position
- Below the diagonal: rabbitmq.RabbitMqCommandBus uses a module listed above it, which is the healthy direction.
36→8 rabbitmq.RabbitMqCommandBus uses interfaces.IObservable✕
- Connections
- 1 pair of types, where a type in rabbitmq.RabbitMqCommandBus uses a type in interfaces.IObservable.
- The types involved
src.rabbitmq.RabbitMqCommandBus.RabbitMqCommandBus→src.interfaces.IObservable.IMessageHandler
- Direction
- rabbitmq.RabbitMqCommandBus uses interfaces.IObservable, so a change to interfaces.IObservable can break rabbitmq.RabbitMqCommandBus, while a change to rabbitmq.RabbitMqCommandBus can't break interfaces.IObservable.
- Position
- Below the diagonal: rabbitmq.RabbitMqCommandBus uses a module listed above it, which is the healthy direction.
36→11 rabbitmq.RabbitMqCommandBus uses rabbitmq.utils.resolveProvider✕
- Connections
- 1 pair of types, where a type in rabbitmq.RabbitMqCommandBus uses a type in rabbitmq.utils.resolveProvider.
- The types involved
src.rabbitmq.RabbitMqCommandBus.RabbitMqCommandBus→src.rabbitmq.utils.resolveProvider.ConfigProvider
- Direction
- rabbitmq.RabbitMqCommandBus uses rabbitmq.utils.resolveProvider, so a change to rabbitmq.utils.resolveProvider can break rabbitmq.RabbitMqCommandBus, while a change to rabbitmq.RabbitMqCommandBus can't break rabbitmq.utils.resolveProvider.
- Position
- Below the diagonal: rabbitmq.RabbitMqCommandBus uses a module listed above it, which is the healthy direction.
36→12 rabbitmq.RabbitMqCommandBus uses interfaces.ICommandBus✕
- Connections
- 1 pair of types, where a type in rabbitmq.RabbitMqCommandBus uses a type in interfaces.ICommandBus.
- The types involved
src.rabbitmq.RabbitMqCommandBus.RabbitMqCommandBus→src.interfaces.ICommandBus.ICommandBus
- Direction
- rabbitmq.RabbitMqCommandBus uses interfaces.ICommandBus, so a change to interfaces.ICommandBus can break rabbitmq.RabbitMqCommandBus, while a change to rabbitmq.RabbitMqCommandBus can't break interfaces.ICommandBus.
- Position
- Below the diagonal: rabbitmq.RabbitMqCommandBus uses a module listed above it, which is the healthy direction.
36→18 rabbitmq.RabbitMqCommandBus uses rabbitmq.RabbitMqGateway✕
- Connections
- 1 pair of types, where a type in rabbitmq.RabbitMqCommandBus uses a type in rabbitmq.RabbitMqGateway.
- The types involved
src.rabbitmq.RabbitMqCommandBus.RabbitMqCommandBus→src.rabbitmq.RabbitMqGateway.RabbitMqGateway
- Direction
- rabbitmq.RabbitMqCommandBus uses rabbitmq.RabbitMqGateway, so a change to rabbitmq.RabbitMqGateway can break rabbitmq.RabbitMqCommandBus, while a change to rabbitmq.RabbitMqCommandBus can't break rabbitmq.RabbitMqGateway.
- Position
- Below the diagonal: rabbitmq.RabbitMqCommandBus uses a module listed above it, which is the healthy direction.
36→31 rabbitmq.RabbitMqCommandBus uses interfaces.IContainer✕
- Connections
- 1 pair of types, where a type in rabbitmq.RabbitMqCommandBus uses a type in interfaces.IContainer.
- The types involved
src.rabbitmq.RabbitMqCommandBus.RabbitMqCommandBus→src.interfaces.IContainer.IContainer
- Direction
- rabbitmq.RabbitMqCommandBus uses interfaces.IContainer, so a change to interfaces.IContainer can break rabbitmq.RabbitMqCommandBus, while a change to rabbitmq.RabbitMqCommandBus can't break interfaces.IContainer.
- Position
- Below the diagonal: rabbitmq.RabbitMqCommandBus uses a module listed above it, which is the healthy direction.
37→7 rabbitmq.RabbitMqEventBus uses interfaces.IMessageMeta✕
- Connections
- 1 pair of types, where a type in rabbitmq.RabbitMqEventBus uses a type in interfaces.IMessageMeta.
- The types involved
src.rabbitmq.RabbitMqEventBus.RabbitMqEventBus→src.interfaces.IMessageMeta.IMessageMeta
- Direction
- rabbitmq.RabbitMqEventBus uses interfaces.IMessageMeta, so a change to interfaces.IMessageMeta can break rabbitmq.RabbitMqEventBus, while a change to rabbitmq.RabbitMqEventBus can't break interfaces.IMessageMeta.
- Position
- Below the diagonal: rabbitmq.RabbitMqEventBus uses a module listed above it, which is the healthy direction.
37→8 rabbitmq.RabbitMqEventBus uses interfaces.IObservable✕
- Connections
- 2 pairs of types, where a type in rabbitmq.RabbitMqEventBus uses a type in interfaces.IObservable.
- The types involved
src.rabbitmq.RabbitMqEventBus.RabbitMqEventBus→src.interfaces.IObservable.IMessageHandlersrc.rabbitmq.RabbitMqEventBus.RabbitMqEventBus→src.interfaces.IObservable.IObservable
- Direction
- rabbitmq.RabbitMqEventBus uses interfaces.IObservable, so a change to interfaces.IObservable can break rabbitmq.RabbitMqEventBus, while a change to rabbitmq.RabbitMqEventBus can't break interfaces.IObservable.
- Position
- Below the diagonal: rabbitmq.RabbitMqEventBus uses a module listed above it, which is the healthy direction.
37→11 rabbitmq.RabbitMqEventBus uses rabbitmq.utils.resolveProvider✕
- Connections
- 1 pair of types, where a type in rabbitmq.RabbitMqEventBus uses a type in rabbitmq.utils.resolveProvider.
- The types involved
src.rabbitmq.RabbitMqEventBus.RabbitMqEventBus→src.rabbitmq.utils.resolveProvider.ConfigProvider
- Direction
- rabbitmq.RabbitMqEventBus uses rabbitmq.utils.resolveProvider, so a change to rabbitmq.utils.resolveProvider can break rabbitmq.RabbitMqEventBus, while a change to rabbitmq.RabbitMqEventBus can't break rabbitmq.utils.resolveProvider.
- Position
- Below the diagonal: rabbitmq.RabbitMqEventBus uses a module listed above it, which is the healthy direction.
37→13 rabbitmq.RabbitMqEventBus uses interfaces.IEventBus✕
- Connections
- 1 pair of types, where a type in rabbitmq.RabbitMqEventBus uses a type in interfaces.IEventBus.
- The types involved
src.rabbitmq.RabbitMqEventBus.RabbitMqEventBus→src.interfaces.IEventBus.IEventBus
- Direction
- rabbitmq.RabbitMqEventBus uses interfaces.IEventBus, so a change to interfaces.IEventBus can break rabbitmq.RabbitMqEventBus, while a change to rabbitmq.RabbitMqEventBus can't break interfaces.IEventBus.
- Position
- Below the diagonal: rabbitmq.RabbitMqEventBus uses a module listed above it, which is the healthy direction.
37→18 rabbitmq.RabbitMqEventBus uses rabbitmq.RabbitMqGateway✕
- Connections
- 1 pair of types, where a type in rabbitmq.RabbitMqEventBus uses a type in rabbitmq.RabbitMqGateway.
- The types involved
src.rabbitmq.RabbitMqEventBus.RabbitMqEventBus→src.rabbitmq.RabbitMqGateway.RabbitMqGateway
- Direction
- rabbitmq.RabbitMqEventBus uses rabbitmq.RabbitMqGateway, so a change to rabbitmq.RabbitMqGateway can break rabbitmq.RabbitMqEventBus, while a change to rabbitmq.RabbitMqEventBus can't break rabbitmq.RabbitMqGateway.
- Position
- Below the diagonal: rabbitmq.RabbitMqEventBus uses a module listed above it, which is the healthy direction.
37→31 rabbitmq.RabbitMqEventBus uses interfaces.IContainer✕
- Connections
- 1 pair of types, where a type in rabbitmq.RabbitMqEventBus uses a type in interfaces.IContainer.
- The types involved
src.rabbitmq.RabbitMqEventBus.RabbitMqEventBus→src.interfaces.IContainer.IContainer
- Direction
- rabbitmq.RabbitMqEventBus uses interfaces.IContainer, so a change to interfaces.IContainer can break rabbitmq.RabbitMqEventBus, while a change to rabbitmq.RabbitMqEventBus can't break interfaces.IContainer.
- Position
- Below the diagonal: rabbitmq.RabbitMqEventBus uses a module listed above it, which is the healthy direction.
38→31 sqlite.AbstractSqliteAccessor uses interfaces.IContainer✕
- Connections
- 1 pair of types, where a type in sqlite.AbstractSqliteAccessor uses a type in interfaces.IContainer.
- The types involved
src.sqlite.AbstractSqliteAccessor.AbstractSqliteAccessor→src.interfaces.IContainer.IContainer
- Direction
- sqlite.AbstractSqliteAccessor uses interfaces.IContainer, so a change to interfaces.IContainer can break sqlite.AbstractSqliteAccessor, while a change to sqlite.AbstractSqliteAccessor can't break interfaces.IContainer.
- Position
- Below the diagonal: sqlite.AbstractSqliteAccessor uses a module listed above it, which is the healthy direction.
39→1 sqlite.AbstractSqliteView uses interfaces✕
- Connections
- 1 pair of types, where a type in sqlite.AbstractSqliteView uses a type in interfaces.
- The types involved
src.sqlite.AbstractSqliteView.AbstractSqliteView→src.interfaces.IEvent
- Direction
- sqlite.AbstractSqliteView uses interfaces, so a change to interfaces can break sqlite.AbstractSqliteView, while a change to sqlite.AbstractSqliteView can't break interfaces.
- Position
- Below the diagonal: sqlite.AbstractSqliteView uses a module listed above it, which is the healthy direction.
39→9 sqlite.AbstractSqliteView uses interfaces.IViewLocker✕
- Connections
- 1 pair of types, where a type in sqlite.AbstractSqliteView uses a type in interfaces.IViewLocker.
- The types involved
src.sqlite.AbstractSqliteView.AbstractSqliteView→src.interfaces.IViewLocker.IViewLocker
- Direction
- sqlite.AbstractSqliteView uses interfaces.IViewLocker, so a change to interfaces.IViewLocker can break sqlite.AbstractSqliteView, while a change to sqlite.AbstractSqliteView can't break interfaces.IViewLocker.
- Position
- Below the diagonal: sqlite.AbstractSqliteView uses a module listed above it, which is the healthy direction.
39→14 sqlite.AbstractSqliteView uses interfaces.IEventLocker✕
- Connections
- 1 pair of types, where a type in sqlite.AbstractSqliteView uses a type in interfaces.IEventLocker.
- The types involved
src.sqlite.AbstractSqliteView.AbstractSqliteView→src.interfaces.IEventLocker.IEventLocker
- Direction
- sqlite.AbstractSqliteView uses interfaces.IEventLocker, so a change to interfaces.IEventLocker can break sqlite.AbstractSqliteView, while a change to sqlite.AbstractSqliteView can't break interfaces.IEventLocker.
- Position
- Below the diagonal: sqlite.AbstractSqliteView uses a module listed above it, which is the healthy direction.
39→38 sqlite.AbstractSqliteView uses sqlite.AbstractSqliteAccessor✕
- Connections
- 1 pair of types, where a type in sqlite.AbstractSqliteView uses a type in sqlite.AbstractSqliteAccessor.
- The types involved
src.sqlite.AbstractSqliteView.AbstractSqliteView→src.sqlite.AbstractSqliteAccessor.AbstractSqliteAccessor
- Direction
- sqlite.AbstractSqliteView uses sqlite.AbstractSqliteAccessor, so a change to sqlite.AbstractSqliteAccessor can break sqlite.AbstractSqliteView, while a change to sqlite.AbstractSqliteView can't break sqlite.AbstractSqliteAccessor.
- Position
- Below the diagonal: sqlite.AbstractSqliteView uses a module listed above it, which is the healthy direction.
40→1 sqlite.SqliteEventStorage uses interfaces✕
- Connections
- 1 pair of types, where a type in sqlite.SqliteEventStorage uses a type in interfaces.
- The types involved
src.sqlite.SqliteEventStorage.SqliteEventStorage→src.interfaces.IEvent
- Direction
- sqlite.SqliteEventStorage uses interfaces, so a change to interfaces can break sqlite.SqliteEventStorage, while a change to sqlite.SqliteEventStorage can't break interfaces.
- Position
- Below the diagonal: sqlite.SqliteEventStorage uses a module listed above it, which is the healthy direction.
40→2 sqlite.SqliteEventStorage uses interfaces.IDispatchPipelineProcessor✕
- Connections
- 1 pair of types, where a type in sqlite.SqliteEventStorage uses a type in interfaces.IDispatchPipelineProcessor.
- The types involved
src.sqlite.SqliteEventStorage.SqliteEventStorage→src.interfaces.IDispatchPipelineProcessor.IDispatchPipelineProcessor
- Direction
- sqlite.SqliteEventStorage uses interfaces.IDispatchPipelineProcessor, so a change to interfaces.IDispatchPipelineProcessor can break sqlite.SqliteEventStorage, while a change to sqlite.SqliteEventStorage can't break interfaces.IDispatchPipelineProcessor.
- Position
- Below the diagonal: sqlite.SqliteEventStorage uses a module listed above it, which is the healthy direction.
40→3 sqlite.SqliteEventStorage uses interfaces.IEventSet✕
- Connections
- 1 pair of types, where a type in sqlite.SqliteEventStorage uses a type in interfaces.IEventSet.
- The types involved
src.sqlite.SqliteEventStorage.SqliteEventStorage→src.interfaces.IEventSet.IEventSet
- Direction
- sqlite.SqliteEventStorage uses interfaces.IEventSet, so a change to interfaces.IEventSet can break sqlite.SqliteEventStorage, while a change to sqlite.SqliteEventStorage can't break interfaces.IEventSet.
- Position
- Below the diagonal: sqlite.SqliteEventStorage uses a module listed above it, which is the healthy direction.
40→4 sqlite.SqliteEventStorage uses interfaces.IEventStream✕
- Connections
- 1 pair of types, where a type in sqlite.SqliteEventStorage uses a type in interfaces.IEventStream.
- The types involved
src.sqlite.SqliteEventStorage.SqliteEventStorage→src.interfaces.IEventStream.IEventStream
- Direction
- sqlite.SqliteEventStorage uses interfaces.IEventStream, so a change to interfaces.IEventStream can break sqlite.SqliteEventStorage, while a change to sqlite.SqliteEventStorage can't break interfaces.IEventStream.
- Position
- Below the diagonal: sqlite.SqliteEventStorage uses a module listed above it, which is the healthy direction.
40→5 sqlite.SqliteEventStorage uses interfaces.IIdentifierProvider✕
- Connections
- 1 pair of types, where a type in sqlite.SqliteEventStorage uses a type in interfaces.IIdentifierProvider.
- The types involved
src.sqlite.SqliteEventStorage.SqliteEventStorage→src.interfaces.IIdentifierProvider.IIdentifierProvider
- Direction
- sqlite.SqliteEventStorage uses interfaces.IIdentifierProvider, so a change to interfaces.IIdentifierProvider can break sqlite.SqliteEventStorage, while a change to sqlite.SqliteEventStorage can't break interfaces.IIdentifierProvider.
- Position
- Below the diagonal: sqlite.SqliteEventStorage uses a module listed above it, which is the healthy direction.
40→10 sqlite.SqliteEventStorage uses interfaces.Identifier✕
- Connections
- 1 pair of types, where a type in sqlite.SqliteEventStorage uses a type in interfaces.Identifier.
- The types involved
src.sqlite.SqliteEventStorage.SqliteEventStorage→src.interfaces.Identifier.Identifier
- Direction
- sqlite.SqliteEventStorage uses interfaces.Identifier, so a change to interfaces.Identifier can break sqlite.SqliteEventStorage, while a change to sqlite.SqliteEventStorage can't break interfaces.Identifier.
- Position
- Below the diagonal: sqlite.SqliteEventStorage uses a module listed above it, which is the healthy direction.
40→15 sqlite.SqliteEventStorage uses interfaces.IEventStorageReader✕
- Connections
- 1 pair of types, where a type in sqlite.SqliteEventStorage uses a type in interfaces.IEventStorageReader.
- The types involved
src.sqlite.SqliteEventStorage.SqliteEventStorage→src.interfaces.IEventStorageReader.IEventStorageReader
- Direction
- sqlite.SqliteEventStorage uses interfaces.IEventStorageReader, so a change to interfaces.IEventStorageReader can break sqlite.SqliteEventStorage, while a change to sqlite.SqliteEventStorage can't break interfaces.IEventStorageReader.
- Position
- Below the diagonal: sqlite.SqliteEventStorage uses a module listed above it, which is the healthy direction.
40→38 sqlite.SqliteEventStorage uses sqlite.AbstractSqliteAccessor✕
- Connections
- 1 pair of types, where a type in sqlite.SqliteEventStorage uses a type in sqlite.AbstractSqliteAccessor.
- The types involved
src.sqlite.SqliteEventStorage.SqliteEventStorage→src.sqlite.AbstractSqliteAccessor.AbstractSqliteAccessor
- Direction
- sqlite.SqliteEventStorage uses sqlite.AbstractSqliteAccessor, so a change to sqlite.AbstractSqliteAccessor can break sqlite.SqliteEventStorage, while a change to sqlite.SqliteEventStorage can't break sqlite.AbstractSqliteAccessor.
- Position
- Below the diagonal: sqlite.SqliteEventStorage 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 — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 21 | High / Critical |
| A05:2025 — Injection | 15 | High / Critical |
Roadmap
Top priorities: 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; 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; Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +7.1 pts | Medium | Security & performance tooling |
| Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with InMemoryMessageBus.test.ts (2). | +2.3 pts | Low | Test Quality |
| 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. | +4.0 pts | Medium | Architecture documentation |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +3.6 pts | Medium | Deployment & Rollback |
| 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. | +1.7 pts | Medium | Documentation (README) |
| Bump outdated dependencies to current versions to limit upgrade debt. | +1.2 pts | Medium | Dependency Freshness |
| Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge. | +1.0 pts | Medium | CI/CD gates |
| Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with jest-axe in tests, then gate axe/pa11y/Lighthouse in CI. | +0.6 pts | Medium | A11y enforcement |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| tests/unit/memory/InMemoryMessageBus.test.ts | 5.0 | Mixed | Test Quality: No assertions (empty test): fails if more than one handler found |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.5 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| tests/unit/memory/InMemoryLock.test.ts | 7.4 | Mixed | Test Quality: No assertions: should call each method explicitly to satisfy coverage |
| package.json | 7.4 | Mixed | Dependency Hygiene: Deprecated: @opentelemetry/sdk-trace-base |
| tests/unit/AbstractProjection.test.ts | 7.6 | Mixed | Test Quality: No assertions: can bypass waiting when invoked as a protected method |
| src/rabbitmq/RabbitMqGateway.ts | 7.8 | Mixed | Cognitive Complexity: RabbitMqGateway.#assertConsumer (cognitive 17) |
| tests/unit/CqrsContainerBuilder.test.ts | 7.8 | Mixed | Test Quality: No assertions: registers aggregate command handler for a given aggregate type |
| tests/unit/memory/InMemoryView.test.ts | 7.8 | Mixed | Test Quality: No assertions: fails, when trying to pass a function as a value |
| tests/integration/workers/AbstractWorkerProjection.test.ts | 8.0 | Near-clean | Test Quality: Fixed-sleep synchronisation: awaits project calls while restoring |
| src/AggregateCommandHandler.ts | 8.5 | Near-clean | Cognitive Complexity: AggregateCommandHandler.execute (cognitive 21) |
| src/sqlite/AbstractSqliteAccessor.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/sqlite/AbstractSqliteAccessor.ts |
| src/sqlite/AbstractSqliteView.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/sqlite/AbstractSqliteView.ts |
| src/sqlite/SqliteEventLocker.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/sqlite/SqliteEventLocker.ts |
| src/sqlite/SqliteEventStorage.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/sqlite/SqliteEventStorage.ts |
| src/sqlite/SqliteObjectStorage.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/sqlite/SqliteObjectStorage.ts |
| src/sqlite/SqliteObjectView.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/sqlite/SqliteObjectView.ts |
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 76 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 76 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, 142 of 152 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 · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D12 Dependency Hygiene — 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 repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because registry.npmjs.org — the registry that answers it — was asked and did not reply (registry returned 429). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add registry.npmjs.org to the allowlist and re-run — not to build anything.
- D16 Bus Factor — 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. Single-maintainer repository — bus factor is not applicable (5 contributor(s) across 798 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 4 hold 0.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- 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.
- D32 Data Compliance (PII/GDPR) — 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. `src/AbstractAggregate.ts`, `src/AggregateCommandHandler.ts`, `src/EventDispatcher.ts`, `src/workers/interfaces/index.ts`, `src/workers/utils/createWorkerInstance.ts`, … (+1 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AXR1 Runtime accessibility — 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. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- 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").
- 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.
- 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.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- 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.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- 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.
- 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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
2 method(s) exceeded the cognitive complexity threshold of 15; the worst was AggregateCommandHandler.execute at 21.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with AggregateCommandHandler.execute (cognitive 21), RabbitMqGateway.#assertConsumer (cognitive 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 9.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
1 god class(es) detected.
What to do
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with RabbitMqGateway.ts. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 43 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 83.4% — 10 file(s) below 50%. Measured from the JavaScript/TypeScript suite (jest via `npm ci --ignore-scripts` in the repository root).
What to do
- Resolve the 10 Low coverage finding(s) in Code Coverage — start with AbstractSqliteAccessor.ts, AbstractSqliteView.ts, SqliteEventLocker.ts. — One of this dimension's main actionable groups (10 warning-level).
- Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
742 test methods: 621 unit, 121 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 742 `it`/`test` case(s) across 64 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 14 zero-assertion, 7 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 742 tests.
What to do
- Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with InMemoryMessageBus.test.ts (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 12 No assertions finding(s) in Test Quality — start with CqrsContainerBuilder.test.ts (2), InMemoryView.test.ts (2), AbstractProjection.test.ts. — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 7 Fixed-sleep synchronisation finding(s) in Test Quality — start with InMemoryLock.test.ts (2), SqliteObjectView.test.ts, RedisView.test.ts. — One of this dimension's main actionable groups (7 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 (jest via `npm ci --ignore-scripts` in the repository root (617 tests)): measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 8316 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 7 document(s) read across 1 unit(s).
D24 · Comment Value
0 of 173 judged comments only repeat the code they sit on (0.0 %). 6 comment(s) in another language or script were not judged.
D26 · Project Cohesion
1 of 1 build units (npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
67 % of calls cross a namespace and 15 % go through an interface, but 38 % 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)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
15 finding(s): 0 critical, 11 high, 4 medium, 0 low. 11 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 17 file(s) — `.jekyll/_includes/header.html` (line 17, line 18, line 19, …), `REDACTED` (line 6, line 27, line 37), `.jekyll/_layouts/docs.html` (lines 42–47, lines 51–69), `examples/mongodb-eventstore/index.ts` (line 50, line 58, line 65), `examples/mongodb-views/index.ts` (line 71, line 81), … (+12 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
- No action in Static Analysis (SAST) — all 11 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (11 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
17 finding(s): 2 critical, 6 high, 5 medium, 4 low.
What to do
- Resolve the 6 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
D31 · IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 36 of the 151 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.
D36 · Supply-chain Provenance & Signing
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
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 0 platform declaration(s) and 3 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
AC1 · Text alternatives
AC2 · Forms & labels
AC3 · Page structure
AC5 · ARIA correctness
AC6 · Visual & motion safety
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI. What was searched, so you can tell an absence from a miss: the 4 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — package.json:129
What to do
- Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with jest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
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
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 a README to the 1 of 1 project(s) that lack one — worth up to 2 pts.
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.
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.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P10 · Library API & versioning
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 2659 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. — REDACTED:7
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:124
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.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- 24 duplicated blocks under src/ have copies in at least two of the sibling directories in-memory, mongodb, rabbitmq, redis, sqlite, sqlite-workers (+1 more sibling(s) not listed) — 21 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 24 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 24 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 24 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/mongodb/MongoViewLocker.ts:83
- src/mongodb/MongoViewLocker.ts:83 · src/redis/RedisViewLocker.ts:76 — the two spans are one implementation copied and then locally edited — 297 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/mongodb/MongoViewLocker.ts:83
- src/redis/RedisViewLocker.ts:66 · src/sqlite/SqliteViewLocker.ts:54 — the two spans are one implementation copied and then locally edited — 272 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/redis/RedisViewLocker.ts:66
- src/rabbitmq/RabbitMqCommandBus.ts:27 · src/rabbitmq/RabbitMqEventBus.ts:25 — the two spans are one implementation copied and then locally edited — 183 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/rabbitmq/RabbitMqCommandBus.ts:27
- src/mongodb/AbstractMongoAccessor.ts:18 · src/redis/AbstractRedisAccessor.ts:18 · src/sqlite/AbstractSqliteAccessor.ts:17 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/mongodb/AbstractMongoAccessor.ts:18
- src/mongodb/AbstractMongoView.ts:40 · src/redis/RedisView.ts:49 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/mongodb/AbstractMongoView.ts:40
- src/mongodb/MongoObjectStorage.ts:90 · src/redis/RedisObjectStorage.ts:116 — the two spans are one implementation copied and then locally edited — 164 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/mongodb/MongoObjectStorage.ts:90
- src/mongodb/MongoObjectStorage.ts:26 · src/redis/RedisObjectStorage.ts:42 — the two spans are one implementation copied and then locally edited — 124 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/mongodb/MongoObjectStorage.ts:26
- src/mongodb/AbstractMongoObjectProjection.ts:5 · src/redis/AbstractRedisProjection.ts:5 · src/sqlite/AbstractSqliteObjectProjection.ts:5 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/mongodb/AbstractMongoObjectProjection.ts:5
- src/mongodb/MongoObjectView.ts:25 · src/redis/RedisView.ts:78 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/mongodb/MongoObjectView.ts:25
- src/redis/RedisObjectStorage.ts:88 · src/redis/RedisObjectStorage.ts:125 — the two spans are one implementation copied and then locally edited — 148 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/redis/RedisObjectStorage.ts:88
- src/mongodb/MongoViewLocker.ts:137 · src/redis/RedisViewLocker.ts:95 · src/sqlite/SqliteViewLocker.ts:114 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/mongodb/MongoViewLocker.ts:137
- src/mongodb/MongoEventLocker.ts:135 · src/redis/RedisEventLocker.ts:106 — the two spans are one implementation copied and then locally edited — 103 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/mongodb/MongoEventLocker.ts:135
- src/mongodb/registerExitCleanup.ts:8 · src/rabbitmq/utils/registerExitCleanup.ts:8 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/mongodb/registerExitCleanup.ts:8
- src/mongodb/MongoEventLocker.ts:137 · src/sqlite/SqliteEventLocker.ts:112 — the two spans are one implementation copied and then locally edited — 76 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/mongodb/MongoEventLocker.ts:137
- src/mongodb/MongoObjectView.ts:32 · src/redis/RedisView.ts:85 · src/sqlite/SqliteObjectView.ts:42 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/mongodb/MongoObjectView.ts:32
- src/interfaces/IEventLocker.ts:35 · src/interfaces/IViewLocker.ts:41 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/interfaces/IEventLocker.ts:35
- src/AbstractProjection.ts:193 · src/workers/WorkerProxyProjection.ts:83 — the two spans are one implementation copied and then locally edited — 101 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/AbstractProjection.ts:193
- src/in-memory/InMemoryMessageBus.ts:80 · src/rabbitmq/RabbitMqCommandBus.ts:80 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/in-memory/InMemoryMessageBus.ts:80
- src/mongodb/MongoViewLocker.ts:194 · src/redis/RedisViewLocker.ts:152 · src/sqlite/SqliteViewLocker.ts:158 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/mongodb/MongoViewLocker.ts:194
- src/AbstractAggregate.ts:159 · src/AbstractSaga.ts:91 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/AbstractAggregate.ts:159
- src/in-memory/InMemoryEventStorage.ts:131 · src/mongodb/MongoEventStorage.ts:262 — the two spans are one implementation copied and then locally edited — 64 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/in-memory/InMemoryEventStorage.ts:131
- src/interfaces/IAggregateSnapshotStorage.ts:11 · src/interfaces/IEventStorageReader.ts:59 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/interfaces/IAggregateSnapshotStorage.ts:11
- src/mongodb/AbstractMongoView.ts:12 · src/sqlite/AbstractSqliteView.ts:10 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/mongodb/AbstractMongoView.ts:12
- src/sqlite/SqliteEventLocker.ts:45 · src/sqlite/SqliteViewLocker.ts:45 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/sqlite/SqliteEventLocker.ts:45
- src/sqlite/SqliteObjectStorage.ts:86 · src/sqlite/SqliteObjectStorage.ts:118 — the two spans are one implementation copied and then locally edited — 79 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/sqlite/SqliteObjectStorage.ts:86
- src/mongodb/MongoEventLocker.ts:93 · src/redis/RedisEventLocker.ts:88 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/mongodb/MongoEventLocker.ts:93
- src/utils/assert.ts:38 · src/utils/assert.ts:48 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/utils/assert.ts:38
- src/sqlite-workers/SqliteWorkerProxy.ts:76 · src/workers/WorkerProxyProjection.ts:64 — the two spans are one implementation copied and then locally edited — 53 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/sqlite-workers/SqliteWorkerProxy.ts:76
- src/AbstractProjection.ts:143 · src/workers/WorkerProxyProjection.ts:146 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/AbstractProjection.ts:143
- src/in-memory/InMemoryEventStorage.ts:92 · src/sqlite/SqliteEventStorage.ts:229 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/in-memory/InMemoryEventStorage.ts:92
- src/mongodb/MongoObjectStorage.ts:71 · src/mongodb/MongoObjectStorage.ts:98 · src/redis/RedisObjectStorage.ts:87 · src/redis/RedisObjectStorage.ts:124 — the 4 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/mongodb/MongoObjectStorage.ts:71
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
- (anonymous) has cyclomatic complexity 15 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/rabbitmq/RabbitMqGateway.ts:664
- (anonymous) has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — tests/unit/redis/mockRedisForView.ts:61
- handle has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SagaEventHandler.ts:104
- execute has cyclomatic complexity 11 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/AggregateCommandHandler.ts:203
- #subscribe has cyclomatic complexity 11 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/rabbitmq/RabbitMqGateway.ts:451
- getAggregateEvents has cyclomatic complexity 11 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/mongodb/MongoEventStorage.ts:155
R3 · Large Files
- src/rabbitmq/RabbitMqGateway.ts has 734 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/rabbitmq/RabbitMqGateway.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
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×2) — scripts/changelog/index.cjs:1, src/workers/utils/createWorker.ts:1
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
R7 · Dead Code
- Unreachable from the 9 application, 3 tooling and 70 test entry point(s) detected in this repo. Gate removals on `npm run build:cjs` — an undetected custom entry would make these reachable.
- no import path from any entry point (9 application, 3 tooling, 70 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — src/workers/utils/createWorker.ts
- Nothing imports this binding — it is safe to review for removal. (×2) — src/sqlite-workers/protocol.ts:56, src/workers/protocol.ts:18
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
R9 · Circular Imports
S1 · Web-Security Posture
- MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×3) — src/mongodb/utils/getEventId.ts:11, src/redis/utils/getEventId.ts:11, src/sqlite/utils/getEventId.ts:9
What to do
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 3 sites, not one: `src/mongodb/utils/getEventId.ts:11` (createHash("md5")), `src/redis/utils/getEventId.ts:11` (createHash("md5")), `src/sqlite/utils/getEventId.ts:9` (createHash("md5")). Each is a separate decision — fixing only the line this row cites leaves the others in place.
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
- `extractErrorDetails` is exported, takes a document from its caller (line 36) and hands it to `extractErrorMessage`, which calls itself at line 17 (`extractErrorMessage`) with a piece of `err` — and nowhere in `extractErrorMessage` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `extractErrorMessage` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/utils/extractErrorDetails.ts:17
- `extractErrorDetails` is exported and takes `err: unknown` from its caller, and it calls itself at line 46 (`extractErrorDetails`) with a piece of `err` — and nowhere in `extractErrorDetails` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `extractErrorDetails` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/utils/extractErrorDetails.ts:46
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
- `debug` at line 95 is called with an argument built by `eventTypes.join(', ')` (line 95), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — src/EventStore.ts:95
- `debug` at line 101 is called with an argument built by `eventTypes.join(', ')` (line 101), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — src/EventStore.ts:101
- `debug` at line 135 is called with an argument built by `commands.map(c => c.type)` (line 135), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — src/SagaEventHandler.ts:135
- `debug` at line 45 is called with an argument built by `messageTypes.join(',')` (line 45), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — src/utils/setupOneTimeEmitterSubscription.ts:45
- `debug` at line 56 is called with an argument built by `messageTypes.join(',')` (line 56), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — src/utils/setupOneTimeEmitterSubscription.ts:56
What to do
- Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is JavaScript's evaluation order, not a guess — then put the construction behind the level check the logger offers (`if (logger.isLevelEnabled('debug'))` for pino and winston, `isDebugEnabled()` for log4js, the repository's own debug flag where it has one), or hand the logger the object and a format string (`logger.debug({ payload }, 'raw request')`) so the serialising happens only when the line is written. Moving the call is not the fix: it is the join/projection/stringify in the argument that is paid, wherever the call sits.
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
- `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×2) — src/CqrsContainerBuilder.ts:91, src/workers/WorkerProxyProjection.ts:72
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- ~7.2 `!` null assertions per 1k TypeScript source lines — 67 assertion(s) across the 9304 source line(s) of the 148 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/sqlite/SqliteEventStorage.ts (9), src/mongodb/MongoObjectStorage.ts (8), src/redis/RedisObjectStorage.ts (8). 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 `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 81% | Strong | Solid. |
| Architecture | 89% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 67% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 58% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 83% | Strong | Solid. |
| Accessibility | 82% | Strong | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- D12 Dependency Hygiene — 9 observation(s) recorded · Dependency currency not established — registry.npmjs.org did not answer
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 52 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- 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
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- 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.
- D14 License Compliance — Not scored — this repository's 9 shipped npm package(s) were resolved from its committed lockfile, but registry.npmjs.org could not be asked for the licence of 3 of them (registry returned 429), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- 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.
- 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 — Naming consistency is measured on C# and TypeScript only; JavaScript not measured.
- 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 (examples), 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"]`.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 6 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 2 aggregate root(s) (AggregateRoot/IAggregateRoot); 5 per-aggregate domain namespaces (…/BasketAggregate, …/OrderAggregate); a top-level examples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (2 CQRS handler(s))
- ED5 Idempotency — 2 mutating command handler(s)/consumer(s) detected and 4 handler method(s) walked, but no persistent write was recognised in any of them — idempotency not assessed
- ES1 Event Sourcing — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 2 projection(s); an append-only event-store seam (IEventStore/Append-of-events)
- P2 Observability — This repository's JavaScript/TypeScript source (1 module(s), 149 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- 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 — coverage data present for 96 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- 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.
- SC1 Supply-chain hygiene — 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 — 21 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No assertions (empty test): fails if more than one handler found tests/unit/memory/InMemoryMessageBus.test.ts:106
- No assertions (empty test): does not allow to setup multiple subscriptions for same event + queueName combination tests/unit/memory/InMemoryMessageBus.test.ts:238
- REDACTED
- REDACTED
Serious — 94 finding(s)
- No assertions: can bypass waiting when invoked as a protected method tests/unit/AbstractProjection.test.ts:244
- No assertions: registers aggregate command handler for a given aggregate type tests/unit/CqrsContainerBuilder.test.ts:25
- No assertions: sets up saga event handler tests/unit/CqrsContainerBuilder.test.ts:96
- No assertions: resolves immediately when not locked tests/unit/sqlite/AbstractSqliteView.test.ts:67
- No assertions: unlock() handles missing lock row gracefully tests/unit/sqlite/SqliteViewLocker.test.ts:124
- No assertions: should call each method explicitly to satisfy coverage tests/unit/memory/InMemoryLock.test.ts:10
- No assertions: fails if no handlers found tests/unit/memory/InMemoryMessageBus.test.ts:95
- No assertions: fails, when trying to pass a function as a value tests/unit/memory/InMemoryView.test.ts:54
- No assertions: validates parameters tests/unit/memory/InMemoryView.test.ts:139
- No assertions: publishes without throwing tests/integration/rabbitmq/RabbitMqCommandBus.test.ts:74
- No assertions: publishes without throwing tests/integration/rabbitmq/RabbitMqEventBus.test.ts:51
- No assertions: publishes without throwing tests/integration/rabbitmq/RabbitMqGateway.test.ts:45
- Low coverage: src/sqlite/AbstractSqliteAccessor.ts src/sqlite/AbstractSqliteAccessor.ts:1
- Low coverage: src/sqlite/AbstractSqliteView.ts src/sqlite/AbstractSqliteView.ts:1
- Low coverage: src/sqlite/SqliteEventLocker.ts src/sqlite/SqliteEventLocker.ts:1
- Low coverage: src/sqlite/SqliteEventStorage.ts src/sqlite/SqliteEventStorage.ts:1
- Low coverage: src/sqlite/SqliteObjectStorage.ts src/sqlite/SqliteObjectStorage.ts:1
- Low coverage: src/sqlite/SqliteObjectView.ts src/sqlite/SqliteObjectView.ts:1
- Low coverage: src/sqlite/SqliteViewLocker.ts src/sqlite/SqliteViewLocker.ts:1
- Low coverage: src/sqlite-workers/AsyncSqliteStatement.ts src/sqlite-workers/AsyncSqliteStatement.ts:1
- Low coverage: src/sqlite-workers/SqliteWorkerRunner.ts src/sqlite-workers/SqliteWorkerRunner.ts:1
- Low coverage: src/sqlite-workers/utils/createWorkerDb.ts src/sqlite-workers/utils/createWorkerDb.ts:1
- Fixed-sleep synchronisation: waits for readiness before returning data tests/unit/sqlite/SqliteObjectView.test.ts:62
- Fixed-sleep synchronisation: waits for readiness in get() tests/unit/redis/RedisView.test.ts:78
- Fixed-sleep synchronisation: blocks second lock() call until unlocked tests/unit/memory/InMemoryLock.test.ts:26
- Fixed-sleep synchronisation: resolves once() only after unlocking tests/unit/memory/InMemoryLock.test.ts:63
- Fixed-sleep synchronisation: awaits project calls while restoring tests/integration/workers/AbstractWorkerProjection.test.ts:138
- Fixed-sleep synchronisation: second lock acquires once first is released tests/integration/redis/RedisLockers.test.ts:75
- Fixed-sleep synchronisation: second lock acquires once first is released tests/integration/mongodb/MongoLockers.test.ts:72
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Weak hash algorithm src/mongodb/utils/getEventId.ts:11
- Weak hash algorithm src/redis/utils/getEventId.ts:11
- Weak hash algorithm src/sqlite/utils/getEventId.ts:9
- Duplicated block (10 lines × 2 locations) src/AbstractAggregate.ts:159
- Duplicated block (10 lines × 2 locations) src/interfaces/IAggregateSnapshotStorage.ts:11
- Duplicated block (9 lines × 2 locations) src/mongodb/AbstractMongoView.ts:12
- Duplicated block (9 lines × 2 locations) src/sqlite/SqliteEventLocker.ts:45
- Duplicated block (8 lines × 2 locations) src/mongodb/MongoEventLocker.ts:93
- Duplicated block (8 lines × 2 locations) src/utils/assert.ts:38
- Duplicated block (6 lines × 2 locations) src/AbstractProjection.ts:143
- Duplicated block (6 lines × 2 locations) src/in-memory/InMemoryEventStorage.ts:92
- No test reaches this file scripts/changelog/index.cjs:1
- No test reaches this file src/workers/utils/createWorker.ts:1
- Recursive walk over a caller-supplied document has no depth cap src/utils/extractErrorDetails.ts:17
- Recursive walk over a caller-supplied document has no depth cap src/utils/extractErrorDetails.ts:46
- Swallowed exception (empty catch) src/CqrsContainerBuilder.ts:91
- Swallowed exception (empty catch) src/workers/WorkerProxyProjection.ts:72
- Accessibility enforcement below the top rung package.json:129
- AggregateCommandHandler.execute (cognitive 21) src/AggregateCommandHandler.ts:203
- RabbitMqGateway.#assertConsumer (cognitive 17) src/rabbitmq/RabbitMqGateway.ts:651
- TooManyMethods: RabbitMqGateway src/rabbitmq/RabbitMqGateway.ts:141
- REDACTED
- REDACTED
- REDACTED
- Coverage collected but not gated
- Duplication concentrated across 7 sibling directories (24 clone groups) src/mongodb/MongoViewLocker.ts:83
- Duplicated block with local edits (44 matched lines × 2 locations) src/mongodb/MongoViewLocker.ts:83
- Duplicated block with local edits (41 matched lines × 2 locations) src/redis/RedisViewLocker.ts:66
- Duplicated block with local edits (31 matched lines × 2 locations) src/rabbitmq/RabbitMqCommandBus.ts:27
- Duplicated block (26 lines × 3 locations) src/mongodb/AbstractMongoAccessor.ts:18
- Duplicated block (23 lines × 2 locations) src/mongodb/AbstractMongoView.ts:40
- Duplicated block with local edits (23 matched lines × 2 locations) src/mongodb/MongoObjectStorage.ts:90
- Duplicated block with local edits (22 matched lines × 2 locations) src/mongodb/MongoObjectStorage.ts:26
- Duplicated block (21 lines × 3 locations) src/mongodb/AbstractMongoObjectProjection.ts:5
- Duplicated block (20 lines × 2 locations) src/mongodb/MongoObjectView.ts:25
- Duplicated block with local edits (20 matched lines × 2 locations) src/redis/RedisObjectStorage.ts:88
- Duplicated block (19 lines × 3 locations) src/mongodb/MongoViewLocker.ts:137
- Duplicated block with local edits (18 matched lines × 2 locations) src/mongodb/MongoEventLocker.ts:135
- Duplicated block (18 lines × 2 locations) src/mongodb/registerExitCleanup.ts:8
- Duplicated block with local edits (17 matched lines × 2 locations) src/mongodb/MongoEventLocker.ts:137
- Duplicated block (15 lines × 3 locations) src/mongodb/MongoObjectView.ts:32
- Duplicated block (14 lines × 2 locations) src/interfaces/IEventLocker.ts:35
- Duplicated block with local edits (13 matched lines × 2 locations) src/AbstractProjection.ts:193
- Duplicated block (13 lines × 2 locations) src/in-memory/InMemoryMessageBus.ts:80
- Duplicated block (11 lines × 3 locations) src/mongodb/MongoViewLocker.ts:194
- Duplicated block with local edits (10 matched lines × 2 locations) src/in-memory/InMemoryEventStorage.ts:131
- Duplicated block with local edits (9 matched lines × 2 locations) src/sqlite/SqliteObjectStorage.ts:86
- Duplicated block with local edits (7 matched lines × 2 locations) src/sqlite-workers/SqliteWorkerProxy.ts:76
- Duplicated block (6 lines × 4 locations) src/mongodb/MongoObjectStorage.ts:71
- Complex function (anonymous) (cyclomatic 15, cognitive 17) src/rabbitmq/RabbitMqGateway.ts:664
- Complex function (anonymous) (cyclomatic 12, cognitive 16) tests/unit/redis/mockRedisForView.ts:61
- Complex function handle (cyclomatic 12, cognitive 13) src/SagaEventHandler.ts:104
- Complex function execute (cyclomatic 11, cognitive 21) src/AggregateCommandHandler.ts:203
- Complex function #subscribe (cyclomatic 11, cognitive 14) src/rabbitmq/RabbitMqGateway.ts:451
- Complex function getAggregateEvents (cyclomatic 11, cognitive 11) src/mongodb/MongoEventStorage.ts:155
- src/rabbitmq/RabbitMqGateway.ts: 734 lines of code src/rabbitmq/RabbitMqGateway.ts:1
- Dead file (~17 LoC) src/workers/utils/createWorker.ts
Minor — 36 finding(s)
- Mock-dominated test: uses eventLocker assigned in a derived constructor tests/unit/AbstractProjection.test.ts:332
- Mock-dominated test: calls markAsLastEvent based on shouldRecordLastEvent tests/unit/AbstractProjection.test.ts:359
- Mock-dominated test: returns early when event lock is not obtained tests/unit/AbstractProjection.test.ts:393
- Mock-dominated test: uses viewLocker assigned in a derived constructor on restore tests/unit/AbstractProjection.test.ts:419
- Mock-dominated test: routes events to pipelines based on meta.origin tests/unit/EventDispatcher.test.ts:295
- Mock-dominated test: routes events according to eventDispatchRouter if provided tests/unit/EventDispatcher.test.ts:320
- Mock-dominated test: routes events to default pipeline when no router is defined tests/unit/EventDispatcher.test.ts:345
- Mock-dominated test: logs rejected disposition when a timed out message is nacked tests/unit/rabbitmq/RabbitMqGateway.test.ts:149
- Mock-dominated test: logs requeued disposition when the timed out message channel is closed tests/unit/rabbitmq/RabbitMqGateway.test.ts:190
- Mock-dominated test: uses custom collection name from mongoEventStorageConfig tests/unit/mongodb/MongoEventStorage.test.ts:54
- Mock-dominated test: defaults collection name to EVENTS_COLLECTION tests/unit/mongodb/MongoEventStorage.test.ts:71
- Mock-dominated test: registers exit cleanup and closes the db client on signal tests/unit/mongodb/MongoEventStorage.test.ts:84
- Mock-dominated test: keeps notifying handlers in other named queues when one named queue handler throws tests/unit/memory/InMemoryMessageBus.test.ts:212
- Mock-dominated test: uses externally assigned viewLocker on restore tests/integration/workers/AbstractWorkerProjection.test.ts:159
- Diagnostic log message is built whether or not it is wanted src/EventStore.ts:95
- Diagnostic log message is built whether or not it is wanted src/EventStore.ts:101
- Diagnostic log message is built whether or not it is wanted src/SagaEventHandler.ts:135
- Diagnostic log message is built whether or not it is wanted src/utils/setupOneTimeEmitterSubscription.ts:45
- Diagnostic log message is built whether or not it is wanted src/utils/setupOneTimeEmitterSubscription.ts:56
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Projects may be oversized for their cohesion
- Scattered collaborators
- REDACTED
- REDACTED
- No ADRs
- CI build step not evidenced
- No SAST REDACTED:7
- No dependency-update automation package.json:124
- No release approval gate
- Unused export 'SqliteWorkerReadyMessage' src/sqlite-workers/protocol.ts:56
- Unused export 'isWorkerInitMessage' src/workers/protocol.ts:18
- Duplicated predicate src/SagaEventHandler.ts:66
- Null assertions (`!`) reduce the strict null checking score
Minor — 1 finding(s)
- doc comments repeat the names src/in-memory/InMemorySnapshotStorage.ts:37
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-8588e6d92c904999a57f272d4a6627a6/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-8588e6d92c904999a57f272d4a6627a6/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 . | 15 | 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 | 17 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 0 | artifacts/raw/trivy-config.json |
| 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. semgrep could not parse 6 file(s) — `src/AbstractAggregate.ts`, `src/AggregateCommandHandler.ts`, `src/EventDispatcher.ts`, `src/workers/interfaces/index.ts`, `src/workers/utils/createWorkerInstance.ts`, … (+1 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 |