Executive summary
equinox-project/equinox-js is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 50 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 28, is the weakest lens and counts most in the score. The best first step is replacing the eight deprecated dependencies, worth about 11 points. Adding automated security scanning would lift Production Readiness itself, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 67.
Fifty known security holes in the packages the code depends on can be used by attackers. Eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and two weaknesses in the code could be used by an attacker. Updating the vulnerable packages, pinning each tool to an exact version and fixing the weaknesses the scanner points to 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 the pipeline step that runs a download without checking it needs each download checked against a known checksum first. The test that checks nothing needs to check the result it produces.
The product code is 10,128 lines, about €14,000 to rebuild.
If Production Readiness rose from 28 to 70, the lowest score rated Strong, the score would rise from 50 to about 67.
New since the last survey: 10 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Web-Security Posture · Weak hash algorithm packages/explorer/bin/index.js
Fixed since the last survey: 31 findings
- Code Coverage · Low coverage: apps/hotel/src/config/equinox.ts apps/hotel/src/config/equinox.ts
- Code Coverage · Low coverage: packages/message-db/message-db-consumer/src/lib/Checkpoints.ts packages/message-db/message-db-consumer/src/lib/Checkpoints.ts
- Code Coverage · Low coverage: packages/message-db/message-db-consumer/src/lib/MessageDbClient.ts packages/message-db/message-db-consumer/src/lib/MessageDbClient.ts
- Code Coverage · Low coverage: packages/message-db/message-db-consumer/src/lib/MessageDbSource.mts packages/message-db/message-db-consumer/src/lib/MessageDbSource.mts
- Code Coverage · Low coverage: packages/projection-pg/src/projection.ts packages/projection-pg/src/projection.ts
- Code Coverage · Low coverage: packages/projection-pg/src/quote.ts packages/projection-pg/src/quote.ts
- Code Coverage · Low coverage: packages/propeller/src/Checkpoints.ts packages/propeller/src/Checkpoints.ts
- Code Coverage · Low coverage: packages/propeller/src/FeedSource.mts packages/propeller/src/FeedSource.mts
- Code Coverage · Low coverage: packages/propeller/src/Stats.ts packages/propeller/src/Stats.ts
- Code Coverage · Low coverage: packages/propeller/src/StreamsSink.mts packages/propeller/src/StreamsSink.mts
- Code Coverage · Low coverage: packages/test-domain/src/domain/Cart.ts packages/test-domain/src/domain/Cart.ts
- Code Coverage · Low coverage: apps/example/src/config/equinox.ts apps/example/src/config/equinox.ts
- Code Coverage · Low coverage: apps/example/src/read-models/PayerReadModel.ts apps/example/src/read-models/PayerReadModel.ts
- Code Coverage · Low coverage: apps/hotel/src/entrypoints/config.ts apps/hotel/src/entrypoints/config.ts
- Code Coverage · Low coverage: packages/message-db/message-db/src/lib/MessageDbClient.ts packages/message-db/message-db/src/lib/MessageDbClient.ts
- Boundary Type-Coupling · Cross-context type StreamId (core → example) apps/example/src/read-models/PayerReadModel.ts
- Boundary Type-Coupling · Cross-context type StreamName (core → libsql) packages/libsql/src/lib/Category.ts
- Boundary Type-Coupling · Cross-context type StreamName (core → memory-store) packages/memory-store/src/index.ts
- Boundary Type-Coupling · Cross-context type StreamName (core → memory-store) packages/memory-store/src/index.ts
- Boundary Type-Coupling · Cross-context type StreamName (core → memory-store) packages/memory-store/src/index.ts
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Import Boundaries · Boundary violation [package:relative-cross-package] packages/explorer/app/layout/navbar.ts
Rebuild cost: about €14,000 · Estimate
| Cost to rebuild | €4,500 to €23,000, for 75 to 238 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 50. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 10,128 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 packages.core.src.lib.Codec | 2 packages.core.src.lib.Core | 3 packages.core.src.lib.StreamId | 4 packages.core.src.lib.StreamName | 5 packages.core.src.lib.Uuid | 6 packages.dynamo-store.indexer.src.Checkpoint | 7 packages.dynamo-store.indexer.src.Identifiers | 8 packages.explorer.app.components.tooltip | 9 packages.libsql.src.lib.LibSqlClient | 10 packages.message-db.message-db-consumer.src.lib.MessageDbClient | 11 packages.message-db.message-db.src.lib.MessageDbClient | 12 packages.projection-pg.src | 13 packages.propeller.src.Checkpoints | 14 packages.propeller.src.Types | 15 apps.hotel.src.reactor | 16 packages.core.src.lib | 17 packages.core.src.lib.Category | 18 packages.dynamo-store.source.src | 19 packages.explorer.app.components.stream-plot | 20 packages.message-db.message-db-consumer.src.lib.Checkpoints | 21 packages.propeller.src.FeedSource | 22 packages.core.src.lib.Cache | 23 packages.message-db.message-db-consumer.src.lib.MessageDbSource | 24 packages.dynamo-store.dynamo-store.src.DynamoStore | 25 packages.memory-store.src | 26 apps.hotel.src.entrypoints | 27 packages.core.src.lib.Decider | 28 packages.dynamo-store.dynamo-store.src | 29 packages.dynamo-store.indexer.src.AppendsIndex | 30 packages.dynamo-store.indexer.src.DynamoStoreIndexer | 31 packages.dynamo-store.source.src.Checkpoints | 32 packages.libsql.src.lib.Category | 33 packages.message-db.message-db.src.lib.Category | 34 packages.dynamo-store.lambda.src | 35 packages.dynamo-store.source.src.DynamoStoreSource | 36 packages.propeller.src.StreamsSink | 37 packages.dynamo-store.indexer.src | 38 packages.dynamo-store.indexer.src.AppendsEpoch | 39 packages.libsql.src.lib | 40 packages.message-db.message-db.src.lib |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 packages.core.src.lib.Codec | ||||||||||||||||||||||||||||||||||||||||
| 2 packages.core.src.lib.Core | ||||||||||||||||||||||||||||||||||||||||
| 3 packages.core.src.lib.StreamId | ||||||||||||||||||||||||||||||||||||||||
| 4 packages.core.src.lib.StreamName | ||||||||||||||||||||||||||||||||||||||||
| 5 packages.core.src.lib.Uuid | ||||||||||||||||||||||||||||||||||||||||
| 6 packages.dynamo-store.indexer.src.Checkpoint | ||||||||||||||||||||||||||||||||||||||||
| 7 packages.dynamo-store.indexer.src.Identifiers | ||||||||||||||||||||||||||||||||||||||||
| 8 packages.explorer.app.components.tooltip | ||||||||||||||||||||||||||||||||||||||||
| 9 packages.libsql.src.lib.LibSqlClient | ||||||||||||||||||||||||||||||||||||||||
| 10 packages.message-db.message-db-consumer.src.lib.MessageDbClient | ||||||||||||||||||||||||||||||||||||||||
| 11 packages.message-db.message-db.src.lib.MessageDbClient | ||||||||||||||||||||||||||||||||||||||||
| 12 packages.projection-pg.src | ||||||||||||||||||||||||||||||||||||||||
| 13 packages.propeller.src.Checkpoints | ||||||||||||||||||||||||||||||||||||||||
| 14 packages.propeller.src.Types | ||||||||||||||||||||||||||||||||||||||||
| 15 apps.hotel.src.reactor | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 packages.core.src.lib | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 packages.core.src.lib.Category | 4 | 3 | ||||||||||||||||||||||||||||||||||||||
| 18 packages.dynamo-store.source.src | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 packages.explorer.app.components.stream-plot | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 packages.message-db.message-db-consumer.src.lib.Checkpoints | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 packages.propeller.src.FeedSource | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 packages.core.src.lib.Cache | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 packages.message-db.message-db-consumer.src.lib.MessageDbSource | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 packages.dynamo-store.dynamo-store.src.DynamoStore | 2 | 1 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 25 packages.memory-store.src | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 26 apps.hotel.src.entrypoints | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 packages.core.src.lib.Decider | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 packages.dynamo-store.dynamo-store.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 packages.dynamo-store.indexer.src.AppendsIndex | 3 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 30 packages.dynamo-store.indexer.src.DynamoStoreIndexer | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 31 packages.dynamo-store.source.src.Checkpoints | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 packages.libsql.src.lib.Category | 2 | 1 | 1 | 1 | 2 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||
| 33 packages.message-db.message-db.src.lib.Category | 2 | 1 | 1 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 34 packages.dynamo-store.lambda.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 packages.dynamo-store.source.src.DynamoStoreSource | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 36 packages.propeller.src.StreamsSink | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 packages.dynamo-store.indexer.src | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 38 packages.dynamo-store.indexer.src.AppendsEpoch | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 packages.libsql.src.lib | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 packages.message-db.message-db.src.lib | 1 | 1 |
15→4 apps.hotel.src.reactor uses packages.core.src.lib.StreamName✕
- Connections
- 1 pair of types, where a type in apps.hotel.src.reactor uses a type in packages.core.src.lib.StreamName.
- The types involved
apps.hotel.src.reactor.Handler→packages.core.src.lib.StreamName.StreamName
- Direction
- apps.hotel.src.reactor uses packages.core.src.lib.StreamName, so a change to packages.core.src.lib.StreamName can break apps.hotel.src.reactor, while a change to apps.hotel.src.reactor can't break packages.core.src.lib.StreamName.
- Position
- Below the diagonal: apps.hotel.src.reactor uses a module listed above it, which is the healthy direction.
16→1 packages.core.src.lib uses packages.core.src.lib.Codec✕
- Connections
- 1 pair of types, where a type in packages.core.src.lib uses a type in packages.core.src.lib.Codec.
- The types involved
packages.core.src.lib.Codec→packages.core.src.lib.Codec.ICodec
- Direction
- packages.core.src.lib uses packages.core.src.lib.Codec, so a change to packages.core.src.lib.Codec can break packages.core.src.lib, while a change to packages.core.src.lib can't break packages.core.src.lib.Codec.
- Position
- Below the diagonal: packages.core.src.lib uses a module listed above it, which is the healthy direction.
16→2 packages.core.src.lib uses packages.core.src.lib.Core✕
- Connections
- 1 pair of types, where a type in packages.core.src.lib uses a type in packages.core.src.lib.Core.
- The types involved
packages.core.src.lib.Core→packages.core.src.lib.Core.IStream
- Direction
- packages.core.src.lib uses packages.core.src.lib.Core, so a change to packages.core.src.lib.Core can break packages.core.src.lib, while a change to packages.core.src.lib can't break packages.core.src.lib.Core.
- Position
- Below the diagonal: packages.core.src.lib uses a module listed above it, which is the healthy direction.
16→5 packages.core.src.lib uses packages.core.src.lib.Uuid✕
- Connections
- 1 pair of types, where a type in packages.core.src.lib uses a type in packages.core.src.lib.Uuid.
- The types involved
packages.core.src.lib.Uuid→packages.core.src.lib.Uuid.Uuid
- Direction
- packages.core.src.lib uses packages.core.src.lib.Uuid, so a change to packages.core.src.lib.Uuid can break packages.core.src.lib, while a change to packages.core.src.lib can't break packages.core.src.lib.Uuid.
- Position
- Below the diagonal: packages.core.src.lib uses a module listed above it, which is the healthy direction.
17→2 packages.core.src.lib.Category uses packages.core.src.lib.Core✕
- Connections
- 4 pairs of types, where a type in packages.core.src.lib.Category uses a type in packages.core.src.lib.Core.
- The types involved
packages.core.src.lib.Category.Category→packages.core.src.lib.Core.IStreampackages.core.src.lib.Category.ICategory→packages.core.src.lib.Core.SyncResultpackages.core.src.lib.Category.Stream→packages.core.src.lib.Core.IStreampackages.core.src.lib.Category.Stream→packages.core.src.lib.Core.SyncResult
- Direction
- packages.core.src.lib.Category uses packages.core.src.lib.Core, so a change to packages.core.src.lib.Core can break packages.core.src.lib.Category, while a change to packages.core.src.lib.Category can't break packages.core.src.lib.Core.
- Position
- Below the diagonal: packages.core.src.lib.Category uses a module listed above it, which is the healthy direction.
17→3 packages.core.src.lib.Category uses packages.core.src.lib.StreamId✕
- Connections
- 3 pairs of types, where a type in packages.core.src.lib.Category uses a type in packages.core.src.lib.StreamId.
- The types involved
packages.core.src.lib.Category.Category→packages.core.src.lib.StreamId.StreamIdpackages.core.src.lib.Category.ICategory→packages.core.src.lib.StreamId.StreamIdpackages.core.src.lib.Category.Stream→packages.core.src.lib.StreamId.StreamId
- Direction
- packages.core.src.lib.Category uses packages.core.src.lib.StreamId, so a change to packages.core.src.lib.StreamId can break packages.core.src.lib.Category, while a change to packages.core.src.lib.Category can't break packages.core.src.lib.StreamId.
- Position
- Below the diagonal: packages.core.src.lib.Category uses a module listed above it, which is the healthy direction.
18→4 packages.dynamo-store.source.src uses packages.core.src.lib.StreamName✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.source.src uses a type in packages.core.src.lib.StreamName.
- The types involved
packages.dynamo-store.source.src.DynamoStoreSource→packages.core.src.lib.StreamName.StreamName
- Direction
- packages.dynamo-store.source.src uses packages.core.src.lib.StreamName, so a change to packages.core.src.lib.StreamName can break packages.dynamo-store.source.src, while a change to packages.dynamo-store.source.src can't break packages.core.src.lib.StreamName.
- Position
- Below the diagonal: packages.dynamo-store.source.src uses a module listed above it, which is the healthy direction.
18→6 packages.dynamo-store.source.src uses packages.dynamo-store.indexer.src.Checkpoint✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.source.src uses a type in packages.dynamo-store.indexer.src.Checkpoint.
- The types involved
packages.dynamo-store.source.src.Checkpoints→packages.dynamo-store.indexer.src.Checkpoint.Checkpoint
- Direction
- packages.dynamo-store.source.src uses packages.dynamo-store.indexer.src.Checkpoint, so a change to packages.dynamo-store.indexer.src.Checkpoint can break packages.dynamo-store.source.src, while a change to packages.dynamo-store.source.src can't break packages.dynamo-store.indexer.src.Checkpoint.
- Position
- Below the diagonal: packages.dynamo-store.source.src uses a module listed above it, which is the healthy direction.
19→8 packages.explorer.app.components.stream-plot uses packages.explorer.app.components.tooltip✕
- Connections
- 1 pair of types, where a type in packages.explorer.app.components.stream-plot uses a type in packages.explorer.app.components.tooltip.
- The types involved
packages.explorer.app.components.stream-plot.EventTimelineChart→packages.explorer.app.components.tooltip.Tooltip
- Direction
- packages.explorer.app.components.stream-plot uses packages.explorer.app.components.tooltip, so a change to packages.explorer.app.components.tooltip can break packages.explorer.app.components.stream-plot, while a change to packages.explorer.app.components.stream-plot can't break packages.explorer.app.components.tooltip.
- Position
- Below the diagonal: packages.explorer.app.components.stream-plot uses a module listed above it, which is the healthy direction.
20→13 packages.message-db.message-db-consumer.src.lib.Checkpoints uses packages.propeller.src.Checkpoints✕
- Connections
- 1 pair of types, where a type in packages.message-db.message-db-consumer.src.lib.Checkpoints uses a type in packages.propeller.src.Checkpoints.
- The types involved
packages.message-db.message-db-consumer.src.lib.Checkpoints.PgCheckpoints→packages.propeller.src.Checkpoints.ICheckpoints
- Direction
- packages.message-db.message-db-consumer.src.lib.Checkpoints uses packages.propeller.src.Checkpoints, so a change to packages.propeller.src.Checkpoints can break packages.message-db.message-db-consumer.src.lib.Checkpoints, while a change to packages.message-db.message-db-consumer.src.lib.Checkpoints can't break packages.propeller.src.Checkpoints.
- Position
- Below the diagonal: packages.message-db.message-db-consumer.src.lib.Checkpoints uses a module listed above it, which is the healthy direction.
21→13 packages.propeller.src.FeedSource uses packages.propeller.src.Checkpoints✕
- Connections
- 1 pair of types, where a type in packages.propeller.src.FeedSource uses a type in packages.propeller.src.Checkpoints.
- The types involved
packages.propeller.src.FeedSource.CheckpointWriter→packages.propeller.src.Checkpoints.ICheckpoints
- Direction
- packages.propeller.src.FeedSource uses packages.propeller.src.Checkpoints, so a change to packages.propeller.src.Checkpoints can break packages.propeller.src.FeedSource, while a change to packages.propeller.src.FeedSource can't break packages.propeller.src.Checkpoints.
- Position
- Below the diagonal: packages.propeller.src.FeedSource uses a module listed above it, which is the healthy direction.
21→36 packages.propeller.src.FeedSource uses packages.propeller.src.StreamsSink part of a loop✕
- Connections
- 1 pair of types, where a type in packages.propeller.src.FeedSource uses a type in packages.propeller.src.StreamsSink.
- The types involved
packages.propeller.src.FeedSource.TailingFeedSource→packages.propeller.src.StreamsSink.Batch
- Direction
- packages.propeller.src.FeedSource uses packages.propeller.src.StreamsSink, so a change to packages.propeller.src.StreamsSink can break packages.propeller.src.FeedSource, while a change to packages.propeller.src.FeedSource can't break packages.propeller.src.StreamsSink.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→2 packages.core.src.lib.Cache uses packages.core.src.lib.Core✕
- Connections
- 1 pair of types, where a type in packages.core.src.lib.Cache uses a type in packages.core.src.lib.Core.
- The types involved
packages.core.src.lib.Cache.CachingCategory→packages.core.src.lib.Core.SyncResult
- Direction
- packages.core.src.lib.Cache uses packages.core.src.lib.Core, so a change to packages.core.src.lib.Core can break packages.core.src.lib.Cache, while a change to packages.core.src.lib.Cache can't break packages.core.src.lib.Core.
- Position
- Below the diagonal: packages.core.src.lib.Cache uses a module listed above it, which is the healthy direction.
22→3 packages.core.src.lib.Cache uses packages.core.src.lib.StreamId✕
- Connections
- 2 pairs of types, where a type in packages.core.src.lib.Cache uses a type in packages.core.src.lib.StreamId.
- The types involved
packages.core.src.lib.Cache.CachingCategory→packages.core.src.lib.StreamId.StreamIdpackages.core.src.lib.Cache.IReloadableCategory→packages.core.src.lib.StreamId.StreamId
- Direction
- packages.core.src.lib.Cache uses packages.core.src.lib.StreamId, so a change to packages.core.src.lib.StreamId can break packages.core.src.lib.Cache, while a change to packages.core.src.lib.Cache can't break packages.core.src.lib.StreamId.
- Position
- Below the diagonal: packages.core.src.lib.Cache uses a module listed above it, which is the healthy direction.
22→17 packages.core.src.lib.Cache uses packages.core.src.lib.Category✕
- Connections
- 1 pair of types, where a type in packages.core.src.lib.Cache uses a type in packages.core.src.lib.Category.
- The types involved
packages.core.src.lib.Cache.CachingCategory→packages.core.src.lib.Category.ICategory
- Direction
- packages.core.src.lib.Cache uses packages.core.src.lib.Category, so a change to packages.core.src.lib.Category can break packages.core.src.lib.Cache, while a change to packages.core.src.lib.Cache can't break packages.core.src.lib.Category.
- Position
- Below the diagonal: packages.core.src.lib.Cache uses a module listed above it, which is the healthy direction.
23→10 packages.message-db.message-db-consumer.src.lib.MessageDbSource uses packages.message-db.message-db-consumer.src.lib.MessageDbClient✕
- Connections
- 1 pair of types, where a type in packages.message-db.message-db-consumer.src.lib.MessageDbSource uses a type in packages.message-db.message-db-consumer.src.lib.MessageDbClient.
- The types involved
packages.message-db.message-db-consumer.src.lib.MessageDbSource.MessageDbSource→packages.message-db.message-db-consumer.src.lib.MessageDbClient.MessageDbCategoryReader
- Direction
- packages.message-db.message-db-consumer.src.lib.MessageDbSource uses packages.message-db.message-db-consumer.src.lib.MessageDbClient, so a change to packages.message-db.message-db-consumer.src.lib.MessageDbClient can break packages.message-db.message-db-consumer.src.lib.MessageDbSource, while a change to packages.message-db.message-db-consumer.src.lib.MessageDbSource can't break packages.message-db.message-db-consumer.src.lib.MessageDbClient.
- Position
- Below the diagonal: packages.message-db.message-db-consumer.src.lib.MessageDbSource uses a module listed above it, which is the healthy direction.
23→13 packages.message-db.message-db-consumer.src.lib.MessageDbSource uses packages.propeller.src.Checkpoints✕
- Connections
- 2 pairs of types, where a type in packages.message-db.message-db-consumer.src.lib.MessageDbSource uses a type in packages.propeller.src.Checkpoints.
- The types involved
packages.message-db.message-db-consumer.src.lib.MessageDbSource.CreateOptions→packages.propeller.src.Checkpoints.ICheckpointspackages.message-db.message-db-consumer.src.lib.MessageDbSource.MessageDbSource→packages.propeller.src.Checkpoints.ICheckpoints
- Direction
- packages.message-db.message-db-consumer.src.lib.MessageDbSource uses packages.propeller.src.Checkpoints, so a change to packages.propeller.src.Checkpoints can break packages.message-db.message-db-consumer.src.lib.MessageDbSource, while a change to packages.message-db.message-db-consumer.src.lib.MessageDbSource can't break packages.propeller.src.Checkpoints.
- Position
- Below the diagonal: packages.message-db.message-db-consumer.src.lib.MessageDbSource uses a module listed above it, which is the healthy direction.
23→14 packages.message-db.message-db-consumer.src.lib.MessageDbSource uses packages.propeller.src.Types✕
- Connections
- 2 pairs of types, where a type in packages.message-db.message-db-consumer.src.lib.MessageDbSource uses a type in packages.propeller.src.Types.
- The types involved
packages.message-db.message-db-consumer.src.lib.MessageDbSource.CreateOptions→packages.propeller.src.Types.Sinkpackages.message-db.message-db-consumer.src.lib.MessageDbSource.MessageDbSource→packages.propeller.src.Types.Sink
- Direction
- packages.message-db.message-db-consumer.src.lib.MessageDbSource uses packages.propeller.src.Types, so a change to packages.propeller.src.Types can break packages.message-db.message-db-consumer.src.lib.MessageDbSource, while a change to packages.message-db.message-db-consumer.src.lib.MessageDbSource can't break packages.propeller.src.Types.
- Position
- Below the diagonal: packages.message-db.message-db-consumer.src.lib.MessageDbSource uses a module listed above it, which is the healthy direction.
23→21 packages.message-db.message-db-consumer.src.lib.MessageDbSource uses packages.propeller.src.FeedSource✕
- Connections
- 1 pair of types, where a type in packages.message-db.message-db-consumer.src.lib.MessageDbSource uses a type in packages.propeller.src.FeedSource.
- The types involved
packages.message-db.message-db-consumer.src.lib.MessageDbSource.MessageDbSource→packages.propeller.src.FeedSource.TailingFeedSource
- Direction
- packages.message-db.message-db-consumer.src.lib.MessageDbSource uses packages.propeller.src.FeedSource, so a change to packages.propeller.src.FeedSource can break packages.message-db.message-db-consumer.src.lib.MessageDbSource, while a change to packages.message-db.message-db-consumer.src.lib.MessageDbSource can't break packages.propeller.src.FeedSource.
- Position
- Below the diagonal: packages.message-db.message-db-consumer.src.lib.MessageDbSource uses a module listed above it, which is the healthy direction.
24→1 packages.dynamo-store.dynamo-store.src.DynamoStore uses packages.core.src.lib.Codec✕
- Connections
- 2 pairs of types, where a type in packages.dynamo-store.dynamo-store.src.DynamoStore uses a type in packages.core.src.lib.Codec.
- The types involved
packages.dynamo-store.dynamo-store.src.DynamoStore.DynamoStoreCategory→packages.core.src.lib.Codec.ICodecpackages.dynamo-store.dynamo-store.src.DynamoStore.StoreCategory→packages.core.src.lib.Codec.ICodec
- Direction
- packages.dynamo-store.dynamo-store.src.DynamoStore uses packages.core.src.lib.Codec, so a change to packages.core.src.lib.Codec can break packages.dynamo-store.dynamo-store.src.DynamoStore, while a change to packages.dynamo-store.dynamo-store.src.DynamoStore can't break packages.core.src.lib.Codec.
- Position
- Below the diagonal: packages.dynamo-store.dynamo-store.src.DynamoStore uses a module listed above it, which is the healthy direction.
24→2 packages.dynamo-store.dynamo-store.src.DynamoStore uses packages.core.src.lib.Core✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.dynamo-store.src.DynamoStore uses a type in packages.core.src.lib.Core.
- The types involved
packages.dynamo-store.dynamo-store.src.DynamoStore.StoreCategory→packages.core.src.lib.Core.SyncResult
- Direction
- packages.dynamo-store.dynamo-store.src.DynamoStore uses packages.core.src.lib.Core, so a change to packages.core.src.lib.Core can break packages.dynamo-store.dynamo-store.src.DynamoStore, while a change to packages.dynamo-store.dynamo-store.src.DynamoStore can't break packages.core.src.lib.Core.
- Position
- Below the diagonal: packages.dynamo-store.dynamo-store.src.DynamoStore uses a module listed above it, which is the healthy direction.
24→3 packages.dynamo-store.dynamo-store.src.DynamoStore uses packages.core.src.lib.StreamId✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.dynamo-store.src.DynamoStore uses a type in packages.core.src.lib.StreamId.
- The types involved
packages.dynamo-store.dynamo-store.src.DynamoStore.StoreCategory→packages.core.src.lib.StreamId.StreamId
- Direction
- packages.dynamo-store.dynamo-store.src.DynamoStore uses packages.core.src.lib.StreamId, so a change to packages.core.src.lib.StreamId can break packages.dynamo-store.dynamo-store.src.DynamoStore, while a change to packages.dynamo-store.dynamo-store.src.DynamoStore can't break packages.core.src.lib.StreamId.
- Position
- Below the diagonal: packages.dynamo-store.dynamo-store.src.DynamoStore uses a module listed above it, which is the healthy direction.
24→4 packages.dynamo-store.dynamo-store.src.DynamoStore uses packages.core.src.lib.StreamName✕
- Connections
- 2 pairs of types, where a type in packages.dynamo-store.dynamo-store.src.DynamoStore uses a type in packages.core.src.lib.StreamName.
- The types involved
packages.dynamo-store.dynamo-store.src.DynamoStore.EventsContext→packages.core.src.lib.StreamName.StreamNamepackages.dynamo-store.dynamo-store.src.DynamoStore.StoreClient→packages.core.src.lib.StreamName.StreamName
- Direction
- packages.dynamo-store.dynamo-store.src.DynamoStore uses packages.core.src.lib.StreamName, so a change to packages.core.src.lib.StreamName can break packages.dynamo-store.dynamo-store.src.DynamoStore, while a change to packages.dynamo-store.dynamo-store.src.DynamoStore can't break packages.core.src.lib.StreamName.
- Position
- Below the diagonal: packages.dynamo-store.dynamo-store.src.DynamoStore uses a module listed above it, which is the healthy direction.
24→17 packages.dynamo-store.dynamo-store.src.DynamoStore uses packages.core.src.lib.Category✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.dynamo-store.src.DynamoStore uses a type in packages.core.src.lib.Category.
- The types involved
packages.dynamo-store.dynamo-store.src.DynamoStore.DynamoStoreCategory→packages.core.src.lib.Category.Category
- Direction
- packages.dynamo-store.dynamo-store.src.DynamoStore uses packages.core.src.lib.Category, so a change to packages.core.src.lib.Category can break packages.dynamo-store.dynamo-store.src.DynamoStore, while a change to packages.dynamo-store.dynamo-store.src.DynamoStore can't break packages.core.src.lib.Category.
- Position
- Below the diagonal: packages.dynamo-store.dynamo-store.src.DynamoStore uses a module listed above it, which is the healthy direction.
24→22 packages.dynamo-store.dynamo-store.src.DynamoStore uses packages.core.src.lib.Cache✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.dynamo-store.src.DynamoStore uses a type in packages.core.src.lib.Cache.
- The types involved
packages.dynamo-store.dynamo-store.src.DynamoStore.StoreCategory→packages.core.src.lib.Cache.IReloadableCategory
- Direction
- packages.dynamo-store.dynamo-store.src.DynamoStore uses packages.core.src.lib.Cache, so a change to packages.core.src.lib.Cache can break packages.dynamo-store.dynamo-store.src.DynamoStore, while a change to packages.dynamo-store.dynamo-store.src.DynamoStore can't break packages.core.src.lib.Cache.
- Position
- Below the diagonal: packages.dynamo-store.dynamo-store.src.DynamoStore uses a module listed above it, which is the healthy direction.
25→1 packages.memory-store.src uses packages.core.src.lib.Codec✕
- Connections
- 2 pairs of types, where a type in packages.memory-store.src uses a type in packages.core.src.lib.Codec.
- The types involved
packages.memory-store.src.Category→packages.core.src.lib.Codec.ICodecpackages.memory-store.src.MemoryStoreCategory→packages.core.src.lib.Codec.ICodec
- Direction
- packages.memory-store.src uses packages.core.src.lib.Codec, so a change to packages.core.src.lib.Codec can break packages.memory-store.src, while a change to packages.memory-store.src can't break packages.core.src.lib.Codec.
- Position
- Below the diagonal: packages.memory-store.src uses a module listed above it, which is the healthy direction.
25→2 packages.memory-store.src uses packages.core.src.lib.Core✕
- Connections
- 1 pair of types, where a type in packages.memory-store.src uses a type in packages.core.src.lib.Core.
- The types involved
packages.memory-store.src.Category→packages.core.src.lib.Core.SyncResult
- Direction
- packages.memory-store.src uses packages.core.src.lib.Core, so a change to packages.core.src.lib.Core can break packages.memory-store.src, while a change to packages.memory-store.src can't break packages.core.src.lib.Core.
- Position
- Below the diagonal: packages.memory-store.src uses a module listed above it, which is the healthy direction.
25→3 packages.memory-store.src uses packages.core.src.lib.StreamId✕
- Connections
- 1 pair of types, where a type in packages.memory-store.src uses a type in packages.core.src.lib.StreamId.
- The types involved
packages.memory-store.src.Category→packages.core.src.lib.StreamId.StreamId
- Direction
- packages.memory-store.src uses packages.core.src.lib.StreamId, so a change to packages.core.src.lib.StreamId can break packages.memory-store.src, while a change to packages.memory-store.src can't break packages.core.src.lib.StreamId.
- Position
- Below the diagonal: packages.memory-store.src uses a module listed above it, which is the healthy direction.
25→4 packages.memory-store.src uses packages.core.src.lib.StreamName✕
- Connections
- 1 pair of types, where a type in packages.memory-store.src uses a type in packages.core.src.lib.StreamName.
- The types involved
packages.memory-store.src.VolatileStore→packages.core.src.lib.StreamName.StreamName
- Direction
- packages.memory-store.src uses packages.core.src.lib.StreamName, so a change to packages.core.src.lib.StreamName can break packages.memory-store.src, while a change to packages.memory-store.src can't break packages.core.src.lib.StreamName.
- Position
- Below the diagonal: packages.memory-store.src uses a module listed above it, which is the healthy direction.
25→22 packages.memory-store.src uses packages.core.src.lib.Cache✕
- Connections
- 1 pair of types, where a type in packages.memory-store.src uses a type in packages.core.src.lib.Cache.
- The types involved
packages.memory-store.src.Category→packages.core.src.lib.Cache.IReloadableCategory
- Direction
- packages.memory-store.src uses packages.core.src.lib.Cache, so a change to packages.core.src.lib.Cache can break packages.memory-store.src, while a change to packages.memory-store.src can't break packages.core.src.lib.Cache.
- Position
- Below the diagonal: packages.memory-store.src uses a module listed above it, which is the healthy direction.
26→24 apps.hotel.src.entrypoints uses packages.dynamo-store.dynamo-store.src.DynamoStore✕
- Connections
- 1 pair of types, where a type in apps.hotel.src.entrypoints uses a type in packages.dynamo-store.dynamo-store.src.DynamoStore.
- The types involved
apps.hotel.src.entrypoints.config→packages.dynamo-store.dynamo-store.src.DynamoStore.DynamoStoreContext
- Direction
- apps.hotel.src.entrypoints uses packages.dynamo-store.dynamo-store.src.DynamoStore, so a change to packages.dynamo-store.dynamo-store.src.DynamoStore can break apps.hotel.src.entrypoints, while a change to apps.hotel.src.entrypoints can't break packages.dynamo-store.dynamo-store.src.DynamoStore.
- Position
- Below the diagonal: apps.hotel.src.entrypoints uses a module listed above it, which is the healthy direction.
27→2 packages.core.src.lib.Decider uses packages.core.src.lib.Core✕
- Connections
- 1 pair of types, where a type in packages.core.src.lib.Decider uses a type in packages.core.src.lib.Core.
- The types involved
packages.core.src.lib.Decider.Decider→packages.core.src.lib.Core.IStream
- Direction
- packages.core.src.lib.Decider uses packages.core.src.lib.Core, so a change to packages.core.src.lib.Core can break packages.core.src.lib.Decider, while a change to packages.core.src.lib.Decider can't break packages.core.src.lib.Core.
- Position
- Below the diagonal: packages.core.src.lib.Decider uses a module listed above it, which is the healthy direction.
27→3 packages.core.src.lib.Decider uses packages.core.src.lib.StreamId✕
- Connections
- 1 pair of types, where a type in packages.core.src.lib.Decider uses a type in packages.core.src.lib.StreamId.
- The types involved
packages.core.src.lib.Decider.Decider→packages.core.src.lib.StreamId.StreamId
- Direction
- packages.core.src.lib.Decider uses packages.core.src.lib.StreamId, so a change to packages.core.src.lib.StreamId can break packages.core.src.lib.Decider, while a change to packages.core.src.lib.Decider can't break packages.core.src.lib.StreamId.
- Position
- Below the diagonal: packages.core.src.lib.Decider uses a module listed above it, which is the healthy direction.
27→17 packages.core.src.lib.Decider uses packages.core.src.lib.Category✕
- Connections
- 1 pair of types, where a type in packages.core.src.lib.Decider uses a type in packages.core.src.lib.Category.
- The types involved
packages.core.src.lib.Decider.Decider→packages.core.src.lib.Category.Category
- Direction
- packages.core.src.lib.Decider uses packages.core.src.lib.Category, so a change to packages.core.src.lib.Category can break packages.core.src.lib.Decider, while a change to packages.core.src.lib.Decider can't break packages.core.src.lib.Category.
- Position
- Below the diagonal: packages.core.src.lib.Decider uses a module listed above it, which is the healthy direction.
27→24 packages.core.src.lib.Decider uses packages.dynamo-store.dynamo-store.src.DynamoStore✕
- Connections
- 1 pair of types, where a type in packages.core.src.lib.Decider uses a type in packages.dynamo-store.dynamo-store.src.DynamoStore.
- The types involved
packages.core.src.lib.Decider.Decider→packages.dynamo-store.dynamo-store.src.DynamoStore.Result
- Direction
- packages.core.src.lib.Decider uses packages.dynamo-store.dynamo-store.src.DynamoStore, so a change to packages.dynamo-store.dynamo-store.src.DynamoStore can break packages.core.src.lib.Decider, while a change to packages.core.src.lib.Decider can't break packages.dynamo-store.dynamo-store.src.DynamoStore.
- Position
- Below the diagonal: packages.core.src.lib.Decider uses a module listed above it, which is the healthy direction.
28→24 packages.dynamo-store.dynamo-store.src uses packages.dynamo-store.dynamo-store.src.DynamoStore✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.dynamo-store.src uses a type in packages.dynamo-store.dynamo-store.src.DynamoStore.
- The types involved
packages.dynamo-store.dynamo-store.src.DynamoStore→packages.dynamo-store.dynamo-store.src.DynamoStore.AccessStrategy
- Direction
- packages.dynamo-store.dynamo-store.src uses packages.dynamo-store.dynamo-store.src.DynamoStore, so a change to packages.dynamo-store.dynamo-store.src.DynamoStore can break packages.dynamo-store.dynamo-store.src, while a change to packages.dynamo-store.dynamo-store.src can't break packages.dynamo-store.dynamo-store.src.DynamoStore.
- Position
- Below the diagonal: packages.dynamo-store.dynamo-store.src uses a module listed above it, which is the healthy direction.
29→7 packages.dynamo-store.indexer.src.AppendsIndex uses packages.dynamo-store.indexer.src.Identifiers✕
- Connections
- 3 pairs of types, where a type in packages.dynamo-store.indexer.src.AppendsIndex uses a type in packages.dynamo-store.indexer.src.Identifiers.
- The types involved
packages.dynamo-store.indexer.src.AppendsIndex.Reader→packages.dynamo-store.indexer.src.Identifiers.AppendsPartitionIdpackages.dynamo-store.indexer.src.AppendsIndex.Service→packages.dynamo-store.indexer.src.Identifiers.AppendsEpochIdpackages.dynamo-store.indexer.src.AppendsIndex.Service→packages.dynamo-store.indexer.src.Identifiers.AppendsPartitionId
- Direction
- packages.dynamo-store.indexer.src.AppendsIndex uses packages.dynamo-store.indexer.src.Identifiers, so a change to packages.dynamo-store.indexer.src.Identifiers can break packages.dynamo-store.indexer.src.AppendsIndex, while a change to packages.dynamo-store.indexer.src.AppendsIndex can't break packages.dynamo-store.indexer.src.Identifiers.
- Position
- Below the diagonal: packages.dynamo-store.indexer.src.AppendsIndex uses a module listed above it, which is the healthy direction.
29→22 packages.dynamo-store.indexer.src.AppendsIndex uses packages.core.src.lib.Cache✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.indexer.src.AppendsIndex uses a type in packages.core.src.lib.Cache.
- The types involved
packages.dynamo-store.indexer.src.AppendsIndex.Service→packages.core.src.lib.Cache.ICachingStrategy
- Direction
- packages.dynamo-store.indexer.src.AppendsIndex uses packages.core.src.lib.Cache, so a change to packages.core.src.lib.Cache can break packages.dynamo-store.indexer.src.AppendsIndex, while a change to packages.dynamo-store.indexer.src.AppendsIndex can't break packages.core.src.lib.Cache.
- Position
- Below the diagonal: packages.dynamo-store.indexer.src.AppendsIndex uses a module listed above it, which is the healthy direction.
29→24 packages.dynamo-store.indexer.src.AppendsIndex uses packages.dynamo-store.dynamo-store.src.DynamoStore✕
- Connections
- 2 pairs of types, where a type in packages.dynamo-store.indexer.src.AppendsIndex uses a type in packages.dynamo-store.dynamo-store.src.DynamoStore.
- The types involved
packages.dynamo-store.indexer.src.AppendsIndex.Reader→packages.dynamo-store.dynamo-store.src.DynamoStore.DynamoStoreContextpackages.dynamo-store.indexer.src.AppendsIndex.Service→packages.dynamo-store.dynamo-store.src.DynamoStore.DynamoStoreContext
- Direction
- packages.dynamo-store.indexer.src.AppendsIndex uses packages.dynamo-store.dynamo-store.src.DynamoStore, so a change to packages.dynamo-store.dynamo-store.src.DynamoStore can break packages.dynamo-store.indexer.src.AppendsIndex, while a change to packages.dynamo-store.indexer.src.AppendsIndex can't break packages.dynamo-store.dynamo-store.src.DynamoStore.
- Position
- Below the diagonal: packages.dynamo-store.indexer.src.AppendsIndex uses a module listed above it, which is the healthy direction.
29→25 packages.dynamo-store.indexer.src.AppendsIndex uses packages.memory-store.src✕
- Connections
- 2 pairs of types, where a type in packages.dynamo-store.indexer.src.AppendsIndex uses a type in packages.memory-store.src.
- The types involved
packages.dynamo-store.indexer.src.AppendsIndex.Reader→packages.memory-store.src.VolatileStorepackages.dynamo-store.indexer.src.AppendsIndex.Service→packages.memory-store.src.VolatileStore
- Direction
- packages.dynamo-store.indexer.src.AppendsIndex uses packages.memory-store.src, so a change to packages.memory-store.src can break packages.dynamo-store.indexer.src.AppendsIndex, while a change to packages.dynamo-store.indexer.src.AppendsIndex can't break packages.memory-store.src.
- Position
- Below the diagonal: packages.dynamo-store.indexer.src.AppendsIndex uses a module listed above it, which is the healthy direction.
30→7 packages.dynamo-store.indexer.src.DynamoStoreIndexer uses packages.dynamo-store.indexer.src.Identifiers✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.indexer.src.DynamoStoreIndexer uses a type in packages.dynamo-store.indexer.src.Identifiers.
- The types involved
packages.dynamo-store.indexer.src.DynamoStoreIndexer.DynamoStoreIndexer→packages.dynamo-store.indexer.src.Identifiers.AppendsPartitionId
- Direction
- packages.dynamo-store.indexer.src.DynamoStoreIndexer uses packages.dynamo-store.indexer.src.Identifiers, so a change to packages.dynamo-store.indexer.src.Identifiers can break packages.dynamo-store.indexer.src.DynamoStoreIndexer, while a change to packages.dynamo-store.indexer.src.DynamoStoreIndexer can't break packages.dynamo-store.indexer.src.Identifiers.
- Position
- Below the diagonal: packages.dynamo-store.indexer.src.DynamoStoreIndexer uses a module listed above it, which is the healthy direction.
30→24 packages.dynamo-store.indexer.src.DynamoStoreIndexer uses packages.dynamo-store.dynamo-store.src.DynamoStore✕
- Connections
- 2 pairs of types, where a type in packages.dynamo-store.indexer.src.DynamoStoreIndexer uses a type in packages.dynamo-store.dynamo-store.src.DynamoStore.
- The types involved
packages.dynamo-store.indexer.src.DynamoStoreIndexer.DynamoStoreIndexer→packages.dynamo-store.dynamo-store.src.DynamoStore.DynamoStoreContextpackages.dynamo-store.indexer.src.DynamoStoreIndexer.DynamoStoreIngester→packages.dynamo-store.dynamo-store.src.DynamoStore.DynamoStoreContext
- Direction
- packages.dynamo-store.indexer.src.DynamoStoreIndexer uses packages.dynamo-store.dynamo-store.src.DynamoStore, so a change to packages.dynamo-store.dynamo-store.src.DynamoStore can break packages.dynamo-store.indexer.src.DynamoStoreIndexer, while a change to packages.dynamo-store.indexer.src.DynamoStoreIndexer can't break packages.dynamo-store.dynamo-store.src.DynamoStore.
- Position
- Below the diagonal: packages.dynamo-store.indexer.src.DynamoStoreIndexer uses a module listed above it, which is the healthy direction.
31→13 packages.dynamo-store.source.src.Checkpoints uses packages.propeller.src.Checkpoints✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.source.src.Checkpoints uses a type in packages.propeller.src.Checkpoints.
- The types involved
packages.dynamo-store.source.src.Checkpoints.DynamoCheckpoints→packages.propeller.src.Checkpoints.ICheckpoints
- Direction
- packages.dynamo-store.source.src.Checkpoints uses packages.propeller.src.Checkpoints, so a change to packages.propeller.src.Checkpoints can break packages.dynamo-store.source.src.Checkpoints, while a change to packages.dynamo-store.source.src.Checkpoints can't break packages.propeller.src.Checkpoints.
- Position
- Below the diagonal: packages.dynamo-store.source.src.Checkpoints uses a module listed above it, which is the healthy direction.
31→22 packages.dynamo-store.source.src.Checkpoints uses packages.core.src.lib.Cache✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.source.src.Checkpoints uses a type in packages.core.src.lib.Cache.
- The types involved
packages.dynamo-store.source.src.Checkpoints.DynamoCheckpoints→packages.core.src.lib.Cache.ICache
- Direction
- packages.dynamo-store.source.src.Checkpoints uses packages.core.src.lib.Cache, so a change to packages.core.src.lib.Cache can break packages.dynamo-store.source.src.Checkpoints, while a change to packages.dynamo-store.source.src.Checkpoints can't break packages.core.src.lib.Cache.
- Position
- Below the diagonal: packages.dynamo-store.source.src.Checkpoints uses a module listed above it, which is the healthy direction.
31→24 packages.dynamo-store.source.src.Checkpoints uses packages.dynamo-store.dynamo-store.src.DynamoStore✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.source.src.Checkpoints uses a type in packages.dynamo-store.dynamo-store.src.DynamoStore.
- The types involved
packages.dynamo-store.source.src.Checkpoints.DynamoCheckpoints→packages.dynamo-store.dynamo-store.src.DynamoStore.DynamoStoreContext
- Direction
- packages.dynamo-store.source.src.Checkpoints uses packages.dynamo-store.dynamo-store.src.DynamoStore, so a change to packages.dynamo-store.dynamo-store.src.DynamoStore can break packages.dynamo-store.source.src.Checkpoints, while a change to packages.dynamo-store.source.src.Checkpoints can't break packages.dynamo-store.dynamo-store.src.DynamoStore.
- Position
- Below the diagonal: packages.dynamo-store.source.src.Checkpoints uses a module listed above it, which is the healthy direction.
32→1 packages.libsql.src.lib.Category uses packages.core.src.lib.Codec✕
- Connections
- 2 pairs of types, where a type in packages.libsql.src.lib.Category uses a type in packages.core.src.lib.Codec.
- The types involved
packages.libsql.src.lib.Category.InternalCategory→packages.core.src.lib.Codec.ICodecpackages.libsql.src.lib.Category.LibSqlCategory→packages.core.src.lib.Codec.ICodec
- Direction
- packages.libsql.src.lib.Category uses packages.core.src.lib.Codec, so a change to packages.core.src.lib.Codec can break packages.libsql.src.lib.Category, while a change to packages.libsql.src.lib.Category can't break packages.core.src.lib.Codec.
- Position
- Below the diagonal: packages.libsql.src.lib.Category uses a module listed above it, which is the healthy direction.
32→2 packages.libsql.src.lib.Category uses packages.core.src.lib.Core✕
- Connections
- 1 pair of types, where a type in packages.libsql.src.lib.Category uses a type in packages.core.src.lib.Core.
- The types involved
packages.libsql.src.lib.Category.InternalCategory→packages.core.src.lib.Core.SyncResult
- Direction
- packages.libsql.src.lib.Category uses packages.core.src.lib.Core, so a change to packages.core.src.lib.Core can break packages.libsql.src.lib.Category, while a change to packages.libsql.src.lib.Category can't break packages.core.src.lib.Core.
- Position
- Below the diagonal: packages.libsql.src.lib.Category uses a module listed above it, which is the healthy direction.
32→3 packages.libsql.src.lib.Category uses packages.core.src.lib.StreamId✕
- Connections
- 1 pair of types, where a type in packages.libsql.src.lib.Category uses a type in packages.core.src.lib.StreamId.
- The types involved
packages.libsql.src.lib.Category.InternalCategory→packages.core.src.lib.StreamId.StreamId
- Direction
- packages.libsql.src.lib.Category uses packages.core.src.lib.StreamId, so a change to packages.core.src.lib.StreamId can break packages.libsql.src.lib.Category, while a change to packages.libsql.src.lib.Category can't break packages.core.src.lib.StreamId.
- Position
- Below the diagonal: packages.libsql.src.lib.Category uses a module listed above it, which is the healthy direction.
32→4 packages.libsql.src.lib.Category uses packages.core.src.lib.StreamName✕
- Connections
- 1 pair of types, where a type in packages.libsql.src.lib.Category uses a type in packages.core.src.lib.StreamName.
- The types involved
packages.libsql.src.lib.Category.LibSqlContext→packages.core.src.lib.StreamName.StreamName
- Direction
- packages.libsql.src.lib.Category uses packages.core.src.lib.StreamName, so a change to packages.core.src.lib.StreamName can break packages.libsql.src.lib.Category, while a change to packages.libsql.src.lib.Category can't break packages.core.src.lib.StreamName.
- Position
- Below the diagonal: packages.libsql.src.lib.Category uses a module listed above it, which is the healthy direction.
32→9 packages.libsql.src.lib.Category uses packages.libsql.src.lib.LibSqlClient✕
- Connections
- 2 pairs of types, where a type in packages.libsql.src.lib.Category uses a type in packages.libsql.src.lib.LibSqlClient.
- The types involved
packages.libsql.src.lib.Category.LibSqlConnection→packages.libsql.src.lib.LibSqlClient.LibSqlReaderpackages.libsql.src.lib.Category.LibSqlConnection→packages.libsql.src.lib.LibSqlClient.LibSqlWriter
- Direction
- packages.libsql.src.lib.Category uses packages.libsql.src.lib.LibSqlClient, so a change to packages.libsql.src.lib.LibSqlClient can break packages.libsql.src.lib.Category, while a change to packages.libsql.src.lib.Category can't break packages.libsql.src.lib.LibSqlClient.
- Position
- Below the diagonal: packages.libsql.src.lib.Category uses a module listed above it, which is the healthy direction.
32→17 packages.libsql.src.lib.Category uses packages.core.src.lib.Category✕
- Connections
- 1 pair of types, where a type in packages.libsql.src.lib.Category uses a type in packages.core.src.lib.Category.
- The types involved
packages.libsql.src.lib.Category.LibSqlCategory→packages.core.src.lib.Category.Category
- Direction
- packages.libsql.src.lib.Category uses packages.core.src.lib.Category, so a change to packages.core.src.lib.Category can break packages.libsql.src.lib.Category, while a change to packages.libsql.src.lib.Category can't break packages.core.src.lib.Category.
- Position
- Below the diagonal: packages.libsql.src.lib.Category uses a module listed above it, which is the healthy direction.
32→22 packages.libsql.src.lib.Category uses packages.core.src.lib.Cache✕
- Connections
- 2 pairs of types, where a type in packages.libsql.src.lib.Category uses a type in packages.core.src.lib.Cache.
- The types involved
packages.libsql.src.lib.Category.InternalCategory→packages.core.src.lib.Cache.IReloadableCategorypackages.libsql.src.lib.Category.LibSqlCategory→packages.core.src.lib.Cache.ICachingStrategy
- Direction
- packages.libsql.src.lib.Category uses packages.core.src.lib.Cache, so a change to packages.core.src.lib.Cache can break packages.libsql.src.lib.Category, while a change to packages.libsql.src.lib.Category can't break packages.core.src.lib.Cache.
- Position
- Below the diagonal: packages.libsql.src.lib.Category uses a module listed above it, which is the healthy direction.
32→24 packages.libsql.src.lib.Category uses packages.dynamo-store.dynamo-store.src.DynamoStore✕
- Connections
- 2 pairs of types, where a type in packages.libsql.src.lib.Category uses a type in packages.dynamo-store.dynamo-store.src.DynamoStore.
- The types involved
packages.libsql.src.lib.Category.InternalCategory→packages.dynamo-store.dynamo-store.src.DynamoStore.AccessStrategypackages.libsql.src.lib.Category.LibSqlCategory→packages.dynamo-store.dynamo-store.src.DynamoStore.AccessStrategy
- Direction
- packages.libsql.src.lib.Category uses packages.dynamo-store.dynamo-store.src.DynamoStore, so a change to packages.dynamo-store.dynamo-store.src.DynamoStore can break packages.libsql.src.lib.Category, while a change to packages.libsql.src.lib.Category can't break packages.dynamo-store.dynamo-store.src.DynamoStore.
- Position
- Below the diagonal: packages.libsql.src.lib.Category uses a module listed above it, which is the healthy direction.
33→1 packages.message-db.message-db.src.lib.Category uses packages.core.src.lib.Codec✕
- Connections
- 2 pairs of types, where a type in packages.message-db.message-db.src.lib.Category uses a type in packages.core.src.lib.Codec.
- The types involved
packages.message-db.message-db.src.lib.Category.InternalCategory→packages.core.src.lib.Codec.ICodecpackages.message-db.message-db.src.lib.Category.MessageDbCategory→packages.core.src.lib.Codec.ICodec
- Direction
- packages.message-db.message-db.src.lib.Category uses packages.core.src.lib.Codec, so a change to packages.core.src.lib.Codec can break packages.message-db.message-db.src.lib.Category, while a change to packages.message-db.message-db.src.lib.Category can't break packages.core.src.lib.Codec.
- Position
- Below the diagonal: packages.message-db.message-db.src.lib.Category uses a module listed above it, which is the healthy direction.
33→2 packages.message-db.message-db.src.lib.Category uses packages.core.src.lib.Core✕
- Connections
- 1 pair of types, where a type in packages.message-db.message-db.src.lib.Category uses a type in packages.core.src.lib.Core.
- The types involved
packages.message-db.message-db.src.lib.Category.InternalCategory→packages.core.src.lib.Core.SyncResult
- Direction
- packages.message-db.message-db.src.lib.Category uses packages.core.src.lib.Core, so a change to packages.core.src.lib.Core can break packages.message-db.message-db.src.lib.Category, while a change to packages.message-db.message-db.src.lib.Category can't break packages.core.src.lib.Core.
- Position
- Below the diagonal: packages.message-db.message-db.src.lib.Category uses a module listed above it, which is the healthy direction.
33→3 packages.message-db.message-db.src.lib.Category uses packages.core.src.lib.StreamId✕
- Connections
- 1 pair of types, where a type in packages.message-db.message-db.src.lib.Category uses a type in packages.core.src.lib.StreamId.
- The types involved
packages.message-db.message-db.src.lib.Category.InternalCategory→packages.core.src.lib.StreamId.StreamId
- Direction
- packages.message-db.message-db.src.lib.Category uses packages.core.src.lib.StreamId, so a change to packages.core.src.lib.StreamId can break packages.message-db.message-db.src.lib.Category, while a change to packages.message-db.message-db.src.lib.Category can't break packages.core.src.lib.StreamId.
- Position
- Below the diagonal: packages.message-db.message-db.src.lib.Category uses a module listed above it, which is the healthy direction.
33→11 packages.message-db.message-db.src.lib.Category uses packages.message-db.message-db.src.lib.MessageDbClient✕
- Connections
- 2 pairs of types, where a type in packages.message-db.message-db.src.lib.Category uses a type in packages.message-db.message-db.src.lib.MessageDbClient.
- The types involved
packages.message-db.message-db.src.lib.Category.MessageDbConnection→packages.message-db.message-db.src.lib.MessageDbClient.MessageDbReaderpackages.message-db.message-db.src.lib.Category.MessageDbConnection→packages.message-db.message-db.src.lib.MessageDbClient.MessageDbWriter
- Direction
- packages.message-db.message-db.src.lib.Category uses packages.message-db.message-db.src.lib.MessageDbClient, so a change to packages.message-db.message-db.src.lib.MessageDbClient can break packages.message-db.message-db.src.lib.Category, while a change to packages.message-db.message-db.src.lib.Category can't break packages.message-db.message-db.src.lib.MessageDbClient.
- Position
- Below the diagonal: packages.message-db.message-db.src.lib.Category uses a module listed above it, which is the healthy direction.
33→22 packages.message-db.message-db.src.lib.Category uses packages.core.src.lib.Cache✕
- Connections
- 2 pairs of types, where a type in packages.message-db.message-db.src.lib.Category uses a type in packages.core.src.lib.Cache.
- The types involved
packages.message-db.message-db.src.lib.Category.InternalCategory→packages.core.src.lib.Cache.IReloadableCategorypackages.message-db.message-db.src.lib.Category.MessageDbCategory→packages.core.src.lib.Cache.ICachingStrategy
- Direction
- packages.message-db.message-db.src.lib.Category uses packages.core.src.lib.Cache, so a change to packages.core.src.lib.Cache can break packages.message-db.message-db.src.lib.Category, while a change to packages.message-db.message-db.src.lib.Category can't break packages.core.src.lib.Cache.
- Position
- Below the diagonal: packages.message-db.message-db.src.lib.Category uses a module listed above it, which is the healthy direction.
33→24 packages.message-db.message-db.src.lib.Category uses packages.dynamo-store.dynamo-store.src.DynamoStore✕
- Connections
- 2 pairs of types, where a type in packages.message-db.message-db.src.lib.Category uses a type in packages.dynamo-store.dynamo-store.src.DynamoStore.
- The types involved
packages.message-db.message-db.src.lib.Category.InternalCategory→packages.dynamo-store.dynamo-store.src.DynamoStore.AccessStrategypackages.message-db.message-db.src.lib.Category.MessageDbCategory→packages.dynamo-store.dynamo-store.src.DynamoStore.AccessStrategy
- Direction
- packages.message-db.message-db.src.lib.Category uses packages.dynamo-store.dynamo-store.src.DynamoStore, so a change to packages.dynamo-store.dynamo-store.src.DynamoStore can break packages.message-db.message-db.src.lib.Category, while a change to packages.message-db.message-db.src.lib.Category can't break packages.dynamo-store.dynamo-store.src.DynamoStore.
- Position
- Below the diagonal: packages.message-db.message-db.src.lib.Category uses a module listed above it, which is the healthy direction.
34→30 packages.dynamo-store.lambda.src uses packages.dynamo-store.indexer.src.DynamoStoreIndexer✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.lambda.src uses a type in packages.dynamo-store.indexer.src.DynamoStoreIndexer.
- The types involved
packages.dynamo-store.lambda.src.Handler→packages.dynamo-store.indexer.src.DynamoStoreIndexer.DynamoStoreIndexer
- Direction
- packages.dynamo-store.lambda.src uses packages.dynamo-store.indexer.src.DynamoStoreIndexer, so a change to packages.dynamo-store.indexer.src.DynamoStoreIndexer can break packages.dynamo-store.lambda.src, while a change to packages.dynamo-store.lambda.src can't break packages.dynamo-store.indexer.src.DynamoStoreIndexer.
- Position
- Below the diagonal: packages.dynamo-store.lambda.src uses a module listed above it, which is the healthy direction.
35→6 packages.dynamo-store.source.src.DynamoStoreSource uses packages.dynamo-store.indexer.src.Checkpoint✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.source.src.DynamoStoreSource uses a type in packages.dynamo-store.indexer.src.Checkpoint.
- The types involved
packages.dynamo-store.source.src.DynamoStoreSource.DynamoStoreSourceClient→packages.dynamo-store.indexer.src.Checkpoint.Checkpoint
- Direction
- packages.dynamo-store.source.src.DynamoStoreSource uses packages.dynamo-store.indexer.src.Checkpoint, so a change to packages.dynamo-store.indexer.src.Checkpoint can break packages.dynamo-store.source.src.DynamoStoreSource, while a change to packages.dynamo-store.source.src.DynamoStoreSource can't break packages.dynamo-store.indexer.src.Checkpoint.
- Position
- Below the diagonal: packages.dynamo-store.source.src.DynamoStoreSource uses a module listed above it, which is the healthy direction.
35→7 packages.dynamo-store.source.src.DynamoStoreSource uses packages.dynamo-store.indexer.src.Identifiers✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.source.src.DynamoStoreSource uses a type in packages.dynamo-store.indexer.src.Identifiers.
- The types involved
packages.dynamo-store.source.src.DynamoStoreSource.DynamoStoreSourceClient→packages.dynamo-store.indexer.src.Identifiers.AppendsPartitionId
- Direction
- packages.dynamo-store.source.src.DynamoStoreSource uses packages.dynamo-store.indexer.src.Identifiers, so a change to packages.dynamo-store.indexer.src.Identifiers can break packages.dynamo-store.source.src.DynamoStoreSource, while a change to packages.dynamo-store.source.src.DynamoStoreSource can't break packages.dynamo-store.indexer.src.Identifiers.
- Position
- Below the diagonal: packages.dynamo-store.source.src.DynamoStoreSource uses a module listed above it, which is the healthy direction.
35→13 packages.dynamo-store.source.src.DynamoStoreSource uses packages.propeller.src.Checkpoints✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.source.src.DynamoStoreSource uses a type in packages.propeller.src.Checkpoints.
- The types involved
packages.dynamo-store.source.src.DynamoStoreSource.CreateOptions→packages.propeller.src.Checkpoints.ICheckpoints
- Direction
- packages.dynamo-store.source.src.DynamoStoreSource uses packages.propeller.src.Checkpoints, so a change to packages.propeller.src.Checkpoints can break packages.dynamo-store.source.src.DynamoStoreSource, while a change to packages.dynamo-store.source.src.DynamoStoreSource can't break packages.propeller.src.Checkpoints.
- Position
- Below the diagonal: packages.dynamo-store.source.src.DynamoStoreSource uses a module listed above it, which is the healthy direction.
35→14 packages.dynamo-store.source.src.DynamoStoreSource uses packages.propeller.src.Types✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.source.src.DynamoStoreSource uses a type in packages.propeller.src.Types.
- The types involved
packages.dynamo-store.source.src.DynamoStoreSource.CreateOptions→packages.propeller.src.Types.Sink
- Direction
- packages.dynamo-store.source.src.DynamoStoreSource uses packages.propeller.src.Types, so a change to packages.propeller.src.Types can break packages.dynamo-store.source.src.DynamoStoreSource, while a change to packages.dynamo-store.source.src.DynamoStoreSource can't break packages.propeller.src.Types.
- Position
- Below the diagonal: packages.dynamo-store.source.src.DynamoStoreSource uses a module listed above it, which is the healthy direction.
35→21 packages.dynamo-store.source.src.DynamoStoreSource uses packages.propeller.src.FeedSource✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.source.src.DynamoStoreSource uses a type in packages.propeller.src.FeedSource.
- The types involved
packages.dynamo-store.source.src.DynamoStoreSource.DynamoStoreSource→packages.propeller.src.FeedSource.TailingFeedSource
- Direction
- packages.dynamo-store.source.src.DynamoStoreSource uses packages.propeller.src.FeedSource, so a change to packages.propeller.src.FeedSource can break packages.dynamo-store.source.src.DynamoStoreSource, while a change to packages.dynamo-store.source.src.DynamoStoreSource can't break packages.propeller.src.FeedSource.
- Position
- Below the diagonal: packages.dynamo-store.source.src.DynamoStoreSource uses a module listed above it, which is the healthy direction.
35→24 packages.dynamo-store.source.src.DynamoStoreSource uses packages.dynamo-store.dynamo-store.src.DynamoStore✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.source.src.DynamoStoreSource uses a type in packages.dynamo-store.dynamo-store.src.DynamoStore.
- The types involved
packages.dynamo-store.source.src.DynamoStoreSource.CreateOptions→packages.dynamo-store.dynamo-store.src.DynamoStore.DynamoStoreContext
- Direction
- packages.dynamo-store.source.src.DynamoStoreSource uses packages.dynamo-store.dynamo-store.src.DynamoStore, so a change to packages.dynamo-store.dynamo-store.src.DynamoStore can break packages.dynamo-store.source.src.DynamoStoreSource, while a change to packages.dynamo-store.source.src.DynamoStoreSource can't break packages.dynamo-store.dynamo-store.src.DynamoStore.
- Position
- Below the diagonal: packages.dynamo-store.source.src.DynamoStoreSource uses a module listed above it, which is the healthy direction.
35→29 packages.dynamo-store.source.src.DynamoStoreSource uses packages.dynamo-store.indexer.src.AppendsIndex✕
- Connections
- 2 pairs of types, where a type in packages.dynamo-store.source.src.DynamoStoreSource uses a type in packages.dynamo-store.indexer.src.AppendsIndex.
- The types involved
packages.dynamo-store.source.src.DynamoStoreSource.DynamoStoreSource→packages.dynamo-store.indexer.src.AppendsIndex.Readerpackages.dynamo-store.source.src.DynamoStoreSource.DynamoStoreSourceClient→packages.dynamo-store.indexer.src.AppendsIndex.Reader
- Direction
- packages.dynamo-store.source.src.DynamoStoreSource uses packages.dynamo-store.indexer.src.AppendsIndex, so a change to packages.dynamo-store.indexer.src.AppendsIndex can break packages.dynamo-store.source.src.DynamoStoreSource, while a change to packages.dynamo-store.source.src.DynamoStoreSource can't break packages.dynamo-store.indexer.src.AppendsIndex.
- Position
- Below the diagonal: packages.dynamo-store.source.src.DynamoStoreSource uses a module listed above it, which is the healthy direction.
35→36 packages.dynamo-store.source.src.DynamoStoreSource uses packages.propeller.src.StreamsSink part of a loop✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.source.src.DynamoStoreSource uses a type in packages.propeller.src.StreamsSink.
- The types involved
packages.dynamo-store.source.src.DynamoStoreSource.DynamoStoreSourceClient→packages.propeller.src.StreamsSink.Batch
- Direction
- packages.dynamo-store.source.src.DynamoStoreSource uses packages.propeller.src.StreamsSink, so a change to packages.propeller.src.StreamsSink can break packages.dynamo-store.source.src.DynamoStoreSource, while a change to packages.dynamo-store.source.src.DynamoStoreSource can't break packages.propeller.src.StreamsSink.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
36→4 packages.propeller.src.StreamsSink uses packages.core.src.lib.StreamName✕
- Connections
- 5 pairs of types, where a type in packages.propeller.src.StreamsSink uses a type in packages.core.src.lib.StreamName.
- The types involved
packages.propeller.src.StreamsSink.Batch→packages.core.src.lib.StreamName.StreamNamepackages.propeller.src.StreamsSink.ProgressState→packages.core.src.lib.StreamName.StreamNamepackages.propeller.src.StreamsSink.StreamStates→packages.core.src.lib.StreamName.StreamNamepackages.propeller.src.StreamsSink.Streams→packages.core.src.lib.StreamName.StreamNamepackages.propeller.src.StreamsSink.StreamsPrioritizer→packages.core.src.lib.StreamName.StreamName
- Direction
- packages.propeller.src.StreamsSink uses packages.core.src.lib.StreamName, so a change to packages.core.src.lib.StreamName can break packages.propeller.src.StreamsSink, while a change to packages.propeller.src.StreamsSink can't break packages.core.src.lib.StreamName.
- Position
- Below the diagonal: packages.propeller.src.StreamsSink uses a module listed above it, which is the healthy direction.
36→14 packages.propeller.src.StreamsSink uses packages.propeller.src.Types✕
- Connections
- 1 pair of types, where a type in packages.propeller.src.StreamsSink uses a type in packages.propeller.src.Types.
- The types involved
packages.propeller.src.StreamsSink.StreamsSink→packages.propeller.src.Types.Sink
- Direction
- packages.propeller.src.StreamsSink uses packages.propeller.src.Types, so a change to packages.propeller.src.Types can break packages.propeller.src.StreamsSink, while a change to packages.propeller.src.StreamsSink can't break packages.propeller.src.Types.
- Position
- Below the diagonal: packages.propeller.src.StreamsSink uses a module listed above it, which is the healthy direction.
36→35 packages.propeller.src.StreamsSink uses packages.dynamo-store.source.src.DynamoStoreSource✕
- Connections
- 1 pair of types, where a type in packages.propeller.src.StreamsSink uses a type in packages.dynamo-store.source.src.DynamoStoreSource.
- The types involved
packages.propeller.src.StreamsSink.StreamsSink→packages.dynamo-store.source.src.DynamoStoreSource.CreateOptions
- Direction
- packages.propeller.src.StreamsSink uses packages.dynamo-store.source.src.DynamoStoreSource, so a change to packages.dynamo-store.source.src.DynamoStoreSource can break packages.propeller.src.StreamsSink, while a change to packages.propeller.src.StreamsSink can't break packages.dynamo-store.source.src.DynamoStoreSource.
- Position
- Below the diagonal: packages.propeller.src.StreamsSink uses a module listed above it, which is the healthy direction.
37→7 packages.dynamo-store.indexer.src uses packages.dynamo-store.indexer.src.Identifiers✕
- Connections
- 2 pairs of types, where a type in packages.dynamo-store.indexer.src uses a type in packages.dynamo-store.indexer.src.Identifiers.
- The types involved
packages.dynamo-store.indexer.src.AppendsIndex→packages.dynamo-store.indexer.src.Identifiers.AppendsEpochIdpackages.dynamo-store.indexer.src.AppendsIndex→packages.dynamo-store.indexer.src.Identifiers.AppendsPartitionId
- Direction
- packages.dynamo-store.indexer.src uses packages.dynamo-store.indexer.src.Identifiers, so a change to packages.dynamo-store.indexer.src.Identifiers can break packages.dynamo-store.indexer.src, while a change to packages.dynamo-store.indexer.src can't break packages.dynamo-store.indexer.src.Identifiers.
- Position
- Below the diagonal: packages.dynamo-store.indexer.src uses a module listed above it, which is the healthy direction.
37→22 packages.dynamo-store.indexer.src uses packages.core.src.lib.Cache✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.indexer.src uses a type in packages.core.src.lib.Cache.
- The types involved
packages.dynamo-store.indexer.src.AppendsIndex→packages.core.src.lib.Cache.ICachingStrategy
- Direction
- packages.dynamo-store.indexer.src uses packages.core.src.lib.Cache, so a change to packages.core.src.lib.Cache can break packages.dynamo-store.indexer.src, while a change to packages.dynamo-store.indexer.src can't break packages.core.src.lib.Cache.
- Position
- Below the diagonal: packages.dynamo-store.indexer.src uses a module listed above it, which is the healthy direction.
37→24 packages.dynamo-store.indexer.src uses packages.dynamo-store.dynamo-store.src.DynamoStore✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.indexer.src uses a type in packages.dynamo-store.dynamo-store.src.DynamoStore.
- The types involved
packages.dynamo-store.indexer.src.AppendsIndex→packages.dynamo-store.dynamo-store.src.DynamoStore.DynamoStoreContext
- Direction
- packages.dynamo-store.indexer.src uses packages.dynamo-store.dynamo-store.src.DynamoStore, so a change to packages.dynamo-store.dynamo-store.src.DynamoStore can break packages.dynamo-store.indexer.src, while a change to packages.dynamo-store.indexer.src can't break packages.dynamo-store.dynamo-store.src.DynamoStore.
- Position
- Below the diagonal: packages.dynamo-store.indexer.src uses a module listed above it, which is the healthy direction.
37→25 packages.dynamo-store.indexer.src uses packages.memory-store.src✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.indexer.src uses a type in packages.memory-store.src.
- The types involved
packages.dynamo-store.indexer.src.AppendsIndex→packages.memory-store.src.VolatileStore
- Direction
- packages.dynamo-store.indexer.src uses packages.memory-store.src, so a change to packages.memory-store.src can break packages.dynamo-store.indexer.src, while a change to packages.dynamo-store.indexer.src can't break packages.memory-store.src.
- Position
- Below the diagonal: packages.dynamo-store.indexer.src uses a module listed above it, which is the healthy direction.
37→36 packages.dynamo-store.indexer.src uses packages.propeller.src.StreamsSink✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.indexer.src uses a type in packages.propeller.src.StreamsSink.
- The types involved
packages.dynamo-store.indexer.src.AppendsEpoch→packages.propeller.src.StreamsSink.StreamSpan
- Direction
- packages.dynamo-store.indexer.src uses packages.propeller.src.StreamsSink, so a change to packages.propeller.src.StreamsSink can break packages.dynamo-store.indexer.src, while a change to packages.dynamo-store.indexer.src can't break packages.propeller.src.StreamsSink.
- Position
- Below the diagonal: packages.dynamo-store.indexer.src uses a module listed above it, which is the healthy direction.
38→7 packages.dynamo-store.indexer.src.AppendsEpoch uses packages.dynamo-store.indexer.src.Identifiers✕
- Connections
- 3 pairs of types, where a type in packages.dynamo-store.indexer.src.AppendsEpoch uses a type in packages.dynamo-store.indexer.src.Identifiers.
- The types involved
packages.dynamo-store.indexer.src.AppendsEpoch.Service→packages.dynamo-store.indexer.src.Identifiers.AppendsEpochIdpackages.dynamo-store.indexer.src.AppendsEpoch.Service→packages.dynamo-store.indexer.src.Identifiers.AppendsPartitionIdpackages.dynamo-store.indexer.src.AppendsEpoch.Service→packages.dynamo-store.indexer.src.Identifiers.IndexStreamId
- Direction
- packages.dynamo-store.indexer.src.AppendsEpoch uses packages.dynamo-store.indexer.src.Identifiers, so a change to packages.dynamo-store.indexer.src.Identifiers can break packages.dynamo-store.indexer.src.AppendsEpoch, while a change to packages.dynamo-store.indexer.src.AppendsEpoch can't break packages.dynamo-store.indexer.src.Identifiers.
- Position
- Below the diagonal: packages.dynamo-store.indexer.src.AppendsEpoch uses a module listed above it, which is the healthy direction.
38→36 packages.dynamo-store.indexer.src.AppendsEpoch uses packages.propeller.src.StreamsSink✕
- Connections
- 1 pair of types, where a type in packages.dynamo-store.indexer.src.AppendsEpoch uses a type in packages.propeller.src.StreamsSink.
- The types involved
packages.dynamo-store.indexer.src.AppendsEpoch.Service→packages.propeller.src.StreamsSink.StreamSpan
- Direction
- packages.dynamo-store.indexer.src.AppendsEpoch uses packages.propeller.src.StreamsSink, so a change to packages.propeller.src.StreamsSink can break packages.dynamo-store.indexer.src.AppendsEpoch, while a change to packages.dynamo-store.indexer.src.AppendsEpoch can't break packages.propeller.src.StreamsSink.
- Position
- Below the diagonal: packages.dynamo-store.indexer.src.AppendsEpoch uses a module listed above it, which is the healthy direction.
39→9 packages.libsql.src.lib uses packages.libsql.src.lib.LibSqlClient✕
- Connections
- 1 pair of types, where a type in packages.libsql.src.lib uses a type in packages.libsql.src.lib.LibSqlClient.
- The types involved
packages.libsql.src.lib.Read→packages.libsql.src.lib.LibSqlClient.LibSqlReader
- Direction
- packages.libsql.src.lib uses packages.libsql.src.lib.LibSqlClient, so a change to packages.libsql.src.lib.LibSqlClient can break packages.libsql.src.lib, while a change to packages.libsql.src.lib can't break packages.libsql.src.lib.LibSqlClient.
- Position
- Below the diagonal: packages.libsql.src.lib uses a module listed above it, which is the healthy direction.
39→36 packages.libsql.src.lib uses packages.propeller.src.StreamsSink✕
- Connections
- 1 pair of types, where a type in packages.libsql.src.lib uses a type in packages.propeller.src.StreamsSink.
- The types involved
packages.libsql.src.lib.Read→packages.propeller.src.StreamsSink.Batch
- Direction
- packages.libsql.src.lib uses packages.propeller.src.StreamsSink, so a change to packages.propeller.src.StreamsSink can break packages.libsql.src.lib, while a change to packages.libsql.src.lib can't break packages.propeller.src.StreamsSink.
- Position
- Below the diagonal: packages.libsql.src.lib uses a module listed above it, which is the healthy direction.
40→11 packages.message-db.message-db.src.lib uses packages.message-db.message-db.src.lib.MessageDbClient✕
- Connections
- 1 pair of types, where a type in packages.message-db.message-db.src.lib uses a type in packages.message-db.message-db.src.lib.MessageDbClient.
- The types involved
packages.message-db.message-db.src.lib.Read→packages.message-db.message-db.src.lib.MessageDbClient.MessageDbReader
- Direction
- packages.message-db.message-db.src.lib uses packages.message-db.message-db.src.lib.MessageDbClient, so a change to packages.message-db.message-db.src.lib.MessageDbClient can break packages.message-db.message-db.src.lib, while a change to packages.message-db.message-db.src.lib can't break packages.message-db.message-db.src.lib.MessageDbClient.
- Position
- Below the diagonal: packages.message-db.message-db.src.lib uses a module listed above it, which is the healthy direction.
40→36 packages.message-db.message-db.src.lib uses packages.propeller.src.StreamsSink✕
- Connections
- 1 pair of types, where a type in packages.message-db.message-db.src.lib uses a type in packages.propeller.src.StreamsSink.
- The types involved
packages.message-db.message-db.src.lib.Read→packages.propeller.src.StreamsSink.Batch
- Direction
- packages.message-db.message-db.src.lib uses packages.propeller.src.StreamsSink, so a change to packages.propeller.src.StreamsSink can break packages.message-db.message-db.src.lib, while a change to packages.message-db.message-db.src.lib can't break packages.propeller.src.StreamsSink.
- Position
- Below the diagonal: packages.message-db.message-db.src.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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 83 | High / Critical |
| A05:2025 — Injection | 14 | High / Critical |
| A02:2025 — Security Misconfiguration | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 8 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (8); Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing; Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 8 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (8). | +10.7 pts | Low | Dependency Hygiene |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.6 pts | Low | ADR Quality |
| Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with FeedSource.test.mts. | +2.3 pts | Low | Test Quality |
| Resolve the 1 Test suite executes none of its 10 test cases finding(s) in Test Reliability. | +2.3 pts | Low | Test Reliability |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing. | +4.6 pts | Medium | Security & performance tooling |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +4.6 pts | Medium | DR & Backup |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.3 pts | Medium | Architecture documentation |
| Adopt pino (or winston) and log at meaningful points in the services you run. | +2.8 pts | Medium | Observability |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.0 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| apps/hotel/test/ReactorIntegration.test.ts | 7.2 | Mixed | Test Quality: No assertions: Pay before |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| packages/dynamo-store/dynamo-store/package.json | 7.8 | Mixed | Dependency Hygiene: Deprecated: @opentelemetry/sdk-trace-base |
| packages/libsql/package.json | 7.8 | Mixed | Dependency Hygiene: Deprecated: @opentelemetry/sdk-trace-base |
| packages/message-db/message-db/package.json | 7.8 | Mixed | Dependency Hygiene: Deprecated: @opentelemetry/sdk-trace-base |
| packages/propeller/src/FeedSource.test.mts | 8.0 | Near-clean | Test Quality: No assertions (empty test): It fails fast |
| packages/projection-pg/src/collapse.ts | 8.5 | Near-clean | Cyclomatic Complexity: collapse.concat (cyclomatic 21) |
| packages/dynamo-store/lambda/src/Handler.ts | 8.5 | Near-clean | Cognitive Complexity: Handler.parse (cognitive 31) |
| packages/dynamo-store/dynamo-store/src/DynamoStore.ts | 8.5 | Near-clean | God Classes: FileTooLong: src/DynamoStore.ts |
| packages/core/src/lib/Category.ts | 8.5 | Near-clean | Code Coverage: Low coverage: packages/core/src/lib/Category.ts |
| packages/core/src/lib/Decider.ts | 8.5 | Near-clean | Code Coverage: Low coverage: packages/core/src/lib/Decider.ts |
| packages/core/src/lib/Internal.ts | 8.5 | Near-clean | Code Coverage: Low coverage: packages/core/src/lib/Internal.ts |
| apps/example/test/read-models/PayerReadModel.test.ts | 8.5 | Near-clean | Test Quality: No assertions: Deleting a payer |
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 80 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 80 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, 184 of 235 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. 24 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 15 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 78.8% 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 (7 contributor(s) across 304 commit(s) sampled, automation and bot accounts excluded). One of them holds 96% of the history; the other 6 hold 0.7% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- 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/src/lib/Uuid.ts`, `packages/libsql/src/lib/Token.ts`, `packages/message-db/message-db/src/lib/Token.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- 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: "• Running dev in 18 packages / • Remote caching disabled / No tasks were executed as part of this run. / Tasks: 0 successful, 0 total / Cached: 0 cached, 0 total / Time: 61ms" 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: "• Running dev in 18 packages / • Remote caching disabled / No tasks were executed as part of this run. / Tasks: 0 successful, 0 total / Cached: 0 cached, 0 total / Time: 61ms" 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/explorer/bin/index.js:4), 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/explorer/bin/index.js:4), 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/explorer/bin/index.js:4), 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/explorer/bin/index.js:4), 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.
- 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 make no call through a named logger, 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.
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was collapse.concat at 21.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with collapse.concat (cyclomatic 21). — Refactoring it lifts Cyclomatic Complexity from 9.6 to about 10.0/10.
- 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
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was Handler.parse at 31.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with Handler.parse (cognitive 31). — Refactoring it lifts Cognitive Complexity from 9.2 to about 10.0/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FileTooLong finding(s) in God Classes — start with DynamoStore.ts. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D5 · Coupling
15 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 14 of the 15 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 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 55 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 78.8% — 3 file(s) below 50%. Measured from the JavaScript/TypeScript suite (vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in apps/example/; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in apps/hotel/; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/core/; vitest in packages/dynamo-store/cli/: not run; vitest in packages/dynamo-store/dynamo-store/: not run; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/dynamo-store/indexer/; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/dynamo-store/source/; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/libsql/; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/memory-store/; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/message-db/message-db/; vitest in packages/message-db/message-db-consumer/: not run).
What to do
- Resolve the 3 Low coverage finding(s) in Code Coverage — start with Category.ts, Decider.ts, Internal.ts. — One of this dimension's main actionable groups (3 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
169 test methods: 169 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 169 `it`/`test` case(s) across 30 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 7 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 169 tests.
What to do
- Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with FeedSource.test.mts. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 6 No assertions finding(s) in Test Quality — start with ReactorIntegration.test.ts (4), PayerReadModel.test.ts, scenario.ts. — One of this dimension's main actionable groups (6 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root (158 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in apps/example/ (22 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in apps/hotel/ (18 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/core/ (29 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/dynamo-store/cli/ (0 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/dynamo-store/dynamo-store/ (0 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/dynamo-store/indexer/ (12 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/dynamo-store/source/ (4 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/libsql/ (11 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/memory-store/ (1 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/message-db/message-db/ (13 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/message-db/message-db-consumer/ (2 tests)): measured (0 flaky).
What to do
- Resolve the 1 Test suite executes none of its 10 test cases finding(s) in Test Reliability. — One of this dimension's main actionable groups (1 issue-level).
D12 · Dependency Hygiene
32 outdated direct production npm dependency(ies) of 37 graded, 0 pinning defect(s), across 19 REDACTED (17 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 2 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.
What to do
- Resolve the 8 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (8). — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 1 Outdated (npm) finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 1378 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 1378 package(s) this repository's committed lockfile installs for a consumer — its 37 production, optional and peer dependency(ies), across 17 product REDACTED manifest(s), and everything those install in turn. Its 135 `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. 1 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 9547 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F2 example. 35 document(s) read across 18 unit(s).
What to do
- Resolve the 3 Documentation finding(s) in Documentation Quality — start with README.md (3). — One of this dimension's main actionable groups (3 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
8 domain type(s) cross context boundaries across 10 contexts; they are measured and withheld (not published, not scored). Contexts: core, docs, example, explorer, hotel, libsql, memory-store, projection-pg, propeller, test-domain.
D24 · Comment Value
0 of 143 judged comments only repeat the code they sit on (0.0 %).
D26 · Project Cohesion
0 of 17 build units (npm) flagged as possibly oversized/incoherent.
D27 · Navigability
52 % of calls cross a namespace and 3 % go through an interface, but 59 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
14 finding(s): 0 critical, 12 high, 2 medium, 0 low. 8 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `packages/core/src/lib/Uuid.ts` (line 31), `packages/libsql/src/lib/Token.ts` (line 6), `packages/message-db/message-db/src/lib/Token.ts` (line 6) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 8 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (8 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
77 finding(s): 7 critical, 43 high, 19 medium, 8 low.
What to do
- Resolve the 42 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (39), REDACTED (3). — One of this dimension's main actionable groups (42 issue-level).
- Resolve the 7 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7). — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
2 finding(s): 0 critical, 1 high, 1 medium, 0 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 41 of the 100 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 1 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 9 of 18 project(s) that lack one — worth up to 1 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging call was found in the 116 JavaScript/TypeScript production file(s) this check read across 19 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Adopt pino (or winston) and log at meaningful points in the services you run.
- Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 3785 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:16
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- 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
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P8 · Schema migrations
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.
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 5 duplicated blocks under packages/ have copies in at least two of the sibling directories dynamo-store, libsql, message-db — 3 of them are reported below, and 2 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 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/libsql/src/lib/Category.ts:31
- packages/libsql/src/lib/Category.ts:31 · packages/message-db/message-db/src/lib/Category.ts:34 — the two spans are one implementation copied and then locally edited — 1344 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/libsql/src/lib/Category.ts:31
- apps/hotel/src/domain/GroupCheckout.ts:22 · apps/hotel/src/domain/GuestStay.ts:24 — the two spans are one implementation copied and then locally edited — 697 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. — apps/hotel/src/domain/GroupCheckout.ts:22
- packages/libsql/src/lib/Read.ts:12 · packages/message-db/message-db/src/lib/Read.ts:12 — the two spans are one implementation copied and then locally edited — 485 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/libsql/src/lib/Read.ts:12
- packages/explorer/app/components/bar-chart.ts:55 · packages/explorer/app/components/stream-plot.ts:47 — the two spans are one implementation copied and then locally edited — 379 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/explorer/app/components/bar-chart.ts:55
- packages/explorer/app/pages/category.ts:46 · packages/explorer/app/pages/main.ts:62 — 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/explorer/app/pages/category.ts:46
- packages/projection-pg/src/projection.ts:47 · packages/projection-pg/src/projection.ts:81 — 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/projection-pg/src/projection.ts:47
- packages/dynamo-store/dynamo-store/src/DynamoStore.ts:616 · packages/dynamo-store/dynamo-store/src/DynamoStore.ts:642 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/dynamo-store/dynamo-store/src/DynamoStore.ts:616
- packages/core/src/lib/Codec.ts:59 · packages/core/src/lib/Codec.ts:73 — the two spans are one implementation copied and then locally edited — 70 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/src/lib/Codec.ts:59
- packages/message-db/message-db/src/lib/MessageDbClient.ts:16 · packages/message-db/message-db/src/lib/MessageDbClient.ts:56 — all 2 copies are in the same file, and the CITED SPAN is inside a TYPE DECLARATION, not executable code. There is no function to extract and no call site to call one from, so do not read this as an extract-a-helper row: the collapse a type offers is a generic — name the shape once, parameterised over the part that varies, and have each copy instantiate it. First check what actually differs between the copies: where they are a MATRIX of cases (one entry per input, differing precisely in the case each one pins), the repetition IS the enumeration and collapsing it would delete cases rather than de-duplicate anything — leave those alone. Reported because the copies that are not a matrix drift apart the first time only one of them is edited. — packages/message-db/message-db/src/lib/MessageDbClient.ts:16
- packages/core/src/lib/Internal.ts:3 · packages/core/src/lib/Internal.ts:14 — the two spans are one implementation copied and then locally edited — 89 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/src/lib/Internal.ts:3
- packages/core/src/lib/Decider.ts:267 · packages/core/src/lib/Decider.ts:288 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/core/src/lib/Decider.ts:267
- packages/core/src/lib/Decider.ts:305 · packages/core/src/lib/Decider.ts:326 — 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/src/lib/Decider.ts:305
- packages/libsql/src/lib/Category.ts:296 · packages/libsql/src/lib/Category.ts:318 — 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/libsql/src/lib/Category.ts:296
- packages/dynamo-store/indexer/src/AppendsIndex.ts:86 · packages/dynamo-store/indexer/src/AppendsIndex.ts:131 — 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/dynamo-store/indexer/src/AppendsIndex.ts:86
- packages/libsql/src/lib/Category.ts:135 · packages/libsql/src/lib/Category.ts:160 — 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/libsql/src/lib/Category.ts:135
- packages/libsql/src/lib/Token.ts:6 · packages/message-db/message-db/src/lib/Token.ts:6 — 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/libsql/src/lib/Token.ts:6
- packages/memory-store/src/index.ts:74 · packages/memory-store/src/index.ts:140 — 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/memory-store/src/index.ts:74
- apps/hotel/src/domain/GuestStay.ts:91 · apps/hotel/src/domain/GuestStay.ts:99 — 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. — apps/hotel/src/domain/GuestStay.ts:91
- packages/dynamo-store/dynamo-store/src/DynamoStore.ts:82 · packages/dynamo-store/dynamo-store/src/DynamoStore.ts:138 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/dynamo-store/dynamo-store/src/DynamoStore.ts:82
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
- concat has cyclomatic complexity 21 and cognitive complexity 9; 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/projection-pg/src/collapse.ts:5
- load has cyclomatic complexity 19 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/dynamo-store/dynamo-store/src/DynamoStore.ts:1023
- (anonymous) has cyclomatic complexity 14 and cognitive complexity 37; 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/dynamo-store/lambda/src/Handler.ts:12
- writeMessages has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/message-db/message-db/src/lib/MessageDbClient.ts:40
- scan has cyclomatic complexity 11 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. — packages/dynamo-store/dynamo-store/src/DynamoStore.ts:912
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
- packages/dynamo-store/dynamo-store/src/DynamoStore.ts has 1494 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/dynamo-store/dynamo-store/src/DynamoStore.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. (×26) — packages/explorer/bin/index.js:1, packages/explorer/app/pages/stream.ts:1, packages/explorer/app/components/bar-chart.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
R7 · Dead Code
- 3 file(s) (~53 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.
- 17 file(s) (~1313 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. — apps/hotel
- Unreachable from the 16 application, 5 tooling and 29 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (16 application, 5 tooling, 29 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — packages/dynamo-store/lambda/src/local.ts
- Nothing imports this binding — it is safe to review for removal. — packages/message-db/message-db/src/lib/Token.ts:12
- 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. — packages/propeller/src/FeedSource.mts:51
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 REDACTED 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.
- Declared in REDACTED 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
S1 · Web-Security Posture
- MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. — packages/explorer/bin/index.js:204
- `https://unpkg.com/@alenaksu/json-viewer@2.0.0/dist/json-viewer.bundle.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. — packages/explorer/index.html:9
What to do
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X1 · Async correctness
- The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it. — packages/propeller/src/Stats.ts:115
What to do
- `async` Promise executor
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
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
- `.catch((err) => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — packages/propeller/src/StreamsSink.mts:354
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- ~4.0 `!` null assertions per 1k TypeScript source lines — 38 assertion(s) across the 9518 source line(s) of the 90 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/explorer/app/components/bar-chart.ts (10), packages/explorer/app/components/stream-plot.ts (9), packages/dynamo-store/lambda/src/Handler.ts (6). 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 | 81% | Strong | Solid. |
| Architecture | 98% | Exemplary | Strongest area. |
| Maturity | 63% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 28% | Weak — gated by P2, P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 63% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 89% | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 2 observation(s) recorded · Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- X10 Duplicated predicate — 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/explorer/bin/index.js:4) 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/explorer/bin/index.js:4) 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/explorer/bin/index.js:4) 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 — 47 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
- AC7 A11y enforcement — Frontend below the scale floor (9 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run 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: "• Running dev in 18 packages / • Remote caching disabled / No tasks were executed as part of this run. / Tasks: 0 successful, 0 total / Cached: 0 cached, 0 total / Time: 61ms" 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/explorer/bin/index.js:4) 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 — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 3 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D4 Code Duplication — This repository's production source (.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.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (a Domain/Aggregates/ValueObjects layer)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 35 current-state document(s) make no claim of a kind M4 checks. 23 claim(s) of kinds M4 does not check were not checked (command argument 13, install 4, environment variable 5, package 1); M4 checks only links and versions and artefact counts.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: packages/explorer/bin/index.js:90 (express.Router())
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 65 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No assertions (empty test): It fails fast packages/propeller/src/FeedSource.test.mts:100
- Test suite executes none of its 10 test cases: packages/dynamo-store/dynamo-store/
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 110 finding(s)
- No test reaches this file packages/explorer/bin/index.js:1
- No test reaches this file packages/explorer/app/pages/stream.ts:1
- No test reaches this file packages/explorer/app/components/bar-chart.ts:1
- No test reaches this file packages/explorer/app/components/stream-plot.ts:1
- No test reaches this file packages/dynamo-store/cli/bin/index.js:1
- No test reaches this file packages/explorer/app/components/correlation-chart.ts:1
- No test reaches this file packages/explorer/app/pages/main.ts:1
- No test reaches this file packages/dynamo-store/lambda/src/Handler.ts:1
- No test reaches this file packages/explorer/app/pages/correlation.ts:1
- No test reaches this file packages/explorer/app/pages/category.ts:1
- No test reaches this file packages/dynamo-store/cli/src/render.js:1
- No test reaches this file packages/dynamo-store/lambda/src/local.ts:1
- No test reaches this file packages/dynamo-store/cdk/lib/table.ts:1
- No test reaches this file packages/explorer/app/layout/navbar.ts:1
- No test reaches this file packages/explorer/app/components/tooltip.ts:1
- No test reaches this file packages/dynamo-store/cdk/lib/indexer-lambda.ts:1
- No test reaches this file packages/explorer/app/data-access/data-access.ts:1
- No test reaches this file packages/dynamo-store/lambda/src/index.ts:1
- No test reaches this file apps/hotel/src/entrypoints/tracing.ts:1
- No test reaches this file packages/dynamo-store/cdk/lib/index.ts:1
- No test reaches this file apps/hotel/infra/stack.ts:1
- No test reaches this file packages/explorer/app/components/table.ts:1
- No test reaches this file apps/hotel/src/entrypoints/main.ts:1
- No test reaches this file packages/explorer/app/app.ts:1
- No test reaches this file packages/explorer/app/components/link.ts:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Deprecated: @opentelemetry/sdk-trace-base REDACTED:31
- Deprecated: @opentelemetry/sdk-trace-node REDACTED:32
- Deprecated: @opentelemetry/sdk-trace-base packages/dynamo-store/dynamo-store/package.json:16
- Deprecated: @opentelemetry/sdk-trace-node packages/dynamo-store/dynamo-store/package.json:17
- Deprecated: @opentelemetry/sdk-trace-base packages/libsql/package.json:20
- Deprecated: @opentelemetry/sdk-trace-node packages/libsql/package.json:21
- Deprecated: @opentelemetry/sdk-trace-base packages/message-db/message-db/package.json:19
- Deprecated: @opentelemetry/sdk-trace-node packages/message-db/message-db/package.json:20
- No assertions: Pay before apps/hotel/test/ReactorIntegration.test.ts:125
- No assertions: Pay after apps/hotel/test/ReactorIntegration.test.ts:126
- No assertions: Pay before apps/hotel/test/ReactorIntegration.test.ts:130
- No assertions: Pay after apps/hotel/test/ReactorIntegration.test.ts:131
- No assertions: Deleting a payer apps/example/test/read-models/PayerReadModel.test.ts:47
- No assertions: (unnamed test) apps/example/test/domain/scenario.ts:31
- Duplicated block (8 lines × 2 locations) packages/dynamo-store/indexer/src/AppendsIndex.ts:86
- Duplicated block (8 lines × 2 locations) packages/libsql/src/lib/Category.ts:135
- Duplicated block (8 lines × 2 locations) packages/libsql/src/lib/Token.ts:6
- Duplicated block (8 lines × 2 locations) packages/memory-store/src/index.ts:74
- Low coverage: packages/core/src/lib/Category.ts packages/core/src/lib/Category.ts:1
- Low coverage: packages/core/src/lib/Decider.ts packages/core/src/lib/Decider.ts:1
- Low coverage: packages/core/src/lib/Internal.ts packages/core/src/lib/Internal.ts:1
- REDACTED
- REDACTED
- Off the main sequence: @equinox-js/projection-pg
- Off the main sequence: @equinox-js/dynamo-store
- Workspace package's tests never run by CI apps/example/package.json:9
- Workspace package's tests never run by CI REDACTED:8
- Duplicated block (9 lines × 2 locations) packages/core/src/lib/Decider.ts:305
- Duplicated block (9 lines × 2 locations) packages/libsql/src/lib/Category.ts:296
- Duplicated block (7 lines × 2 locations) apps/hotel/src/domain/GuestStay.ts:91
- Duplicated block (7 lines × 2 locations) packages/dynamo-store/dynamo-store/src/DynamoStore.ts:82
- collapse.concat (cyclomatic 21) packages/projection-pg/src/collapse.ts:5
- Handler.parse (cognitive 31) packages/dynamo-store/lambda/src/Handler.ts:12
- FileTooLong: src/DynamoStore.ts packages/dynamo-store/dynamo-store/src/DynamoStore.ts
- REDACTED
- REDACTED
- REDACTED
- No structured logging
- No DR/backup evidence
- Duplication concentrated across 3 sibling directories (5 clone groups) packages/libsql/src/lib/Category.ts:31
- Duplicated block with local edits (168 matched lines × 2 locations) packages/libsql/src/lib/Category.ts:31
- Duplicated block with local edits (90 matched lines × 2 locations) apps/hotel/src/domain/GroupCheckout.ts:22
- Duplicated block with local edits (69 matched lines × 2 locations) packages/libsql/src/lib/Read.ts:12
- Duplicated block with local edits (60 matched lines × 2 locations) packages/explorer/app/components/bar-chart.ts:55
- Duplicated block (16 lines × 2 locations) packages/explorer/app/pages/category.ts:46
- Duplicated block (15 lines × 2 locations) packages/projection-pg/src/projection.ts:47
- Duplicated block (13 lines × 2 locations) packages/dynamo-store/dynamo-store/src/DynamoStore.ts:616
- Duplicated block with local edits (12 matched lines × 2 locations) packages/core/src/lib/Codec.ts:59
- Duplicated block (12 lines × 2 locations) packages/message-db/message-db/src/lib/MessageDbClient.ts:16
- Duplicated block with local edits (11 matched lines × 2 locations) packages/core/src/lib/Internal.ts:3
- Duplicated block (10 lines × 2 locations) packages/core/src/lib/Decider.ts:267
- Complex function concat (cyclomatic 21, cognitive 9) packages/projection-pg/src/collapse.ts:5
- Complex function load (cyclomatic 19, cognitive 19) packages/dynamo-store/dynamo-store/src/DynamoStore.ts:1023
- Complex function (anonymous) (cyclomatic 14, cognitive 37) packages/dynamo-store/lambda/src/Handler.ts:12
- Complex function writeMessages (cyclomatic 12, cognitive 13) packages/message-db/message-db/src/lib/MessageDbClient.ts:40
- Complex function scan (cyclomatic 11, cognitive 15) packages/dynamo-store/dynamo-store/src/DynamoStore.ts:912
- packages/dynamo-store/dynamo-store/src/DynamoStore.ts: 1494 lines of code packages/dynamo-store/dynamo-store/src/DynamoStore.ts:1
- Dead file (~63 LoC) packages/dynamo-store/lambda/src/local.ts
- Unused dependency '@equinox-js/explorer'
- Unused dependency '@opentelemetry/sdk-trace-base'
- Unused dependency '@opentelemetry/sdk-trace-node'
- Weak hash algorithm packages/explorer/bin/index.js:204
- Third-party script without Subresource Integrity packages/explorer/index.html:9
- `async` Promise executor packages/propeller/src/Stats.ts:115
- Swallowed exception (empty catch) packages/propeller/src/StreamsSink.mts:354
Minor — 27 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Documentation: no build, run or usage example packages/dynamo-store/dynamo-store/README.md:1
- Documentation: no build, run or usage example packages/dynamo-store/indexer/README.md:1
- Documentation: no build, run or usage example packages/projection-pg/README.md:1
- Outdated (npm): commander packages/dynamo-store/cli/package.json:18
- No ADRs found
- Scattered collaborators
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:6
- No dependency-update automation REDACTED:16
- No rollback/health safety
- No changelog
- Unused export 'maxIndex' packages/message-db/message-db/src/lib/Token.ts:12
- Unused private field 'async' packages/propeller/src/FeedSource.mts:51
- Duplicated predicate packages/libsql/src/lib/Read.ts:48
- Null assertions (`!`) reduce the strict null checking score
Minor — 33 finding(s)
- Outdated (npm): @algolia/client-search
- Outdated (npm): @aws-sdk/client-dynamodb
- Outdated (npm): @aws-sdk/client-dynamodb-streams
- Outdated (npm): @docusaurus/core
- Outdated (npm): @docusaurus/preset-classic
- Outdated (npm): @js-joda/core
- Outdated (npm): @libsql/client
- Outdated (npm): @opentelemetry/api
- Outdated (npm): @opentelemetry/instrumentation-express
- Outdated (npm): @opentelemetry/instrumentation-http
- Outdated (npm): @opentelemetry/instrumentation-pg
- Outdated (npm): @opentelemetry/sdk-node
- Outdated (npm): @opentelemetry/sdk-trace-base
- Outdated (npm): @opentelemetry/sdk-trace-node
- Outdated (npm): clsx
- Outdated (npm): cors
- Outdated (npm): d3
- Outdated (npm): date-fns
- Outdated (npm): esbuild
- Outdated (npm): express
- Outdated (npm): get-port
- Outdated (npm): immer
- Outdated (npm): immutable
- Outdated (npm): pg
- Outdated (npm): ramda
- core: 1 contract type(s) expose producer-owned ids/enums
- doc comments repeat the names packages/core/src/lib/Tags.ts:5
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-03f93665e52a41e7a3bdd9b17ca6f51e/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-03f93665e52a41e7a3bdd9b17ca6f51e/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 . | 14 | 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 | 77 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 2 | 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 3 file(s) — `packages/core/src/lib/Uuid.ts`, `packages/libsql/src/lib/Token.ts`, `packages/message-db/message-db/src/lib/Token.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |