Executive summary
ocoda/event-sourcing falls short of our standard for production because the documentation refers to things that don't exist. It scores 58 out of 100 and is rated Adequate, and seven of its 23 critical findings are security problems.
Maturity, at 50, is the weakest lens and counts most in the score. The best first step is bringing the documentation in line with the code, worth about 6 points. Replacing the 14 packages under a banned licence comes next, worth about 5 points. Raising Maturity to 70 would lift the score to about 64.
Three passwords or keys are open to anyone who can read the repository. Two known security holes in the packages the code depends on can be used by attackers, and fourteen packages carry licence risk. Replacing each exposed password or key, updating the vulnerable packages and replacing or clearing the banned-licence packages would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and fixing the weaknesses the scanner points to would deal with the security weakness in the code. The loop of files that import each other needs breaking.
The product code is 24,340 lines, about €66,000 to rebuild.
If Maturity rose from 50 to 70, the lowest score rated Strong, the score would rise from 58 to about 64.
Rebuild cost: about €66,000 · Estimate
| Cost to rebuild | €22,000 to €110,000, for 367 to 1,165 hours of work, about 0.5 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 58. 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 | Medium: 24,340 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.lib.constants | 2 core.lib.exceptions.event-sourcing-error | 3 core.lib.interfaces.aggregate.snapshot-collection_type | 4 core.lib.interfaces.events.event-collection_type | 5 core.lib.interfaces.events.event-store-capabilities_interface | 6 core.lib.interfaces.migration.migration-options_interface | 7 core.lib.interfaces.migration.migration-report_interface | 8 core.lib.models.aggregate-root | 9 core.lib.models.event-envelope | 10 core.lib.models.id | 11 core.lib.models.snapshot-envelope | 12 core.lib.registration.registration | 13 integration.mariadb.lib.mariadb_schema | 14 core.lib.event-bus | 15 core.lib.event-map | 16 core.lib.helpers.metadata | 17 core.lib.interfaces.aggregate.snapshot-filter_interface | 18 core.lib.interfaces.events.event-filter_interface | 19 core.lib.models.event-stream | 20 core.lib.models.snapshot-stream | 21 integration.mariadb.lib | 22 integration.mariadb.lib.migration.migrate | 23 integration.mongodb.lib.migration | 24 core.lib.interfaces.events.persist-outcome_type | 25 core.lib.snapshot-store | 26 integration.mariadb.lib.migration | 27 integration.postgres.lib.migration | 28 core.lib.event-store | 29 core.lib.integration.snapshot-store.in-memory_snapshot-store | 30 integration.mariadb.lib.mariadb_snapshot-store | 31 integration.mongodb.lib.mongodb_snapshot-store | 32 integration.postgres.lib.postgres_snapshot-store | 33 core.lib.integration.event-store.in-memory_event-store | 34 core.lib.stores | 35 core.lib.testing | 36 integration.mariadb.lib.mariadb_event-store | 37 integration.mongodb.lib.mongodb_event-store | 38 integration.postgres.lib.postgres_event-store | 39 testing.cross-version | 40 integration.mongodb.lib |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 core.lib.constants | ||||||||||||||||||||||||||||||||||||||||
| 2 core.lib.exceptions.event-sourcing-error | ||||||||||||||||||||||||||||||||||||||||
| 3 core.lib.interfaces.aggregate.snapshot-collection_type | ||||||||||||||||||||||||||||||||||||||||
| 4 core.lib.interfaces.events.event-collection_type | ||||||||||||||||||||||||||||||||||||||||
| 5 core.lib.interfaces.events.event-store-capabilities_interface | ||||||||||||||||||||||||||||||||||||||||
| 6 core.lib.interfaces.migration.migration-options_interface | ||||||||||||||||||||||||||||||||||||||||
| 7 core.lib.interfaces.migration.migration-report_interface | ||||||||||||||||||||||||||||||||||||||||
| 8 core.lib.models.aggregate-root | ||||||||||||||||||||||||||||||||||||||||
| 9 core.lib.models.event-envelope | ||||||||||||||||||||||||||||||||||||||||
| 10 core.lib.models.id | ||||||||||||||||||||||||||||||||||||||||
| 11 core.lib.models.snapshot-envelope | ||||||||||||||||||||||||||||||||||||||||
| 12 core.lib.registration.registration | ||||||||||||||||||||||||||||||||||||||||
| 13 integration.mariadb.lib.mariadb_schema | ||||||||||||||||||||||||||||||||||||||||
| 14 core.lib.event-bus | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 core.lib.event-map | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 core.lib.helpers.metadata | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 core.lib.interfaces.aggregate.snapshot-filter_interface | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 core.lib.interfaces.events.event-filter_interface | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 core.lib.models.event-stream | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 core.lib.models.snapshot-stream | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 integration.mariadb.lib | 1 | 1 | 1 | 1 | 8 | |||||||||||||||||||||||||||||||||||
| 22 integration.mariadb.lib.migration.migrate | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 integration.mongodb.lib.migration | 5 | |||||||||||||||||||||||||||||||||||||||
| 24 core.lib.interfaces.events.persist-outcome_type | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 core.lib.snapshot-store | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 integration.mariadb.lib.migration | 1 | 3 | 2 | 7 | ||||||||||||||||||||||||||||||||||||
| 27 integration.postgres.lib.migration | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 core.lib.event-store | 1 | 1 | 1 | 3 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 29 core.lib.integration.snapshot-store.in-memory_snapshot-store | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 30 integration.mariadb.lib.mariadb_snapshot-store | 1 | 1 | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 31 integration.mongodb.lib.mongodb_snapshot-store | 2 | 1 | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 32 integration.postgres.lib.postgres_snapshot-store | 1 | 1 | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 33 core.lib.integration.event-store.in-memory_event-store | 1 | 1 | 1 | 3 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 34 core.lib.stores | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 core.lib.testing | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 36 integration.mariadb.lib.mariadb_event-store | 1 | 1 | 1 | 1 | 1 | 3 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||
| 37 integration.mongodb.lib.mongodb_event-store | 1 | 1 | 1 | 1 | 3 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 38 integration.postgres.lib.postgres_event-store | 1 | 1 | 1 | 1 | 1 | 3 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||
| 39 testing.cross-version | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 40 integration.mongodb.lib | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
14→9 core.lib.event-bus uses core.lib.models.event-envelope✕
- Connections
- 1 pair of types, where a type in core.lib.event-bus uses a type in core.lib.models.event-envelope.
- The types involved
packages.core.lib.event-bus.EventBus→packages.core.lib.models.event-envelope.EventEnvelope
- Direction
- core.lib.event-bus uses core.lib.models.event-envelope, so a change to core.lib.models.event-envelope can break core.lib.event-bus, while a change to core.lib.event-bus can't break core.lib.models.event-envelope.
- Position
- Below the diagonal: core.lib.event-bus uses a module listed above it, which is the healthy direction.
14→12 core.lib.event-bus uses core.lib.registration.registration✕
- Connections
- 1 pair of types, where a type in core.lib.event-bus uses a type in core.lib.registration.registration.
- The types involved
packages.core.lib.event-bus.EventBus→packages.core.lib.registration.registration.Registration
- Direction
- core.lib.event-bus uses core.lib.registration.registration, so a change to core.lib.registration.registration can break core.lib.event-bus, while a change to core.lib.event-bus can't break core.lib.registration.registration.
- Position
- Below the diagonal: core.lib.event-bus uses a module listed above it, which is the healthy direction.
15→12 core.lib.event-map uses core.lib.registration.registration✕
- Connections
- 1 pair of types, where a type in core.lib.event-map uses a type in core.lib.registration.registration.
- The types involved
packages.core.lib.event-map.EventMap→packages.core.lib.registration.registration.Registration
- Direction
- core.lib.event-map uses core.lib.registration.registration, so a change to core.lib.registration.registration can break core.lib.event-map, while a change to core.lib.event-map can't break core.lib.registration.registration.
- Position
- Below the diagonal: core.lib.event-map uses a module listed above it, which is the healthy direction.
16→8 core.lib.helpers.metadata uses core.lib.models.aggregate-root✕
- Connections
- 2 pairs of types, where a type in core.lib.helpers.metadata uses a type in core.lib.models.aggregate-root.
- The types involved
packages.core.lib.helpers.metadata.get-aggregate-metadata→packages.core.lib.models.aggregate-root.AggregateRootpackages.core.lib.helpers.metadata.get-event-handler-metadata→packages.core.lib.models.aggregate-root.AggregateRoot
- Direction
- core.lib.helpers.metadata uses core.lib.models.aggregate-root, so a change to core.lib.models.aggregate-root can break core.lib.helpers.metadata, while a change to core.lib.helpers.metadata can't break core.lib.models.aggregate-root.
- Position
- Below the diagonal: core.lib.helpers.metadata uses a module listed above it, which is the healthy direction.
17→1 core.lib.interfaces.aggregate.snapshot-filter_interface uses core.lib.constants✕
- Connections
- 1 pair of types, where a type in core.lib.interfaces.aggregate.snapshot-filter_interface uses a type in core.lib.constants.
- The types involved
packages.core.lib.interfaces.aggregate.snapshot-filter_interface.ISnapshotFilter→packages.core.lib.constants.StreamReadingDirection
- Direction
- core.lib.interfaces.aggregate.snapshot-filter_interface uses core.lib.constants, so a change to core.lib.constants can break core.lib.interfaces.aggregate.snapshot-filter_interface, while a change to core.lib.interfaces.aggregate.snapshot-filter_interface can't break core.lib.constants.
- Position
- Below the diagonal: core.lib.interfaces.aggregate.snapshot-filter_interface uses a module listed above it, which is the healthy direction.
18→1 core.lib.interfaces.events.event-filter_interface uses core.lib.constants✕
- Connections
- 1 pair of types, where a type in core.lib.interfaces.events.event-filter_interface uses a type in core.lib.constants.
- The types involved
packages.core.lib.interfaces.events.event-filter_interface.IEventFilter→packages.core.lib.constants.StreamReadingDirection
- Direction
- core.lib.interfaces.events.event-filter_interface uses core.lib.constants, so a change to core.lib.constants can break core.lib.interfaces.events.event-filter_interface, while a change to core.lib.interfaces.events.event-filter_interface can't break core.lib.constants.
- Position
- Below the diagonal: core.lib.interfaces.events.event-filter_interface uses a module listed above it, which is the healthy direction.
19→10 core.lib.models.event-stream uses core.lib.models.id✕
- Connections
- 1 pair of types, where a type in core.lib.models.event-stream uses a type in core.lib.models.id.
- The types involved
packages.core.lib.models.event-stream.EventStream→packages.core.lib.models.id.Id
- Direction
- core.lib.models.event-stream uses core.lib.models.id, so a change to core.lib.models.id can break core.lib.models.event-stream, while a change to core.lib.models.event-stream can't break core.lib.models.id.
- Position
- Below the diagonal: core.lib.models.event-stream uses a module listed above it, which is the healthy direction.
20→10 core.lib.models.snapshot-stream uses core.lib.models.id✕
- Connections
- 1 pair of types, where a type in core.lib.models.snapshot-stream uses a type in core.lib.models.id.
- The types involved
packages.core.lib.models.snapshot-stream.SnapshotStream→packages.core.lib.models.id.Id
- Direction
- core.lib.models.snapshot-stream uses core.lib.models.id, so a change to core.lib.models.id can break core.lib.models.snapshot-stream, while a change to core.lib.models.snapshot-stream can't break core.lib.models.id.
- Position
- Below the diagonal: core.lib.models.snapshot-stream uses a module listed above it, which is the healthy direction.
21→4 integration.mariadb.lib uses core.lib.interfaces.events.event-collection_type✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib uses a type in core.lib.interfaces.events.event-collection_type.
- The types involved
packages.integration.mariadb.lib.mariadb.event-store→packages.core.lib.interfaces.events.event-collection_type.IEventCollection
- Direction
- integration.mariadb.lib uses core.lib.interfaces.events.event-collection_type, so a change to core.lib.interfaces.events.event-collection_type can break integration.mariadb.lib, while a change to integration.mariadb.lib can't break core.lib.interfaces.events.event-collection_type.
- Position
- Below the diagonal: integration.mariadb.lib uses a module listed above it, which is the healthy direction.
21→5 integration.mariadb.lib uses core.lib.interfaces.events.event-store-capabilities_interface✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib uses a type in core.lib.interfaces.events.event-store-capabilities_interface.
- The types involved
packages.integration.mariadb.lib.mariadb.server→packages.core.lib.interfaces.events.event-store-capabilities_interface.EventStoreCapabilities
- Direction
- integration.mariadb.lib uses core.lib.interfaces.events.event-store-capabilities_interface, so a change to core.lib.interfaces.events.event-store-capabilities_interface can break integration.mariadb.lib, while a change to integration.mariadb.lib can't break core.lib.interfaces.events.event-store-capabilities_interface.
- Position
- Below the diagonal: integration.mariadb.lib uses a module listed above it, which is the healthy direction.
21→9 integration.mariadb.lib uses core.lib.models.event-envelope✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib uses a type in core.lib.models.event-envelope.
- The types involved
packages.integration.mariadb.lib.mariadb.event-store→packages.core.lib.models.event-envelope.EventEnvelope
- Direction
- integration.mariadb.lib uses core.lib.models.event-envelope, so a change to core.lib.models.event-envelope can break integration.mariadb.lib, while a change to integration.mariadb.lib can't break core.lib.models.event-envelope.
- Position
- Below the diagonal: integration.mariadb.lib uses a module listed above it, which is the healthy direction.
21→11 integration.mariadb.lib uses core.lib.models.snapshot-envelope✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib uses a type in core.lib.models.snapshot-envelope.
- The types involved
packages.integration.mariadb.lib.mariadb.snapshot-store→packages.core.lib.models.snapshot-envelope.SnapshotEnvelope
- Direction
- integration.mariadb.lib uses core.lib.models.snapshot-envelope, so a change to core.lib.models.snapshot-envelope can break integration.mariadb.lib, while a change to integration.mariadb.lib can't break core.lib.models.snapshot-envelope.
- Position
- Below the diagonal: integration.mariadb.lib uses a module listed above it, which is the healthy direction.
21→13 integration.mariadb.lib uses integration.mariadb.lib.mariadb_schema✕
- Connections
- 8 pairs of types, where a type in integration.mariadb.lib uses a type in integration.mariadb.lib.mariadb_schema.
- The types involved
packages.integration.mariadb.lib.mariadb.schema→packages.integration.mariadb.lib.mariadb_schema.CollectionStatepackages.integration.mariadb.lib.mariadb.schema→packages.integration.mariadb.lib.mariadb_schema.ColumnInfopackages.integration.mariadb.lib.mariadb.schema→packages.integration.mariadb.lib.mariadb_schema.EventTableInspectionpackages.integration.mariadb.lib.mariadb.schema→packages.integration.mariadb.lib.mariadb_schema.Queryablepackages.integration.mariadb.lib.mariadb.schema→packages.integration.mariadb.lib.mariadb_schema.SnapshotTableInspectionpackages.integration.mariadb.lib.mariadb.schema→packages.integration.mariadb.lib.mariadb_schema.TableDdlOptionspackages.integration.mariadb.lib.mariadb.server→packages.integration.mariadb.lib.mariadb_schema.Queryablepackages.integration.mariadb.lib.mariadb.utils→packages.integration.mariadb.lib.mariadb_schema.Queryable
- Direction
- integration.mariadb.lib uses integration.mariadb.lib.mariadb_schema, so a change to integration.mariadb.lib.mariadb_schema can break integration.mariadb.lib, while a change to integration.mariadb.lib can't break integration.mariadb.lib.mariadb_schema.
- Position
- Below the diagonal: integration.mariadb.lib uses a module listed above it, which is the healthy direction.
22→6 integration.mariadb.lib.migration.migrate uses core.lib.interfaces.migration.migration-options_interface✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib.migration.migrate uses a type in core.lib.interfaces.migration.migration-options_interface.
- The types involved
packages.integration.mariadb.lib.migration.migrate.MigrateTableContext→packages.core.lib.interfaces.migration.migration-options_interface.MigrationOptions
- Direction
- integration.mariadb.lib.migration.migrate uses core.lib.interfaces.migration.migration-options_interface, so a change to core.lib.interfaces.migration.migration-options_interface can break integration.mariadb.lib.migration.migrate, while a change to integration.mariadb.lib.migration.migrate can't break core.lib.interfaces.migration.migration-options_interface.
- Position
- Below the diagonal: integration.mariadb.lib.migration.migrate uses a module listed above it, which is the healthy direction.
22→7 integration.mariadb.lib.migration.migrate uses core.lib.interfaces.migration.migration-report_interface✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib.migration.migrate uses a type in core.lib.interfaces.migration.migration-report_interface.
- The types involved
packages.integration.mariadb.lib.migration.migrate.InspectedTable→packages.core.lib.interfaces.migration.migration-report_interface.MigrationCollectionReport
- Direction
- integration.mariadb.lib.migration.migrate uses core.lib.interfaces.migration.migration-report_interface, so a change to core.lib.interfaces.migration.migration-report_interface can break integration.mariadb.lib.migration.migrate, while a change to integration.mariadb.lib.migration.migrate can't break core.lib.interfaces.migration.migration-report_interface.
- Position
- Below the diagonal: integration.mariadb.lib.migration.migrate uses a module listed above it, which is the healthy direction.
22→13 integration.mariadb.lib.migration.migrate uses integration.mariadb.lib.mariadb_schema✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib.migration.migrate uses a type in integration.mariadb.lib.mariadb_schema.
- The types involved
packages.integration.mariadb.lib.migration.migrate.TableMigration→packages.integration.mariadb.lib.mariadb_schema.Queryable
- Direction
- integration.mariadb.lib.migration.migrate uses integration.mariadb.lib.mariadb_schema, so a change to integration.mariadb.lib.mariadb_schema can break integration.mariadb.lib.migration.migrate, while a change to integration.mariadb.lib.migration.migrate can't break integration.mariadb.lib.mariadb_schema.
- Position
- Below the diagonal: integration.mariadb.lib.migration.migrate uses a module listed above it, which is the healthy direction.
23→7 integration.mongodb.lib.migration uses core.lib.interfaces.migration.migration-report_interface✕
- Connections
- 5 pairs of types, where a type in integration.mongodb.lib.migration uses a type in core.lib.interfaces.migration.migration-report_interface.
- The types involved
packages.integration.mongodb.lib.migration.events→packages.core.lib.interfaces.migration.migration-report_interface.MigrationReportpackages.integration.mongodb.lib.migration.plan→packages.core.lib.interfaces.migration.migration-report_interface.MigrationCollectionReportpackages.integration.mongodb.lib.migration.runner→packages.core.lib.interfaces.migration.migration-report_interface.MigrationCollectionReportpackages.integration.mongodb.lib.migration.runner→packages.core.lib.interfaces.migration.migration-report_interface.MigrationReportpackages.integration.mongodb.lib.migration.snapshots→packages.core.lib.interfaces.migration.migration-report_interface.MigrationReport
- Direction
- integration.mongodb.lib.migration uses core.lib.interfaces.migration.migration-report_interface, so a change to core.lib.interfaces.migration.migration-report_interface can break integration.mongodb.lib.migration, while a change to integration.mongodb.lib.migration can't break core.lib.interfaces.migration.migration-report_interface.
- Position
- Below the diagonal: integration.mongodb.lib.migration uses a module listed above it, which is the healthy direction.
24→4 core.lib.interfaces.events.persist-outcome_type uses core.lib.interfaces.events.event-collection_type✕
- Connections
- 1 pair of types, where a type in core.lib.interfaces.events.persist-outcome_type uses a type in core.lib.interfaces.events.event-collection_type.
- The types involved
packages.core.lib.interfaces.events.persist-outcome_type.PersistTarget→packages.core.lib.interfaces.events.event-collection_type.IEventCollection
- Direction
- core.lib.interfaces.events.persist-outcome_type uses core.lib.interfaces.events.event-collection_type, so a change to core.lib.interfaces.events.event-collection_type can break core.lib.interfaces.events.persist-outcome_type, while a change to core.lib.interfaces.events.persist-outcome_type can't break core.lib.interfaces.events.event-collection_type.
- Position
- Below the diagonal: core.lib.interfaces.events.persist-outcome_type uses a module listed above it, which is the healthy direction.
24→19 core.lib.interfaces.events.persist-outcome_type uses core.lib.models.event-stream✕
- Connections
- 1 pair of types, where a type in core.lib.interfaces.events.persist-outcome_type uses a type in core.lib.models.event-stream.
- The types involved
packages.core.lib.interfaces.events.persist-outcome_type.PersistTarget→packages.core.lib.models.event-stream.EventStream
- Direction
- core.lib.interfaces.events.persist-outcome_type uses core.lib.models.event-stream, so a change to core.lib.models.event-stream can break core.lib.interfaces.events.persist-outcome_type, while a change to core.lib.interfaces.events.persist-outcome_type can't break core.lib.models.event-stream.
- Position
- Below the diagonal: core.lib.interfaces.events.persist-outcome_type uses a module listed above it, which is the healthy direction.
25→3 core.lib.snapshot-store uses core.lib.interfaces.aggregate.snapshot-collection_type✕
- Connections
- 1 pair of types, where a type in core.lib.snapshot-store uses a type in core.lib.interfaces.aggregate.snapshot-collection_type.
- The types involved
packages.core.lib.snapshot-store.SnapshotStore→packages.core.lib.interfaces.aggregate.snapshot-collection_type.ISnapshotCollection
- Direction
- core.lib.snapshot-store uses core.lib.interfaces.aggregate.snapshot-collection_type, so a change to core.lib.interfaces.aggregate.snapshot-collection_type can break core.lib.snapshot-store, while a change to core.lib.snapshot-store can't break core.lib.interfaces.aggregate.snapshot-collection_type.
- Position
- Below the diagonal: core.lib.snapshot-store uses a module listed above it, which is the healthy direction.
25→11 core.lib.snapshot-store uses core.lib.models.snapshot-envelope✕
- Connections
- 1 pair of types, where a type in core.lib.snapshot-store uses a type in core.lib.models.snapshot-envelope.
- The types involved
packages.core.lib.snapshot-store.SnapshotStore→packages.core.lib.models.snapshot-envelope.SnapshotEnvelope
- Direction
- core.lib.snapshot-store uses core.lib.models.snapshot-envelope, so a change to core.lib.models.snapshot-envelope can break core.lib.snapshot-store, while a change to core.lib.snapshot-store can't break core.lib.models.snapshot-envelope.
- Position
- Below the diagonal: core.lib.snapshot-store uses a module listed above it, which is the healthy direction.
25→17 core.lib.snapshot-store uses core.lib.interfaces.aggregate.snapshot-filter_interface✕
- Connections
- 2 pairs of types, where a type in core.lib.snapshot-store uses a type in core.lib.interfaces.aggregate.snapshot-filter_interface.
- The types involved
packages.core.lib.snapshot-store.SnapshotStore→packages.core.lib.interfaces.aggregate.snapshot-filter_interface.ISnapshotCollectionFilterpackages.core.lib.snapshot-store.SnapshotStore→packages.core.lib.interfaces.aggregate.snapshot-filter_interface.ISnapshotFilter
- Direction
- core.lib.snapshot-store uses core.lib.interfaces.aggregate.snapshot-filter_interface, so a change to core.lib.interfaces.aggregate.snapshot-filter_interface can break core.lib.snapshot-store, while a change to core.lib.snapshot-store can't break core.lib.interfaces.aggregate.snapshot-filter_interface.
- Position
- Below the diagonal: core.lib.snapshot-store uses a module listed above it, which is the healthy direction.
25→20 core.lib.snapshot-store uses core.lib.models.snapshot-stream✕
- Connections
- 1 pair of types, where a type in core.lib.snapshot-store uses a type in core.lib.models.snapshot-stream.
- The types involved
packages.core.lib.snapshot-store.SnapshotStore→packages.core.lib.models.snapshot-stream.SnapshotStream
- Direction
- core.lib.snapshot-store uses core.lib.models.snapshot-stream, so a change to core.lib.models.snapshot-stream can break core.lib.snapshot-store, while a change to core.lib.snapshot-store can't break core.lib.models.snapshot-stream.
- Position
- Below the diagonal: core.lib.snapshot-store uses a module listed above it, which is the healthy direction.
26→6 integration.mariadb.lib.migration uses core.lib.interfaces.migration.migration-options_interface✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib.migration uses a type in core.lib.interfaces.migration.migration-options_interface.
- The types involved
packages.integration.mariadb.lib.migration.migrate→packages.core.lib.interfaces.migration.migration-options_interface.MigrationOptions
- Direction
- integration.mariadb.lib.migration uses core.lib.interfaces.migration.migration-options_interface, so a change to core.lib.interfaces.migration.migration-options_interface can break integration.mariadb.lib.migration, while a change to integration.mariadb.lib.migration can't break core.lib.interfaces.migration.migration-options_interface.
- Position
- Below the diagonal: integration.mariadb.lib.migration uses a module listed above it, which is the healthy direction.
26→7 integration.mariadb.lib.migration uses core.lib.interfaces.migration.migration-report_interface✕
- Connections
- 3 pairs of types, where a type in integration.mariadb.lib.migration uses a type in core.lib.interfaces.migration.migration-report_interface.
- The types involved
packages.integration.mariadb.lib.migration.migrate→packages.core.lib.interfaces.migration.migration-report_interface.MigrationCollectionReportpackages.integration.mariadb.lib.migration.migrate→packages.core.lib.interfaces.migration.migration-report_interface.MigrationGappedStreampackages.integration.mariadb.lib.migration.migrate→packages.core.lib.interfaces.migration.migration-report_interface.MigrationReport
- Direction
- integration.mariadb.lib.migration uses core.lib.interfaces.migration.migration-report_interface, so a change to core.lib.interfaces.migration.migration-report_interface can break integration.mariadb.lib.migration, while a change to integration.mariadb.lib.migration can't break core.lib.interfaces.migration.migration-report_interface.
- Position
- Below the diagonal: integration.mariadb.lib.migration uses a module listed above it, which is the healthy direction.
26→13 integration.mariadb.lib.migration uses integration.mariadb.lib.mariadb_schema✕
- Connections
- 2 pairs of types, where a type in integration.mariadb.lib.migration uses a type in integration.mariadb.lib.mariadb_schema.
- The types involved
packages.integration.mariadb.lib.migration.migrate→packages.integration.mariadb.lib.mariadb_schema.ColumnInfopackages.integration.mariadb.lib.migration.migrate→packages.integration.mariadb.lib.mariadb_schema.Queryable
- Direction
- integration.mariadb.lib.migration uses integration.mariadb.lib.mariadb_schema, so a change to integration.mariadb.lib.mariadb_schema can break integration.mariadb.lib.migration, while a change to integration.mariadb.lib.migration can't break integration.mariadb.lib.mariadb_schema.
- Position
- Below the diagonal: integration.mariadb.lib.migration uses a module listed above it, which is the healthy direction.
26→22 integration.mariadb.lib.migration uses integration.mariadb.lib.migration.migrate✕
- Connections
- 7 pairs of types, where a type in integration.mariadb.lib.migration uses a type in integration.mariadb.lib.migration.migrate.
- The types involved
packages.integration.mariadb.lib.migration.migrate→packages.integration.mariadb.lib.migration.migrate.Environmentpackages.integration.mariadb.lib.migration.migrate→packages.integration.mariadb.lib.migration.migrate.EventSourcepackages.integration.mariadb.lib.migration.migrate→packages.integration.mariadb.lib.migration.migrate.InspectedTablepackages.integration.mariadb.lib.migration.migrate→packages.integration.mariadb.lib.migration.migrate.MigrateTableContextpackages.integration.mariadb.lib.migration.migrate→packages.integration.mariadb.lib.migration.migrate.MigrationHookspackages.integration.mariadb.lib.migration.migrate→packages.integration.mariadb.lib.migration.migrate.MigrationKindpackages.integration.mariadb.lib.migration.migrate→packages.integration.mariadb.lib.migration.migrate.TableMigration
- Direction
- integration.mariadb.lib.migration uses integration.mariadb.lib.migration.migrate, so a change to integration.mariadb.lib.migration.migrate can break integration.mariadb.lib.migration, while a change to integration.mariadb.lib.migration can't break integration.mariadb.lib.migration.migrate.
- Position
- Below the diagonal: integration.mariadb.lib.migration uses a module listed above it, which is the healthy direction.
27→6 integration.postgres.lib.migration uses core.lib.interfaces.migration.migration-options_interface✕
- Connections
- 1 pair of types, where a type in integration.postgres.lib.migration uses a type in core.lib.interfaces.migration.migration-options_interface.
- The types involved
packages.integration.postgres.lib.migration.migrate→packages.core.lib.interfaces.migration.migration-options_interface.MigrationOptions
- Direction
- integration.postgres.lib.migration uses core.lib.interfaces.migration.migration-options_interface, so a change to core.lib.interfaces.migration.migration-options_interface can break integration.postgres.lib.migration, while a change to integration.postgres.lib.migration can't break core.lib.interfaces.migration.migration-options_interface.
- Position
- Below the diagonal: integration.postgres.lib.migration uses a module listed above it, which is the healthy direction.
27→7 integration.postgres.lib.migration uses core.lib.interfaces.migration.migration-report_interface✕
- Connections
- 1 pair of types, where a type in integration.postgres.lib.migration uses a type in core.lib.interfaces.migration.migration-report_interface.
- The types involved
packages.integration.postgres.lib.migration.migrate→packages.core.lib.interfaces.migration.migration-report_interface.MigrationReport
- Direction
- integration.postgres.lib.migration uses core.lib.interfaces.migration.migration-report_interface, so a change to core.lib.interfaces.migration.migration-report_interface can break integration.postgres.lib.migration, while a change to integration.postgres.lib.migration can't break core.lib.interfaces.migration.migration-report_interface.
- Position
- Below the diagonal: integration.postgres.lib.migration uses a module listed above it, which is the healthy direction.
27→13 integration.postgres.lib.migration uses integration.mariadb.lib.mariadb_schema✕
- Connections
- 3 pairs of types, where a type in integration.postgres.lib.migration uses a type in integration.mariadb.lib.mariadb_schema.
- The types involved
packages.integration.postgres.lib.migration.inspect→packages.integration.mariadb.lib.mariadb_schema.Queryablepackages.integration.postgres.lib.migration.sql→packages.integration.mariadb.lib.mariadb_schema.ColumnInfopackages.integration.postgres.lib.migration.sql→packages.integration.mariadb.lib.mariadb_schema.IndexInfo
- Direction
- integration.postgres.lib.migration uses integration.mariadb.lib.mariadb_schema, so a change to integration.mariadb.lib.mariadb_schema can break integration.postgres.lib.migration, while a change to integration.postgres.lib.migration can't break integration.mariadb.lib.mariadb_schema.
- Position
- Below the diagonal: integration.postgres.lib.migration uses a module listed above it, which is the healthy direction.
27→22 integration.postgres.lib.migration uses integration.mariadb.lib.migration.migrate✕
- Connections
- 1 pair of types, where a type in integration.postgres.lib.migration uses a type in integration.mariadb.lib.migration.migrate.
- The types involved
packages.integration.postgres.lib.migration.migrate→packages.integration.mariadb.lib.migration.migrate.MigrationHooks
- Direction
- integration.postgres.lib.migration uses integration.mariadb.lib.migration.migrate, so a change to integration.mariadb.lib.migration.migrate can break integration.postgres.lib.migration, while a change to integration.postgres.lib.migration can't break integration.mariadb.lib.migration.migrate.
- Position
- Below the diagonal: integration.postgres.lib.migration uses a module listed above it, which is the healthy direction.
28→4 core.lib.event-store uses core.lib.interfaces.events.event-collection_type✕
- Connections
- 1 pair of types, where a type in core.lib.event-store uses a type in core.lib.interfaces.events.event-collection_type.
- The types involved
packages.core.lib.event-store.EventStore→packages.core.lib.interfaces.events.event-collection_type.IEventCollection
- Direction
- core.lib.event-store uses core.lib.interfaces.events.event-collection_type, so a change to core.lib.interfaces.events.event-collection_type can break core.lib.event-store, while a change to core.lib.event-store can't break core.lib.interfaces.events.event-collection_type.
- Position
- Below the diagonal: core.lib.event-store uses a module listed above it, which is the healthy direction.
28→5 core.lib.event-store uses core.lib.interfaces.events.event-store-capabilities_interface✕
- Connections
- 1 pair of types, where a type in core.lib.event-store uses a type in core.lib.interfaces.events.event-store-capabilities_interface.
- The types involved
packages.core.lib.event-store.EventStore→packages.core.lib.interfaces.events.event-store-capabilities_interface.EventStoreCapabilities
- Direction
- core.lib.event-store uses core.lib.interfaces.events.event-store-capabilities_interface, so a change to core.lib.interfaces.events.event-store-capabilities_interface can break core.lib.event-store, while a change to core.lib.event-store can't break core.lib.interfaces.events.event-store-capabilities_interface.
- Position
- Below the diagonal: core.lib.event-store uses a module listed above it, which is the healthy direction.
28→9 core.lib.event-store uses core.lib.models.event-envelope✕
- Connections
- 1 pair of types, where a type in core.lib.event-store uses a type in core.lib.models.event-envelope.
- The types involved
packages.core.lib.event-store.EventStore→packages.core.lib.models.event-envelope.EventEnvelope
- Direction
- core.lib.event-store uses core.lib.models.event-envelope, so a change to core.lib.models.event-envelope can break core.lib.event-store, while a change to core.lib.event-store can't break core.lib.models.event-envelope.
- Position
- Below the diagonal: core.lib.event-store uses a module listed above it, which is the healthy direction.
28→18 core.lib.event-store uses core.lib.interfaces.events.event-filter_interface✕
- Connections
- 3 pairs of types, where a type in core.lib.event-store uses a type in core.lib.interfaces.events.event-filter_interface.
- The types involved
packages.core.lib.event-store.EventStore→packages.core.lib.interfaces.events.event-filter_interface.IEventCollectionFilterpackages.core.lib.event-store.EventStore→packages.core.lib.interfaces.events.event-filter_interface.IEventFilterpackages.core.lib.event-store.EventStore→packages.core.lib.interfaces.events.event-filter_interface.IReadAllFilter
- Direction
- core.lib.event-store uses core.lib.interfaces.events.event-filter_interface, so a change to core.lib.interfaces.events.event-filter_interface can break core.lib.event-store, while a change to core.lib.event-store can't break core.lib.interfaces.events.event-filter_interface.
- Position
- Below the diagonal: core.lib.event-store uses a module listed above it, which is the healthy direction.
28→19 core.lib.event-store uses core.lib.models.event-stream✕
- Connections
- 1 pair of types, where a type in core.lib.event-store uses a type in core.lib.models.event-stream.
- The types involved
packages.core.lib.event-store.EventStore→packages.core.lib.models.event-stream.EventStream
- Direction
- core.lib.event-store uses core.lib.models.event-stream, so a change to core.lib.models.event-stream can break core.lib.event-store, while a change to core.lib.event-store can't break core.lib.models.event-stream.
- Position
- Below the diagonal: core.lib.event-store uses a module listed above it, which is the healthy direction.
28→24 core.lib.event-store uses core.lib.interfaces.events.persist-outcome_type✕
- Connections
- 2 pairs of types, where a type in core.lib.event-store uses a type in core.lib.interfaces.events.persist-outcome_type.
- The types involved
packages.core.lib.event-store.EventStore→packages.core.lib.interfaces.events.persist-outcome_type.PersistOutcomepackages.core.lib.event-store.EventStore→packages.core.lib.interfaces.events.persist-outcome_type.PersistTarget
- Direction
- core.lib.event-store uses core.lib.interfaces.events.persist-outcome_type, so a change to core.lib.interfaces.events.persist-outcome_type can break core.lib.event-store, while a change to core.lib.event-store can't break core.lib.interfaces.events.persist-outcome_type.
- Position
- Below the diagonal: core.lib.event-store uses a module listed above it, which is the healthy direction.
29→3 core.lib.integration.snapshot-store.in-memory_snapshot-store uses core.lib.interfaces.aggregate.snapshot-collection_type✕
- Connections
- 1 pair of types, where a type in core.lib.integration.snapshot-store.in-memory_snapshot-store uses a type in core.lib.interfaces.aggregate.snapshot-collection_type.
- The types involved
packages.core.lib.integration.snapshot-store.in-memory_snapshot-store.InMemorySnapshotStore→packages.core.lib.interfaces.aggregate.snapshot-collection_type.ISnapshotCollection
- Direction
- core.lib.integration.snapshot-store.in-memory_snapshot-store uses core.lib.interfaces.aggregate.snapshot-collection_type, so a change to core.lib.interfaces.aggregate.snapshot-collection_type can break core.lib.integration.snapshot-store.in-memory_snapshot-store, while a change to core.lib.integration.snapshot-store.in-memory_snapshot-store can't break core.lib.interfaces.aggregate.snapshot-collection_type.
- Position
- Below the diagonal: core.lib.integration.snapshot-store.in-memory_snapshot-store uses a module listed above it, which is the healthy direction.
29→11 core.lib.integration.snapshot-store.in-memory_snapshot-store uses core.lib.models.snapshot-envelope✕
- Connections
- 1 pair of types, where a type in core.lib.integration.snapshot-store.in-memory_snapshot-store uses a type in core.lib.models.snapshot-envelope.
- The types involved
packages.core.lib.integration.snapshot-store.in-memory_snapshot-store.InMemorySnapshotStore→packages.core.lib.models.snapshot-envelope.SnapshotEnvelope
- Direction
- core.lib.integration.snapshot-store.in-memory_snapshot-store uses core.lib.models.snapshot-envelope, so a change to core.lib.models.snapshot-envelope can break core.lib.integration.snapshot-store.in-memory_snapshot-store, while a change to core.lib.integration.snapshot-store.in-memory_snapshot-store can't break core.lib.models.snapshot-envelope.
- Position
- Below the diagonal: core.lib.integration.snapshot-store.in-memory_snapshot-store uses a module listed above it, which is the healthy direction.
29→17 core.lib.integration.snapshot-store.in-memory_snapshot-store uses core.lib.interfaces.aggregate.snapshot-filter_interface✕
- Connections
- 2 pairs of types, where a type in core.lib.integration.snapshot-store.in-memory_snapshot-store uses a type in core.lib.interfaces.aggregate.snapshot-filter_interface.
- The types involved
packages.core.lib.integration.snapshot-store.in-memory_snapshot-store.InMemorySnapshotStore→packages.core.lib.interfaces.aggregate.snapshot-filter_interface.ISnapshotCollectionFilterpackages.core.lib.integration.snapshot-store.in-memory_snapshot-store.InMemorySnapshotStore→packages.core.lib.interfaces.aggregate.snapshot-filter_interface.ISnapshotFilter
- Direction
- core.lib.integration.snapshot-store.in-memory_snapshot-store uses core.lib.interfaces.aggregate.snapshot-filter_interface, so a change to core.lib.interfaces.aggregate.snapshot-filter_interface can break core.lib.integration.snapshot-store.in-memory_snapshot-store, while a change to core.lib.integration.snapshot-store.in-memory_snapshot-store can't break core.lib.interfaces.aggregate.snapshot-filter_interface.
- Position
- Below the diagonal: core.lib.integration.snapshot-store.in-memory_snapshot-store uses a module listed above it, which is the healthy direction.
29→20 core.lib.integration.snapshot-store.in-memory_snapshot-store uses core.lib.models.snapshot-stream✕
- Connections
- 1 pair of types, where a type in core.lib.integration.snapshot-store.in-memory_snapshot-store uses a type in core.lib.models.snapshot-stream.
- The types involved
packages.core.lib.integration.snapshot-store.in-memory_snapshot-store.InMemorySnapshotStore→packages.core.lib.models.snapshot-stream.SnapshotStream
- Direction
- core.lib.integration.snapshot-store.in-memory_snapshot-store uses core.lib.models.snapshot-stream, so a change to core.lib.models.snapshot-stream can break core.lib.integration.snapshot-store.in-memory_snapshot-store, while a change to core.lib.integration.snapshot-store.in-memory_snapshot-store can't break core.lib.models.snapshot-stream.
- Position
- Below the diagonal: core.lib.integration.snapshot-store.in-memory_snapshot-store uses a module listed above it, which is the healthy direction.
29→25 core.lib.integration.snapshot-store.in-memory_snapshot-store uses core.lib.snapshot-store✕
- Connections
- 1 pair of types, where a type in core.lib.integration.snapshot-store.in-memory_snapshot-store uses a type in core.lib.snapshot-store.
- The types involved
packages.core.lib.integration.snapshot-store.in-memory_snapshot-store.InMemorySnapshotStore→packages.core.lib.snapshot-store.SnapshotStore
- Direction
- core.lib.integration.snapshot-store.in-memory_snapshot-store uses core.lib.snapshot-store, so a change to core.lib.snapshot-store can break core.lib.integration.snapshot-store.in-memory_snapshot-store, while a change to core.lib.integration.snapshot-store.in-memory_snapshot-store can't break core.lib.snapshot-store.
- Position
- Below the diagonal: core.lib.integration.snapshot-store.in-memory_snapshot-store uses a module listed above it, which is the healthy direction.
30→3 integration.mariadb.lib.mariadb_snapshot-store uses core.lib.interfaces.aggregate.snapshot-collection_type✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib.mariadb_snapshot-store uses a type in core.lib.interfaces.aggregate.snapshot-collection_type.
- The types involved
packages.integration.mariadb.lib.mariadb_snapshot-store.MariaDBSnapshotStore→packages.core.lib.interfaces.aggregate.snapshot-collection_type.ISnapshotCollection
- Direction
- integration.mariadb.lib.mariadb_snapshot-store uses core.lib.interfaces.aggregate.snapshot-collection_type, so a change to core.lib.interfaces.aggregate.snapshot-collection_type can break integration.mariadb.lib.mariadb_snapshot-store, while a change to integration.mariadb.lib.mariadb_snapshot-store can't break core.lib.interfaces.aggregate.snapshot-collection_type.
- Position
- Below the diagonal: integration.mariadb.lib.mariadb_snapshot-store uses a module listed above it, which is the healthy direction.
30→6 integration.mariadb.lib.mariadb_snapshot-store uses core.lib.interfaces.migration.migration-options_interface✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib.mariadb_snapshot-store uses a type in core.lib.interfaces.migration.migration-options_interface.
- The types involved
packages.integration.mariadb.lib.mariadb_snapshot-store.MariaDBSnapshotStore→packages.core.lib.interfaces.migration.migration-options_interface.MigrationOptions
- Direction
- integration.mariadb.lib.mariadb_snapshot-store uses core.lib.interfaces.migration.migration-options_interface, so a change to core.lib.interfaces.migration.migration-options_interface can break integration.mariadb.lib.mariadb_snapshot-store, while a change to integration.mariadb.lib.mariadb_snapshot-store can't break core.lib.interfaces.migration.migration-options_interface.
- Position
- Below the diagonal: integration.mariadb.lib.mariadb_snapshot-store uses a module listed above it, which is the healthy direction.
30→7 integration.mariadb.lib.mariadb_snapshot-store uses core.lib.interfaces.migration.migration-report_interface✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib.mariadb_snapshot-store uses a type in core.lib.interfaces.migration.migration-report_interface.
- The types involved
packages.integration.mariadb.lib.mariadb_snapshot-store.MariaDBSnapshotStore→packages.core.lib.interfaces.migration.migration-report_interface.MigrationReport
- Direction
- integration.mariadb.lib.mariadb_snapshot-store uses core.lib.interfaces.migration.migration-report_interface, so a change to core.lib.interfaces.migration.migration-report_interface can break integration.mariadb.lib.mariadb_snapshot-store, while a change to integration.mariadb.lib.mariadb_snapshot-store can't break core.lib.interfaces.migration.migration-report_interface.
- Position
- Below the diagonal: integration.mariadb.lib.mariadb_snapshot-store uses a module listed above it, which is the healthy direction.
30→11 integration.mariadb.lib.mariadb_snapshot-store uses core.lib.models.snapshot-envelope✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib.mariadb_snapshot-store uses a type in core.lib.models.snapshot-envelope.
- The types involved
packages.integration.mariadb.lib.mariadb_snapshot-store.MariaDBSnapshotStore→packages.core.lib.models.snapshot-envelope.SnapshotEnvelope
- Direction
- integration.mariadb.lib.mariadb_snapshot-store uses core.lib.models.snapshot-envelope, so a change to core.lib.models.snapshot-envelope can break integration.mariadb.lib.mariadb_snapshot-store, while a change to integration.mariadb.lib.mariadb_snapshot-store can't break core.lib.models.snapshot-envelope.
- Position
- Below the diagonal: integration.mariadb.lib.mariadb_snapshot-store uses a module listed above it, which is the healthy direction.
30→17 integration.mariadb.lib.mariadb_snapshot-store uses core.lib.interfaces.aggregate.snapshot-filter_interface✕
- Connections
- 2 pairs of types, where a type in integration.mariadb.lib.mariadb_snapshot-store uses a type in core.lib.interfaces.aggregate.snapshot-filter_interface.
- The types involved
packages.integration.mariadb.lib.mariadb_snapshot-store.MariaDBSnapshotStore→packages.core.lib.interfaces.aggregate.snapshot-filter_interface.ISnapshotCollectionFilterpackages.integration.mariadb.lib.mariadb_snapshot-store.MariaDBSnapshotStore→packages.core.lib.interfaces.aggregate.snapshot-filter_interface.ISnapshotFilter
- Direction
- integration.mariadb.lib.mariadb_snapshot-store uses core.lib.interfaces.aggregate.snapshot-filter_interface, so a change to core.lib.interfaces.aggregate.snapshot-filter_interface can break integration.mariadb.lib.mariadb_snapshot-store, while a change to integration.mariadb.lib.mariadb_snapshot-store can't break core.lib.interfaces.aggregate.snapshot-filter_interface.
- Position
- Below the diagonal: integration.mariadb.lib.mariadb_snapshot-store uses a module listed above it, which is the healthy direction.
30→20 integration.mariadb.lib.mariadb_snapshot-store uses core.lib.models.snapshot-stream✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib.mariadb_snapshot-store uses a type in core.lib.models.snapshot-stream.
- The types involved
packages.integration.mariadb.lib.mariadb_snapshot-store.MariaDBSnapshotStore→packages.core.lib.models.snapshot-stream.SnapshotStream
- Direction
- integration.mariadb.lib.mariadb_snapshot-store uses core.lib.models.snapshot-stream, so a change to core.lib.models.snapshot-stream can break integration.mariadb.lib.mariadb_snapshot-store, while a change to integration.mariadb.lib.mariadb_snapshot-store can't break core.lib.models.snapshot-stream.
- Position
- Below the diagonal: integration.mariadb.lib.mariadb_snapshot-store uses a module listed above it, which is the healthy direction.
30→25 integration.mariadb.lib.mariadb_snapshot-store uses core.lib.snapshot-store✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib.mariadb_snapshot-store uses a type in core.lib.snapshot-store.
- The types involved
packages.integration.mariadb.lib.mariadb_snapshot-store.MariaDBSnapshotStore→packages.core.lib.snapshot-store.SnapshotStore
- Direction
- integration.mariadb.lib.mariadb_snapshot-store uses core.lib.snapshot-store, so a change to core.lib.snapshot-store can break integration.mariadb.lib.mariadb_snapshot-store, while a change to integration.mariadb.lib.mariadb_snapshot-store can't break core.lib.snapshot-store.
- Position
- Below the diagonal: integration.mariadb.lib.mariadb_snapshot-store uses a module listed above it, which is the healthy direction.
31→3 integration.mongodb.lib.mongodb_snapshot-store uses core.lib.interfaces.aggregate.snapshot-collection_type✕
- Connections
- 2 pairs of types, where a type in integration.mongodb.lib.mongodb_snapshot-store uses a type in core.lib.interfaces.aggregate.snapshot-collection_type.
- The types involved
packages.integration.mongodb.lib.mongodb_snapshot-store.AppendTarget→packages.core.lib.interfaces.aggregate.snapshot-collection_type.ISnapshotCollectionpackages.integration.mongodb.lib.mongodb_snapshot-store.MongoDBSnapshotStore→packages.core.lib.interfaces.aggregate.snapshot-collection_type.ISnapshotCollection
- Direction
- integration.mongodb.lib.mongodb_snapshot-store uses core.lib.interfaces.aggregate.snapshot-collection_type, so a change to core.lib.interfaces.aggregate.snapshot-collection_type can break integration.mongodb.lib.mongodb_snapshot-store, while a change to integration.mongodb.lib.mongodb_snapshot-store can't break core.lib.interfaces.aggregate.snapshot-collection_type.
- Position
- Below the diagonal: integration.mongodb.lib.mongodb_snapshot-store uses a module listed above it, which is the healthy direction.
31→7 integration.mongodb.lib.mongodb_snapshot-store uses core.lib.interfaces.migration.migration-report_interface✕
- Connections
- 1 pair of types, where a type in integration.mongodb.lib.mongodb_snapshot-store uses a type in core.lib.interfaces.migration.migration-report_interface.
- The types involved
packages.integration.mongodb.lib.mongodb_snapshot-store.MongoDBSnapshotStore→packages.core.lib.interfaces.migration.migration-report_interface.MigrationReport
- Direction
- integration.mongodb.lib.mongodb_snapshot-store uses core.lib.interfaces.migration.migration-report_interface, so a change to core.lib.interfaces.migration.migration-report_interface can break integration.mongodb.lib.mongodb_snapshot-store, while a change to integration.mongodb.lib.mongodb_snapshot-store can't break core.lib.interfaces.migration.migration-report_interface.
- Position
- Below the diagonal: integration.mongodb.lib.mongodb_snapshot-store uses a module listed above it, which is the healthy direction.
31→11 integration.mongodb.lib.mongodb_snapshot-store uses core.lib.models.snapshot-envelope✕
- Connections
- 1 pair of types, where a type in integration.mongodb.lib.mongodb_snapshot-store uses a type in core.lib.models.snapshot-envelope.
- The types involved
packages.integration.mongodb.lib.mongodb_snapshot-store.MongoDBSnapshotStore→packages.core.lib.models.snapshot-envelope.SnapshotEnvelope
- Direction
- integration.mongodb.lib.mongodb_snapshot-store uses core.lib.models.snapshot-envelope, so a change to core.lib.models.snapshot-envelope can break integration.mongodb.lib.mongodb_snapshot-store, while a change to integration.mongodb.lib.mongodb_snapshot-store can't break core.lib.models.snapshot-envelope.
- Position
- Below the diagonal: integration.mongodb.lib.mongodb_snapshot-store uses a module listed above it, which is the healthy direction.
31→17 integration.mongodb.lib.mongodb_snapshot-store uses core.lib.interfaces.aggregate.snapshot-filter_interface✕
- Connections
- 2 pairs of types, where a type in integration.mongodb.lib.mongodb_snapshot-store uses a type in core.lib.interfaces.aggregate.snapshot-filter_interface.
- The types involved
packages.integration.mongodb.lib.mongodb_snapshot-store.MongoDBSnapshotStore→packages.core.lib.interfaces.aggregate.snapshot-filter_interface.ISnapshotCollectionFilterpackages.integration.mongodb.lib.mongodb_snapshot-store.MongoDBSnapshotStore→packages.core.lib.interfaces.aggregate.snapshot-filter_interface.ISnapshotFilter
- Direction
- integration.mongodb.lib.mongodb_snapshot-store uses core.lib.interfaces.aggregate.snapshot-filter_interface, so a change to core.lib.interfaces.aggregate.snapshot-filter_interface can break integration.mongodb.lib.mongodb_snapshot-store, while a change to integration.mongodb.lib.mongodb_snapshot-store can't break core.lib.interfaces.aggregate.snapshot-filter_interface.
- Position
- Below the diagonal: integration.mongodb.lib.mongodb_snapshot-store uses a module listed above it, which is the healthy direction.
31→20 integration.mongodb.lib.mongodb_snapshot-store uses core.lib.models.snapshot-stream✕
- Connections
- 2 pairs of types, where a type in integration.mongodb.lib.mongodb_snapshot-store uses a type in core.lib.models.snapshot-stream.
- The types involved
packages.integration.mongodb.lib.mongodb_snapshot-store.AppendTarget→packages.core.lib.models.snapshot-stream.SnapshotStreampackages.integration.mongodb.lib.mongodb_snapshot-store.MongoDBSnapshotStore→packages.core.lib.models.snapshot-stream.SnapshotStream
- Direction
- integration.mongodb.lib.mongodb_snapshot-store uses core.lib.models.snapshot-stream, so a change to core.lib.models.snapshot-stream can break integration.mongodb.lib.mongodb_snapshot-store, while a change to integration.mongodb.lib.mongodb_snapshot-store can't break core.lib.models.snapshot-stream.
- Position
- Below the diagonal: integration.mongodb.lib.mongodb_snapshot-store uses a module listed above it, which is the healthy direction.
31→25 integration.mongodb.lib.mongodb_snapshot-store uses core.lib.snapshot-store✕
- Connections
- 1 pair of types, where a type in integration.mongodb.lib.mongodb_snapshot-store uses a type in core.lib.snapshot-store.
- The types involved
packages.integration.mongodb.lib.mongodb_snapshot-store.MongoDBSnapshotStore→packages.core.lib.snapshot-store.SnapshotStore
- Direction
- integration.mongodb.lib.mongodb_snapshot-store uses core.lib.snapshot-store, so a change to core.lib.snapshot-store can break integration.mongodb.lib.mongodb_snapshot-store, while a change to integration.mongodb.lib.mongodb_snapshot-store can't break core.lib.snapshot-store.
- Position
- Below the diagonal: integration.mongodb.lib.mongodb_snapshot-store uses a module listed above it, which is the healthy direction.
32→3 integration.postgres.lib.postgres_snapshot-store uses core.lib.interfaces.aggregate.snapshot-collection_type✕
- Connections
- 1 pair of types, where a type in integration.postgres.lib.postgres_snapshot-store uses a type in core.lib.interfaces.aggregate.snapshot-collection_type.
- The types involved
packages.integration.postgres.lib.postgres_snapshot-store.PostgresSnapshotStore→packages.core.lib.interfaces.aggregate.snapshot-collection_type.ISnapshotCollection
- Direction
- integration.postgres.lib.postgres_snapshot-store uses core.lib.interfaces.aggregate.snapshot-collection_type, so a change to core.lib.interfaces.aggregate.snapshot-collection_type can break integration.postgres.lib.postgres_snapshot-store, while a change to integration.postgres.lib.postgres_snapshot-store can't break core.lib.interfaces.aggregate.snapshot-collection_type.
- Position
- Below the diagonal: integration.postgres.lib.postgres_snapshot-store uses a module listed above it, which is the healthy direction.
32→6 integration.postgres.lib.postgres_snapshot-store uses core.lib.interfaces.migration.migration-options_interface✕
- Connections
- 1 pair of types, where a type in integration.postgres.lib.postgres_snapshot-store uses a type in core.lib.interfaces.migration.migration-options_interface.
- The types involved
packages.integration.postgres.lib.postgres_snapshot-store.PostgresSnapshotStore→packages.core.lib.interfaces.migration.migration-options_interface.MigrationOptions
- Direction
- integration.postgres.lib.postgres_snapshot-store uses core.lib.interfaces.migration.migration-options_interface, so a change to core.lib.interfaces.migration.migration-options_interface can break integration.postgres.lib.postgres_snapshot-store, while a change to integration.postgres.lib.postgres_snapshot-store can't break core.lib.interfaces.migration.migration-options_interface.
- Position
- Below the diagonal: integration.postgres.lib.postgres_snapshot-store uses a module listed above it, which is the healthy direction.
32→7 integration.postgres.lib.postgres_snapshot-store uses core.lib.interfaces.migration.migration-report_interface✕
- Connections
- 1 pair of types, where a type in integration.postgres.lib.postgres_snapshot-store uses a type in core.lib.interfaces.migration.migration-report_interface.
- The types involved
packages.integration.postgres.lib.postgres_snapshot-store.PostgresSnapshotStore→packages.core.lib.interfaces.migration.migration-report_interface.MigrationReport
- Direction
- integration.postgres.lib.postgres_snapshot-store uses core.lib.interfaces.migration.migration-report_interface, so a change to core.lib.interfaces.migration.migration-report_interface can break integration.postgres.lib.postgres_snapshot-store, while a change to integration.postgres.lib.postgres_snapshot-store can't break core.lib.interfaces.migration.migration-report_interface.
- Position
- Below the diagonal: integration.postgres.lib.postgres_snapshot-store uses a module listed above it, which is the healthy direction.
32→11 integration.postgres.lib.postgres_snapshot-store uses core.lib.models.snapshot-envelope✕
- Connections
- 1 pair of types, where a type in integration.postgres.lib.postgres_snapshot-store uses a type in core.lib.models.snapshot-envelope.
- The types involved
packages.integration.postgres.lib.postgres_snapshot-store.PostgresSnapshotStore→packages.core.lib.models.snapshot-envelope.SnapshotEnvelope
- Direction
- integration.postgres.lib.postgres_snapshot-store uses core.lib.models.snapshot-envelope, so a change to core.lib.models.snapshot-envelope can break integration.postgres.lib.postgres_snapshot-store, while a change to integration.postgres.lib.postgres_snapshot-store can't break core.lib.models.snapshot-envelope.
- Position
- Below the diagonal: integration.postgres.lib.postgres_snapshot-store uses a module listed above it, which is the healthy direction.
32→17 integration.postgres.lib.postgres_snapshot-store uses core.lib.interfaces.aggregate.snapshot-filter_interface✕
- Connections
- 2 pairs of types, where a type in integration.postgres.lib.postgres_snapshot-store uses a type in core.lib.interfaces.aggregate.snapshot-filter_interface.
- The types involved
packages.integration.postgres.lib.postgres_snapshot-store.PostgresSnapshotStore→packages.core.lib.interfaces.aggregate.snapshot-filter_interface.ISnapshotCollectionFilterpackages.integration.postgres.lib.postgres_snapshot-store.PostgresSnapshotStore→packages.core.lib.interfaces.aggregate.snapshot-filter_interface.ISnapshotFilter
- Direction
- integration.postgres.lib.postgres_snapshot-store uses core.lib.interfaces.aggregate.snapshot-filter_interface, so a change to core.lib.interfaces.aggregate.snapshot-filter_interface can break integration.postgres.lib.postgres_snapshot-store, while a change to integration.postgres.lib.postgres_snapshot-store can't break core.lib.interfaces.aggregate.snapshot-filter_interface.
- Position
- Below the diagonal: integration.postgres.lib.postgres_snapshot-store uses a module listed above it, which is the healthy direction.
32→20 integration.postgres.lib.postgres_snapshot-store uses core.lib.models.snapshot-stream✕
- Connections
- 1 pair of types, where a type in integration.postgres.lib.postgres_snapshot-store uses a type in core.lib.models.snapshot-stream.
- The types involved
packages.integration.postgres.lib.postgres_snapshot-store.PostgresSnapshotStore→packages.core.lib.models.snapshot-stream.SnapshotStream
- Direction
- integration.postgres.lib.postgres_snapshot-store uses core.lib.models.snapshot-stream, so a change to core.lib.models.snapshot-stream can break integration.postgres.lib.postgres_snapshot-store, while a change to integration.postgres.lib.postgres_snapshot-store can't break core.lib.models.snapshot-stream.
- Position
- Below the diagonal: integration.postgres.lib.postgres_snapshot-store uses a module listed above it, which is the healthy direction.
32→25 integration.postgres.lib.postgres_snapshot-store uses core.lib.snapshot-store✕
- Connections
- 1 pair of types, where a type in integration.postgres.lib.postgres_snapshot-store uses a type in core.lib.snapshot-store.
- The types involved
packages.integration.postgres.lib.postgres_snapshot-store.PostgresSnapshotStore→packages.core.lib.snapshot-store.SnapshotStore
- Direction
- integration.postgres.lib.postgres_snapshot-store uses core.lib.snapshot-store, so a change to core.lib.snapshot-store can break integration.postgres.lib.postgres_snapshot-store, while a change to integration.postgres.lib.postgres_snapshot-store can't break core.lib.snapshot-store.
- Position
- Below the diagonal: integration.postgres.lib.postgres_snapshot-store uses a module listed above it, which is the healthy direction.
33→4 core.lib.integration.event-store.in-memory_event-store uses core.lib.interfaces.events.event-collection_type✕
- Connections
- 1 pair of types, where a type in core.lib.integration.event-store.in-memory_event-store uses a type in core.lib.interfaces.events.event-collection_type.
- The types involved
packages.core.lib.integration.event-store.in-memory_event-store.InMemoryEventStore→packages.core.lib.interfaces.events.event-collection_type.IEventCollection
- Direction
- core.lib.integration.event-store.in-memory_event-store uses core.lib.interfaces.events.event-collection_type, so a change to core.lib.interfaces.events.event-collection_type can break core.lib.integration.event-store.in-memory_event-store, while a change to core.lib.integration.event-store.in-memory_event-store can't break core.lib.interfaces.events.event-collection_type.
- Position
- Below the diagonal: core.lib.integration.event-store.in-memory_event-store uses a module listed above it, which is the healthy direction.
33→5 core.lib.integration.event-store.in-memory_event-store uses core.lib.interfaces.events.event-store-capabilities_interface✕
- Connections
- 1 pair of types, where a type in core.lib.integration.event-store.in-memory_event-store uses a type in core.lib.interfaces.events.event-store-capabilities_interface.
- The types involved
packages.core.lib.integration.event-store.in-memory_event-store.InMemoryEventStore→packages.core.lib.interfaces.events.event-store-capabilities_interface.EventStoreCapabilities
- Direction
- core.lib.integration.event-store.in-memory_event-store uses core.lib.interfaces.events.event-store-capabilities_interface, so a change to core.lib.interfaces.events.event-store-capabilities_interface can break core.lib.integration.event-store.in-memory_event-store, while a change to core.lib.integration.event-store.in-memory_event-store can't break core.lib.interfaces.events.event-store-capabilities_interface.
- Position
- Below the diagonal: core.lib.integration.event-store.in-memory_event-store uses a module listed above it, which is the healthy direction.
33→9 core.lib.integration.event-store.in-memory_event-store uses core.lib.models.event-envelope✕
- Connections
- 1 pair of types, where a type in core.lib.integration.event-store.in-memory_event-store uses a type in core.lib.models.event-envelope.
- The types involved
packages.core.lib.integration.event-store.in-memory_event-store.InMemoryEventStore→packages.core.lib.models.event-envelope.EventEnvelope
- Direction
- core.lib.integration.event-store.in-memory_event-store uses core.lib.models.event-envelope, so a change to core.lib.models.event-envelope can break core.lib.integration.event-store.in-memory_event-store, while a change to core.lib.integration.event-store.in-memory_event-store can't break core.lib.models.event-envelope.
- Position
- Below the diagonal: core.lib.integration.event-store.in-memory_event-store uses a module listed above it, which is the healthy direction.
33→18 core.lib.integration.event-store.in-memory_event-store uses core.lib.interfaces.events.event-filter_interface✕
- Connections
- 3 pairs of types, where a type in core.lib.integration.event-store.in-memory_event-store uses a type in core.lib.interfaces.events.event-filter_interface.
- The types involved
packages.core.lib.integration.event-store.in-memory_event-store.InMemoryEventStore→packages.core.lib.interfaces.events.event-filter_interface.IEventCollectionFilterpackages.core.lib.integration.event-store.in-memory_event-store.InMemoryEventStore→packages.core.lib.interfaces.events.event-filter_interface.IEventFilterpackages.core.lib.integration.event-store.in-memory_event-store.InMemoryEventStore→packages.core.lib.interfaces.events.event-filter_interface.IReadAllFilter
- Direction
- core.lib.integration.event-store.in-memory_event-store uses core.lib.interfaces.events.event-filter_interface, so a change to core.lib.interfaces.events.event-filter_interface can break core.lib.integration.event-store.in-memory_event-store, while a change to core.lib.integration.event-store.in-memory_event-store can't break core.lib.interfaces.events.event-filter_interface.
- Position
- Below the diagonal: core.lib.integration.event-store.in-memory_event-store uses a module listed above it, which is the healthy direction.
33→19 core.lib.integration.event-store.in-memory_event-store uses core.lib.models.event-stream✕
- Connections
- 1 pair of types, where a type in core.lib.integration.event-store.in-memory_event-store uses a type in core.lib.models.event-stream.
- The types involved
packages.core.lib.integration.event-store.in-memory_event-store.InMemoryEventStore→packages.core.lib.models.event-stream.EventStream
- Direction
- core.lib.integration.event-store.in-memory_event-store uses core.lib.models.event-stream, so a change to core.lib.models.event-stream can break core.lib.integration.event-store.in-memory_event-store, while a change to core.lib.integration.event-store.in-memory_event-store can't break core.lib.models.event-stream.
- Position
- Below the diagonal: core.lib.integration.event-store.in-memory_event-store uses a module listed above it, which is the healthy direction.
33→24 core.lib.integration.event-store.in-memory_event-store uses core.lib.interfaces.events.persist-outcome_type✕
- Connections
- 2 pairs of types, where a type in core.lib.integration.event-store.in-memory_event-store uses a type in core.lib.interfaces.events.persist-outcome_type.
- The types involved
packages.core.lib.integration.event-store.in-memory_event-store.InMemoryEventStore→packages.core.lib.interfaces.events.persist-outcome_type.PersistOutcomepackages.core.lib.integration.event-store.in-memory_event-store.InMemoryEventStore→packages.core.lib.interfaces.events.persist-outcome_type.PersistTarget
- Direction
- core.lib.integration.event-store.in-memory_event-store uses core.lib.interfaces.events.persist-outcome_type, so a change to core.lib.interfaces.events.persist-outcome_type can break core.lib.integration.event-store.in-memory_event-store, while a change to core.lib.integration.event-store.in-memory_event-store can't break core.lib.interfaces.events.persist-outcome_type.
- Position
- Below the diagonal: core.lib.integration.event-store.in-memory_event-store uses a module listed above it, which is the healthy direction.
33→28 core.lib.integration.event-store.in-memory_event-store uses core.lib.event-store✕
- Connections
- 1 pair of types, where a type in core.lib.integration.event-store.in-memory_event-store uses a type in core.lib.event-store.
- The types involved
packages.core.lib.integration.event-store.in-memory_event-store.InMemoryEventStore→packages.core.lib.event-store.EventStore
- Direction
- core.lib.integration.event-store.in-memory_event-store uses core.lib.event-store, so a change to core.lib.event-store can break core.lib.integration.event-store.in-memory_event-store, while a change to core.lib.integration.event-store.in-memory_event-store can't break core.lib.event-store.
- Position
- Below the diagonal: core.lib.integration.event-store.in-memory_event-store uses a module listed above it, which is the healthy direction.
34→1 core.lib.stores uses core.lib.constants✕
- Connections
- 1 pair of types, where a type in core.lib.stores uses a type in core.lib.constants.
- The types involved
packages.core.lib.stores.append-validation→packages.core.lib.constants.ExpectedVersion
- Direction
- core.lib.stores uses core.lib.constants, so a change to core.lib.constants can break core.lib.stores, while a change to core.lib.stores can't break core.lib.constants.
- Position
- Below the diagonal: core.lib.stores uses a module listed above it, which is the healthy direction.
34→5 core.lib.stores uses core.lib.interfaces.events.event-store-capabilities_interface✕
- Connections
- 1 pair of types, where a type in core.lib.stores uses a type in core.lib.interfaces.events.event-store-capabilities_interface.
- The types involved
packages.core.lib.stores.capabilities→packages.core.lib.interfaces.events.event-store-capabilities_interface.EventStoreCapabilities
- Direction
- core.lib.stores uses core.lib.interfaces.events.event-store-capabilities_interface, so a change to core.lib.interfaces.events.event-store-capabilities_interface can break core.lib.stores, while a change to core.lib.stores can't break core.lib.interfaces.events.event-store-capabilities_interface.
- Position
- Below the diagonal: core.lib.stores uses a module listed above it, which is the healthy direction.
34→19 core.lib.stores uses core.lib.models.event-stream✕
- Connections
- 1 pair of types, where a type in core.lib.stores uses a type in core.lib.models.event-stream.
- The types involved
packages.core.lib.stores.append-validation→packages.core.lib.models.event-stream.EventStream
- Direction
- core.lib.stores uses core.lib.models.event-stream, so a change to core.lib.models.event-stream can break core.lib.stores, while a change to core.lib.stores can't break core.lib.models.event-stream.
- Position
- Below the diagonal: core.lib.stores uses a module listed above it, which is the healthy direction.
34→28 core.lib.stores uses core.lib.event-store✕
- Connections
- 1 pair of types, where a type in core.lib.stores uses a type in core.lib.event-store.
- The types involved
packages.core.lib.stores.implementation-guard→packages.core.lib.event-store.EventStore
- Direction
- core.lib.stores uses core.lib.event-store, so a change to core.lib.event-store can break core.lib.stores, while a change to core.lib.stores can't break core.lib.event-store.
- Position
- Below the diagonal: core.lib.stores uses a module listed above it, which is the healthy direction.
35→9 core.lib.testing uses core.lib.models.event-envelope✕
- Connections
- 1 pair of types, where a type in core.lib.testing uses a type in core.lib.models.event-envelope.
- The types involved
packages.core.lib.testing.event-store.conformance→packages.core.lib.models.event-envelope.EventEnvelope
- Direction
- core.lib.testing uses core.lib.models.event-envelope, so a change to core.lib.models.event-envelope can break core.lib.testing, while a change to core.lib.testing can't break core.lib.models.event-envelope.
- Position
- Below the diagonal: core.lib.testing uses a module listed above it, which is the healthy direction.
35→11 core.lib.testing uses core.lib.models.snapshot-envelope✕
- Connections
- 1 pair of types, where a type in core.lib.testing uses a type in core.lib.models.snapshot-envelope.
- The types involved
packages.core.lib.testing.snapshot-store.conformance→packages.core.lib.models.snapshot-envelope.SnapshotEnvelope
- Direction
- core.lib.testing uses core.lib.models.snapshot-envelope, so a change to core.lib.models.snapshot-envelope can break core.lib.testing, while a change to core.lib.testing can't break core.lib.models.snapshot-envelope.
- Position
- Below the diagonal: core.lib.testing uses a module listed above it, which is the healthy direction.
35→15 core.lib.testing uses core.lib.event-map✕
- Connections
- 1 pair of types, where a type in core.lib.testing uses a type in core.lib.event-map.
- The types involved
packages.core.lib.testing.fixtures→packages.core.lib.event-map.EventMap
- Direction
- core.lib.testing uses core.lib.event-map, so a change to core.lib.event-map can break core.lib.testing, while a change to core.lib.testing can't break core.lib.event-map.
- Position
- Below the diagonal: core.lib.testing uses a module listed above it, which is the healthy direction.
35→19 core.lib.testing uses core.lib.models.event-stream✕
- Connections
- 1 pair of types, where a type in core.lib.testing uses a type in core.lib.models.event-stream.
- The types involved
packages.core.lib.testing.fixtures→packages.core.lib.models.event-stream.EventStream
- Direction
- core.lib.testing uses core.lib.models.event-stream, so a change to core.lib.models.event-stream can break core.lib.testing, while a change to core.lib.testing can't break core.lib.models.event-stream.
- Position
- Below the diagonal: core.lib.testing uses a module listed above it, which is the healthy direction.
35→20 core.lib.testing uses core.lib.models.snapshot-stream✕
- Connections
- 1 pair of types, where a type in core.lib.testing uses a type in core.lib.models.snapshot-stream.
- The types involved
packages.core.lib.testing.fixtures→packages.core.lib.models.snapshot-stream.SnapshotStream
- Direction
- core.lib.testing uses core.lib.models.snapshot-stream, so a change to core.lib.models.snapshot-stream can break core.lib.testing, while a change to core.lib.testing can't break core.lib.models.snapshot-stream.
- Position
- Below the diagonal: core.lib.testing uses a module listed above it, which is the healthy direction.
35→29 core.lib.testing uses core.lib.integration.snapshot-store.in-memory_snapshot-store✕
- Connections
- 1 pair of types, where a type in core.lib.testing uses a type in core.lib.integration.snapshot-store.in-memory_snapshot-store.
- The types involved
packages.core.lib.testing.in-memory→packages.core.lib.integration.snapshot-store.in-memory_snapshot-store.InMemorySnapshotStore
- Direction
- core.lib.testing uses core.lib.integration.snapshot-store.in-memory_snapshot-store, so a change to core.lib.integration.snapshot-store.in-memory_snapshot-store can break core.lib.testing, while a change to core.lib.testing can't break core.lib.integration.snapshot-store.in-memory_snapshot-store.
- Position
- Below the diagonal: core.lib.testing uses a module listed above it, which is the healthy direction.
36→4 integration.mariadb.lib.mariadb_event-store uses core.lib.interfaces.events.event-collection_type✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib.mariadb_event-store uses a type in core.lib.interfaces.events.event-collection_type.
- The types involved
packages.integration.mariadb.lib.mariadb_event-store.MariaDBEventStore→packages.core.lib.interfaces.events.event-collection_type.IEventCollection
- Direction
- integration.mariadb.lib.mariadb_event-store uses core.lib.interfaces.events.event-collection_type, so a change to core.lib.interfaces.events.event-collection_type can break integration.mariadb.lib.mariadb_event-store, while a change to integration.mariadb.lib.mariadb_event-store can't break core.lib.interfaces.events.event-collection_type.
- Position
- Below the diagonal: integration.mariadb.lib.mariadb_event-store uses a module listed above it, which is the healthy direction.
36→5 integration.mariadb.lib.mariadb_event-store uses core.lib.interfaces.events.event-store-capabilities_interface✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib.mariadb_event-store uses a type in core.lib.interfaces.events.event-store-capabilities_interface.
- The types involved
packages.integration.mariadb.lib.mariadb_event-store.MariaDBEventStore→packages.core.lib.interfaces.events.event-store-capabilities_interface.EventStoreCapabilities
- Direction
- integration.mariadb.lib.mariadb_event-store uses core.lib.interfaces.events.event-store-capabilities_interface, so a change to core.lib.interfaces.events.event-store-capabilities_interface can break integration.mariadb.lib.mariadb_event-store, while a change to integration.mariadb.lib.mariadb_event-store can't break core.lib.interfaces.events.event-store-capabilities_interface.
- Position
- Below the diagonal: integration.mariadb.lib.mariadb_event-store uses a module listed above it, which is the healthy direction.
36→6 integration.mariadb.lib.mariadb_event-store uses core.lib.interfaces.migration.migration-options_interface✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib.mariadb_event-store uses a type in core.lib.interfaces.migration.migration-options_interface.
- The types involved
packages.integration.mariadb.lib.mariadb_event-store.MariaDBEventStore→packages.core.lib.interfaces.migration.migration-options_interface.MigrationOptions
- Direction
- integration.mariadb.lib.mariadb_event-store uses core.lib.interfaces.migration.migration-options_interface, so a change to core.lib.interfaces.migration.migration-options_interface can break integration.mariadb.lib.mariadb_event-store, while a change to integration.mariadb.lib.mariadb_event-store can't break core.lib.interfaces.migration.migration-options_interface.
- Position
- Below the diagonal: integration.mariadb.lib.mariadb_event-store uses a module listed above it, which is the healthy direction.
36→7 integration.mariadb.lib.mariadb_event-store uses core.lib.interfaces.migration.migration-report_interface✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib.mariadb_event-store uses a type in core.lib.interfaces.migration.migration-report_interface.
- The types involved
packages.integration.mariadb.lib.mariadb_event-store.MariaDBEventStore→packages.core.lib.interfaces.migration.migration-report_interface.MigrationReport
- Direction
- integration.mariadb.lib.mariadb_event-store uses core.lib.interfaces.migration.migration-report_interface, so a change to core.lib.interfaces.migration.migration-report_interface can break integration.mariadb.lib.mariadb_event-store, while a change to integration.mariadb.lib.mariadb_event-store can't break core.lib.interfaces.migration.migration-report_interface.
- Position
- Below the diagonal: integration.mariadb.lib.mariadb_event-store uses a module listed above it, which is the healthy direction.
36→9 integration.mariadb.lib.mariadb_event-store uses core.lib.models.event-envelope✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib.mariadb_event-store uses a type in core.lib.models.event-envelope.
- The types involved
packages.integration.mariadb.lib.mariadb_event-store.MariaDBEventStore→packages.core.lib.models.event-envelope.EventEnvelope
- Direction
- integration.mariadb.lib.mariadb_event-store uses core.lib.models.event-envelope, so a change to core.lib.models.event-envelope can break integration.mariadb.lib.mariadb_event-store, while a change to integration.mariadb.lib.mariadb_event-store can't break core.lib.models.event-envelope.
- Position
- Below the diagonal: integration.mariadb.lib.mariadb_event-store uses a module listed above it, which is the healthy direction.
36→18 integration.mariadb.lib.mariadb_event-store uses core.lib.interfaces.events.event-filter_interface✕
- Connections
- 3 pairs of types, where a type in integration.mariadb.lib.mariadb_event-store uses a type in core.lib.interfaces.events.event-filter_interface.
- The types involved
packages.integration.mariadb.lib.mariadb_event-store.MariaDBEventStore→packages.core.lib.interfaces.events.event-filter_interface.IEventCollectionFilterpackages.integration.mariadb.lib.mariadb_event-store.MariaDBEventStore→packages.core.lib.interfaces.events.event-filter_interface.IEventFilterpackages.integration.mariadb.lib.mariadb_event-store.MariaDBEventStore→packages.core.lib.interfaces.events.event-filter_interface.IReadAllFilter
- Direction
- integration.mariadb.lib.mariadb_event-store uses core.lib.interfaces.events.event-filter_interface, so a change to core.lib.interfaces.events.event-filter_interface can break integration.mariadb.lib.mariadb_event-store, while a change to integration.mariadb.lib.mariadb_event-store can't break core.lib.interfaces.events.event-filter_interface.
- Position
- Below the diagonal: integration.mariadb.lib.mariadb_event-store uses a module listed above it, which is the healthy direction.
36→19 integration.mariadb.lib.mariadb_event-store uses core.lib.models.event-stream✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib.mariadb_event-store uses a type in core.lib.models.event-stream.
- The types involved
packages.integration.mariadb.lib.mariadb_event-store.MariaDBEventStore→packages.core.lib.models.event-stream.EventStream
- Direction
- integration.mariadb.lib.mariadb_event-store uses core.lib.models.event-stream, so a change to core.lib.models.event-stream can break integration.mariadb.lib.mariadb_event-store, while a change to integration.mariadb.lib.mariadb_event-store can't break core.lib.models.event-stream.
- Position
- Below the diagonal: integration.mariadb.lib.mariadb_event-store uses a module listed above it, which is the healthy direction.
36→24 integration.mariadb.lib.mariadb_event-store uses core.lib.interfaces.events.persist-outcome_type✕
- Connections
- 2 pairs of types, where a type in integration.mariadb.lib.mariadb_event-store uses a type in core.lib.interfaces.events.persist-outcome_type.
- The types involved
packages.integration.mariadb.lib.mariadb_event-store.MariaDBEventStore→packages.core.lib.interfaces.events.persist-outcome_type.PersistOutcomepackages.integration.mariadb.lib.mariadb_event-store.MariaDBEventStore→packages.core.lib.interfaces.events.persist-outcome_type.PersistTarget
- Direction
- integration.mariadb.lib.mariadb_event-store uses core.lib.interfaces.events.persist-outcome_type, so a change to core.lib.interfaces.events.persist-outcome_type can break integration.mariadb.lib.mariadb_event-store, while a change to integration.mariadb.lib.mariadb_event-store can't break core.lib.interfaces.events.persist-outcome_type.
- Position
- Below the diagonal: integration.mariadb.lib.mariadb_event-store uses a module listed above it, which is the healthy direction.
36→28 integration.mariadb.lib.mariadb_event-store uses core.lib.event-store✕
- Connections
- 1 pair of types, where a type in integration.mariadb.lib.mariadb_event-store uses a type in core.lib.event-store.
- The types involved
packages.integration.mariadb.lib.mariadb_event-store.MariaDBEventStore→packages.core.lib.event-store.EventStore
- Direction
- integration.mariadb.lib.mariadb_event-store uses core.lib.event-store, so a change to core.lib.event-store can break integration.mariadb.lib.mariadb_event-store, while a change to integration.mariadb.lib.mariadb_event-store can't break core.lib.event-store.
- Position
- Below the diagonal: integration.mariadb.lib.mariadb_event-store uses a module listed above it, which is the healthy direction.
37→4 integration.mongodb.lib.mongodb_event-store uses core.lib.interfaces.events.event-collection_type✕
- Connections
- 1 pair of types, where a type in integration.mongodb.lib.mongodb_event-store uses a type in core.lib.interfaces.events.event-collection_type.
- The types involved
packages.integration.mongodb.lib.mongodb_event-store.MongoDBEventStore→packages.core.lib.interfaces.events.event-collection_type.IEventCollection
- Direction
- integration.mongodb.lib.mongodb_event-store uses core.lib.interfaces.events.event-collection_type, so a change to core.lib.interfaces.events.event-collection_type can break integration.mongodb.lib.mongodb_event-store, while a change to integration.mongodb.lib.mongodb_event-store can't break core.lib.interfaces.events.event-collection_type.
- Position
- Below the diagonal: integration.mongodb.lib.mongodb_event-store uses a module listed above it, which is the healthy direction.
37→5 integration.mongodb.lib.mongodb_event-store uses core.lib.interfaces.events.event-store-capabilities_interface✕
- Connections
- 1 pair of types, where a type in integration.mongodb.lib.mongodb_event-store uses a type in core.lib.interfaces.events.event-store-capabilities_interface.
- The types involved
packages.integration.mongodb.lib.mongodb_event-store.MongoDBEventStore→packages.core.lib.interfaces.events.event-store-capabilities_interface.EventStoreCapabilities
- Direction
- integration.mongodb.lib.mongodb_event-store uses core.lib.interfaces.events.event-store-capabilities_interface, so a change to core.lib.interfaces.events.event-store-capabilities_interface can break integration.mongodb.lib.mongodb_event-store, while a change to integration.mongodb.lib.mongodb_event-store can't break core.lib.interfaces.events.event-store-capabilities_interface.
- Position
- Below the diagonal: integration.mongodb.lib.mongodb_event-store uses a module listed above it, which is the healthy direction.
37→7 integration.mongodb.lib.mongodb_event-store uses core.lib.interfaces.migration.migration-report_interface✕
- Connections
- 1 pair of types, where a type in integration.mongodb.lib.mongodb_event-store uses a type in core.lib.interfaces.migration.migration-report_interface.
- The types involved
packages.integration.mongodb.lib.mongodb_event-store.MongoDBEventStore→packages.core.lib.interfaces.migration.migration-report_interface.MigrationReport
- Direction
- integration.mongodb.lib.mongodb_event-store uses core.lib.interfaces.migration.migration-report_interface, so a change to core.lib.interfaces.migration.migration-report_interface can break integration.mongodb.lib.mongodb_event-store, while a change to integration.mongodb.lib.mongodb_event-store can't break core.lib.interfaces.migration.migration-report_interface.
- Position
- Below the diagonal: integration.mongodb.lib.mongodb_event-store uses a module listed above it, which is the healthy direction.
37→9 integration.mongodb.lib.mongodb_event-store uses core.lib.models.event-envelope✕
- Connections
- 1 pair of types, where a type in integration.mongodb.lib.mongodb_event-store uses a type in core.lib.models.event-envelope.
- The types involved
packages.integration.mongodb.lib.mongodb_event-store.MongoDBEventStore→packages.core.lib.models.event-envelope.EventEnvelope
- Direction
- integration.mongodb.lib.mongodb_event-store uses core.lib.models.event-envelope, so a change to core.lib.models.event-envelope can break integration.mongodb.lib.mongodb_event-store, while a change to integration.mongodb.lib.mongodb_event-store can't break core.lib.models.event-envelope.
- Position
- Below the diagonal: integration.mongodb.lib.mongodb_event-store uses a module listed above it, which is the healthy direction.
37→18 integration.mongodb.lib.mongodb_event-store uses core.lib.interfaces.events.event-filter_interface✕
- Connections
- 3 pairs of types, where a type in integration.mongodb.lib.mongodb_event-store uses a type in core.lib.interfaces.events.event-filter_interface.
- The types involved
packages.integration.mongodb.lib.mongodb_event-store.MongoDBEventStore→packages.core.lib.interfaces.events.event-filter_interface.IEventCollectionFilterpackages.integration.mongodb.lib.mongodb_event-store.MongoDBEventStore→packages.core.lib.interfaces.events.event-filter_interface.IEventFilterpackages.integration.mongodb.lib.mongodb_event-store.MongoDBEventStore→packages.core.lib.interfaces.events.event-filter_interface.IReadAllFilter
- Direction
- integration.mongodb.lib.mongodb_event-store uses core.lib.interfaces.events.event-filter_interface, so a change to core.lib.interfaces.events.event-filter_interface can break integration.mongodb.lib.mongodb_event-store, while a change to integration.mongodb.lib.mongodb_event-store can't break core.lib.interfaces.events.event-filter_interface.
- Position
- Below the diagonal: integration.mongodb.lib.mongodb_event-store uses a module listed above it, which is the healthy direction.
37→19 integration.mongodb.lib.mongodb_event-store uses core.lib.models.event-stream✕
- Connections
- 1 pair of types, where a type in integration.mongodb.lib.mongodb_event-store uses a type in core.lib.models.event-stream.
- The types involved
packages.integration.mongodb.lib.mongodb_event-store.MongoDBEventStore→packages.core.lib.models.event-stream.EventStream
- Direction
- integration.mongodb.lib.mongodb_event-store uses core.lib.models.event-stream, so a change to core.lib.models.event-stream can break integration.mongodb.lib.mongodb_event-store, while a change to integration.mongodb.lib.mongodb_event-store can't break core.lib.models.event-stream.
- Position
- Below the diagonal: integration.mongodb.lib.mongodb_event-store uses a module listed above it, which is the healthy direction.
37→24 integration.mongodb.lib.mongodb_event-store uses core.lib.interfaces.events.persist-outcome_type✕
- Connections
- 2 pairs of types, where a type in integration.mongodb.lib.mongodb_event-store uses a type in core.lib.interfaces.events.persist-outcome_type.
- The types involved
packages.integration.mongodb.lib.mongodb_event-store.MongoDBEventStore→packages.core.lib.interfaces.events.persist-outcome_type.PersistOutcomepackages.integration.mongodb.lib.mongodb_event-store.MongoDBEventStore→packages.core.lib.interfaces.events.persist-outcome_type.PersistTarget
- Direction
- integration.mongodb.lib.mongodb_event-store uses core.lib.interfaces.events.persist-outcome_type, so a change to core.lib.interfaces.events.persist-outcome_type can break integration.mongodb.lib.mongodb_event-store, while a change to integration.mongodb.lib.mongodb_event-store can't break core.lib.interfaces.events.persist-outcome_type.
- Position
- Below the diagonal: integration.mongodb.lib.mongodb_event-store uses a module listed above it, which is the healthy direction.
37→28 integration.mongodb.lib.mongodb_event-store uses core.lib.event-store✕
- Connections
- 1 pair of types, where a type in integration.mongodb.lib.mongodb_event-store uses a type in core.lib.event-store.
- The types involved
packages.integration.mongodb.lib.mongodb_event-store.MongoDBEventStore→packages.core.lib.event-store.EventStore
- Direction
- integration.mongodb.lib.mongodb_event-store uses core.lib.event-store, so a change to core.lib.event-store can break integration.mongodb.lib.mongodb_event-store, while a change to integration.mongodb.lib.mongodb_event-store can't break core.lib.event-store.
- Position
- Below the diagonal: integration.mongodb.lib.mongodb_event-store uses a module listed above it, which is the healthy direction.
38→4 integration.postgres.lib.postgres_event-store uses core.lib.interfaces.events.event-collection_type✕
- Connections
- 1 pair of types, where a type in integration.postgres.lib.postgres_event-store uses a type in core.lib.interfaces.events.event-collection_type.
- The types involved
packages.integration.postgres.lib.postgres_event-store.PostgresEventStore→packages.core.lib.interfaces.events.event-collection_type.IEventCollection
- Direction
- integration.postgres.lib.postgres_event-store uses core.lib.interfaces.events.event-collection_type, so a change to core.lib.interfaces.events.event-collection_type can break integration.postgres.lib.postgres_event-store, while a change to integration.postgres.lib.postgres_event-store can't break core.lib.interfaces.events.event-collection_type.
- Position
- Below the diagonal: integration.postgres.lib.postgres_event-store uses a module listed above it, which is the healthy direction.
38→5 integration.postgres.lib.postgres_event-store uses core.lib.interfaces.events.event-store-capabilities_interface✕
- Connections
- 1 pair of types, where a type in integration.postgres.lib.postgres_event-store uses a type in core.lib.interfaces.events.event-store-capabilities_interface.
- The types involved
packages.integration.postgres.lib.postgres_event-store.PostgresEventStore→packages.core.lib.interfaces.events.event-store-capabilities_interface.EventStoreCapabilities
- Direction
- integration.postgres.lib.postgres_event-store uses core.lib.interfaces.events.event-store-capabilities_interface, so a change to core.lib.interfaces.events.event-store-capabilities_interface can break integration.postgres.lib.postgres_event-store, while a change to integration.postgres.lib.postgres_event-store can't break core.lib.interfaces.events.event-store-capabilities_interface.
- Position
- Below the diagonal: integration.postgres.lib.postgres_event-store uses a module listed above it, which is the healthy direction.
38→6 integration.postgres.lib.postgres_event-store uses core.lib.interfaces.migration.migration-options_interface✕
- Connections
- 1 pair of types, where a type in integration.postgres.lib.postgres_event-store uses a type in core.lib.interfaces.migration.migration-options_interface.
- The types involved
packages.integration.postgres.lib.postgres_event-store.PostgresEventStore→packages.core.lib.interfaces.migration.migration-options_interface.MigrationOptions
- Direction
- integration.postgres.lib.postgres_event-store uses core.lib.interfaces.migration.migration-options_interface, so a change to core.lib.interfaces.migration.migration-options_interface can break integration.postgres.lib.postgres_event-store, while a change to integration.postgres.lib.postgres_event-store can't break core.lib.interfaces.migration.migration-options_interface.
- Position
- Below the diagonal: integration.postgres.lib.postgres_event-store uses a module listed above it, which is the healthy direction.
38→7 integration.postgres.lib.postgres_event-store uses core.lib.interfaces.migration.migration-report_interface✕
- Connections
- 1 pair of types, where a type in integration.postgres.lib.postgres_event-store uses a type in core.lib.interfaces.migration.migration-report_interface.
- The types involved
packages.integration.postgres.lib.postgres_event-store.PostgresEventStore→packages.core.lib.interfaces.migration.migration-report_interface.MigrationReport
- Direction
- integration.postgres.lib.postgres_event-store uses core.lib.interfaces.migration.migration-report_interface, so a change to core.lib.interfaces.migration.migration-report_interface can break integration.postgres.lib.postgres_event-store, while a change to integration.postgres.lib.postgres_event-store can't break core.lib.interfaces.migration.migration-report_interface.
- Position
- Below the diagonal: integration.postgres.lib.postgres_event-store uses a module listed above it, which is the healthy direction.
38→9 integration.postgres.lib.postgres_event-store uses core.lib.models.event-envelope✕
- Connections
- 1 pair of types, where a type in integration.postgres.lib.postgres_event-store uses a type in core.lib.models.event-envelope.
- The types involved
packages.integration.postgres.lib.postgres_event-store.PostgresEventStore→packages.core.lib.models.event-envelope.EventEnvelope
- Direction
- integration.postgres.lib.postgres_event-store uses core.lib.models.event-envelope, so a change to core.lib.models.event-envelope can break integration.postgres.lib.postgres_event-store, while a change to integration.postgres.lib.postgres_event-store can't break core.lib.models.event-envelope.
- Position
- Below the diagonal: integration.postgres.lib.postgres_event-store uses a module listed above it, which is the healthy direction.
38→18 integration.postgres.lib.postgres_event-store uses core.lib.interfaces.events.event-filter_interface✕
- Connections
- 3 pairs of types, where a type in integration.postgres.lib.postgres_event-store uses a type in core.lib.interfaces.events.event-filter_interface.
- The types involved
packages.integration.postgres.lib.postgres_event-store.PostgresEventStore→packages.core.lib.interfaces.events.event-filter_interface.IEventCollectionFilterpackages.integration.postgres.lib.postgres_event-store.PostgresEventStore→packages.core.lib.interfaces.events.event-filter_interface.IEventFilterpackages.integration.postgres.lib.postgres_event-store.PostgresEventStore→packages.core.lib.interfaces.events.event-filter_interface.IReadAllFilter
- Direction
- integration.postgres.lib.postgres_event-store uses core.lib.interfaces.events.event-filter_interface, so a change to core.lib.interfaces.events.event-filter_interface can break integration.postgres.lib.postgres_event-store, while a change to integration.postgres.lib.postgres_event-store can't break core.lib.interfaces.events.event-filter_interface.
- Position
- Below the diagonal: integration.postgres.lib.postgres_event-store uses a module listed above it, which is the healthy direction.
38→19 integration.postgres.lib.postgres_event-store uses core.lib.models.event-stream✕
- Connections
- 1 pair of types, where a type in integration.postgres.lib.postgres_event-store uses a type in core.lib.models.event-stream.
- The types involved
packages.integration.postgres.lib.postgres_event-store.PostgresEventStore→packages.core.lib.models.event-stream.EventStream
- Direction
- integration.postgres.lib.postgres_event-store uses core.lib.models.event-stream, so a change to core.lib.models.event-stream can break integration.postgres.lib.postgres_event-store, while a change to integration.postgres.lib.postgres_event-store can't break core.lib.models.event-stream.
- Position
- Below the diagonal: integration.postgres.lib.postgres_event-store uses a module listed above it, which is the healthy direction.
38→24 integration.postgres.lib.postgres_event-store uses core.lib.interfaces.events.persist-outcome_type✕
- Connections
- 2 pairs of types, where a type in integration.postgres.lib.postgres_event-store uses a type in core.lib.interfaces.events.persist-outcome_type.
- The types involved
packages.integration.postgres.lib.postgres_event-store.PostgresEventStore→packages.core.lib.interfaces.events.persist-outcome_type.PersistOutcomepackages.integration.postgres.lib.postgres_event-store.PostgresEventStore→packages.core.lib.interfaces.events.persist-outcome_type.PersistTarget
- Direction
- integration.postgres.lib.postgres_event-store uses core.lib.interfaces.events.persist-outcome_type, so a change to core.lib.interfaces.events.persist-outcome_type can break integration.postgres.lib.postgres_event-store, while a change to integration.postgres.lib.postgres_event-store can't break core.lib.interfaces.events.persist-outcome_type.
- Position
- Below the diagonal: integration.postgres.lib.postgres_event-store uses a module listed above it, which is the healthy direction.
38→28 integration.postgres.lib.postgres_event-store uses core.lib.event-store✕
- Connections
- 1 pair of types, where a type in integration.postgres.lib.postgres_event-store uses a type in core.lib.event-store.
- The types involved
packages.integration.postgres.lib.postgres_event-store.PostgresEventStore→packages.core.lib.event-store.EventStore
- Direction
- integration.postgres.lib.postgres_event-store uses core.lib.event-store, so a change to core.lib.event-store can break integration.postgres.lib.postgres_event-store, while a change to integration.postgres.lib.postgres_event-store can't break core.lib.event-store.
- Position
- Below the diagonal: integration.postgres.lib.postgres_event-store uses a module listed above it, which is the healthy direction.
39→8 testing.cross-version uses core.lib.models.aggregate-root✕
- Connections
- 1 pair of types, where a type in testing.cross-version uses a type in core.lib.models.aggregate-root.
- The types involved
packages.testing.cross-version.domain→packages.core.lib.models.aggregate-root.AggregateRoot
- Direction
- testing.cross-version uses core.lib.models.aggregate-root, so a change to core.lib.models.aggregate-root can break testing.cross-version, while a change to testing.cross-version can't break core.lib.models.aggregate-root.
- Position
- Below the diagonal: testing.cross-version uses a module listed above it, which is the healthy direction.
39→9 testing.cross-version uses core.lib.models.event-envelope✕
- Connections
- 1 pair of types, where a type in testing.cross-version uses a type in core.lib.models.event-envelope.
- The types involved
packages.testing.cross-version.manifest→packages.core.lib.models.event-envelope.EventEnvelope
- Direction
- testing.cross-version uses core.lib.models.event-envelope, so a change to core.lib.models.event-envelope can break testing.cross-version, while a change to testing.cross-version can't break core.lib.models.event-envelope.
- Position
- Below the diagonal: testing.cross-version uses a module listed above it, which is the healthy direction.
39→15 testing.cross-version uses core.lib.event-map✕
- Connections
- 1 pair of types, where a type in testing.cross-version uses a type in core.lib.event-map.
- The types involved
packages.testing.cross-version.domain→packages.core.lib.event-map.EventMap
- Direction
- testing.cross-version uses core.lib.event-map, so a change to core.lib.event-map can break testing.cross-version, while a change to testing.cross-version can't break core.lib.event-map.
- Position
- Below the diagonal: testing.cross-version uses a module listed above it, which is the healthy direction.
39→25 testing.cross-version uses core.lib.snapshot-store✕
- Connections
- 1 pair of types, where a type in testing.cross-version uses a type in core.lib.snapshot-store.
- The types involved
packages.testing.cross-version.verify→packages.core.lib.snapshot-store.SnapshotStore
- Direction
- testing.cross-version uses core.lib.snapshot-store, so a change to core.lib.snapshot-store can break testing.cross-version, while a change to testing.cross-version can't break core.lib.snapshot-store.
- Position
- Below the diagonal: testing.cross-version uses a module listed above it, which is the healthy direction.
39→28 testing.cross-version uses core.lib.event-store✕
- Connections
- 1 pair of types, where a type in testing.cross-version uses a type in core.lib.event-store.
- The types involved
packages.testing.cross-version.verify→packages.core.lib.event-store.EventStore
- Direction
- testing.cross-version uses core.lib.event-store, so a change to core.lib.event-store can break testing.cross-version, while a change to testing.cross-version can't break core.lib.event-store.
- Position
- Below the diagonal: testing.cross-version uses a module listed above it, which is the healthy direction.
40→4 integration.mongodb.lib uses core.lib.interfaces.events.event-collection_type✕
- Connections
- 1 pair of types, where a type in integration.mongodb.lib uses a type in core.lib.interfaces.events.event-collection_type.
- The types involved
packages.integration.mongodb.lib.mongodb.event-store→packages.core.lib.interfaces.events.event-collection_type.IEventCollection
- Direction
- integration.mongodb.lib uses core.lib.interfaces.events.event-collection_type, so a change to core.lib.interfaces.events.event-collection_type can break integration.mongodb.lib, while a change to integration.mongodb.lib can't break core.lib.interfaces.events.event-collection_type.
- Position
- Below the diagonal: integration.mongodb.lib uses a module listed above it, which is the healthy direction.
40→5 integration.mongodb.lib uses core.lib.interfaces.events.event-store-capabilities_interface✕
- Connections
- 1 pair of types, where a type in integration.mongodb.lib uses a type in core.lib.interfaces.events.event-store-capabilities_interface.
- The types involved
packages.integration.mongodb.lib.mongodb.topology→packages.core.lib.interfaces.events.event-store-capabilities_interface.EventStoreCapabilities
- Direction
- integration.mongodb.lib uses core.lib.interfaces.events.event-store-capabilities_interface, so a change to core.lib.interfaces.events.event-store-capabilities_interface can break integration.mongodb.lib, while a change to integration.mongodb.lib can't break core.lib.interfaces.events.event-store-capabilities_interface.
- Position
- Below the diagonal: integration.mongodb.lib uses a module listed above it, which is the healthy direction.
40→9 integration.mongodb.lib uses core.lib.models.event-envelope✕
- Connections
- 1 pair of types, where a type in integration.mongodb.lib uses a type in core.lib.models.event-envelope.
- The types involved
packages.integration.mongodb.lib.mongodb.event-store→packages.core.lib.models.event-envelope.EventEnvelope
- Direction
- integration.mongodb.lib uses core.lib.models.event-envelope, so a change to core.lib.models.event-envelope can break integration.mongodb.lib, while a change to integration.mongodb.lib can't break core.lib.models.event-envelope.
- Position
- Below the diagonal: integration.mongodb.lib uses a module listed above it, which is the healthy direction.
40→11 integration.mongodb.lib uses core.lib.models.snapshot-envelope✕
- Connections
- 1 pair of types, where a type in integration.mongodb.lib uses a type in core.lib.models.snapshot-envelope.
- The types involved
packages.integration.mongodb.lib.mongodb.snapshot-store→packages.core.lib.models.snapshot-envelope.SnapshotEnvelope
- Direction
- integration.mongodb.lib uses core.lib.models.snapshot-envelope, so a change to core.lib.models.snapshot-envelope can break integration.mongodb.lib, while a change to integration.mongodb.lib can't break core.lib.models.snapshot-envelope.
- Position
- Below the diagonal: integration.mongodb.lib uses a module listed above it, which is the healthy direction.
40→24 integration.mongodb.lib uses core.lib.interfaces.events.persist-outcome_type✕
- Connections
- 1 pair of types, where a type in integration.mongodb.lib uses a type in core.lib.interfaces.events.persist-outcome_type.
- The types involved
packages.integration.mongodb.lib.mongodb.event-store→packages.core.lib.interfaces.events.persist-outcome_type.PersistTarget
- Direction
- integration.mongodb.lib uses core.lib.interfaces.events.persist-outcome_type, so a change to core.lib.interfaces.events.persist-outcome_type can break integration.mongodb.lib, while a change to integration.mongodb.lib can't break core.lib.interfaces.events.persist-outcome_type.
- Position
- Below the diagonal: integration.mongodb.lib uses a module listed above it, which is the healthy direction.
40→31 integration.mongodb.lib uses integration.mongodb.lib.mongodb_snapshot-store✕
- Connections
- 1 pair of types, where a type in integration.mongodb.lib uses a type in integration.mongodb.lib.mongodb_snapshot-store.
- The types involved
packages.integration.mongodb.lib.mongodb.snapshot-store→packages.integration.mongodb.lib.mongodb_snapshot-store.SnapshotDocument
- Direction
- integration.mongodb.lib uses integration.mongodb.lib.mongodb_snapshot-store, so a change to integration.mongodb.lib.mongodb_snapshot-store can break integration.mongodb.lib, while a change to integration.mongodb.lib can't break integration.mongodb.lib.mongodb_snapshot-store.
- Position
- Below the diagonal: integration.mongodb.lib uses a module listed above it, which is the healthy direction.
40→37 integration.mongodb.lib uses integration.mongodb.lib.mongodb_event-store✕
- Connections
- 1 pair of types, where a type in integration.mongodb.lib uses a type in integration.mongodb.lib.mongodb_event-store.
- The types involved
packages.integration.mongodb.lib.mongodb.event-store→packages.integration.mongodb.lib.mongodb_event-store.EventDocument
- Direction
- integration.mongodb.lib uses integration.mongodb.lib.mongodb_event-store, so a change to integration.mongodb.lib.mongodb_event-store can break integration.mongodb.lib, while a change to integration.mongodb.lib can't break integration.mongodb.lib.mongodb_event-store.
- Position
- Below the diagonal: integration.mongodb.lib uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Event-Driven
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 22 | Medium |
| A03:2025 — Software Supply Chain Failures | 8 | High / Critical |
| A07:2025 — Authentication Failures | 4 | High / Critical |
| A05:2025 — Injection | 2 | High / Critical |
Roadmap
Top priorities: Reconcile the README with reality: packages/integration/mongodb/README.md names MongoDB 8, but the manifest declares `mongodb` 6.21.0; docs/src/content/docs/integrations/mariadb.mdx names MariaDB 11, but the manifest declares `mariadb` 3.5.4; docs/src/content/docs/integrations/mongodb.mdx names MongoDB 8, but the manifest declares `mongodb` 6.21.0; docs/src/content/docs/upgrading/v4.mdx names MongoDB 7, but the manifest declares `mongodb` 6.21.0; docs/src/content/docs/upgrading/v4.mdx names MongoDB 8, but the manifest declares `mongodb` 6.21.0; Resolve the 14 Banned license finding(s) in License Compliance — start with REDACTED (14); Grow the ADR log (currently 3) — reach 8 to raise the maturity tier; document significant decisions as they're made.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Reconcile the README with reality: packages/integration/mongodb/README.md names MongoDB 8, but the manifest declares `mongodb` 6.21.0; docs/src/content/docs/integrations/mariadb.mdx names MariaDB 11, but the manifest declares `mariadb` 3.5.4; docs/src/content/docs/integrations/mongodb.mdx names MongoDB 8, but the manifest declares `mongodb` 6.21.0; docs/src/content/docs/upgrading/v4.mdx names MongoDB 7, but the manifest declares `mongodb` 6.21.0; docs/src/content/docs/upgrading/v4.mdx names MongoDB 8, but the manifest declares `mongodb` 6.21.0. | +6.3 pts | Medium | Documentation accuracy |
| Resolve the 14 Banned license finding(s) in License Compliance — start with REDACTED (14). | +5.3 pts | Medium | License Compliance |
| Grow the ADR log (currently 3) — reach 8 to raise the maturity tier; document significant decisions as they're made. | +4.4 pts | Medium | Architecture documentation |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +4.0 pts | Medium | DR & Backup |
| Resolve the 1 Test suite executes none of its 8 test cases finding(s) in Test Reliability. | +1.3 pts | Low | Test Reliability |
| Add an 'Architecture' / 'How it works' section to the root README — the high-level shape. | +1.1 pts | Medium | Documentation (README) |
| 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 `?`). | +1.0 pts | Medium | Nullable reference types |
| Resolve the 3 High secret finding(s) in Secrets (history) — start with REDACTED (3). | +0.3 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | License Compliance: Banned license: @img/sharp-libvips-darwin-arm64 |
| packages/integration/postgres/lib/postgres.event-store.ts | 5.5 | Mixed | Cognitive Complexity: PostgresEventStore.persistEvents (cognitive 20) |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| packages/integration/mongodb/lib/mongodb.event-store.ts | 6.3 | Mixed | Cognitive Complexity: MongoDBEventStore.ensureCollection (cognitive 20) |
| packages/integration/mariadb/lib/mariadb.snapshot-store.ts | 7.0 | Mixed | Cognitive Complexity: MariaDBSnapshotStore.appendSnapshot (cognitive 20) |
| packages/integration/mariadb/lib/migration/migrate.ts | 7.0 | Mixed | God Classes: FileTooLong: migration/migrate.ts |
| packages/integration/mariadb/lib/mariadb.event-store.ts | 7.0 | Mixed | Code Coverage: Low coverage: packages/integration/mariadb/lib/mariadb.event-store.ts |
| packages/core/tests/unit/conformance/fixtures.spec.ts | 7.0 | Mixed | Test Quality: No assertions: needs-headers |
| packages/integration/postgres/lib/migration/plan.ts | 7.1 | Mixed | Cyclomatic Complexity: plan.planEventMigration (cyclomatic 31) |
| packages/core/tests/unit/stores/contract-types.spec.ts | 7.1 | Mixed | Test Quality: No assertions: defines the append options (§1, §8) |
| packages/core/lib/testing/event-store.conformance.ts | 7.2 | Mixed | Cyclomatic Complexity: event-store.conformance.describeEventStoreConformance (cyclomatic 59) |
| packages/core/lib/testing/snapshot-store.conformance.ts | 7.2 | Mixed | Cyclomatic Complexity: snapshot-store.conformance.describeSnapshotStoreConformance (cyclomatic 53) |
| packages/integration/postgres/lib/migration/migrate.ts | 7.2 | Mixed | Cyclomatic Complexity: migrate.runMigration (cyclomatic 25) |
| packages/integration/postgres/tests/cross-version/cross-version.spec.ts | 7.2 | Mixed | Test Quality: No assertions: refuses every 3.x event table until it is migrated |
| packages/core/tests/unit/integration/snapshot-store/in-memory.snapshot-store.conformance.spec.ts | 7.3 | Mixed | Explicit Debt: TodoComment |
| packages/core/lib/registration/plan.ts | 7.4 | Mixed | Cyclomatic Complexity: plan.planRegistration (cyclomatic 49) |
| packages/core/tests/unit/command-bus.spec.ts | 7.4 | Mixed | Test Quality: No assertions: resolves ResultOf to the result of a Command, and to any for a plain class |
| packages/integration/mongodb/lib/migration/plan.ts | 7.8 | Mixed | Cyclomatic Complexity: plan.planEventCollection (cyclomatic 31) |
| packages/integration/mongodb/lib/mongodb.topology.ts | 7.8 | Mixed | Cyclomatic Complexity: mongodb.topology.detectEngine (cyclomatic 19) |
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 83 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 83 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, 258 of 285 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — 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. 11 test file(s) failed while being loaded here, so none of their cases ran (typically a native addon or generated module the package's install scripts build, which the analyzer's scripts-off install does not run). The 9 production file(s) those files import that read under half covered are unmeasured in this run, not untested, so their figures are left out of the per-file rows and the 80.2% rather than published as low coverage. You can widen what we reach: optional: commit the lcov report of a run where those test files load, and their modules are read from it.
- 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 (4 contributor(s) across 1472 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 3 hold 0.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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (packages/integration/postgres/package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D23 Boundary Type-Coupling — 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. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
- 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. `packages/core/lib/exceptions/event-sourcing-error.ts`, `packages/core/lib/interfaces/aggregate/index.ts`, `packages/core/lib/interfaces/commands/index.ts`, `packages/core/lib/interfaces/events/index.ts`, `packages/core/lib/interfaces/index.ts`, … (+10 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AXB2 Runtime readiness — 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 dev server exited, and its output does not match a cause we recognise. (rule: unrecognised-exit). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (not identified): the dev server exited, and its output does not match a cause we recognise. Last output: "https://turborepo.dev/docs/telemetry / • turbo 2.11.9 / • Packages in scope: @ocoda/event-sourcing, @ocoda/event-sourcing-config, @ocoda/event-sourcing-docs, @ocoda/event-sourcing-example, @ocoda/event-sourcing-mariadb, @ocoda/event-sourcing-mongodb, @ocoda/event-sourcing-postgres, @ocoda/event-sourcing-testing / • Running dev in 8 packages / • Remote caching disabled / x Unable to find package manager binary: cannot find binary path / `-> cannot find binary path" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (not identified): the dev server exited, and its output does not match a cause we recognise. Last output: "https://turborepo.dev/docs/telemetry / • turbo 2.11.9 / • Packages in scope: @ocoda/event-sourcing, @ocoda/event-sourcing-config, @ocoda/event-sourcing-docs, @ocoda/event-sourcing-example, @ocoda/event-sourcing-mariadb, @ocoda/event-sourcing-mongodb, @ocoda/event-sourcing-postgres, @ocoda/event-sourcing-testing / • Running dev in 8 packages / • Remote caching disabled / x Unable to find package manager binary: cannot find binary path / `-> cannot find binary path" No runtime evidence was gathered.
- C1 Data Protection — 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. 'pg' is imported (packages/integration/postgres/lib/postgres.event-store.ts:30), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C3 Audit Trail — 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. 'pg' is imported (packages/integration/postgres/lib/postgres.event-store.ts:30), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — 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. 'pg' is imported (packages/integration/postgres/lib/postgres.event-store.ts:30), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — 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. 'pg' is imported (packages/integration/postgres/lib/postgres.event-store.ts:30), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- 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. 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.
- R10 Code Duplication — 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. 18 further occurrence(s) are not listed individually; the score already reflects all 58.
- 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. 252 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.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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
11 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was event-store.conformance.describeEventStoreConformance at 59.
What to do
- Bring the 11 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with event-store.conformance.describeEventStoreConformance (cyclomatic 59), snapshot-store.conformance.describeSnapshotStoreConformance (cyclomatic 53), plan.planRegistration (cyclomatic 49). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 11 together lifts Cyclomatic Complexity from 7.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
19 method(s) exceeded the cognitive complexity threshold of 15; the worst was plan.planRegistration at 93.
What to do
- Bring the 6 bodies over 30 down to 30 or less in Cognitive Complexity — start with plan.planRegistration (cognitive 93), event-store.conformance.describeEventStoreConformance (cognitive 78), snapshot-store.conformance.describeSnapshotStoreConformance (cognitive 76). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cognitive Complexity from 6.6 to about 7.8/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- 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
6 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 3 FunctionTooLong finding(s) in God Classes — start with event-store.conformance.ts, snapshot-store.conformance.ts, plan.ts. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 FileTooLong finding(s) in God Classes — start with event-store.conformance.ts, snapshot-store.conformance.ts, migrate.ts. — One of this dimension's main actionable groups (3 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D5 · Coupling
5 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 32 classes have LCOM4 above 3.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
What to do
- Resolve the 2 Classify ADR enforcement finding(s) in Architectural Integrity — start with 0001-v4-core-api.md, 0002-schema-v2.md. — One of this dimension's main actionable groups (2 recommendation-level).
- Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D8 · Code Coverage
Line coverage 80.2% — 5 file(s) below 50%. Measured from the JavaScript/TypeScript suite (vitest in the repository root: not run; vitest in example/: not run; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/core/; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/integration/mariadb/; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/integration/mongodb/; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/integration/postgres/; vitest in packages/testing/: not run).
What to do
- Resolve the 5 Low coverage finding(s) in Code Coverage — start with mariadb.event-store.ts, mariadb.snapshot-store.ts, migrate.ts. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
1170 test methods: 579 unit, 567 integration, 0 BDD, 24 e2e. The JavaScript/TypeScript suite contributes 1170 `it`/`test` case(s) across 95 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
1 skipped (1 with a documented reason), 38 zero-assertion, 2 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1170 tests.
What to do
- Resolve the 38 No assertions finding(s) in Test Quality — start with fixtures.spec.ts (12), cross-version.spec.ts (7), contract-types.spec.ts (6). — One of this dimension's main actionable groups (38 warning-level).
- Resolve the 2 Fixed-sleep synchronisation finding(s) in Test Quality — start with event-bus.shutdown.spec.ts (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Mock-dominated test finding(s) in Test Quality — start with mongodb.topology.spec.ts, event-bus.publishing.spec.ts. — One of this dimension's main actionable groups (2 recommendation-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root (124 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in example/ (0 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/core/ (1138 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/integration/mariadb/ (147 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/integration/mongodb/ (131 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/integration/postgres/ (60 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/testing/ (0 tests)): measured (0 flaky).
What to do
- Resolve the 1 Test suite executes none of its 8 test cases finding(s) in Test Reliability. — One of this dimension's main actionable groups (1 issue-level).
D12 · Dependency Hygiene
12 outdated direct production npm dependency(ies) of 20 graded, 0 pinning defect(s), across 9 package.json (6 of them the product) and 2 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 0 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
14 of 516 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 516 package(s) this repository's committed lockfile installs for a consumer — its 20 production, optional and peer dependency(ies), across 6 product package.json manifest(s), and everything those install in turn. Its 80 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under MIT, which is its own choice and is not judged here.
What to do
- Resolve the 14 Banned license finding(s) in License Compliance — start with REDACTED (14). — One of this dimension's main actionable groups (14 issue-level).
D15 · Churn × Complexity Hotspots
Top hotspots: packages/core/lib/testing/event-store.conformance.ts (6×59=354); packages/core/lib/testing/snapshot-store.conformance.ts (4×53=212)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with event-store.conformance.ts, snapshot-store.conformance.ts. — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
7 deducted task-comment markers across 22432 LoC (0.0/KLoC) → score 9.9. 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.
What to do
- Resolve the 7 TodoComment finding(s) in Explicit Debt — start with in-memory.snapshot-store.conformance.spec.ts (2), mongodb.event-store.conformance.spec.ts, mongodb.snapshot-store.conformance.spec.ts. — One of this dimension's main actionable groups (7 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 36 document(s) read across 8 unit(s).
D20 · ADR Quality
0 of 2 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D23 · Boundary Type-Coupling
14 domain type(s) cross context boundaries across 8 contexts; they are measured and withheld (not published, not scored). Contexts: core, docs, example, fixtures, mariadb, mongodb, postgres, testing.
D24 · Comment Value
0 of 619 judged comments only repeat the code they sit on (0.0 %). 10 comment(s) in another language or script were not judged.
D26 · Project Cohesion
1 of 8 build units (npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
34 % of calls cross a namespace and 3 % go through an interface, but 90 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 3 High secret finding(s) in Secrets (history) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. semgrep hit a parse error in 16 file(s) — `.github/scripts/docs-site.sh` (line 44, line 64, line 90), `packages/core/lib/exceptions/event-sourcing-error.ts` (line 186), `packages/core/lib/interfaces/aggregate/index.ts` (line 1, line 2, line 3, …), `packages/core/lib/interfaces/commands/index.ts` (line 1, line 2, line 3, …), `packages/core/lib/interfaces/events/index.ts` (line 1, line 2, line 3, …), … (+11 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
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).
D30 · Dependency Vulnerabilities
4 finding(s): 0 critical, 2 high, 0 medium, 0 low. 2 advisory suppression(s) declared in REDACTED, 2 stale.
What to do
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 Stale vulnerability suppression finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
D31 · IaC & Container Security
22 finding(s): 0 critical, 0 high, 22 medium, 0 low.
What to do
- Resolve the 22 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (22). — One of this dimension's main actionable groups (22 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 65 of the 255 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: mariadb.event-store.ts↔mariadb.snapshot-store.ts 57%; postgres.event-store.ts↔postgres.snapshot-store.ts 56%; mongodb.event-store.ts↔mongodb.snapshot-store.ts 50%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with mariadb.event-store.ts, postgres.event-store.ts, mongodb.event-store.ts. — One of this dimension's main actionable groups (3 warning-level).
D36 · Supply-chain Provenance & Signing
1/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 recommendation-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).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious. 2 advisory suppression(s) declared in REDACTED, 2 stale.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
AX9 · CQS / query purity
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
ED3 · Event naming
- `CardCaptureEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — packages/testing/e2e/fixtures/banking/event-suite.ts:276
What to do
- Name events in the past tense — they record facts that already happened.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. — packages/integration/mariadb/tests/unit/mariadb.event-store.spec.ts:875
What to do
- Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
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 3 of 9 project(s) that lack one — worth up to 0.7 pts.
M2 · Architecture documentation
What to do
- Grow the ADR log (currently 3) — reach 8 to raise the maturity tier; document significant decisions as they're made.
M3 · Folder & project structure
M4 · Documentation accuracy
- packages/integration/mongodb/README.md names MongoDB 8, but the manifest declares `mongodb` 6.21.0. 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. — packages/integration/mongodb/README.md:29
- docs/src/content/docs/integrations/mariadb.mdx names MariaDB 11, but the manifest declares `mariadb` 3.5.4. 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. — docs/src/content/docs/integrations/mariadb.mdx:167
- docs/src/content/docs/integrations/mongodb.mdx names MongoDB 8, but the manifest declares `mongodb` 6.21.0. 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. — docs/src/content/docs/integrations/mongodb.mdx:9
- docs/src/content/docs/upgrading/v4.mdx names MongoDB 7, but the manifest declares `mongodb` 6.21.0. 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. — docs/src/content/docs/upgrading/v4.mdx:51
- docs/src/content/docs/upgrading/v4.mdx names MongoDB 8, but the manifest declares `mongodb` 6.21.0. 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. — docs/src/content/docs/upgrading/v4.mdx:111
- docs/src/content/docs/upgrading/versioning.mdx names MongoDB 8, but the manifest declares `mongodb` 6.21.0. 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. — docs/src/content/docs/upgrading/versioning.mdx:65
What to do
- Reconcile the README with reality: packages/integration/mongodb/README.md names MongoDB 8, but the manifest declares `mongodb` 6.21.0; docs/src/content/docs/integrations/mariadb.mdx names MariaDB 11, but the manifest declares `mariadb` 3.5.4; docs/src/content/docs/integrations/mongodb.mdx names MongoDB 8, but the manifest declares `mongodb` 6.21.0; docs/src/content/docs/upgrading/v4.mdx names MongoDB 7, but the manifest declares `mongodb` 6.21.0; docs/src/content/docs/upgrading/v4.mdx names MongoDB 8, but the manifest declares `mongodb` 6.21.0.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- The pipeline declares a deployment environment, but whether required reviewers / protection rules are attached to it lives in repository settings we cannot read — confirm the gate is enforced before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P6 · Release Hygiene
P9 · Domain vs controller coverage
What to do
- Raise domain coverage toward 100% — cover the remaining aggregates / value objects / domain services where the business invariants and costly bugs live.
PF3 · Async & latency hygiene
- `writeFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — fixtures/cross-version/v3/writer.mjs:496
What to do
- TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 12 duplicated blocks under packages/integration/ have copies in at least two of the sibling directories mariadb, mongodb, postgres — 9 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 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 12 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. — packages/integration/mariadb/lib/mariadb.snapshot-store.ts:208
- packages/integration/mariadb/lib/mariadb.snapshot-store.ts:208 · packages/integration/postgres/lib/postgres.snapshot-store.ts:197 — the two spans are one implementation copied and then locally edited — 996 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. — packages/integration/mariadb/lib/mariadb.snapshot-store.ts:208
- packages/integration/mongodb/lib/mongodb.event-store.ts:121 · packages/integration/mongodb/lib/mongodb.snapshot-store.ts:91 — the two spans are one implementation copied and then locally edited — 549 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. — packages/integration/mongodb/lib/mongodb.event-store.ts:121
- packages/integration/postgres/lib/migration/plan.ts:293 · packages/integration/postgres/lib/migration/plan.ts:456 — the two spans are one implementation copied and then locally edited — 411 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/integration/postgres/lib/migration/plan.ts:293
- packages/core/lib/integration/snapshot-store/in-memory.snapshot-store.ts:69 · packages/core/lib/integration/snapshot-store/in-memory.snapshot-store.ts:226 — the two spans are one implementation copied and then locally edited — 521 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/core/lib/integration/snapshot-store/in-memory.snapshot-store.ts:69
- packages/integration/mariadb/lib/mariadb.event-store.ts:119 · packages/integration/mariadb/lib/mariadb.snapshot-store.ts:107 — the two spans are one implementation copied and then locally edited — 430 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. — packages/integration/mariadb/lib/mariadb.event-store.ts:119
- packages/core/lib/command-bus.ts:18 · packages/core/lib/query-bus.ts:18 — 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. — packages/core/lib/command-bus.ts:18
- packages/integration/postgres/lib/postgres.event-store.ts:113 · packages/integration/postgres/lib/postgres.snapshot-store.ts:64 — 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. — packages/integration/postgres/lib/postgres.event-store.ts:113
- packages/integration/postgres/lib/postgres.event-store.ts:217 · packages/integration/postgres/lib/postgres.snapshot-store.ts:161 — 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. — packages/integration/postgres/lib/postgres.event-store.ts:217
- packages/core/lib/models/event-stream.ts:7 · packages/core/lib/models/snapshot-stream.ts:7 — 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. — packages/core/lib/models/event-stream.ts:7
- packages/integration/mariadb/lib/mariadb.snapshot-store.ts:351 · packages/integration/mongodb/lib/mongodb.snapshot-store.ts:251 · packages/integration/postgres/lib/postgres.snapshot-store.ts:311 — 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. — packages/integration/mariadb/lib/mariadb.snapshot-store.ts:351
- packages/core/lib/exceptions/integration/event-store-version-conflict.exception.ts:23 · packages/core/lib/exceptions/integration/snapshot-store-version-conflict.exception.ts:21 — 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. — packages/core/lib/exceptions/integration/event-store-version-conflict.exception.ts:23
- packages/core/lib/testing/event-store.conformance.ts:877 · packages/core/lib/testing/snapshot-store.conformance.ts:425 — 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. — packages/core/lib/testing/event-store.conformance.ts:877
- packages/integration/mariadb/lib/migration/plan.ts:176 · packages/integration/mariadb/lib/migration/plan.ts:297 — the two spans are one implementation copied and then locally edited — 154 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/integration/mariadb/lib/migration/plan.ts:176
- packages/core/lib/models/ulid.ts:22 · packages/core/lib/models/uuid.ts:12 — 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. — packages/core/lib/models/ulid.ts:22
- packages/integration/mongodb/vitest.config.mts:6 · packages/integration/postgres/vitest.config.mts:6 — 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. — packages/integration/mongodb/vitest.config.mts:6
- packages/core/lib/exceptions/application/invalid-command-handler.exception.ts:7 · packages/core/lib/exceptions/application/invalid-query-handler.exception.ts:7 — the 2 copies are spread across 2 files, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited. — packages/core/lib/exceptions/application/invalid-command-handler.exception.ts:7
- packages/core/lib/exceptions/application/missing-aggregate-metadata.exception.ts:7 · packages/core/lib/exceptions/application/missing-command-handler-metadata.exception.ts:7 · packages/core/lib/exceptions/application/missing-event-publisher-metadata.exception.ts:7 · packages/core/lib/exceptions/application/missing-event-serializer-metadata.exception.ts:7 · +3 more site(s) not listed — the 7 copies are spread across 7 files, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited. — packages/core/lib/exceptions/application/missing-aggregate-metadata.exception.ts:7
- packages/integration/mariadb/lib/mariadb.snapshot-store.ts:379 · packages/integration/mongodb/lib/mongodb.snapshot-store.ts:281 · packages/integration/postgres/lib/postgres.snapshot-store.ts:344 — 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. — packages/integration/mariadb/lib/mariadb.snapshot-store.ts:379
- packages/integration/mariadb/lib/mariadb.utils.ts:192 · packages/integration/mongodb/lib/mongodb.utils.ts:179 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/integration/mariadb/lib/mariadb.utils.ts:192
- packages/integration/postgres/lib/postgres.event-store.ts:293 · packages/integration/postgres/lib/postgres.snapshot-store.ts:352 — 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. — packages/integration/postgres/lib/postgres.event-store.ts:293
- packages/core/lib/exceptions/application/event-serialization.exception.ts:34 · packages/core/lib/exceptions/application/invalid-event-envelope.exception.ts:51 · packages/core/lib/exceptions/application/invalid-event-metadata.exception.ts:41 — 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. — packages/core/lib/exceptions/application/event-serialization.exception.ts:34
- packages/core/lib/exceptions/domain/id-already-registered.error.ts:8 · packages/core/lib/exceptions/domain/id-not-found.error.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. — packages/core/lib/exceptions/domain/id-already-registered.error.ts:8
- packages/integration/mariadb/lib/mariadb.snapshot-store.ts:449 · packages/integration/mongodb/lib/mongodb.snapshot-store.ts:351 — 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. — packages/integration/mariadb/lib/mariadb.snapshot-store.ts:449
- packages/integration/mongodb/lib/migration/events.ts:34 · packages/integration/mongodb/lib/migration/snapshots.ts:19 — 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. — packages/integration/mongodb/lib/migration/events.ts:34
- packages/integration/mongodb/lib/migration/events.ts:106 · packages/integration/mongodb/lib/mongodb.event-store.ts:495 — the two spans are one implementation copied and then locally edited — 99 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. — packages/integration/mongodb/lib/migration/events.ts:106
- packages/integration/mongodb/lib/migration/inspect.ts:210 · packages/integration/mongodb/lib/migration/inspect.ts:258 — 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. — packages/integration/mongodb/lib/migration/inspect.ts:210
- packages/core/lib/integration/snapshot-store/in-memory.snapshot-store.ts:175 · packages/integration/mongodb/lib/mongodb.snapshot-store.ts:245 — 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. — packages/core/lib/integration/snapshot-store/in-memory.snapshot-store.ts:175
- packages/core/lib/testing/event-store.conformance.ts:1749 · packages/core/lib/testing/snapshot-store.conformance.ts:1013 — 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. — packages/core/lib/testing/event-store.conformance.ts:1749
- packages/integration/mongodb/lib/migration/plan.ts:573 · packages/integration/mongodb/lib/migration/plan.ts:659 — 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. — packages/integration/mongodb/lib/migration/plan.ts:573
- packages/integration/mongodb/lib/mongodb.event-store.ts:206 · packages/integration/postgres/lib/postgres.event-store.ts:210 — 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. — packages/integration/mongodb/lib/mongodb.event-store.ts:206
- packages/core/lib/helpers/json-event-serializer.ts:150 · packages/core/lib/helpers/json-event-serializer.ts:191 — 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. — packages/core/lib/helpers/json-event-serializer.ts:150
- packages/core/lib/integration/snapshot-store/in-memory.snapshot-store.ts:255 · packages/core/lib/integration/snapshot-store/in-memory.snapshot-store.ts:319 — 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. — packages/core/lib/integration/snapshot-store/in-memory.snapshot-store.ts:255
- packages/testing/unit/index.ts:54 · packages/testing/unit/index.ts:119 — 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. — packages/testing/unit/index.ts:54
- packages/core/lib/event-map.ts:69 · packages/core/lib/event-map.ts:84 — 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. — packages/core/lib/event-map.ts:69
- packages/core/lib/exceptions/application/command-handler-not-found.exception.ts:10 · packages/core/lib/exceptions/application/missing-command-metadata.exception.ts:13 · packages/core/lib/exceptions/application/missing-query-metadata.exception.ts:13 · packages/core/lib/exceptions/application/query-handler-not-found.exception.ts:10 — the 4 copies are spread across 4 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. — packages/core/lib/exceptions/application/command-handler-not-found.exception.ts:10
- packages/core/lib/exceptions/application/event-not-found.exception.ts:14 · packages/core/lib/exceptions/application/snapshot-not-found.exception.ts:14 — 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. — packages/core/lib/exceptions/application/event-not-found.exception.ts:14
- packages/core/lib/exceptions/integration/event-store-collection-creation.exception.ts:8 · packages/core/lib/exceptions/integration/snapshot-store-collection-creation.exception.ts:8 · packages/core/lib/exceptions/integration/snapshot-store-persistence.exception.ts:8 — the 3 copies are spread across 3 files, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited. — packages/core/lib/exceptions/integration/event-store-collection-creation.exception.ts:8
- packages/core/lib/testing/event-store.conformance.ts:446 · packages/core/lib/testing/snapshot-store.conformance.ts:1002 — 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. — packages/core/lib/testing/event-store.conformance.ts:446
- packages/core/lib/testing/event-store.conformance.ts:1026 · packages/core/lib/testing/snapshot-store.conformance.ts:736 — 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. — packages/core/lib/testing/event-store.conformance.ts:1026
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- (anonymous) has cyclomatic complexity 43 and cognitive complexity 86; 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. — packages/core/lib/registration/plan.ts:88
- (anonymous) has cyclomatic complexity 31 and cognitive complexity 30; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — packages/integration/postgres/lib/migration/plan.ts:454
- (anonymous) has cyclomatic complexity 28 and cognitive complexity 42; 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. — packages/integration/postgres/lib/migration/migrate.ts:49
- (anonymous) has cyclomatic complexity 24 and cognitive complexity 23; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — packages/integration/postgres/lib/migration/plan.ts:292
- (anonymous) has cyclomatic complexity 21 and cognitive complexity 25; 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. — packages/integration/mongodb/lib/migration/plan.ts:477
- (anonymous) has cyclomatic complexity 20 and cognitive complexity 36; 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. — packages/integration/postgres/lib/migration/migrate.ts:163
- (anonymous) has cyclomatic complexity 19 and cognitive complexity 20; 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. — packages/integration/mongodb/lib/mongodb.topology.ts:95
- (anonymous) has cyclomatic complexity 16 and cognitive complexity 19; 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. — packages/testing/cross-version/manifest.ts:158
- analyze has cyclomatic complexity 16 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/integration/mariadb/lib/migration/migrate.ts:765
- appendEvents has cyclomatic complexity 15 and cognitive complexity 22; 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. — packages/core/lib/event-store.ts:130
- (anonymous) has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — packages/integration/mariadb/lib/migration/migrate.ts:423
- (anonymous) has cyclomatic complexity 14 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. (×2) — packages/integration/mariadb/lib/migration/plan.ts:179, packages/integration/postgres/lib/migration/plan.ts:220
- (anonymous) has cyclomatic complexity 13 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/lib/helpers/json-event-serializer.ts:138
- (anonymous) has cyclomatic complexity 13 and cognitive complexity 15; 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. (×2) — packages/core/lib/stores/append-validation.ts:120, packages/integration/mariadb/lib/migration/plan.ts:300
- (top-level) has cyclomatic complexity 13 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — packages/core/lib/command-bus.ts:1, packages/core/lib/query-bus.ts:1
- (anonymous) has cyclomatic complexity 13 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/lib/registration/providers.ts:11
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
- packages/core/lib/testing/event-store.conformance.ts has 1630 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/lib/testing/event-store.conformance.ts:1
- packages/core/lib/testing/snapshot-store.conformance.ts has 966 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/lib/testing/snapshot-store.conformance.ts:1
- packages/integration/mariadb/lib/migration/migrate.ts has 771 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/integration/mariadb/lib/migration/migrate.ts:1
- packages/integration/mongodb/lib/migration/plan.ts has 628 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/integration/mongodb/lib/migration/plan.ts:1
- packages/integration/mongodb/lib/mongodb.event-store.ts has 600 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/integration/mongodb/lib/mongodb.event-store.ts:1
- packages/integration/postgres/lib/postgres.event-store.ts has 570 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/integration/postgres/lib/postgres.event-store.ts:1
- packages/integration/postgres/lib/migration/plan.ts has 549 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/integration/postgres/lib/migration/plan.ts:1
- packages/integration/mariadb/lib/mariadb.event-store.ts has 536 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/integration/mariadb/lib/mariadb.event-store.ts:1
- packages/integration/mongodb/lib/mongodb.snapshot-store.ts has 525 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/integration/mongodb/lib/mongodb.snapshot-store.ts:1
- packages/integration/mariadb/lib/mariadb.snapshot-store.ts has 518 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/integration/mariadb/lib/mariadb.snapshot-store.ts:1
- packages/core/lib/event-bus.ts has 516 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/lib/event-bus.ts:1
- packages/integration/mariadb/lib/mariadb.schema.ts has 429 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/integration/mariadb/lib/mariadb.schema.ts:1
- packages/integration/postgres/lib/postgres.snapshot-store.ts has 429 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/integration/postgres/lib/postgres.snapshot-store.ts:1
- packages/integration/mariadb/lib/migration/sql.ts has 414 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/integration/mariadb/lib/migration/sql.ts:1
- packages/core/lib/event-store.ts has 403 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/lib/event-store.ts:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×7) — scripts/test-cross-version.mjs:1, scripts/test-consumers.mjs:1, scripts/check-packages.mjs:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
R7 · Dead Code
- 1 file(s) (~51 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/config
- Nothing imports this binding — it is safe to review for removal. — packages/integration/mariadb/lib/migration/sql.ts:473
- Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect. (×6) — packages/core/tests/unit/models/id.spec.ts:6, packages/core/tests/unit/models/id.spec.ts:15, packages/core/tests/unit/models/ulid.spec.ts:6, …
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
- Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- packages/core/lib/decorators/event-handler.decorator.ts → packages/core/lib/helpers/index.ts → packages/core/lib/helpers/metadata/index.ts → packages/core/lib/helpers/metadata/get-aggregate-metadata.ts → packages/core/lib/decorators/index.ts → packages/core/lib/decorators/event-handler.decorator.ts (one verified cycle inside a mutually-dependent group of 17 files) — packages/core/lib/decorators/event-handler.decorator.ts:4
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
- `encodeValue` is exported and takes `value: unknown` from its caller, and it calls itself at line 166 (`encodeValue`) with a piece of `value` (and at line 173) — and nowhere in `encodeValue` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `encodeValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/testing/cross-version/manifest.ts:166
- `toShell` is exported and takes `value: unknown` from its caller, and it calls itself at line 136 (`toShell`) with a piece of `value` (and at line 139) — and nowhere in `toShell` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `toShell` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/integration/mongodb/lib/mongodb.schema.ts:136
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
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
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — packages/core/lib/event-bus.ts:63
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- 1/6 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.
- ~0.2 `!` null assertions per 1k TypeScript source lines — 4 assertion(s) across the 22796 source line(s) of the 251 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: packages/testing/cross-version/verify.ts (2), packages/integration/mongodb/lib/mongodb.event-store.ts (1), packages/integration/mongodb/lib/mongodb.snapshot-store.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 70% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 88% | Strong | Solid. |
| Maturity | 50% | Adequate — gated by M4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 54% | Adequate — gated by D14, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 69% | Checked 5 of 11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Performance | 85% | Strong | Solid. |
Unscored — 3 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 4 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'pg' (packages/integration/postgres/lib/postgres.event-store.ts:30) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'pg' (packages/integration/postgres/lib/postgres.event-store.ts:30) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'pg' (packages/integration/postgres/lib/postgres.event-store.ts:30) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
Not included — 51 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: NestJS makes a provider that injects a request-scoped one request-scoped itself (scope bubbles up the injection chain), and gives every consumer its own transient instance by contract.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (not identified): the dev server exited, and its output does not match a cause we recognise. Last output: "https://turborepo.dev/docs/telemetry / • turbo 2.11.9 / • Packages in scope: @ocoda/event-sourcing, @ocoda/event-sourcing-config, @ocoda/event-sourcing-docs, @ocoda/event-sourcing-example, @ocoda/event-sourcing-mariadb, @ocoda/event-sourcing-mongodb, @ocoda/event-sourcing-postgres, @ocoda/event-sourcing-testing / • Running dev in 8 packages / • Remote caching disabled / x Unable to find package manager binary: cannot find binary path / `-> cannot find binary path" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: this repository stores data through 'pg' (packages/integration/postgres/lib/postgres.event-store.ts:30) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- 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.
- 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.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D25 ADR Conformance — None of 2 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D32 Data Compliance (PII/GDPR) — 15 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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 (.mts, .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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- DM1 Aggregate boundaries — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM10 One transaction, one aggregate — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM2 Strongly-typed ids — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM4 Rich vs anemic model — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM5 Encapsulated state — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- ED5 Idempotency — 16 mutating command handler(s)/consumer(s) detected and 16 handler method(s) walked, but no persistent write was recognised in any of them — idempotency not assessed
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- S1 Web-Security Posture — Not assessed: 252 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.
- 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.
- 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 — 23 finding(s)
- Banned license: @img/sharp-libvips-darwin-arm64 REDACTED:760
- Banned license: @img/sharp-libvips-darwin-x64 REDACTED:765
- Banned license: @img/sharp-libvips-linux-arm REDACTED:776
- Banned license: @img/sharp-libvips-linux-arm64 REDACTED:770
- Banned license: @img/sharp-libvips-linux-ppc64 REDACTED:782
- Banned license: @img/sharp-libvips-linux-riscv64 REDACTED:788
- Banned license: @img/sharp-libvips-linux-s390x REDACTED:794
- Banned license: @img/sharp-libvips-linux-x64 REDACTED:800
- Banned license: @img/sharp-libvips-linuxmusl-arm64 REDACTED:806
- Banned license: @img/sharp-libvips-linuxmusl-x64 REDACTED:812
- Banned license: @img/sharp-wasm32 REDACTED:874
- Banned license: @img/sharp-win32-arm64 REDACTED:883
- Banned license: @img/sharp-win32-ia32 REDACTED:889
- Banned license: @img/sharp-win32-x64 REDACTED:895
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test suite executes none of its 8 test cases: example/
- REDACTED
- REDACTED
- Import cycle (5 files) packages/core/lib/decorators/event-handler.decorator.ts:4
Serious — 208 finding(s)
- No assertions: refuses every 3.x event table until it is migrated packages/integration/postgres/tests/cross-version/cross-version.spec.ts:186
- No assertions: has every case of the fixture in the corpus packages/integration/postgres/tests/cross-version/cross-version.spec.ts:280
- No assertions: returns every stream as 3.0.2 did, with the positions of readAll packages/integration/postgres/tests/cross-version/cross-version.spec.ts:340
- No assertions: reads every snapshot as 3.0.2 did, with the registeredOn 3.x wrote, and the highest version as the last packages/integration/postgres/tests/cross-version/cross-version.spec.ts:410
- No assertions: returns every stream as 3.0.2 did, to the millisecond, with the positions of readAll packages/integration/mongodb/tests/cross-version/cross-version.spec.ts:311
- No assertions: restores occurredOn to the millisecond 3.x appended, also for the rows a New York process shifted packages/integration/mariadb/tests/cross-version/cross-version.spec.ts:447
- No assertions: returns every stream as 3.0.2 did, with the positions of readAll packages/integration/mariadb/tests/cross-version/cross-version.spec.ts:462
- No assertions: resolves ResultOf to the result of a Command, and to any for a plain class packages/core/tests/unit/command-bus.spec.ts:81
- No assertions: types the handler interface and the bus interface with the result of the command packages/core/tests/unit/command-bus.spec.ts:88
- No assertions: rejects what is not a command, and handlers with the wrong result, at compile time packages/core/tests/unit/command-bus.spec.ts:96
- No assertions: is the envelope publisher an event store gets packages/core/tests/unit/event-bus.publish-all.spec.ts:21
- No assertions: keeps accepting the 3.x publishers, which may return anything packages/core/tests/unit/event-bus.publishing.spec.ts:756
- No assertions: resolves ResultOf and the handler interface to the result of the query packages/core/tests/unit/query-bus.spec.ts:65
- No assertions: rejects what is not a query, and handlers with the wrong result, at compile time packages/core/tests/unit/query-bus.spec.ts:79
- No assertions: removes the types packages/core/tests/unit/removed-api.spec.ts:55
- No assertions: is Promise-only packages/core/tests/unit/snapshot-store.spec.ts:137
- No assertions: types a driver as the class of a snapshot store, created with its options packages/core/tests/unit/snapshot-store.spec.ts:158
- No assertions: defines the append options (§1, §8) packages/core/tests/unit/stores/contract-types.spec.ts:25
- No assertions: defines the capabilities and the store context (§1) packages/core/tests/unit/stores/contract-types.spec.ts:43
- No assertions: defines the outcome and the target of persistEvents (§1) packages/core/tests/unit/stores/contract-types.spec.ts:58
- No assertions: adds headers, the event version and the global position to the envelope metadata (§8, §9) packages/core/tests/unit/stores/contract-types.spec.ts:71
- No assertions: defines the readAll filter (§9) packages/core/tests/unit/stores/contract-types.spec.ts:77
- No assertions: defines the migration types packages/core/tests/unit/stores/contract-types.spec.ts:81
- No assertions: narrows through instanceof and isEventSourcingError packages/core/tests/unit/exceptions/exceptions.spec.ts:227
- No assertions: takes an event class (ADR 0001 §7) packages/core/tests/unit/decorators/event-serializer.decorator.spec.ts:22
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment packages/integration/mongodb/tests/unit/mongodb.event-store.conformance.spec.ts:42
- TodoComment packages/integration/mongodb/tests/unit/mongodb.snapshot-store.conformance.spec.ts:28
- TodoComment packages/integration/mariadb/tests/unit/mariadb.migration-sql.spec.ts:53
- TodoComment packages/integration/mariadb/tests/unit/mariadb.migration.spec.ts:55
- TodoComment packages/core/tests/unit/integration/snapshot-store/in-memory.snapshot-store.conformance.spec.ts:5
- TodoComment packages/core/tests/unit/integration/snapshot-store/in-memory.snapshot-store.conformance.spec.ts:7
- TodoComment packages/core/tests/unit/integration/event-store/in-memory.event-store.conformance.spec.ts:58
- No test reaches this file scripts/test-cross-version.mjs:1
- No test reaches this file scripts/test-consumers.mjs:1
- No test reaches this file scripts/check-packages.mjs:1
- No test reaches this file scripts/pack-packages.mjs:1
- No test reaches this file packages/integration/mariadb/vitest.cross-version.mts:1
- No test reaches this file packages/integration/mongodb/vitest.cross-version.mts:1
- No test reaches this file packages/integration/postgres/vitest.cross-version.mts:1
- Low coverage: packages/integration/mariadb/lib/mariadb.event-store.ts packages/integration/mariadb/lib/mariadb.event-store.ts:1
- Low coverage: packages/integration/mariadb/lib/mariadb.snapshot-store.ts packages/integration/mariadb/lib/mariadb.snapshot-store.ts:1
- Low coverage: packages/integration/mariadb/lib/migration/migrate.ts packages/integration/mariadb/lib/migration/migrate.ts:1
- Low coverage: packages/integration/postgres/lib/postgres.event-store.ts packages/integration/postgres/lib/postgres.event-store.ts:1
- Low coverage: packages/integration/postgres/lib/postgres.snapshot-store.ts packages/integration/postgres/lib/postgres.snapshot-store.ts:1
- Duplicated block (12 lines × 2 locations) packages/core/lib/exceptions/domain/id-already-registered.error.ts:8
- Duplicated block (12 lines × 2 locations) packages/integration/mariadb/lib/mariadb.snapshot-store.ts:449
- Duplicated block (12 lines × 2 locations) packages/integration/mongodb/lib/migration/events.ts:34
- Duplicated block (12 lines × 2 locations) packages/integration/mongodb/lib/migration/inspect.ts:210
- Duplicated block (11 lines × 2 locations) packages/core/lib/integration/snapshot-store/in-memory.snapshot-store.ts:175
- Duplicated block (11 lines × 2 locations) packages/core/lib/testing/event-store.conformance.ts:1749
- Duplicated block (11 lines × 2 locations) packages/integration/mongodb/lib/migration/plan.ts:573
- Duplicated block (11 lines × 2 locations) packages/integration/mongodb/lib/mongodb.event-store.ts:206
- Duplicated block (9 lines × 2 locations) packages/core/lib/event-map.ts:69
- Duplicated block (9 lines × 2 locations) packages/core/lib/exceptions/application/event-not-found.exception.ts:14
- Duplicated block (9 lines × 2 locations) packages/core/lib/testing/event-store.conformance.ts:446
- Duplicated block (9 lines × 2 locations) packages/core/lib/testing/event-store.conformance.ts:1026
- FunctionTooLong: event-store.conformance.describeEventStoreConformance packages/core/lib/testing/event-store.conformance.ts:265
- FunctionTooLong: snapshot-store.conformance.describeSnapshotStoreConformance packages/core/lib/testing/snapshot-store.conformance.ts:212
- FunctionTooLong: plan.planRegistration packages/core/lib/registration/plan.ts:84
- FileTooLong: testing/event-store.conformance.ts packages/core/lib/testing/event-store.conformance.ts
- FileTooLong: testing/snapshot-store.conformance.ts packages/core/lib/testing/snapshot-store.conformance.ts
- FileTooLong: migration/migrate.ts packages/integration/mariadb/lib/migration/migrate.ts
- Change coupling: mariadb.event-store.ts ↔ mariadb.snapshot-store.ts packages/integration/mariadb/lib/mariadb.event-store.ts:1
- Change coupling: postgres.event-store.ts ↔ postgres.snapshot-store.ts packages/integration/postgres/lib/postgres.event-store.ts:1
- Change coupling: mongodb.event-store.ts ↔ mongodb.snapshot-store.ts packages/integration/mongodb/lib/mongodb.event-store.ts:1
- Workspace package's tests never run by CI packages/integration/mariadb/package.json:50
- Workspace package's tests never run by CI packages/integration/mongodb/package.json:50
- Workspace package's tests never run by CI packages/integration/postgres/package.json:51
- Duplicated block (13 lines × 2 locations) packages/core/lib/exceptions/application/invalid-command-handler.exception.ts:7
- Duplicated block (13 lines × 2 locations) packages/integration/mariadb/lib/mariadb.utils.ts:192
- Duplicated block (13 lines × 2 locations) packages/integration/postgres/lib/postgres.event-store.ts:293
- Duplicated block (10 lines × 2 locations) packages/core/lib/helpers/json-event-serializer.ts:150
- Duplicated block (10 lines × 2 locations) packages/core/lib/integration/snapshot-store/in-memory.snapshot-store.ts:255
- Duplicated block (10 lines × 2 locations) packages/testing/unit/index.ts:54
- Fixed-sleep synchronisation: app.close() drains the running subscribers, then disconnects each store once packages/core/tests/unit/event-bus.shutdown.spec.ts:111
- Fixed-sleep synchronisation: app.close() drains a publication that is still running, then disconnects each store once packages/core/tests/unit/event-bus.shutdown.spec.ts:139
- Hotspot: packages/core/lib/testing/event-store.conformance.ts packages/core/lib/testing/event-store.conformance.ts:265
- Hotspot: packages/core/lib/testing/snapshot-store.conformance.ts packages/core/lib/testing/snapshot-store.conformance.ts:212
- Duplicated block (19 lines × 2 locations) packages/core/lib/exceptions/integration/event-store-version-conflict.exception.ts:23
- Duplicated block (19 lines × 2 locations) packages/core/lib/testing/event-store.conformance.ts:877
- Duplicated block (15 lines × 2 locations) packages/core/lib/models/ulid.ts:22
- Duplicated block (15 lines × 2 locations) packages/integration/mongodb/vitest.config.mts:6
- Complex function (anonymous) (cyclomatic 14, cognitive 17) packages/integration/mariadb/lib/migration/plan.ts:179
- Complex function (anonymous) (cyclomatic 14, cognitive 17) packages/integration/postgres/lib/migration/plan.ts:220
- Complex function (anonymous) (cyclomatic 13, cognitive 15) packages/core/lib/stores/append-validation.ts:120
- Complex function (anonymous) (cyclomatic 13, cognitive 15) packages/integration/mariadb/lib/migration/plan.ts:300
- Complex function (top-level) (cyclomatic 13, cognitive 13) packages/core/lib/command-bus.ts:1
- Complex function (top-level) (cyclomatic 13, cognitive 13) packages/core/lib/query-bus.ts:1
- Recursive walk over a caller-supplied document has no depth cap packages/testing/cross-version/manifest.ts:166
- Recursive walk over a caller-supplied document has no depth cap packages/integration/mongodb/lib/mongodb.schema.ts:136
- event-store.conformance.describeEventStoreConformance (cyclomatic 59) packages/core/lib/testing/event-store.conformance.ts:265
- snapshot-store.conformance.describeSnapshotStoreConformance (cyclomatic 53) packages/core/lib/testing/snapshot-store.conformance.ts:212
- plan.planRegistration (cyclomatic 49) packages/core/lib/registration/plan.ts:84
- plan.planEventCollection (cyclomatic 31) packages/integration/mongodb/lib/migration/plan.ts:473
- plan.planEventMigration (cyclomatic 31) packages/integration/postgres/lib/migration/plan.ts:292
- plan.planSnapshotMigration (cyclomatic 29) packages/integration/postgres/lib/migration/plan.ts:454
- migrate.runMigration (cyclomatic 25) packages/integration/postgres/lib/migration/migrate.ts:43
- migrate.execute (cyclomatic 20) packages/integration/postgres/lib/migration/migrate.ts:158
- mongodb.topology.detectEngine (cyclomatic 19) packages/integration/mongodb/lib/mongodb.topology.ts:95
- plan.planEventSteps (cyclomatic 16) packages/integration/mariadb/lib/migration/plan.ts:179
- plan.commonBlocking (cyclomatic 16) packages/integration/postgres/lib/migration/plan.ts:217
- plan.planRegistration (cognitive 93) packages/core/lib/registration/plan.ts:84
- event-store.conformance.describeEventStoreConformance (cognitive 78) packages/core/lib/testing/event-store.conformance.ts:265
- snapshot-store.conformance.describeSnapshotStoreConformance (cognitive 76) packages/core/lib/testing/snapshot-store.conformance.ts:212
- migrate.runMigration (cognitive 35) packages/integration/postgres/lib/migration/migrate.ts:43
- migrate.execute (cognitive 35) packages/integration/postgres/lib/migration/migrate.ts:158
- plan.planEventCollection (cognitive 31) packages/integration/mongodb/lib/migration/plan.ts:473
- plan.planSnapshotMigration (cognitive 24) packages/integration/postgres/lib/migration/plan.ts:454
- plan.planEventMigration (cognitive 23) packages/integration/postgres/lib/migration/plan.ts:292
- EventStore.appendEvents (cognitive 21) packages/core/lib/event-store.ts:130
- plan.commonBlocking (cognitive 21) packages/integration/postgres/lib/migration/plan.ts:217
- json-event-serializer.toPlain (cognitive 20) packages/core/lib/helpers/json-event-serializer.ts:138
- MariaDBSnapshotStore.appendSnapshot (cognitive 20) packages/integration/mariadb/lib/mariadb.snapshot-store.ts:237
- MongoDBEventStore.ensureCollection (cognitive 20) packages/integration/mongodb/lib/mongodb.event-store.ts:165
- PostgresEventStore.persistEvents (cognitive 20) packages/integration/postgres/lib/postgres.event-store.ts:368
- plan.planEventSteps (cognitive 19) packages/integration/mariadb/lib/migration/plan.ts:179
- mongodb.topology.detectEngine (cognitive 19) packages/integration/mongodb/lib/mongodb.topology.ts:95
- MongoDBEventStore.persistInTransaction (cognitive 19) packages/integration/mongodb/lib/mongodb.event-store.ts:335
- manifest.encodeValue (cognitive 18) packages/testing/cross-version/manifest.ts:158
- runner.runUnderLease (cognitive 17) packages/integration/mongodb/lib/migration/runner.ts:108
- Off the main sequence: @ocoda/event-sourcing
- Coverage collected but not gated
- No DR/backup evidence
- Sync-over-async blocking fixtures/cross-version/v3/writer.mjs:496
- Duplication concentrated across 3 sibling directories (12 clone groups) packages/integration/mariadb/lib/mariadb.snapshot-store.ts:208
- Duplicated block with local edits (155 matched lines × 2 locations) packages/integration/mariadb/lib/mariadb.snapshot-store.ts:208
- Duplicated block with local edits (72 matched lines × 2 locations) packages/integration/mongodb/lib/mongodb.event-store.ts:121
- Duplicated block with local edits (71 matched lines × 2 locations) packages/integration/postgres/lib/migration/plan.ts:293
- Duplicated block with local edits (68 matched lines × 2 locations) packages/core/lib/integration/snapshot-store/in-memory.snapshot-store.ts:69
- Duplicated block with local edits (67 matched lines × 2 locations) packages/integration/mariadb/lib/mariadb.event-store.ts:119
- Duplicated block (58 lines × 2 locations) packages/core/lib/command-bus.ts:18
- Duplicated block (39 lines × 2 locations) packages/integration/postgres/lib/postgres.event-store.ts:113
- Duplicated block (32 lines × 2 locations) packages/integration/postgres/lib/postgres.event-store.ts:217
- Duplicated block (20 lines × 2 locations) packages/core/lib/models/event-stream.ts:7
- Duplicated block (20 lines × 3 locations) packages/integration/mariadb/lib/mariadb.snapshot-store.ts:351
- Duplicated block with local edits (17 matched lines × 2 locations) packages/integration/mariadb/lib/migration/plan.ts:176
- Duplicated block (13 lines × 7 locations) packages/core/lib/exceptions/application/missing-aggregate-metadata.exception.ts:7
- Duplicated block (13 lines × 3 locations) packages/integration/mariadb/lib/mariadb.snapshot-store.ts:379
- Duplicated block (12 lines × 3 locations) packages/core/lib/exceptions/application/event-serialization.exception.ts:34
- Duplicated block with local edits (12 matched lines × 2 locations) packages/integration/mongodb/lib/migration/events.ts:106
- Duplicated block (9 lines × 4 locations) packages/core/lib/exceptions/application/command-handler-not-found.exception.ts:10
- Duplicated block (9 lines × 3 locations) packages/core/lib/exceptions/integration/event-store-collection-creation.exception.ts:8
- Complex function (anonymous) (cyclomatic 43, cognitive 86) packages/core/lib/registration/plan.ts:88
- Complex function (anonymous) (cyclomatic 31, cognitive 30) packages/integration/postgres/lib/migration/plan.ts:454
- Complex function (anonymous) (cyclomatic 28, cognitive 42) packages/integration/postgres/lib/migration/migrate.ts:49
- Complex function (anonymous) (cyclomatic 24, cognitive 23) packages/integration/postgres/lib/migration/plan.ts:292
- Complex function (anonymous) (cyclomatic 21, cognitive 25) packages/integration/mongodb/lib/migration/plan.ts:477
- Complex function (anonymous) (cyclomatic 20, cognitive 36) packages/integration/postgres/lib/migration/migrate.ts:163
- Complex function (anonymous) (cyclomatic 19, cognitive 20) packages/integration/mongodb/lib/mongodb.topology.ts:95
- Complex function (anonymous) (cyclomatic 16, cognitive 19) packages/testing/cross-version/manifest.ts:158
- Complex function analyze (cyclomatic 16, cognitive 16) packages/integration/mariadb/lib/migration/migrate.ts:765
- Complex function appendEvents (cyclomatic 15, cognitive 22) packages/core/lib/event-store.ts:130
- Complex function (anonymous) (cyclomatic 15, cognitive 14) packages/integration/mariadb/lib/migration/migrate.ts:423
- Complex function (anonymous) (cyclomatic 13, cognitive 21) packages/core/lib/helpers/json-event-serializer.ts:138
- Complex function (anonymous) (cyclomatic 13, cognitive 13) packages/core/lib/registration/providers.ts:11
- packages/core/lib/testing/event-store.conformance.ts: 1630 lines of code packages/core/lib/testing/event-store.conformance.ts:1
- packages/core/lib/testing/snapshot-store.conformance.ts: 966 lines of code packages/core/lib/testing/snapshot-store.conformance.ts:1
- packages/integration/mariadb/lib/migration/migrate.ts: 771 lines of code packages/integration/mariadb/lib/migration/migrate.ts:1
- packages/integration/mongodb/lib/migration/plan.ts: 628 lines of code packages/integration/mongodb/lib/migration/plan.ts:1
- packages/integration/mongodb/lib/mongodb.event-store.ts: 600 lines of code packages/integration/mongodb/lib/mongodb.event-store.ts:1
- packages/integration/postgres/lib/postgres.event-store.ts: 570 lines of code packages/integration/postgres/lib/postgres.event-store.ts:1
- packages/integration/postgres/lib/migration/plan.ts: 549 lines of code packages/integration/postgres/lib/migration/plan.ts:1
- packages/integration/mariadb/lib/mariadb.event-store.ts: 536 lines of code packages/integration/mariadb/lib/mariadb.event-store.ts:1
- packages/integration/mongodb/lib/mongodb.snapshot-store.ts: 525 lines of code packages/integration/mongodb/lib/mongodb.snapshot-store.ts:1
- packages/integration/mariadb/lib/mariadb.snapshot-store.ts: 518 lines of code packages/integration/mariadb/lib/mariadb.snapshot-store.ts:1
- packages/core/lib/event-bus.ts: 516 lines of code packages/core/lib/event-bus.ts:1
- packages/integration/mariadb/lib/mariadb.schema.ts: 429 lines of code packages/integration/mariadb/lib/mariadb.schema.ts:1
- packages/integration/postgres/lib/postgres.snapshot-store.ts: 429 lines of code packages/integration/postgres/lib/postgres.snapshot-store.ts:1
- packages/integration/mariadb/lib/migration/sql.ts: 414 lines of code packages/integration/mariadb/lib/migration/sql.ts:1
- packages/core/lib/event-store.ts: 403 lines of code packages/core/lib/event-store.ts:1
- Unused dependency '@arethetypeswrong/cli'
- Unused dependency 'publint'
- Swallowed exception (empty catch) packages/core/lib/event-bus.ts:63
Minor — 37 finding(s)
- Duplicated predicate packages/testing/cross-version/verify.ts:25
- Duplicated predicate packages/integration/mongodb/lib/mongodb.event-store.ts:183
- Duplicated predicate packages/core/lib/integration/event-store/in-memory.event-store.ts:111
- Duplicated predicate packages/core/lib/integration/event-store/in-memory.event-store.ts:112
- Duplicated predicate packages/integration/mariadb/lib/migration/migrate.ts:355
- Duplicated predicate packages/core/lib/helpers/json-event-serializer.ts:100
- Duplicated predicate packages/core/lib/stores/append-arguments.ts:61
- README/code drift packages/integration/mongodb/README.md:29
- README/code drift docs/src/content/docs/integrations/mariadb.mdx:167
- README/code drift docs/src/content/docs/integrations/mongodb.mdx:9
- README/code drift docs/src/content/docs/upgrading/v4.mdx:51
- README/code drift docs/src/content/docs/upgrading/v4.mdx:111
- README/code drift docs/src/content/docs/upgrading/versioning.mdx:65
- Unused private field 'brand' packages/core/tests/unit/models/id.spec.ts:6
- Unused private field 'brand' packages/core/tests/unit/models/id.spec.ts:15
- Unused private field 'brand' packages/core/tests/unit/models/ulid.spec.ts:6
- Unused private field 'brand' packages/core/tests/unit/models/ulid.spec.ts:9
- Unused private field 'brand' packages/core/tests/unit/models/uuid.spec.ts:6
- Unused private field 'brand' packages/core/tests/unit/models/uuid.spec.ts:9
- Mock-dominated test: bounds every probe with maxTimeMS packages/integration/mongodb/tests/unit/mongodb.topology.spec.ts:194
- Mock-dominated test: holds back only the publisher that is still busy: the others get the next append at once packages/core/tests/unit/event-bus.publishing.spec.ts:271
- REDACTED
- REDACTED
- Classify ADR enforcement: ADR 0001: v4 core API docs/decisions/0001-v4-core-api.md
- Classify ADR enforcement: ADR 0002: Schema v2 (global position, catalog, migration) docs/decisions/0002-schema-v2.md
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Event not named in past tense: CardCaptureEvent packages/testing/e2e/fixtures/banking/event-suite.ts:276
- Disabled test packages/integration/mariadb/tests/unit/mariadb.event-store.spec.ts:875
- Unused export 'catalogId' packages/integration/mariadb/lib/migration/sql.ts:473
- Strict null checking is not enabled everywhere the repository type-checks
- Null assertions (`!`) reduce the strict null checking score
- Silent fallback default in catch packages/integration/mariadb/lib/migration/migrate.ts:412
Minor — 17 finding(s)
- Outdated (npm): @astrojs/markdown-satteri
- Outdated (npm): @astrojs/starlight
- Outdated (npm): @nestjs/common
- Outdated (npm): @nestjs/core
- Outdated (npm): @nestjs/platform-express
- Outdated (npm): @ocoda/event-sourcing
- Outdated (npm): @ocoda/event-sourcing-mariadb
- Outdated (npm): @ocoda/event-sourcing-mongodb
- Outdated (npm): @ocoda/event-sourcing-postgres
- Outdated (npm): astro
- Outdated (npm): mariadb
- Outdated (npm): mongodb
- doc comments repeat the names packages/core/lib/exceptions/application/command-handler-not-found.exception.ts:12
- doc comments repeat the names packages/integration/mariadb/lib/mariadb.schema.ts:103
- doc comments repeat the names packages/integration/mongodb/lib/mongodb.schema.ts:49
- Skipped (documented): appends in sessions with innodb_snapshot_isolation on, also when they race packages/integration/mariadb/tests/unit/mariadb.event-store.spec.ts:864
- core: 3 contract type(s) expose producer-owned ids/enums
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-ecbe17a5786c42c880f99a98178aeb0e/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-ecbe17a5786c42c880f99a98178aeb0e/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 --exclude packages/integration/mariadb/migrations --exclude packages/integration/mongodb/migrations --exclude packages/integration/postgres/migrations . | 2 | 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 | 4 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 22 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 15 file(s) — `packages/core/lib/exceptions/event-sourcing-error.ts`, `packages/core/lib/interfaces/aggregate/index.ts`, `packages/core/lib/interfaces/commands/index.ts`, `packages/core/lib/interfaces/events/index.ts`, `packages/core/lib/interfaces/index.ts`, … (+10 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 |