Executive summary
NickTsitlakidis/event-nest falls short of our standard for production because we found no automated security scanning of the code, its secrets or its dependencies. It scores 60 out of 100 and is rated Adequate, and 12 of its 16 critical findings are security problems.
Production Readiness, at 55, is the weakest lens and counts most in the score. The best first step is adding automated security scanning, worth about 4 points. Improving the documentation comes next, worth about 2 points. Raising Production Readiness to 70 would lift the score to about 64.
Eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two weaknesses in the code could be used by an attacker, and one automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version, fixing the weaknesses the scanner points to and setting a waiting period for automatic updates would close these risks. Updating the vulnerable packages would fix the package with a known security hole. The two pieces of business logic tied to the database or web code need separating from the database and web code.
The product code is 5,451 lines, about €17,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 55 to 70, the lowest score rated Strong, the score would rise from 60 to about 64.
New since the last survey: 6 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 7 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Code Duplication · Duplicated block with local edits (19 matched lines × 2 locations) libs/core/src/lib/storage/abstract-event-store.ts
Rebuild cost: about €17,000 · Estimate
| Cost to rebuild | €5,600 to €28,000, for 93 to 296 hours of work, about 0.1 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.8 at a score of 60. 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: 5,451 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 — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 core.src.lib.aggregate-root.aggregate-root-config | 2 core.src.lib.aggregate-root.aggregate-root-event | 3 core.src.lib.published-domain-event | 4 core.src.lib.storage.snapshot.stored-snapshot | 5 core.src.lib.storage.stored-aggregate-root | 6 core.src.lib.storage.stored-event | 7 mongodb.src.lib.mongodb-module-options | 8 mssql.src.lib.mssql-module-options | 9 mssql.src.lib.schema-configuration | 10 mssql.src.lib.storage.event-row | 11 postgresql.src.lib.postgresql-module-options | 12 core.src.lib.aggregate-root.aggregate-root | 13 core.src.lib.on-domain-event | 14 core.src.lib.storage.event-store | 15 mongodb.src.lib.module-providers | 16 mssql.src.lib.module-providers | 17 core.src.lib | 18 core.src.lib.aggregate-root | 19 core.src.lib.domain-event-emitter | 20 core.src.lib.snapshot-strategy.snapshot-strategy | 21 core.src.lib.storage.aggregate-repository | 22 core.src.lib.storage.snapshot.snapshot-store | 23 core.src.lib.snapshot-strategy.all-of-snapshot-strategy | 24 core.src.lib.snapshot-strategy.any-of-snapshot-strategy | 25 core.src.lib.snapshot-strategy.for-aggregate-roots-strategy | 26 core.src.lib.snapshot-strategy.for-count-snapshot-strategy | 27 core.src.lib.snapshot-strategy.for-events-snapshot-strategy | 28 core.src.lib.snapshot-strategy.no-snapshot-strategy | 29 core.src.lib.storage.snapshot.abstract-snapshot-store | 30 mongodb.src.lib.event-nest-mongodb_module | 31 mssql.src.lib.event-nest-mssql_module | 32 postgresql.src.lib.event-nest-postgresql_module | 33 core.src.lib.storage.abstract-event-store | 34 core.src.lib.storage.snapshot.no-op-snapshot-store | 35 mongodb.src.lib.storage.mongo-snapshot-store | 36 mssql.src.lib.storage.mssql-snapshot-store | 37 postgresql.src.lib.storage.postgresql-snapshot-store | 38 mongodb.src.lib.storage.mongo-event-store | 39 mssql.src.lib.storage.mssql-event-store | 40 postgresql.src.lib.storage.postgresql-event-store |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 core.src.lib.aggregate-root.aggregate-root-config | ||||||||||||||||||||||||||||||||||||||||
| 2 core.src.lib.aggregate-root.aggregate-root-event | ||||||||||||||||||||||||||||||||||||||||
| 3 core.src.lib.published-domain-event | ||||||||||||||||||||||||||||||||||||||||
| 4 core.src.lib.storage.snapshot.stored-snapshot | ||||||||||||||||||||||||||||||||||||||||
| 5 core.src.lib.storage.stored-aggregate-root | ||||||||||||||||||||||||||||||||||||||||
| 6 core.src.lib.storage.stored-event | ||||||||||||||||||||||||||||||||||||||||
| 7 mongodb.src.lib.mongodb-module-options | ||||||||||||||||||||||||||||||||||||||||
| 8 mssql.src.lib.mssql-module-options | ||||||||||||||||||||||||||||||||||||||||
| 9 mssql.src.lib.schema-configuration | ||||||||||||||||||||||||||||||||||||||||
| 10 mssql.src.lib.storage.event-row | ||||||||||||||||||||||||||||||||||||||||
| 11 postgresql.src.lib.postgresql-module-options | ||||||||||||||||||||||||||||||||||||||||
| 12 core.src.lib.aggregate-root.aggregate-root | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 core.src.lib.on-domain-event | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 core.src.lib.storage.event-store | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 mongodb.src.lib.module-providers | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 mssql.src.lib.module-providers | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 core.src.lib | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 core.src.lib.aggregate-root | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 core.src.lib.domain-event-emitter | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 core.src.lib.snapshot-strategy.snapshot-strategy | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 core.src.lib.storage.aggregate-repository | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 core.src.lib.storage.snapshot.snapshot-store | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 core.src.lib.snapshot-strategy.all-of-snapshot-strategy | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 core.src.lib.snapshot-strategy.any-of-snapshot-strategy | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 core.src.lib.snapshot-strategy.for-aggregate-roots-strategy | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 core.src.lib.snapshot-strategy.for-count-snapshot-strategy | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 core.src.lib.snapshot-strategy.for-events-snapshot-strategy | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 core.src.lib.snapshot-strategy.no-snapshot-strategy | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 core.src.lib.storage.snapshot.abstract-snapshot-store | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 mongodb.src.lib.event-nest-mongodb_module | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 mssql.src.lib.event-nest-mssql_module | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 postgresql.src.lib.event-nest-postgresql_module | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 core.src.lib.storage.abstract-event-store | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 34 core.src.lib.storage.snapshot.no-op-snapshot-store | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 mongodb.src.lib.storage.mongo-snapshot-store | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 mssql.src.lib.storage.mssql-snapshot-store | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 postgresql.src.lib.storage.postgresql-snapshot-store | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 mongodb.src.lib.storage.mongo-event-store | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 mssql.src.lib.storage.mssql-event-store | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 40 postgresql.src.lib.storage.postgresql-event-store | 1 | 1 | 1 | 1 | 1 | 1 |
12→2 core.src.lib.aggregate-root.aggregate-root uses core.src.lib.aggregate-root.aggregate-root-event✕
- Connections
- 1 pair of types, where a type in core.src.lib.aggregate-root.aggregate-root uses a type in core.src.lib.aggregate-root.aggregate-root-event.
- The types involved
libs.core.src.lib.aggregate-root.aggregate-root.AggregateRoot→libs.core.src.lib.aggregate-root.aggregate-root-event.AggregateRootEvent
- Direction
- core.src.lib.aggregate-root.aggregate-root uses core.src.lib.aggregate-root.aggregate-root-event, so a change to core.src.lib.aggregate-root.aggregate-root-event can break core.src.lib.aggregate-root.aggregate-root, while a change to core.src.lib.aggregate-root.aggregate-root can't break core.src.lib.aggregate-root.aggregate-root-event.
- Position
- Below the diagonal: core.src.lib.aggregate-root.aggregate-root uses a module listed above it, which is the healthy direction.
12→6 core.src.lib.aggregate-root.aggregate-root uses core.src.lib.storage.stored-event✕
- Connections
- 1 pair of types, where a type in core.src.lib.aggregate-root.aggregate-root uses a type in core.src.lib.storage.stored-event.
- The types involved
libs.core.src.lib.aggregate-root.aggregate-root.AggregateRoot→libs.core.src.lib.storage.stored-event.StoredEvent
- Direction
- core.src.lib.aggregate-root.aggregate-root uses core.src.lib.storage.stored-event, so a change to core.src.lib.storage.stored-event can break core.src.lib.aggregate-root.aggregate-root, while a change to core.src.lib.aggregate-root.aggregate-root can't break core.src.lib.storage.stored-event.
- Position
- Below the diagonal: core.src.lib.aggregate-root.aggregate-root uses a module listed above it, which is the healthy direction.
13→3 core.src.lib.on-domain-event uses core.src.lib.published-domain-event✕
- Connections
- 1 pair of types, where a type in core.src.lib.on-domain-event uses a type in core.src.lib.published-domain-event.
- The types involved
libs.core.src.lib.on-domain-event.OnDomainEvent→libs.core.src.lib.published-domain-event.PublishedDomainEvent
- Direction
- core.src.lib.on-domain-event uses core.src.lib.published-domain-event, so a change to core.src.lib.published-domain-event can break core.src.lib.on-domain-event, while a change to core.src.lib.on-domain-event can't break core.src.lib.published-domain-event.
- Position
- Below the diagonal: core.src.lib.on-domain-event uses a module listed above it, which is the healthy direction.
14→5 core.src.lib.storage.event-store uses core.src.lib.storage.stored-aggregate-root✕
- Connections
- 1 pair of types, where a type in core.src.lib.storage.event-store uses a type in core.src.lib.storage.stored-aggregate-root.
- The types involved
libs.core.src.lib.storage.event-store.EventStore→libs.core.src.lib.storage.stored-aggregate-root.StoredAggregateRoot
- Direction
- core.src.lib.storage.event-store uses core.src.lib.storage.stored-aggregate-root, so a change to core.src.lib.storage.stored-aggregate-root can break core.src.lib.storage.event-store, while a change to core.src.lib.storage.event-store can't break core.src.lib.storage.stored-aggregate-root.
- Position
- Below the diagonal: core.src.lib.storage.event-store uses a module listed above it, which is the healthy direction.
14→6 core.src.lib.storage.event-store uses core.src.lib.storage.stored-event✕
- Connections
- 1 pair of types, where a type in core.src.lib.storage.event-store uses a type in core.src.lib.storage.stored-event.
- The types involved
libs.core.src.lib.storage.event-store.EventStore→libs.core.src.lib.storage.stored-event.StoredEvent
- Direction
- core.src.lib.storage.event-store uses core.src.lib.storage.stored-event, so a change to core.src.lib.storage.stored-event can break core.src.lib.storage.event-store, while a change to core.src.lib.storage.event-store can't break core.src.lib.storage.stored-event.
- Position
- Below the diagonal: core.src.lib.storage.event-store uses a module listed above it, which is the healthy direction.
15→7 mongodb.src.lib.module-providers uses mongodb.src.lib.mongodb-module-options✕
- Connections
- 1 pair of types, where a type in mongodb.src.lib.module-providers uses a type in mongodb.src.lib.mongodb-module-options.
- The types involved
libs.mongodb.src.lib.module-providers.ModuleProviders→libs.mongodb.src.lib.mongodb-module-options.MongoDbModuleAsyncOptions
- Direction
- mongodb.src.lib.module-providers uses mongodb.src.lib.mongodb-module-options, so a change to mongodb.src.lib.mongodb-module-options can break mongodb.src.lib.module-providers, while a change to mongodb.src.lib.module-providers can't break mongodb.src.lib.mongodb-module-options.
- Position
- Below the diagonal: mongodb.src.lib.module-providers uses a module listed above it, which is the healthy direction.
16→8 mssql.src.lib.module-providers uses mssql.src.lib.mssql-module-options✕
- Connections
- 1 pair of types, where a type in mssql.src.lib.module-providers uses a type in mssql.src.lib.mssql-module-options.
- The types involved
libs.mssql.src.lib.module-providers.ModuleProviders→libs.mssql.src.lib.mssql-module-options.MSSQLModuleAsyncOptions
- Direction
- mssql.src.lib.module-providers uses mssql.src.lib.mssql-module-options, so a change to mssql.src.lib.mssql-module-options can break mssql.src.lib.module-providers, while a change to mssql.src.lib.module-providers can't break mssql.src.lib.mssql-module-options.
- Position
- Below the diagonal: mssql.src.lib.module-providers uses a module listed above it, which is the healthy direction.
17→13 core.src.lib uses core.src.lib.on-domain-event✕
- Connections
- 1 pair of types, where a type in core.src.lib uses a type in core.src.lib.on-domain-event.
- The types involved
libs.core.src.lib.domain-event-subscription→libs.core.src.lib.on-domain-event.OnDomainEvent
- Direction
- core.src.lib uses core.src.lib.on-domain-event, so a change to core.src.lib.on-domain-event can break core.src.lib, while a change to core.src.lib can't break core.src.lib.on-domain-event.
- Position
- Below the diagonal: core.src.lib uses a module listed above it, which is the healthy direction.
18→1 core.src.lib.aggregate-root uses core.src.lib.aggregate-root.aggregate-root-config✕
- Connections
- 1 pair of types, where a type in core.src.lib.aggregate-root uses a type in core.src.lib.aggregate-root.aggregate-root-config.
- The types involved
libs.core.src.lib.aggregate-root.aggregate-root-config→libs.core.src.lib.aggregate-root.aggregate-root-config.AggregateRootConfigParameters
- Direction
- core.src.lib.aggregate-root uses core.src.lib.aggregate-root.aggregate-root-config, so a change to core.src.lib.aggregate-root.aggregate-root-config can break core.src.lib.aggregate-root, while a change to core.src.lib.aggregate-root can't break core.src.lib.aggregate-root.aggregate-root-config.
- Position
- Below the diagonal: core.src.lib.aggregate-root uses a module listed above it, which is the healthy direction.
18→12 core.src.lib.aggregate-root uses core.src.lib.aggregate-root.aggregate-root✕
- Connections
- 2 pairs of types, where a type in core.src.lib.aggregate-root uses a type in core.src.lib.aggregate-root.aggregate-root.
- The types involved
libs.core.src.lib.aggregate-root.reflection→libs.core.src.lib.aggregate-root.aggregate-root.AggregateRootlibs.core.src.lib.aggregate-root.snapshot-aware→libs.core.src.lib.aggregate-root.aggregate-root.AggregateRoot
- Direction
- core.src.lib.aggregate-root uses core.src.lib.aggregate-root.aggregate-root, so a change to core.src.lib.aggregate-root.aggregate-root can break core.src.lib.aggregate-root, while a change to core.src.lib.aggregate-root can't break core.src.lib.aggregate-root.aggregate-root.
- Position
- Below the diagonal: core.src.lib.aggregate-root uses a module listed above it, which is the healthy direction.
19→13 core.src.lib.domain-event-emitter uses core.src.lib.on-domain-event✕
- Connections
- 1 pair of types, where a type in core.src.lib.domain-event-emitter uses a type in core.src.lib.on-domain-event.
- The types involved
libs.core.src.lib.domain-event-emitter.DomainEventEmitter→libs.core.src.lib.on-domain-event.OnDomainEvent
- Direction
- core.src.lib.domain-event-emitter uses core.src.lib.on-domain-event, so a change to core.src.lib.on-domain-event can break core.src.lib.domain-event-emitter, while a change to core.src.lib.domain-event-emitter can't break core.src.lib.on-domain-event.
- Position
- Below the diagonal: core.src.lib.domain-event-emitter uses a module listed above it, which is the healthy direction.
20→12 core.src.lib.snapshot-strategy.snapshot-strategy uses core.src.lib.aggregate-root.aggregate-root✕
- Connections
- 1 pair of types, where a type in core.src.lib.snapshot-strategy.snapshot-strategy uses a type in core.src.lib.aggregate-root.aggregate-root.
- The types involved
libs.core.src.lib.snapshot-strategy.snapshot-strategy.SnapshotStrategy→libs.core.src.lib.aggregate-root.aggregate-root.AggregateRoot
- Direction
- core.src.lib.snapshot-strategy.snapshot-strategy uses core.src.lib.aggregate-root.aggregate-root, so a change to core.src.lib.aggregate-root.aggregate-root can break core.src.lib.snapshot-strategy.snapshot-strategy, while a change to core.src.lib.snapshot-strategy.snapshot-strategy can't break core.src.lib.aggregate-root.aggregate-root.
- Position
- Below the diagonal: core.src.lib.snapshot-strategy.snapshot-strategy uses a module listed above it, which is the healthy direction.
21→14 core.src.lib.storage.aggregate-repository uses core.src.lib.storage.event-store✕
- Connections
- 1 pair of types, where a type in core.src.lib.storage.aggregate-repository uses a type in core.src.lib.storage.event-store.
- The types involved
libs.core.src.lib.storage.aggregate-repository.AggregateRepository→libs.core.src.lib.storage.event-store.EventStore
- Direction
- core.src.lib.storage.aggregate-repository uses core.src.lib.storage.event-store, so a change to core.src.lib.storage.event-store can break core.src.lib.storage.aggregate-repository, while a change to core.src.lib.storage.aggregate-repository can't break core.src.lib.storage.event-store.
- Position
- Below the diagonal: core.src.lib.storage.aggregate-repository uses a module listed above it, which is the healthy direction.
22→4 core.src.lib.storage.snapshot.snapshot-store uses core.src.lib.storage.snapshot.stored-snapshot✕
- Connections
- 1 pair of types, where a type in core.src.lib.storage.snapshot.snapshot-store uses a type in core.src.lib.storage.snapshot.stored-snapshot.
- The types involved
libs.core.src.lib.storage.snapshot.snapshot-store.SnapshotStore→libs.core.src.lib.storage.snapshot.stored-snapshot.StoredSnapshot
- Direction
- core.src.lib.storage.snapshot.snapshot-store uses core.src.lib.storage.snapshot.stored-snapshot, so a change to core.src.lib.storage.snapshot.stored-snapshot can break core.src.lib.storage.snapshot.snapshot-store, while a change to core.src.lib.storage.snapshot.snapshot-store can't break core.src.lib.storage.snapshot.stored-snapshot.
- Position
- Below the diagonal: core.src.lib.storage.snapshot.snapshot-store uses a module listed above it, which is the healthy direction.
22→12 core.src.lib.storage.snapshot.snapshot-store uses core.src.lib.aggregate-root.aggregate-root✕
- Connections
- 1 pair of types, where a type in core.src.lib.storage.snapshot.snapshot-store uses a type in core.src.lib.aggregate-root.aggregate-root.
- The types involved
libs.core.src.lib.storage.snapshot.snapshot-store.SnapshotStore→libs.core.src.lib.aggregate-root.aggregate-root.AggregateRoot
- Direction
- core.src.lib.storage.snapshot.snapshot-store uses core.src.lib.aggregate-root.aggregate-root, so a change to core.src.lib.aggregate-root.aggregate-root can break core.src.lib.storage.snapshot.snapshot-store, while a change to core.src.lib.storage.snapshot.snapshot-store can't break core.src.lib.aggregate-root.aggregate-root.
- Position
- Below the diagonal: core.src.lib.storage.snapshot.snapshot-store uses a module listed above it, which is the healthy direction.
23→12 core.src.lib.snapshot-strategy.all-of-snapshot-strategy uses core.src.lib.aggregate-root.aggregate-root✕
- Connections
- 1 pair of types, where a type in core.src.lib.snapshot-strategy.all-of-snapshot-strategy uses a type in core.src.lib.aggregate-root.aggregate-root.
- The types involved
libs.core.src.lib.snapshot-strategy.all-of-snapshot-strategy.AllOfSnapshotStrategy→libs.core.src.lib.aggregate-root.aggregate-root.AggregateRoot
- Direction
- core.src.lib.snapshot-strategy.all-of-snapshot-strategy uses core.src.lib.aggregate-root.aggregate-root, so a change to core.src.lib.aggregate-root.aggregate-root can break core.src.lib.snapshot-strategy.all-of-snapshot-strategy, while a change to core.src.lib.snapshot-strategy.all-of-snapshot-strategy can't break core.src.lib.aggregate-root.aggregate-root.
- Position
- Below the diagonal: core.src.lib.snapshot-strategy.all-of-snapshot-strategy uses a module listed above it, which is the healthy direction.
23→20 core.src.lib.snapshot-strategy.all-of-snapshot-strategy uses core.src.lib.snapshot-strategy.snapshot-strategy✕
- Connections
- 1 pair of types, where a type in core.src.lib.snapshot-strategy.all-of-snapshot-strategy uses a type in core.src.lib.snapshot-strategy.snapshot-strategy.
- The types involved
libs.core.src.lib.snapshot-strategy.all-of-snapshot-strategy.AllOfSnapshotStrategy→libs.core.src.lib.snapshot-strategy.snapshot-strategy.SnapshotStrategy
- Direction
- core.src.lib.snapshot-strategy.all-of-snapshot-strategy uses core.src.lib.snapshot-strategy.snapshot-strategy, so a change to core.src.lib.snapshot-strategy.snapshot-strategy can break core.src.lib.snapshot-strategy.all-of-snapshot-strategy, while a change to core.src.lib.snapshot-strategy.all-of-snapshot-strategy can't break core.src.lib.snapshot-strategy.snapshot-strategy.
- Position
- Below the diagonal: core.src.lib.snapshot-strategy.all-of-snapshot-strategy uses a module listed above it, which is the healthy direction.
24→12 core.src.lib.snapshot-strategy.any-of-snapshot-strategy uses core.src.lib.aggregate-root.aggregate-root✕
- Connections
- 1 pair of types, where a type in core.src.lib.snapshot-strategy.any-of-snapshot-strategy uses a type in core.src.lib.aggregate-root.aggregate-root.
- The types involved
libs.core.src.lib.snapshot-strategy.any-of-snapshot-strategy.AnyOfSnapshotStrategy→libs.core.src.lib.aggregate-root.aggregate-root.AggregateRoot
- Direction
- core.src.lib.snapshot-strategy.any-of-snapshot-strategy uses core.src.lib.aggregate-root.aggregate-root, so a change to core.src.lib.aggregate-root.aggregate-root can break core.src.lib.snapshot-strategy.any-of-snapshot-strategy, while a change to core.src.lib.snapshot-strategy.any-of-snapshot-strategy can't break core.src.lib.aggregate-root.aggregate-root.
- Position
- Below the diagonal: core.src.lib.snapshot-strategy.any-of-snapshot-strategy uses a module listed above it, which is the healthy direction.
24→20 core.src.lib.snapshot-strategy.any-of-snapshot-strategy uses core.src.lib.snapshot-strategy.snapshot-strategy✕
- Connections
- 1 pair of types, where a type in core.src.lib.snapshot-strategy.any-of-snapshot-strategy uses a type in core.src.lib.snapshot-strategy.snapshot-strategy.
- The types involved
libs.core.src.lib.snapshot-strategy.any-of-snapshot-strategy.AnyOfSnapshotStrategy→libs.core.src.lib.snapshot-strategy.snapshot-strategy.SnapshotStrategy
- Direction
- core.src.lib.snapshot-strategy.any-of-snapshot-strategy uses core.src.lib.snapshot-strategy.snapshot-strategy, so a change to core.src.lib.snapshot-strategy.snapshot-strategy can break core.src.lib.snapshot-strategy.any-of-snapshot-strategy, while a change to core.src.lib.snapshot-strategy.any-of-snapshot-strategy can't break core.src.lib.snapshot-strategy.snapshot-strategy.
- Position
- Below the diagonal: core.src.lib.snapshot-strategy.any-of-snapshot-strategy uses a module listed above it, which is the healthy direction.
25→12 core.src.lib.snapshot-strategy.for-aggregate-roots-strategy uses core.src.lib.aggregate-root.aggregate-root✕
- Connections
- 1 pair of types, where a type in core.src.lib.snapshot-strategy.for-aggregate-roots-strategy uses a type in core.src.lib.aggregate-root.aggregate-root.
- The types involved
libs.core.src.lib.snapshot-strategy.for-aggregate-roots-strategy.ForAggregateRootsStrategy→libs.core.src.lib.aggregate-root.aggregate-root.AggregateRoot
- Direction
- core.src.lib.snapshot-strategy.for-aggregate-roots-strategy uses core.src.lib.aggregate-root.aggregate-root, so a change to core.src.lib.aggregate-root.aggregate-root can break core.src.lib.snapshot-strategy.for-aggregate-roots-strategy, while a change to core.src.lib.snapshot-strategy.for-aggregate-roots-strategy can't break core.src.lib.aggregate-root.aggregate-root.
- Position
- Below the diagonal: core.src.lib.snapshot-strategy.for-aggregate-roots-strategy uses a module listed above it, which is the healthy direction.
25→20 core.src.lib.snapshot-strategy.for-aggregate-roots-strategy uses core.src.lib.snapshot-strategy.snapshot-strategy✕
- Connections
- 1 pair of types, where a type in core.src.lib.snapshot-strategy.for-aggregate-roots-strategy uses a type in core.src.lib.snapshot-strategy.snapshot-strategy.
- The types involved
libs.core.src.lib.snapshot-strategy.for-aggregate-roots-strategy.ForAggregateRootsStrategy→libs.core.src.lib.snapshot-strategy.snapshot-strategy.SnapshotStrategy
- Direction
- core.src.lib.snapshot-strategy.for-aggregate-roots-strategy uses core.src.lib.snapshot-strategy.snapshot-strategy, so a change to core.src.lib.snapshot-strategy.snapshot-strategy can break core.src.lib.snapshot-strategy.for-aggregate-roots-strategy, while a change to core.src.lib.snapshot-strategy.for-aggregate-roots-strategy can't break core.src.lib.snapshot-strategy.snapshot-strategy.
- Position
- Below the diagonal: core.src.lib.snapshot-strategy.for-aggregate-roots-strategy uses a module listed above it, which is the healthy direction.
26→12 core.src.lib.snapshot-strategy.for-count-snapshot-strategy uses core.src.lib.aggregate-root.aggregate-root✕
- Connections
- 1 pair of types, where a type in core.src.lib.snapshot-strategy.for-count-snapshot-strategy uses a type in core.src.lib.aggregate-root.aggregate-root.
- The types involved
libs.core.src.lib.snapshot-strategy.for-count-snapshot-strategy.ForCountSnapshotStrategy→libs.core.src.lib.aggregate-root.aggregate-root.AggregateRoot
- Direction
- core.src.lib.snapshot-strategy.for-count-snapshot-strategy uses core.src.lib.aggregate-root.aggregate-root, so a change to core.src.lib.aggregate-root.aggregate-root can break core.src.lib.snapshot-strategy.for-count-snapshot-strategy, while a change to core.src.lib.snapshot-strategy.for-count-snapshot-strategy can't break core.src.lib.aggregate-root.aggregate-root.
- Position
- Below the diagonal: core.src.lib.snapshot-strategy.for-count-snapshot-strategy uses a module listed above it, which is the healthy direction.
26→20 core.src.lib.snapshot-strategy.for-count-snapshot-strategy uses core.src.lib.snapshot-strategy.snapshot-strategy✕
- Connections
- 1 pair of types, where a type in core.src.lib.snapshot-strategy.for-count-snapshot-strategy uses a type in core.src.lib.snapshot-strategy.snapshot-strategy.
- The types involved
libs.core.src.lib.snapshot-strategy.for-count-snapshot-strategy.ForCountSnapshotStrategy→libs.core.src.lib.snapshot-strategy.snapshot-strategy.SnapshotStrategy
- Direction
- core.src.lib.snapshot-strategy.for-count-snapshot-strategy uses core.src.lib.snapshot-strategy.snapshot-strategy, so a change to core.src.lib.snapshot-strategy.snapshot-strategy can break core.src.lib.snapshot-strategy.for-count-snapshot-strategy, while a change to core.src.lib.snapshot-strategy.for-count-snapshot-strategy can't break core.src.lib.snapshot-strategy.snapshot-strategy.
- Position
- Below the diagonal: core.src.lib.snapshot-strategy.for-count-snapshot-strategy uses a module listed above it, which is the healthy direction.
27→12 core.src.lib.snapshot-strategy.for-events-snapshot-strategy uses core.src.lib.aggregate-root.aggregate-root✕
- Connections
- 1 pair of types, where a type in core.src.lib.snapshot-strategy.for-events-snapshot-strategy uses a type in core.src.lib.aggregate-root.aggregate-root.
- The types involved
libs.core.src.lib.snapshot-strategy.for-events-snapshot-strategy.ForEventsSnapshotStrategy→libs.core.src.lib.aggregate-root.aggregate-root.AggregateRoot
- Direction
- core.src.lib.snapshot-strategy.for-events-snapshot-strategy uses core.src.lib.aggregate-root.aggregate-root, so a change to core.src.lib.aggregate-root.aggregate-root can break core.src.lib.snapshot-strategy.for-events-snapshot-strategy, while a change to core.src.lib.snapshot-strategy.for-events-snapshot-strategy can't break core.src.lib.aggregate-root.aggregate-root.
- Position
- Below the diagonal: core.src.lib.snapshot-strategy.for-events-snapshot-strategy uses a module listed above it, which is the healthy direction.
27→20 core.src.lib.snapshot-strategy.for-events-snapshot-strategy uses core.src.lib.snapshot-strategy.snapshot-strategy✕
- Connections
- 1 pair of types, where a type in core.src.lib.snapshot-strategy.for-events-snapshot-strategy uses a type in core.src.lib.snapshot-strategy.snapshot-strategy.
- The types involved
libs.core.src.lib.snapshot-strategy.for-events-snapshot-strategy.ForEventsSnapshotStrategy→libs.core.src.lib.snapshot-strategy.snapshot-strategy.SnapshotStrategy
- Direction
- core.src.lib.snapshot-strategy.for-events-snapshot-strategy uses core.src.lib.snapshot-strategy.snapshot-strategy, so a change to core.src.lib.snapshot-strategy.snapshot-strategy can break core.src.lib.snapshot-strategy.for-events-snapshot-strategy, while a change to core.src.lib.snapshot-strategy.for-events-snapshot-strategy can't break core.src.lib.snapshot-strategy.snapshot-strategy.
- Position
- Below the diagonal: core.src.lib.snapshot-strategy.for-events-snapshot-strategy uses a module listed above it, which is the healthy direction.
28→20 core.src.lib.snapshot-strategy.no-snapshot-strategy uses core.src.lib.snapshot-strategy.snapshot-strategy✕
- Connections
- 1 pair of types, where a type in core.src.lib.snapshot-strategy.no-snapshot-strategy uses a type in core.src.lib.snapshot-strategy.snapshot-strategy.
- The types involved
libs.core.src.lib.snapshot-strategy.no-snapshot-strategy.NoSnapshotStrategy→libs.core.src.lib.snapshot-strategy.snapshot-strategy.SnapshotStrategy
- Direction
- core.src.lib.snapshot-strategy.no-snapshot-strategy uses core.src.lib.snapshot-strategy.snapshot-strategy, so a change to core.src.lib.snapshot-strategy.snapshot-strategy can break core.src.lib.snapshot-strategy.no-snapshot-strategy, while a change to core.src.lib.snapshot-strategy.no-snapshot-strategy can't break core.src.lib.snapshot-strategy.snapshot-strategy.
- Position
- Below the diagonal: core.src.lib.snapshot-strategy.no-snapshot-strategy uses a module listed above it, which is the healthy direction.
29→4 core.src.lib.storage.snapshot.abstract-snapshot-store uses core.src.lib.storage.snapshot.stored-snapshot✕
- Connections
- 1 pair of types, where a type in core.src.lib.storage.snapshot.abstract-snapshot-store uses a type in core.src.lib.storage.snapshot.stored-snapshot.
- The types involved
libs.core.src.lib.storage.snapshot.abstract-snapshot-store.AbstractSnapshotStore→libs.core.src.lib.storage.snapshot.stored-snapshot.StoredSnapshot
- Direction
- core.src.lib.storage.snapshot.abstract-snapshot-store uses core.src.lib.storage.snapshot.stored-snapshot, so a change to core.src.lib.storage.snapshot.stored-snapshot can break core.src.lib.storage.snapshot.abstract-snapshot-store, while a change to core.src.lib.storage.snapshot.abstract-snapshot-store can't break core.src.lib.storage.snapshot.stored-snapshot.
- Position
- Below the diagonal: core.src.lib.storage.snapshot.abstract-snapshot-store uses a module listed above it, which is the healthy direction.
29→12 core.src.lib.storage.snapshot.abstract-snapshot-store uses core.src.lib.aggregate-root.aggregate-root✕
- Connections
- 1 pair of types, where a type in core.src.lib.storage.snapshot.abstract-snapshot-store uses a type in core.src.lib.aggregate-root.aggregate-root.
- The types involved
libs.core.src.lib.storage.snapshot.abstract-snapshot-store.AbstractSnapshotStore→libs.core.src.lib.aggregate-root.aggregate-root.AggregateRoot
- Direction
- core.src.lib.storage.snapshot.abstract-snapshot-store uses core.src.lib.aggregate-root.aggregate-root, so a change to core.src.lib.aggregate-root.aggregate-root can break core.src.lib.storage.snapshot.abstract-snapshot-store, while a change to core.src.lib.storage.snapshot.abstract-snapshot-store can't break core.src.lib.aggregate-root.aggregate-root.
- Position
- Below the diagonal: core.src.lib.storage.snapshot.abstract-snapshot-store uses a module listed above it, which is the healthy direction.
29→20 core.src.lib.storage.snapshot.abstract-snapshot-store uses core.src.lib.snapshot-strategy.snapshot-strategy✕
- Connections
- 1 pair of types, where a type in core.src.lib.storage.snapshot.abstract-snapshot-store uses a type in core.src.lib.snapshot-strategy.snapshot-strategy.
- The types involved
libs.core.src.lib.storage.snapshot.abstract-snapshot-store.AbstractSnapshotStore→libs.core.src.lib.snapshot-strategy.snapshot-strategy.SnapshotStrategy
- Direction
- core.src.lib.storage.snapshot.abstract-snapshot-store uses core.src.lib.snapshot-strategy.snapshot-strategy, so a change to core.src.lib.snapshot-strategy.snapshot-strategy can break core.src.lib.storage.snapshot.abstract-snapshot-store, while a change to core.src.lib.storage.snapshot.abstract-snapshot-store can't break core.src.lib.snapshot-strategy.snapshot-strategy.
- Position
- Below the diagonal: core.src.lib.storage.snapshot.abstract-snapshot-store uses a module listed above it, which is the healthy direction.
29→22 core.src.lib.storage.snapshot.abstract-snapshot-store uses core.src.lib.storage.snapshot.snapshot-store✕
- Connections
- 1 pair of types, where a type in core.src.lib.storage.snapshot.abstract-snapshot-store uses a type in core.src.lib.storage.snapshot.snapshot-store.
- The types involved
libs.core.src.lib.storage.snapshot.abstract-snapshot-store.AbstractSnapshotStore→libs.core.src.lib.storage.snapshot.snapshot-store.SnapshotStore
- Direction
- core.src.lib.storage.snapshot.abstract-snapshot-store uses core.src.lib.storage.snapshot.snapshot-store, so a change to core.src.lib.storage.snapshot.snapshot-store can break core.src.lib.storage.snapshot.abstract-snapshot-store, while a change to core.src.lib.storage.snapshot.abstract-snapshot-store can't break core.src.lib.storage.snapshot.snapshot-store.
- Position
- Below the diagonal: core.src.lib.storage.snapshot.abstract-snapshot-store uses a module listed above it, which is the healthy direction.
30→7 mongodb.src.lib.event-nest-mongodb_module uses mongodb.src.lib.mongodb-module-options✕
- Connections
- 1 pair of types, where a type in mongodb.src.lib.event-nest-mongodb_module uses a type in mongodb.src.lib.mongodb-module-options.
- The types involved
libs.mongodb.src.lib.event-nest-mongodb_module.EventNestMongoDbModule→libs.mongodb.src.lib.mongodb-module-options.MongoDbModuleAsyncOptions
- Direction
- mongodb.src.lib.event-nest-mongodb_module uses mongodb.src.lib.mongodb-module-options, so a change to mongodb.src.lib.mongodb-module-options can break mongodb.src.lib.event-nest-mongodb_module, while a change to mongodb.src.lib.event-nest-mongodb_module can't break mongodb.src.lib.mongodb-module-options.
- Position
- Below the diagonal: mongodb.src.lib.event-nest-mongodb_module uses a module listed above it, which is the healthy direction.
30→19 mongodb.src.lib.event-nest-mongodb_module uses core.src.lib.domain-event-emitter✕
- Connections
- 1 pair of types, where a type in mongodb.src.lib.event-nest-mongodb_module uses a type in core.src.lib.domain-event-emitter.
- The types involved
libs.mongodb.src.lib.event-nest-mongodb_module.EventNestMongoDbModule→libs.core.src.lib.domain-event-emitter.DomainEventEmitter
- Direction
- mongodb.src.lib.event-nest-mongodb_module uses core.src.lib.domain-event-emitter, so a change to core.src.lib.domain-event-emitter can break mongodb.src.lib.event-nest-mongodb_module, while a change to mongodb.src.lib.event-nest-mongodb_module can't break core.src.lib.domain-event-emitter.
- Position
- Below the diagonal: mongodb.src.lib.event-nest-mongodb_module uses a module listed above it, which is the healthy direction.
31→8 mssql.src.lib.event-nest-mssql_module uses mssql.src.lib.mssql-module-options✕
- Connections
- 1 pair of types, where a type in mssql.src.lib.event-nest-mssql_module uses a type in mssql.src.lib.mssql-module-options.
- The types involved
libs.mssql.src.lib.event-nest-mssql_module.EventNestMSSQLModule→libs.mssql.src.lib.mssql-module-options.MSSQLModuleAsyncOptions
- Direction
- mssql.src.lib.event-nest-mssql_module uses mssql.src.lib.mssql-module-options, so a change to mssql.src.lib.mssql-module-options can break mssql.src.lib.event-nest-mssql_module, while a change to mssql.src.lib.event-nest-mssql_module can't break mssql.src.lib.mssql-module-options.
- Position
- Below the diagonal: mssql.src.lib.event-nest-mssql_module uses a module listed above it, which is the healthy direction.
31→19 mssql.src.lib.event-nest-mssql_module uses core.src.lib.domain-event-emitter✕
- Connections
- 1 pair of types, where a type in mssql.src.lib.event-nest-mssql_module uses a type in core.src.lib.domain-event-emitter.
- The types involved
libs.mssql.src.lib.event-nest-mssql_module.EventNestMSSQLModule→libs.core.src.lib.domain-event-emitter.DomainEventEmitter
- Direction
- mssql.src.lib.event-nest-mssql_module uses core.src.lib.domain-event-emitter, so a change to core.src.lib.domain-event-emitter can break mssql.src.lib.event-nest-mssql_module, while a change to mssql.src.lib.event-nest-mssql_module can't break core.src.lib.domain-event-emitter.
- Position
- Below the diagonal: mssql.src.lib.event-nest-mssql_module uses a module listed above it, which is the healthy direction.
32→11 postgresql.src.lib.event-nest-postgresql_module uses postgresql.src.lib.postgresql-module-options✕
- Connections
- 1 pair of types, where a type in postgresql.src.lib.event-nest-postgresql_module uses a type in postgresql.src.lib.postgresql-module-options.
- The types involved
libs.postgresql.src.lib.event-nest-postgresql_module.EventNestPostgreSQLModule→libs.postgresql.src.lib.postgresql-module-options.PostgreSQLModuleAsyncOptions
- Direction
- postgresql.src.lib.event-nest-postgresql_module uses postgresql.src.lib.postgresql-module-options, so a change to postgresql.src.lib.postgresql-module-options can break postgresql.src.lib.event-nest-postgresql_module, while a change to postgresql.src.lib.event-nest-postgresql_module can't break postgresql.src.lib.postgresql-module-options.
- Position
- Below the diagonal: postgresql.src.lib.event-nest-postgresql_module uses a module listed above it, which is the healthy direction.
32→19 postgresql.src.lib.event-nest-postgresql_module uses core.src.lib.domain-event-emitter✕
- Connections
- 1 pair of types, where a type in postgresql.src.lib.event-nest-postgresql_module uses a type in core.src.lib.domain-event-emitter.
- The types involved
libs.postgresql.src.lib.event-nest-postgresql_module.EventNestPostgreSQLModule→libs.core.src.lib.domain-event-emitter.DomainEventEmitter
- Direction
- postgresql.src.lib.event-nest-postgresql_module uses core.src.lib.domain-event-emitter, so a change to core.src.lib.domain-event-emitter can break postgresql.src.lib.event-nest-postgresql_module, while a change to postgresql.src.lib.event-nest-postgresql_module can't break core.src.lib.domain-event-emitter.
- Position
- Below the diagonal: postgresql.src.lib.event-nest-postgresql_module uses a module listed above it, which is the healthy direction.
33→5 core.src.lib.storage.abstract-event-store uses core.src.lib.storage.stored-aggregate-root✕
- Connections
- 1 pair of types, where a type in core.src.lib.storage.abstract-event-store uses a type in core.src.lib.storage.stored-aggregate-root.
- The types involved
libs.core.src.lib.storage.abstract-event-store.AbstractEventStore→libs.core.src.lib.storage.stored-aggregate-root.StoredAggregateRoot
- Direction
- core.src.lib.storage.abstract-event-store uses core.src.lib.storage.stored-aggregate-root, so a change to core.src.lib.storage.stored-aggregate-root can break core.src.lib.storage.abstract-event-store, while a change to core.src.lib.storage.abstract-event-store can't break core.src.lib.storage.stored-aggregate-root.
- Position
- Below the diagonal: core.src.lib.storage.abstract-event-store uses a module listed above it, which is the healthy direction.
33→6 core.src.lib.storage.abstract-event-store uses core.src.lib.storage.stored-event✕
- Connections
- 1 pair of types, where a type in core.src.lib.storage.abstract-event-store uses a type in core.src.lib.storage.stored-event.
- The types involved
libs.core.src.lib.storage.abstract-event-store.AbstractEventStore→libs.core.src.lib.storage.stored-event.StoredEvent
- Direction
- core.src.lib.storage.abstract-event-store uses core.src.lib.storage.stored-event, so a change to core.src.lib.storage.stored-event can break core.src.lib.storage.abstract-event-store, while a change to core.src.lib.storage.abstract-event-store can't break core.src.lib.storage.stored-event.
- Position
- Below the diagonal: core.src.lib.storage.abstract-event-store uses a module listed above it, which is the healthy direction.
33→14 core.src.lib.storage.abstract-event-store uses core.src.lib.storage.event-store✕
- Connections
- 1 pair of types, where a type in core.src.lib.storage.abstract-event-store uses a type in core.src.lib.storage.event-store.
- The types involved
libs.core.src.lib.storage.abstract-event-store.AbstractEventStore→libs.core.src.lib.storage.event-store.EventStore
- Direction
- core.src.lib.storage.abstract-event-store uses core.src.lib.storage.event-store, so a change to core.src.lib.storage.event-store can break core.src.lib.storage.abstract-event-store, while a change to core.src.lib.storage.abstract-event-store can't break core.src.lib.storage.event-store.
- Position
- Below the diagonal: core.src.lib.storage.abstract-event-store uses a module listed above it, which is the healthy direction.
33→19 core.src.lib.storage.abstract-event-store uses core.src.lib.domain-event-emitter✕
- Connections
- 1 pair of types, where a type in core.src.lib.storage.abstract-event-store uses a type in core.src.lib.domain-event-emitter.
- The types involved
libs.core.src.lib.storage.abstract-event-store.AbstractEventStore→libs.core.src.lib.domain-event-emitter.DomainEventEmitter
- Direction
- core.src.lib.storage.abstract-event-store uses core.src.lib.domain-event-emitter, so a change to core.src.lib.domain-event-emitter can break core.src.lib.storage.abstract-event-store, while a change to core.src.lib.storage.abstract-event-store can't break core.src.lib.domain-event-emitter.
- Position
- Below the diagonal: core.src.lib.storage.abstract-event-store uses a module listed above it, which is the healthy direction.
33→29 core.src.lib.storage.abstract-event-store uses core.src.lib.storage.snapshot.abstract-snapshot-store✕
- Connections
- 1 pair of types, where a type in core.src.lib.storage.abstract-event-store uses a type in core.src.lib.storage.snapshot.abstract-snapshot-store.
- The types involved
libs.core.src.lib.storage.abstract-event-store.AbstractEventStore→libs.core.src.lib.storage.snapshot.abstract-snapshot-store.AbstractSnapshotStore
- Direction
- core.src.lib.storage.abstract-event-store uses core.src.lib.storage.snapshot.abstract-snapshot-store, so a change to core.src.lib.storage.snapshot.abstract-snapshot-store can break core.src.lib.storage.abstract-event-store, while a change to core.src.lib.storage.abstract-event-store can't break core.src.lib.storage.snapshot.abstract-snapshot-store.
- Position
- Below the diagonal: core.src.lib.storage.abstract-event-store uses a module listed above it, which is the healthy direction.
34→29 core.src.lib.storage.snapshot.no-op-snapshot-store uses core.src.lib.storage.snapshot.abstract-snapshot-store✕
- Connections
- 1 pair of types, where a type in core.src.lib.storage.snapshot.no-op-snapshot-store uses a type in core.src.lib.storage.snapshot.abstract-snapshot-store.
- The types involved
libs.core.src.lib.storage.snapshot.no-op-snapshot-store.NoOpSnapshotStore→libs.core.src.lib.storage.snapshot.abstract-snapshot-store.AbstractSnapshotStore
- Direction
- core.src.lib.storage.snapshot.no-op-snapshot-store uses core.src.lib.storage.snapshot.abstract-snapshot-store, so a change to core.src.lib.storage.snapshot.abstract-snapshot-store can break core.src.lib.storage.snapshot.no-op-snapshot-store, while a change to core.src.lib.storage.snapshot.no-op-snapshot-store can't break core.src.lib.storage.snapshot.abstract-snapshot-store.
- Position
- Below the diagonal: core.src.lib.storage.snapshot.no-op-snapshot-store uses a module listed above it, which is the healthy direction.
35→4 mongodb.src.lib.storage.mongo-snapshot-store uses core.src.lib.storage.snapshot.stored-snapshot✕
- Connections
- 1 pair of types, where a type in mongodb.src.lib.storage.mongo-snapshot-store uses a type in core.src.lib.storage.snapshot.stored-snapshot.
- The types involved
libs.mongodb.src.lib.storage.mongo-snapshot-store.MongoSnapshotStore→libs.core.src.lib.storage.snapshot.stored-snapshot.StoredSnapshot
- Direction
- mongodb.src.lib.storage.mongo-snapshot-store uses core.src.lib.storage.snapshot.stored-snapshot, so a change to core.src.lib.storage.snapshot.stored-snapshot can break mongodb.src.lib.storage.mongo-snapshot-store, while a change to mongodb.src.lib.storage.mongo-snapshot-store can't break core.src.lib.storage.snapshot.stored-snapshot.
- Position
- Below the diagonal: mongodb.src.lib.storage.mongo-snapshot-store uses a module listed above it, which is the healthy direction.
35→20 mongodb.src.lib.storage.mongo-snapshot-store uses core.src.lib.snapshot-strategy.snapshot-strategy✕
- Connections
- 1 pair of types, where a type in mongodb.src.lib.storage.mongo-snapshot-store uses a type in core.src.lib.snapshot-strategy.snapshot-strategy.
- The types involved
libs.mongodb.src.lib.storage.mongo-snapshot-store.MongoSnapshotStore→libs.core.src.lib.snapshot-strategy.snapshot-strategy.SnapshotStrategy
- Direction
- mongodb.src.lib.storage.mongo-snapshot-store uses core.src.lib.snapshot-strategy.snapshot-strategy, so a change to core.src.lib.snapshot-strategy.snapshot-strategy can break mongodb.src.lib.storage.mongo-snapshot-store, while a change to mongodb.src.lib.storage.mongo-snapshot-store can't break core.src.lib.snapshot-strategy.snapshot-strategy.
- Position
- Below the diagonal: mongodb.src.lib.storage.mongo-snapshot-store uses a module listed above it, which is the healthy direction.
35→29 mongodb.src.lib.storage.mongo-snapshot-store uses core.src.lib.storage.snapshot.abstract-snapshot-store✕
- Connections
- 1 pair of types, where a type in mongodb.src.lib.storage.mongo-snapshot-store uses a type in core.src.lib.storage.snapshot.abstract-snapshot-store.
- The types involved
libs.mongodb.src.lib.storage.mongo-snapshot-store.MongoSnapshotStore→libs.core.src.lib.storage.snapshot.abstract-snapshot-store.AbstractSnapshotStore
- Direction
- mongodb.src.lib.storage.mongo-snapshot-store uses core.src.lib.storage.snapshot.abstract-snapshot-store, so a change to core.src.lib.storage.snapshot.abstract-snapshot-store can break mongodb.src.lib.storage.mongo-snapshot-store, while a change to mongodb.src.lib.storage.mongo-snapshot-store can't break core.src.lib.storage.snapshot.abstract-snapshot-store.
- Position
- Below the diagonal: mongodb.src.lib.storage.mongo-snapshot-store uses a module listed above it, which is the healthy direction.
36→4 mssql.src.lib.storage.mssql-snapshot-store uses core.src.lib.storage.snapshot.stored-snapshot✕
- Connections
- 1 pair of types, where a type in mssql.src.lib.storage.mssql-snapshot-store uses a type in core.src.lib.storage.snapshot.stored-snapshot.
- The types involved
libs.mssql.src.lib.storage.mssql-snapshot-store.MSSQLSnapshotStore→libs.core.src.lib.storage.snapshot.stored-snapshot.StoredSnapshot
- Direction
- mssql.src.lib.storage.mssql-snapshot-store uses core.src.lib.storage.snapshot.stored-snapshot, so a change to core.src.lib.storage.snapshot.stored-snapshot can break mssql.src.lib.storage.mssql-snapshot-store, while a change to mssql.src.lib.storage.mssql-snapshot-store can't break core.src.lib.storage.snapshot.stored-snapshot.
- Position
- Below the diagonal: mssql.src.lib.storage.mssql-snapshot-store uses a module listed above it, which is the healthy direction.
36→20 mssql.src.lib.storage.mssql-snapshot-store uses core.src.lib.snapshot-strategy.snapshot-strategy✕
- Connections
- 1 pair of types, where a type in mssql.src.lib.storage.mssql-snapshot-store uses a type in core.src.lib.snapshot-strategy.snapshot-strategy.
- The types involved
libs.mssql.src.lib.storage.mssql-snapshot-store.MSSQLSnapshotStore→libs.core.src.lib.snapshot-strategy.snapshot-strategy.SnapshotStrategy
- Direction
- mssql.src.lib.storage.mssql-snapshot-store uses core.src.lib.snapshot-strategy.snapshot-strategy, so a change to core.src.lib.snapshot-strategy.snapshot-strategy can break mssql.src.lib.storage.mssql-snapshot-store, while a change to mssql.src.lib.storage.mssql-snapshot-store can't break core.src.lib.snapshot-strategy.snapshot-strategy.
- Position
- Below the diagonal: mssql.src.lib.storage.mssql-snapshot-store uses a module listed above it, which is the healthy direction.
36→29 mssql.src.lib.storage.mssql-snapshot-store uses core.src.lib.storage.snapshot.abstract-snapshot-store✕
- Connections
- 1 pair of types, where a type in mssql.src.lib.storage.mssql-snapshot-store uses a type in core.src.lib.storage.snapshot.abstract-snapshot-store.
- The types involved
libs.mssql.src.lib.storage.mssql-snapshot-store.MSSQLSnapshotStore→libs.core.src.lib.storage.snapshot.abstract-snapshot-store.AbstractSnapshotStore
- Direction
- mssql.src.lib.storage.mssql-snapshot-store uses core.src.lib.storage.snapshot.abstract-snapshot-store, so a change to core.src.lib.storage.snapshot.abstract-snapshot-store can break mssql.src.lib.storage.mssql-snapshot-store, while a change to mssql.src.lib.storage.mssql-snapshot-store can't break core.src.lib.storage.snapshot.abstract-snapshot-store.
- Position
- Below the diagonal: mssql.src.lib.storage.mssql-snapshot-store uses a module listed above it, which is the healthy direction.
37→4 postgresql.src.lib.storage.postgresql-snapshot-store uses core.src.lib.storage.snapshot.stored-snapshot✕
- Connections
- 1 pair of types, where a type in postgresql.src.lib.storage.postgresql-snapshot-store uses a type in core.src.lib.storage.snapshot.stored-snapshot.
- The types involved
libs.postgresql.src.lib.storage.postgresql-snapshot-store.PostgreSQLSnapshotStore→libs.core.src.lib.storage.snapshot.stored-snapshot.StoredSnapshot
- Direction
- postgresql.src.lib.storage.postgresql-snapshot-store uses core.src.lib.storage.snapshot.stored-snapshot, so a change to core.src.lib.storage.snapshot.stored-snapshot can break postgresql.src.lib.storage.postgresql-snapshot-store, while a change to postgresql.src.lib.storage.postgresql-snapshot-store can't break core.src.lib.storage.snapshot.stored-snapshot.
- Position
- Below the diagonal: postgresql.src.lib.storage.postgresql-snapshot-store uses a module listed above it, which is the healthy direction.
37→20 postgresql.src.lib.storage.postgresql-snapshot-store uses core.src.lib.snapshot-strategy.snapshot-strategy✕
- Connections
- 1 pair of types, where a type in postgresql.src.lib.storage.postgresql-snapshot-store uses a type in core.src.lib.snapshot-strategy.snapshot-strategy.
- The types involved
libs.postgresql.src.lib.storage.postgresql-snapshot-store.PostgreSQLSnapshotStore→libs.core.src.lib.snapshot-strategy.snapshot-strategy.SnapshotStrategy
- Direction
- postgresql.src.lib.storage.postgresql-snapshot-store uses core.src.lib.snapshot-strategy.snapshot-strategy, so a change to core.src.lib.snapshot-strategy.snapshot-strategy can break postgresql.src.lib.storage.postgresql-snapshot-store, while a change to postgresql.src.lib.storage.postgresql-snapshot-store can't break core.src.lib.snapshot-strategy.snapshot-strategy.
- Position
- Below the diagonal: postgresql.src.lib.storage.postgresql-snapshot-store uses a module listed above it, which is the healthy direction.
37→29 postgresql.src.lib.storage.postgresql-snapshot-store uses core.src.lib.storage.snapshot.abstract-snapshot-store✕
- Connections
- 1 pair of types, where a type in postgresql.src.lib.storage.postgresql-snapshot-store uses a type in core.src.lib.storage.snapshot.abstract-snapshot-store.
- The types involved
libs.postgresql.src.lib.storage.postgresql-snapshot-store.PostgreSQLSnapshotStore→libs.core.src.lib.storage.snapshot.abstract-snapshot-store.AbstractSnapshotStore
- Direction
- postgresql.src.lib.storage.postgresql-snapshot-store uses core.src.lib.storage.snapshot.abstract-snapshot-store, so a change to core.src.lib.storage.snapshot.abstract-snapshot-store can break postgresql.src.lib.storage.postgresql-snapshot-store, while a change to postgresql.src.lib.storage.postgresql-snapshot-store can't break core.src.lib.storage.snapshot.abstract-snapshot-store.
- Position
- Below the diagonal: postgresql.src.lib.storage.postgresql-snapshot-store uses a module listed above it, which is the healthy direction.
38→5 mongodb.src.lib.storage.mongo-event-store uses core.src.lib.storage.stored-aggregate-root✕
- Connections
- 1 pair of types, where a type in mongodb.src.lib.storage.mongo-event-store uses a type in core.src.lib.storage.stored-aggregate-root.
- The types involved
libs.mongodb.src.lib.storage.mongo-event-store.MongoEventStore→libs.core.src.lib.storage.stored-aggregate-root.StoredAggregateRoot
- Direction
- mongodb.src.lib.storage.mongo-event-store uses core.src.lib.storage.stored-aggregate-root, so a change to core.src.lib.storage.stored-aggregate-root can break mongodb.src.lib.storage.mongo-event-store, while a change to mongodb.src.lib.storage.mongo-event-store can't break core.src.lib.storage.stored-aggregate-root.
- Position
- Below the diagonal: mongodb.src.lib.storage.mongo-event-store uses a module listed above it, which is the healthy direction.
38→6 mongodb.src.lib.storage.mongo-event-store uses core.src.lib.storage.stored-event✕
- Connections
- 1 pair of types, where a type in mongodb.src.lib.storage.mongo-event-store uses a type in core.src.lib.storage.stored-event.
- The types involved
libs.mongodb.src.lib.storage.mongo-event-store.MongoEventStore→libs.core.src.lib.storage.stored-event.StoredEvent
- Direction
- mongodb.src.lib.storage.mongo-event-store uses core.src.lib.storage.stored-event, so a change to core.src.lib.storage.stored-event can break mongodb.src.lib.storage.mongo-event-store, while a change to mongodb.src.lib.storage.mongo-event-store can't break core.src.lib.storage.stored-event.
- Position
- Below the diagonal: mongodb.src.lib.storage.mongo-event-store uses a module listed above it, which is the healthy direction.
38→19 mongodb.src.lib.storage.mongo-event-store uses core.src.lib.domain-event-emitter✕
- Connections
- 1 pair of types, where a type in mongodb.src.lib.storage.mongo-event-store uses a type in core.src.lib.domain-event-emitter.
- The types involved
libs.mongodb.src.lib.storage.mongo-event-store.MongoEventStore→libs.core.src.lib.domain-event-emitter.DomainEventEmitter
- Direction
- mongodb.src.lib.storage.mongo-event-store uses core.src.lib.domain-event-emitter, so a change to core.src.lib.domain-event-emitter can break mongodb.src.lib.storage.mongo-event-store, while a change to mongodb.src.lib.storage.mongo-event-store can't break core.src.lib.domain-event-emitter.
- Position
- Below the diagonal: mongodb.src.lib.storage.mongo-event-store uses a module listed above it, which is the healthy direction.
38→29 mongodb.src.lib.storage.mongo-event-store uses core.src.lib.storage.snapshot.abstract-snapshot-store✕
- Connections
- 1 pair of types, where a type in mongodb.src.lib.storage.mongo-event-store uses a type in core.src.lib.storage.snapshot.abstract-snapshot-store.
- The types involved
libs.mongodb.src.lib.storage.mongo-event-store.MongoEventStore→libs.core.src.lib.storage.snapshot.abstract-snapshot-store.AbstractSnapshotStore
- Direction
- mongodb.src.lib.storage.mongo-event-store uses core.src.lib.storage.snapshot.abstract-snapshot-store, so a change to core.src.lib.storage.snapshot.abstract-snapshot-store can break mongodb.src.lib.storage.mongo-event-store, while a change to mongodb.src.lib.storage.mongo-event-store can't break core.src.lib.storage.snapshot.abstract-snapshot-store.
- Position
- Below the diagonal: mongodb.src.lib.storage.mongo-event-store uses a module listed above it, which is the healthy direction.
38→33 mongodb.src.lib.storage.mongo-event-store uses core.src.lib.storage.abstract-event-store✕
- Connections
- 1 pair of types, where a type in mongodb.src.lib.storage.mongo-event-store uses a type in core.src.lib.storage.abstract-event-store.
- The types involved
libs.mongodb.src.lib.storage.mongo-event-store.MongoEventStore→libs.core.src.lib.storage.abstract-event-store.AbstractEventStore
- Direction
- mongodb.src.lib.storage.mongo-event-store uses core.src.lib.storage.abstract-event-store, so a change to core.src.lib.storage.abstract-event-store can break mongodb.src.lib.storage.mongo-event-store, while a change to mongodb.src.lib.storage.mongo-event-store can't break core.src.lib.storage.abstract-event-store.
- Position
- Below the diagonal: mongodb.src.lib.storage.mongo-event-store uses a module listed above it, which is the healthy direction.
39→5 mssql.src.lib.storage.mssql-event-store uses core.src.lib.storage.stored-aggregate-root✕
- Connections
- 1 pair of types, where a type in mssql.src.lib.storage.mssql-event-store uses a type in core.src.lib.storage.stored-aggregate-root.
- The types involved
libs.mssql.src.lib.storage.mssql-event-store.MSSQLEventStore→libs.core.src.lib.storage.stored-aggregate-root.StoredAggregateRoot
- Direction
- mssql.src.lib.storage.mssql-event-store uses core.src.lib.storage.stored-aggregate-root, so a change to core.src.lib.storage.stored-aggregate-root can break mssql.src.lib.storage.mssql-event-store, while a change to mssql.src.lib.storage.mssql-event-store can't break core.src.lib.storage.stored-aggregate-root.
- Position
- Below the diagonal: mssql.src.lib.storage.mssql-event-store uses a module listed above it, which is the healthy direction.
39→6 mssql.src.lib.storage.mssql-event-store uses core.src.lib.storage.stored-event✕
- Connections
- 1 pair of types, where a type in mssql.src.lib.storage.mssql-event-store uses a type in core.src.lib.storage.stored-event.
- The types involved
libs.mssql.src.lib.storage.mssql-event-store.MSSQLEventStore→libs.core.src.lib.storage.stored-event.StoredEvent
- Direction
- mssql.src.lib.storage.mssql-event-store uses core.src.lib.storage.stored-event, so a change to core.src.lib.storage.stored-event can break mssql.src.lib.storage.mssql-event-store, while a change to mssql.src.lib.storage.mssql-event-store can't break core.src.lib.storage.stored-event.
- Position
- Below the diagonal: mssql.src.lib.storage.mssql-event-store uses a module listed above it, which is the healthy direction.
39→9 mssql.src.lib.storage.mssql-event-store uses mssql.src.lib.schema-configuration✕
- Connections
- 1 pair of types, where a type in mssql.src.lib.storage.mssql-event-store uses a type in mssql.src.lib.schema-configuration.
- The types involved
libs.mssql.src.lib.storage.mssql-event-store.MSSQLEventStore→libs.mssql.src.lib.schema-configuration.SchemaConfiguration
- Direction
- mssql.src.lib.storage.mssql-event-store uses mssql.src.lib.schema-configuration, so a change to mssql.src.lib.schema-configuration can break mssql.src.lib.storage.mssql-event-store, while a change to mssql.src.lib.storage.mssql-event-store can't break mssql.src.lib.schema-configuration.
- Position
- Below the diagonal: mssql.src.lib.storage.mssql-event-store uses a module listed above it, which is the healthy direction.
39→10 mssql.src.lib.storage.mssql-event-store uses mssql.src.lib.storage.event-row✕
- Connections
- 1 pair of types, where a type in mssql.src.lib.storage.mssql-event-store uses a type in mssql.src.lib.storage.event-row.
- The types involved
libs.mssql.src.lib.storage.mssql-event-store.MSSQLEventStore→libs.mssql.src.lib.storage.event-row.EventRow
- Direction
- mssql.src.lib.storage.mssql-event-store uses mssql.src.lib.storage.event-row, so a change to mssql.src.lib.storage.event-row can break mssql.src.lib.storage.mssql-event-store, while a change to mssql.src.lib.storage.mssql-event-store can't break mssql.src.lib.storage.event-row.
- Position
- Below the diagonal: mssql.src.lib.storage.mssql-event-store uses a module listed above it, which is the healthy direction.
39→19 mssql.src.lib.storage.mssql-event-store uses core.src.lib.domain-event-emitter✕
- Connections
- 1 pair of types, where a type in mssql.src.lib.storage.mssql-event-store uses a type in core.src.lib.domain-event-emitter.
- The types involved
libs.mssql.src.lib.storage.mssql-event-store.MSSQLEventStore→libs.core.src.lib.domain-event-emitter.DomainEventEmitter
- Direction
- mssql.src.lib.storage.mssql-event-store uses core.src.lib.domain-event-emitter, so a change to core.src.lib.domain-event-emitter can break mssql.src.lib.storage.mssql-event-store, while a change to mssql.src.lib.storage.mssql-event-store can't break core.src.lib.domain-event-emitter.
- Position
- Below the diagonal: mssql.src.lib.storage.mssql-event-store uses a module listed above it, which is the healthy direction.
39→29 mssql.src.lib.storage.mssql-event-store uses core.src.lib.storage.snapshot.abstract-snapshot-store✕
- Connections
- 1 pair of types, where a type in mssql.src.lib.storage.mssql-event-store uses a type in core.src.lib.storage.snapshot.abstract-snapshot-store.
- The types involved
libs.mssql.src.lib.storage.mssql-event-store.MSSQLEventStore→libs.core.src.lib.storage.snapshot.abstract-snapshot-store.AbstractSnapshotStore
- Direction
- mssql.src.lib.storage.mssql-event-store uses core.src.lib.storage.snapshot.abstract-snapshot-store, so a change to core.src.lib.storage.snapshot.abstract-snapshot-store can break mssql.src.lib.storage.mssql-event-store, while a change to mssql.src.lib.storage.mssql-event-store can't break core.src.lib.storage.snapshot.abstract-snapshot-store.
- Position
- Below the diagonal: mssql.src.lib.storage.mssql-event-store uses a module listed above it, which is the healthy direction.
39→33 mssql.src.lib.storage.mssql-event-store uses core.src.lib.storage.abstract-event-store✕
- Connections
- 1 pair of types, where a type in mssql.src.lib.storage.mssql-event-store uses a type in core.src.lib.storage.abstract-event-store.
- The types involved
libs.mssql.src.lib.storage.mssql-event-store.MSSQLEventStore→libs.core.src.lib.storage.abstract-event-store.AbstractEventStore
- Direction
- mssql.src.lib.storage.mssql-event-store uses core.src.lib.storage.abstract-event-store, so a change to core.src.lib.storage.abstract-event-store can break mssql.src.lib.storage.mssql-event-store, while a change to mssql.src.lib.storage.mssql-event-store can't break core.src.lib.storage.abstract-event-store.
- Position
- Below the diagonal: mssql.src.lib.storage.mssql-event-store uses a module listed above it, which is the healthy direction.
40→5 postgresql.src.lib.storage.postgresql-event-store uses core.src.lib.storage.stored-aggregate-root✕
- Connections
- 1 pair of types, where a type in postgresql.src.lib.storage.postgresql-event-store uses a type in core.src.lib.storage.stored-aggregate-root.
- The types involved
libs.postgresql.src.lib.storage.postgresql-event-store.PostgreSQLEventStore→libs.core.src.lib.storage.stored-aggregate-root.StoredAggregateRoot
- Direction
- postgresql.src.lib.storage.postgresql-event-store uses core.src.lib.storage.stored-aggregate-root, so a change to core.src.lib.storage.stored-aggregate-root can break postgresql.src.lib.storage.postgresql-event-store, while a change to postgresql.src.lib.storage.postgresql-event-store can't break core.src.lib.storage.stored-aggregate-root.
- Position
- Below the diagonal: postgresql.src.lib.storage.postgresql-event-store uses a module listed above it, which is the healthy direction.
40→6 postgresql.src.lib.storage.postgresql-event-store uses core.src.lib.storage.stored-event✕
- Connections
- 1 pair of types, where a type in postgresql.src.lib.storage.postgresql-event-store uses a type in core.src.lib.storage.stored-event.
- The types involved
libs.postgresql.src.lib.storage.postgresql-event-store.PostgreSQLEventStore→libs.core.src.lib.storage.stored-event.StoredEvent
- Direction
- postgresql.src.lib.storage.postgresql-event-store uses core.src.lib.storage.stored-event, so a change to core.src.lib.storage.stored-event can break postgresql.src.lib.storage.postgresql-event-store, while a change to postgresql.src.lib.storage.postgresql-event-store can't break core.src.lib.storage.stored-event.
- Position
- Below the diagonal: postgresql.src.lib.storage.postgresql-event-store uses a module listed above it, which is the healthy direction.
40→9 postgresql.src.lib.storage.postgresql-event-store uses mssql.src.lib.schema-configuration✕
- Connections
- 1 pair of types, where a type in postgresql.src.lib.storage.postgresql-event-store uses a type in mssql.src.lib.schema-configuration.
- The types involved
libs.postgresql.src.lib.storage.postgresql-event-store.PostgreSQLEventStore→libs.mssql.src.lib.schema-configuration.SchemaConfiguration
- Direction
- postgresql.src.lib.storage.postgresql-event-store uses mssql.src.lib.schema-configuration, so a change to mssql.src.lib.schema-configuration can break postgresql.src.lib.storage.postgresql-event-store, while a change to postgresql.src.lib.storage.postgresql-event-store can't break mssql.src.lib.schema-configuration.
- Position
- Below the diagonal: postgresql.src.lib.storage.postgresql-event-store uses a module listed above it, which is the healthy direction.
40→19 postgresql.src.lib.storage.postgresql-event-store uses core.src.lib.domain-event-emitter✕
- Connections
- 1 pair of types, where a type in postgresql.src.lib.storage.postgresql-event-store uses a type in core.src.lib.domain-event-emitter.
- The types involved
libs.postgresql.src.lib.storage.postgresql-event-store.PostgreSQLEventStore→libs.core.src.lib.domain-event-emitter.DomainEventEmitter
- Direction
- postgresql.src.lib.storage.postgresql-event-store uses core.src.lib.domain-event-emitter, so a change to core.src.lib.domain-event-emitter can break postgresql.src.lib.storage.postgresql-event-store, while a change to postgresql.src.lib.storage.postgresql-event-store can't break core.src.lib.domain-event-emitter.
- Position
- Below the diagonal: postgresql.src.lib.storage.postgresql-event-store uses a module listed above it, which is the healthy direction.
40→29 postgresql.src.lib.storage.postgresql-event-store uses core.src.lib.storage.snapshot.abstract-snapshot-store✕
- Connections
- 1 pair of types, where a type in postgresql.src.lib.storage.postgresql-event-store uses a type in core.src.lib.storage.snapshot.abstract-snapshot-store.
- The types involved
libs.postgresql.src.lib.storage.postgresql-event-store.PostgreSQLEventStore→libs.core.src.lib.storage.snapshot.abstract-snapshot-store.AbstractSnapshotStore
- Direction
- postgresql.src.lib.storage.postgresql-event-store uses core.src.lib.storage.snapshot.abstract-snapshot-store, so a change to core.src.lib.storage.snapshot.abstract-snapshot-store can break postgresql.src.lib.storage.postgresql-event-store, while a change to postgresql.src.lib.storage.postgresql-event-store can't break core.src.lib.storage.snapshot.abstract-snapshot-store.
- Position
- Below the diagonal: postgresql.src.lib.storage.postgresql-event-store uses a module listed above it, which is the healthy direction.
40→33 postgresql.src.lib.storage.postgresql-event-store uses core.src.lib.storage.abstract-event-store✕
- Connections
- 1 pair of types, where a type in postgresql.src.lib.storage.postgresql-event-store uses a type in core.src.lib.storage.abstract-event-store.
- The types involved
libs.postgresql.src.lib.storage.postgresql-event-store.PostgreSQLEventStore→libs.core.src.lib.storage.abstract-event-store.AbstractEventStore
- Direction
- postgresql.src.lib.storage.postgresql-event-store uses core.src.lib.storage.abstract-event-store, so a change to core.src.lib.storage.abstract-event-store can break postgresql.src.lib.storage.postgresql-event-store, while a change to postgresql.src.lib.storage.postgresql-event-store can't break core.src.lib.storage.abstract-event-store.
- Position
- Below the diagonal: postgresql.src.lib.storage.postgresql-event-store uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 13 | High / Critical |
| A05:2025 — Injection | 11 | 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; Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it; Resolve the 3 Documentation finding(s) in Documentation Quality — start with README.md (3).
| 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. | +4.4 pts | Medium | Security & performance tooling |
| Resolve the 3 Documentation finding(s) in Documentation Quality — start with README.md (3). | +2.0 pts | Low | Documentation Quality |
| Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it. | +2.9 pts | Medium | Deployment & Rollback |
| Resolve the 5 Orphaned file finding(s) in Knowledge Freshness — start with snapshot-aware.ts, aggregate-root-config.ts, mongo-snapshot-store.ts. | +1.1 pts | Low | Knowledge Freshness |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +2.0 pts | Medium | Observability |
| 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. | +1.9 pts | Medium | Architecture documentation |
| Add `tsc --noEmit` as package.json scripts and run them in CI. | +1.6 pts | Medium | Tooling |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +1.3 pts | Medium | Keyboard semantics |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.6 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| libs/core/src/lib/aggregate-root/aggregate-root-config.spec.ts | 7.8 | Mixed | Test Quality: No assertions: test return type at type-level |
| libs/core/src/lib/aggregate-root/aggregate-root.ts | 8.5 | Near-clean | Cognitive Complexity: AggregateRoot.reconstitute (cognitive 17) |
| apps/docs/tests/viewport.spec.ts | 8.5 | Near-clean | Test Quality: No assertions: generated pages fit the ${viewport.name} viewport |
| libs/mongodb/README.md | 9.5 | Near-clean | Documentation Quality: Documentation: no build, run or usage example |
| libs/mssql/README.md | 9.5 | Near-clean | Documentation Quality: Documentation: no build, run or usage example |
| libs/postgresql/README.md | 9.5 | Near-clean | Documentation Quality: Documentation: no build, run or usage example |
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 79 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 79 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, 64 of 78 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D11 Test Reliability — 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. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the jest run in the repository root produced no per-test report (Error: Jest: Failed to parse the TypeScript config file jest.config.ts). This is OUR limitation, not a defect in the repo — it is excluded from the score.
- D11 Test Reliability — 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. Test reliability for the jest suite in the repository root was NOT MEASURED: the jest run in the repository root produced no per-test report (Error: Jest: Failed to parse the TypeScript config file jest.config.ts). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- 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 (2 contributor(s) across 288 commit(s) sampled, automation and bot accounts excluded). One of them holds 97% of the history; the other 1 hold 3% 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's deterministic call-shape 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. This says nothing about whether that surface is consistent.
- 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. `libs/core/src/lib/storage/event-store.ts` 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.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a web-server dependency ('@nestjs/core') — a service to boot even with no user interface. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- 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. A badge or prose version claim scored 9/17 in its adjudication (docs/plans/deterministic-engine/adjudication/M4-v3.md: badges 9/9, prose 0/8, where prose versions are minimums or history), short of the 95 % precision gate, so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them. The .NET and Node.js version checks are a different kind and still publish.
- 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.
- P8 Schema migrations — 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. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 82 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- 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.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- 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.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was AggregateRoot.reconstitute at 17.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with AggregateRoot.reconstitute (cognitive 17). — Refactoring it lifts Cognitive Complexity from 9.8 to about 10.0/10.
- 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
0 god class(es) detected.
D5 · Coupling
4 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling 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 18 classes have LCOM4 above 3.
D9 · Test Distribution
389 test methods: 389 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 389 `it`/`test` case(s) across 34 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 3 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 389 tests.
What to do
- Resolve the 3 No assertions finding(s) in Test Quality — start with aggregate-root-config.spec.ts (2), viewport.spec.ts. — One of this dimension's main actionable groups (3 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.
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 4372 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 2 documentation facets pass in full; short on: F2 example. 41 document(s) read across 6 unit(s).
What to do
- Resolve the 3 Documentation finding(s) in Documentation Quality — start with README.md (3). — One of this dimension's main actionable groups (3 recommendation-level).
D23 · Boundary Type-Coupling
No domain types leak across context boundaries (6 contexts). Contexts: core, docs, example, mongodb, mssql, postgresql.
D26 · Project Cohesion
0 of 5 build units (npm) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
11 finding(s): 0 critical, 11 high, 0 medium, 0 low. 8 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 1 file(s) — `libs/core/src/lib/storage/event-store.ts` (line 18) — 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 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 8 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 (8 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
8 finding(s): 0 critical, 1 high, 6 medium, 1 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 6 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 1 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
5 of 28 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is libs/core/src/lib/aggregate-root/snapshot-aware.ts. Counted over 28 of the 83 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 5 Orphaned file finding(s) in Knowledge Freshness — start with snapshot-aware.ts, aggregate-root-config.ts, mongo-snapshot-store.ts. — One of this dimension's main actionable groups (5 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/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. — One of this dimension's main actionable groups (1 recommendation-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 4 platform declaration(s) and 10 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
AC2 · Forms & labels
AC3 · Page structure
AC4 · Keyboard semantics
- A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0". — apps/docs/src/lib/components/search.svelte:186
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
AC7 · A11y enforcement
- An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add jest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 20 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:45
What to do
- Accessibility linting is already configured — 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
AX4 · Dependency direction
AX6 · Interface segregation
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM4 · Rich vs anemic model
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
- `DomainEventEmitter` (domain layer) imports `@nestjs/common` — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — libs/core/src/lib/domain-event-emitter.ts:2
- `DomainEventEmitter` (domain layer) imports `@nestjs/core/injector/module` — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — libs/core/src/lib/domain-event-emitter.ts:3
What to do
- Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository).
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 1 of 6 project(s) that lack one — worth up to 0.3 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
- CONTRIBUTING.md names Node.js 24, but the repository declares engines `>=22.13`, engines `>= 22`, engines `>= 22`, engines `>= 22`, engines `>= 22`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:48
- apps/docs/src/routes/help/compatibility/+page.md names Node.js 24, but the repository declares engines `>=22.13`, engines `>= 22`, engines `>= 22`, engines `>= 22`, engines `>= 22`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — apps/docs/src/routes/help/compatibility/+page.md:17
What to do
- Reconcile the README with reality: CONTRIBUTING.md names Node.js 24, but the repository declares engines `>=22.13`, engines `>= 22`, engines `>= 22`, engines `>= 22`, engines `>= 22`; apps/docs/src/routes/help/compatibility/+page.md names Node.js 24, but the repository declares engines `>=22.13`, engines `>= 22`, engines `>= 22`, engines `>= 22`, engines `>= 22`.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 5/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `apps/docs`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 6941 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:9
- `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:21
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
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 16 duplicated blocks under libs/ have copies in at least two of the sibling directories core, mongodb, mssql, postgresql — 9 of them are reported below, and 7 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 16 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 16 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 16 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. — libs/mssql/src/lib/module-providers.ts:68
- libs/mssql/src/lib/module-providers.ts:68 · libs/postgresql/src/lib/module-providers.ts:64 — 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. — libs/mssql/src/lib/module-providers.ts:68
- libs/mongodb/src/lib/storage/mongo-event-store.ts:87 · libs/postgresql/src/lib/storage/postgresql-event-store.ts:67 — the two spans are one implementation copied and then locally edited — 607 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. — libs/mongodb/src/lib/storage/mongo-event-store.ts:87
- libs/mssql/src/lib/storage/mssql-event-store.ts:110 · libs/postgresql/src/lib/storage/postgresql-event-store.ts:130 — the two spans are one implementation copied and then locally edited — 462 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. — libs/mssql/src/lib/storage/mssql-event-store.ts:110
- libs/mongodb/src/lib/event-nest-mongodb.module.ts:8 · libs/postgresql/src/lib/event-nest-postgresql.module.ts:8 — 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. — libs/mongodb/src/lib/event-nest-mongodb.module.ts:8
- libs/mssql/src/lib/storage/mssql-snapshot-store.ts:9 · libs/postgresql/src/lib/storage/postgresql-snapshot-store.ts:9 — the two spans are one implementation copied and then locally edited — 307 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. — libs/mssql/src/lib/storage/mssql-snapshot-store.ts:9
- libs/mssql/src/lib/schema-configuration.ts:9 · libs/postgresql/src/lib/schema-configuration.ts:4 — the two spans are one implementation copied and then locally edited — 118 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. — libs/mssql/src/lib/schema-configuration.ts:9
- libs/mssql/src/lib/table-initializer.ts:7 · libs/postgresql/src/lib/table-initializer.ts:7 — 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. — libs/mssql/src/lib/table-initializer.ts:7
- libs/mongodb/src/lib/storage/mongo-event-store.ts:124 · libs/mssql/src/lib/storage/mssql-event-store.ts:88 · libs/postgresql/src/lib/storage/postgresql-event-store.ts:104 — 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. — libs/mongodb/src/lib/storage/mongo-event-store.ts:124
- libs/postgresql/src/lib/module-providers.ts:51 · libs/postgresql/src/lib/module-providers.ts:166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — libs/postgresql/src/lib/module-providers.ts:51
- libs/core/src/lib/snapshot-strategy/all-of-snapshot-strategy.ts:26 · libs/core/src/lib/snapshot-strategy/any-of-snapshot-strategy.ts:27 — 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. — libs/core/src/lib/snapshot-strategy/all-of-snapshot-strategy.ts:26
- libs/mongodb/src/lib/module-providers.ts:34 · libs/mongodb/src/lib/module-providers.ts:81 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — libs/mongodb/src/lib/module-providers.ts:34
- libs/mongodb/src/lib/module-providers.ts:96 · libs/mssql/src/lib/module-providers.ts:100 · libs/postgresql/src/lib/module-providers.ts:96 — the 3 copies are spread across 3 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. — libs/mongodb/src/lib/module-providers.ts:96
- libs/mongodb/src/lib/storage/mongo-event-store.ts:58 · libs/mongodb/src/lib/storage/mongo-event-store.ts:94 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — libs/mongodb/src/lib/storage/mongo-event-store.ts:58
- libs/mongodb/src/lib/storage/mongo-event-store.ts:74 · libs/mongodb/src/lib/storage/mongo-event-store.ts:155 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — libs/mongodb/src/lib/storage/mongo-event-store.ts:74
- libs/core/src/lib/domain-event-emitter.ts:45 · libs/core/src/lib/domain-event-emitter.ts:55 — 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. — libs/core/src/lib/domain-event-emitter.ts:45
- libs/mssql/src/lib/table-initializer.ts:39 · libs/mssql/src/lib/table-initializer.ts:50 — 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. — libs/mssql/src/lib/table-initializer.ts:39
- libs/postgresql/src/lib/table-initializer.ts:60 · libs/postgresql/src/lib/table-initializer.ts:82 — 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. — libs/postgresql/src/lib/table-initializer.ts:60
- libs/mssql/src/lib/table-initializer.ts:57 · libs/mssql/src/lib/table-initializer.ts:82 — 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. — libs/mssql/src/lib/table-initializer.ts:57
- libs/core/src/lib/domain-event-emitter.ts:113 · libs/core/src/lib/domain-event-emitter.ts:123 — 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. — libs/core/src/lib/domain-event-emitter.ts:113
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
- reconstitute has cyclomatic complexity 11 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. — libs/core/src/lib/aggregate-root/aggregate-root.ts:125
R3 · Large Files
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. — libs/core/setup-tests.ts:1
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 7 application, 7 tooling and 30 test entry point(s) detected in this repo. Nothing this repository declares compiles or type-checks these files, so a wrong deletion here would raise no compile error — gate removals on `pnpm test`, which loads the modules, and note that it only covers what it exercises. An undetected custom entry would make these reachable.
- no import path from any entry point (7 application, 7 tooling, 30 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 — libs/core/setup-tests.ts
- This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. — libs/core/src/lib/domain-event-emitter.spec.ts:23
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
- libs/core/src/lib/aggregate-root/aggregate-root.ts → libs/core/src/lib/aggregate-root/reflection.ts → libs/core/src/lib/aggregate-root/aggregate-root.ts (one verified cycle inside a mutually-dependent group of 3 files) — libs/core/src/lib/aggregate-root/aggregate-root.ts:10
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- 9/13 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
- ~2.1 `!` null assertions per 1k TypeScript source lines — 10 assertion(s) across the 4653 source line(s) of the 79 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: libs/core/src/lib/storage/snapshot/stored-snapshot.ts (4), libs/core/src/lib/storage/stored-event.ts (4), libs/postgresql/src/lib/module-providers.ts (2). 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 |
|---|---|---|
| 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 |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | 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 | 83% | Strong | Solid. |
| Architecture | 93% | Exemplary | Solid. |
| Maturity | 61% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 55% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 65% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 73% | Adequate — gated by DM6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 64% | Adequate — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- D12 Dependency Hygiene — 2 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.
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 — 59 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AX1 Captive dependencies — Not applicable: NestJS makes a provider that injects a request-scoped one request-scoped itself (scope bubbles up the injection chain), and gives every consumer its own transient instance by contract.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) 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
- 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
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
- D14 License Compliance — Not scored — this repository's 182 shipped npm package(s) were resolved from its committed lockfile, but registry.npmjs.org could not be asked for the licence of 5 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 — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
- D24 Comment Value — Too few judgeable comments (10 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 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.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in the repository root ran and not one test passed (Error: Jest: Failed to parse the TypeScript config file jest.config.ts), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an append-only event-store seam (IEventStore/Append-of-events))
- 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 — Knex is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `jest --coverage --coverageReporters=lcovonly`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: 82 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 16 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Domain depends on infrastructure: DomainEventEmitter libs/core/src/lib/domain-event-emitter.ts:2
- Domain depends on infrastructure: DomainEventEmitter libs/core/src/lib/domain-event-emitter.ts:3
- Click handler on a non-interactive <dialog> apps/docs/src/lib/components/search.svelte:186
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Import cycle (2 files) libs/core/src/lib/aggregate-root/aggregate-root.ts:10
Serious — 38 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No assertions: test return type at type-level libs/core/src/lib/aggregate-root/aggregate-root-config.spec.ts:26
- No assertions: test return type at type-level libs/core/src/lib/aggregate-root/aggregate-root-config.spec.ts:46
- No assertions: generated pages fit the ${viewport.name} viewport apps/docs/tests/viewport.spec.ts:40
- Duplicated block (9 lines × 2 locations) libs/core/src/lib/domain-event-emitter.ts:45
- Duplicated block (9 lines × 2 locations) libs/mssql/src/lib/table-initializer.ts:39
- Duplicated block (9 lines × 2 locations) libs/postgresql/src/lib/table-initializer.ts:60
- Duplicated block (11 lines × 2 locations) libs/mongodb/src/lib/storage/mongo-event-store.ts:58
- Duplicated block (11 lines × 2 locations) libs/mongodb/src/lib/storage/mongo-event-store.ts:74
- AggregateRoot.reconstitute (cognitive 17) libs/core/src/lib/aggregate-root/aggregate-root.ts:125
- REDACTED
- Off the main sequence: @event-nest/core
- Coverage not measured — JavaScript/TypeScript suite
- Coverage collected but not gated
- Duplication concentrated across 4 sibling directories (16 clone groups) libs/mssql/src/lib/module-providers.ts:68
- Duplicated block (104 lines × 2 locations) libs/mssql/src/lib/module-providers.ts:68
- Duplicated block with local edits (97 matched lines × 2 locations) libs/mongodb/src/lib/storage/mongo-event-store.ts:87
- Duplicated block with local edits (75 matched lines × 2 locations) libs/mssql/src/lib/storage/mssql-event-store.ts:110
- Duplicated block (42 lines × 2 locations) libs/mongodb/src/lib/event-nest-mongodb.module.ts:8
- Duplicated block with local edits (42 matched lines × 2 locations) libs/mssql/src/lib/storage/mssql-snapshot-store.ts:9
- Duplicated block with local edits (28 matched lines × 2 locations) libs/mssql/src/lib/schema-configuration.ts:9
- Duplicated block (20 lines × 2 locations) libs/mssql/src/lib/table-initializer.ts:7
- Duplicated block (18 lines × 3 locations) libs/mongodb/src/lib/storage/mongo-event-store.ts:124
- Duplicated block (16 lines × 2 locations) libs/postgresql/src/lib/module-providers.ts:51
- Duplicated block (14 lines × 2 locations) libs/core/src/lib/snapshot-strategy/all-of-snapshot-strategy.ts:26
- Duplicated block (12 lines × 2 locations) libs/mongodb/src/lib/module-providers.ts:34
- Duplicated block (12 lines × 3 locations) libs/mongodb/src/lib/module-providers.ts:96
- Duplicated block (6 lines × 2 locations) libs/mssql/src/lib/table-initializer.ts:57
- Duplicated block (5 lines × 2 locations) libs/core/src/lib/domain-event-emitter.ts:113
- Complex function reconstitute (cyclomatic 11, cognitive 17) libs/core/src/lib/aggregate-root/aggregate-root.ts:125
- No test reaches this file libs/core/setup-tests.ts:1
- No typecheck script
- Dead file (~1 LoC) libs/core/setup-tests.ts
Minor — 24 finding(s)
- Orphaned file libs/core/src/lib/aggregate-root/snapshot-aware.ts:1
- Orphaned file libs/core/src/lib/aggregate-root/aggregate-root-config.ts:1
- Orphaned file libs/mongodb/src/lib/storage/mongo-snapshot-store.ts:1
- Orphaned file libs/postgresql/src/lib/storage/postgresql-snapshot-store.ts:1
- Orphaned file libs/core/src/lib/snapshot-strategy/for-aggregate-roots-strategy.ts:1
- Documentation: no build, run or usage example libs/mongodb/README.md:1
- Documentation: no build, run or usage example libs/mssql/README.md:1
- Documentation: no build, run or usage example libs/postgresql/README.md:1
- README/code drift CONTRIBUTING.md:48
- README/code drift apps/docs/src/routes/help/compatibility/+page.md:17
- Accessibility enforcement below the top rung package.json:45
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- No SAST REDACTED:9
- No dependency-update automation package.json:21
- Unused module-local declaration 'OtherSubscription' libs/core/src/lib/domain-event-emitter.spec.ts:23
- Strict null checking is not enabled everywhere the repository type-checks
- Null assertions (`!`) reduce the strict null checking score
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-add9f78d5ba9454ca21b8e79fe03e375/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-add9f78d5ba9454ca21b8e79fe03e375/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 . | 11 | 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 | 8 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `libs/core/src/lib/storage/event-store.ts` — 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 |