Executive summary
kurrent-io/KurrentDB-Client-NodeJS 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 it has packages with a known security hole. It scores 59 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 56, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step for the work it takes is fixing the seven comments that repeat the code, or contradict it, worth about 2 points. Recording design decisions comes next, worth about 3 points.
Thirty-six known security holes in the packages the code depends on can be used by attackers. Thirteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and eight secrets can leak from the build pipeline. Updating the vulnerable packages, pinning each tool to an exact version and limiting each secret to its own step would close these risks. Giving the pull-request workflow read-only access would fix the pipeline that outsiders can trigger with write access, and the password or key in the code's history needs replacing, with the old one switched off. The loop of files that import each other needs breaking.
The product code is 9,963 lines, about €26,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 15 findings
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 45, cognitive 28) packages/db-client/src/utils/CommandError.ts
- Large Files · packages/db-client/src/utils/CommandError.ts: 661 lines of code packages/db-client/src/utils/CommandError.ts
- Cancellation propagation · Async function without AbortSignal: makeRequest packages/db-client/src/Client/http.ts
Fixed since the last survey: 19 findings
- Code Coverage · Coverage not measured — JavaScript/TypeScript suite
- Churn × Complexity Hotspots · Hotspot: packages/db-client/src/streams/appendToStream/batchAppend.ts packages/db-client/src/streams/appendToStream/batchAppend.ts
- Boundary Type-Coupling · Cross-context type Credentials (db-client → opentelemetry) packages/opentelemetry/src/utils.ts
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Supply-chain Provenance & Signing · REDACTED REDACTED
- Supply-chain Provenance & Signing · REDACTED REDACTED
- Code Duplication · Duplicated block (7 lines × 2 locations) packages/db-client/src/persistentSubscription/utils/PersistentSubscriptionImpl.ts
- Code Duplication · Duplicated block (7 lines × 2 locations) packages/db-client/src/projections/getProjectionStatus.ts
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 43, cognitive 24) packages/db-client/src/utils/CommandError.ts
- Large Files · packages/db-client/src/utils/CommandError.ts: 647 lines of code packages/db-client/src/utils/CommandError.ts
- Documentation (README) · README may be stale
Rebuild cost: about €26,000 · Estimate
| Cost to rebuild | €8,700 to €44,000, for 144 to 458 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 59. 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: 9,963 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 Client.ServerFeatures | 2 persistentSubscription.deletePersistentSubscriptionToAll | 3 persistentSubscription.deletePersistentSubscriptionToStream | 4 persistentSubscription.listAllPersistentSubscriptions | 5 persistentSubscription.listPersistentSubscriptionsToAll | 6 persistentSubscription.listPersistentSubscriptionsToStream | 7 persistentSubscription.replayParkedMessagesToAll | 8 persistentSubscription.replayParkedMessagesToStream | 9 persistentSubscription.restartPersistentSubscriptionSubsystem | 10 persistentSubscription.subscribeToPersistentSubscriptionToStream | 11 persistentSubscription.utils.persistentSubscriptionSettings | 12 types | 13 types.events | 14 Client.discovery | 15 Client.http | 16 Client.parseConnectionString | 17 persistentSubscription.createPersistentSubscriptionToAll | 18 persistentSubscription.createPersistentSubscriptionToStream | 19 persistentSubscription.subscribeToPersistentSubscriptionToAll | 20 persistentSubscription.updatePersistentSubscriptionToAll | 21 persistentSubscription.updatePersistentSubscriptionToStream | 22 persistentSubscription.utils.mapPersistentSubscriptionInfo | 23 projections.createProjection | 24 projections.getProjectionStatus | 25 streams.deleteStream | 26 streams.readAll | 27 streams.readStream | 28 streams.setStreamMetadata | 29 streams.subscribeToAll | 30 streams.subscribeToStream | 31 streams.tombstoneStream | 32 utils | 33 Client | 34 persistentSubscription.getPersistentSubscriptionToAllInfo | 35 persistentSubscription.getPersistentSubscriptionToStreamInfo | 36 persistentSubscription.utils | 37 persistentSubscription | 38 projections | 39 streams.appendToStream | 40 streams |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Client.ServerFeatures | ||||||||||||||||||||||||||||||||||||||||
| 2 persistentSubscription.deletePersistentSubscriptionToAll | ||||||||||||||||||||||||||||||||||||||||
| 3 persistentSubscription.deletePersistentSubscriptionToStream | ||||||||||||||||||||||||||||||||||||||||
| 4 persistentSubscription.listAllPersistentSubscriptions | ||||||||||||||||||||||||||||||||||||||||
| 5 persistentSubscription.listPersistentSubscriptionsToAll | ||||||||||||||||||||||||||||||||||||||||
| 6 persistentSubscription.listPersistentSubscriptionsToStream | ||||||||||||||||||||||||||||||||||||||||
| 7 persistentSubscription.replayParkedMessagesToAll | ||||||||||||||||||||||||||||||||||||||||
| 8 persistentSubscription.replayParkedMessagesToStream | ||||||||||||||||||||||||||||||||||||||||
| 9 persistentSubscription.restartPersistentSubscriptionSubsystem | ||||||||||||||||||||||||||||||||||||||||
| 10 persistentSubscription.subscribeToPersistentSubscriptionToStream | ||||||||||||||||||||||||||||||||||||||||
| 11 persistentSubscription.utils.persistentSubscriptionSettings | ||||||||||||||||||||||||||||||||||||||||
| 12 types | ||||||||||||||||||||||||||||||||||||||||
| 13 types.events | ||||||||||||||||||||||||||||||||||||||||
| 14 Client.discovery | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 Client.http | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 Client.parseConnectionString | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 persistentSubscription.createPersistentSubscriptionToAll | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 persistentSubscription.createPersistentSubscriptionToStream | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 persistentSubscription.subscribeToPersistentSubscriptionToAll | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 persistentSubscription.updatePersistentSubscriptionToAll | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 persistentSubscription.updatePersistentSubscriptionToStream | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 persistentSubscription.utils.mapPersistentSubscriptionInfo | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 projections.createProjection | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 projections.getProjectionStatus | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 streams.deleteStream | 2 | |||||||||||||||||||||||||||||||||||||||
| 26 streams.readAll | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 streams.readStream | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 streams.setStreamMetadata | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 streams.subscribeToAll | 2 | |||||||||||||||||||||||||||||||||||||||
| 30 streams.subscribeToStream | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 streams.tombstoneStream | 2 | |||||||||||||||||||||||||||||||||||||||
| 32 utils | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 Client | 1 | 9 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 34 persistentSubscription.getPersistentSubscriptionToAllInfo | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 persistentSubscription.getPersistentSubscriptionToStreamInfo | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 persistentSubscription.utils | 5 | 9 | ||||||||||||||||||||||||||||||||||||||
| 37 persistentSubscription | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 4 | 3 | 1 | 1 | 1 | 2 | 16 | 1 | 1 | ||||||||||||||||||||||
| 38 projections | 1 | 1 | 1 | 11 | ||||||||||||||||||||||||||||||||||||
| 39 streams.appendToStream | 6 | 4 | ||||||||||||||||||||||||||||||||||||||
| 40 streams | 5 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 9 | 1 |
14→12 Client.discovery uses types✕
- Connections
- 1 pair of types, where a type in Client.discovery uses a type in types.
- The types involved
packages.db-client.src.Client.discovery.MemberInfo→packages.db-client.src.types.EndPoint
- Direction
- Client.discovery uses types, so a change to types can break Client.discovery, while a change to Client.discovery can't break types.
- Position
- Below the diagonal: Client.discovery uses a module listed above it, which is the healthy direction.
15→33 Client.http uses Client part of a loop✕
- Connections
- 2 pairs of types, where a type in Client.http uses a type in Client.
- The types involved
packages.db-client.src.Client.http.HTTP→packages.db-client.src.Client.ChannelCredentialOptionspackages.db-client.src.Client.http.HTTP→packages.db-client.src.Client.Client
- Direction
- Client.http uses Client, so a change to Client can break Client.http, while a change to Client.http can't break Client.
- 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.
16→12 Client.parseConnectionString uses types✕
- Connections
- 2 pairs of types, where a type in Client.parseConnectionString uses a type in types.
- The types involved
packages.db-client.src.Client.parseConnectionString.ConnectionOptions→packages.db-client.src.types.BasicCredentialspackages.db-client.src.Client.parseConnectionString.QueryOptions→packages.db-client.src.types.NodePreference
- Direction
- Client.parseConnectionString uses types, so a change to types can break Client.parseConnectionString, while a change to Client.parseConnectionString can't break types.
- Position
- Below the diagonal: Client.parseConnectionString uses a module listed above it, which is the healthy direction.
17→11 persistentSubscription.createPersistentSubscriptionToAll uses persistentSubscription.utils.persistentSubscriptionSettings✕
- Connections
- 1 pair of types, where a type in persistentSubscription.createPersistentSubscriptionToAll uses a type in persistentSubscription.utils.persistentSubscriptionSettings.
- The types involved
packages.db-client.src.persistentSubscription.createPersistentSubscriptionToAll.Client→packages.db-client.src.persistentSubscription.utils.persistentSubscriptionSettings.PersistentSubscriptionToAllSettings
- Direction
- persistentSubscription.createPersistentSubscriptionToAll uses persistentSubscription.utils.persistentSubscriptionSettings, so a change to persistentSubscription.utils.persistentSubscriptionSettings can break persistentSubscription.createPersistentSubscriptionToAll, while a change to persistentSubscription.createPersistentSubscriptionToAll can't break persistentSubscription.utils.persistentSubscriptionSettings.
- Position
- Below the diagonal: persistentSubscription.createPersistentSubscriptionToAll uses a module listed above it, which is the healthy direction.
17→12 persistentSubscription.createPersistentSubscriptionToAll uses types✕
- Connections
- 1 pair of types, where a type in persistentSubscription.createPersistentSubscriptionToAll uses a type in types.
- The types involved
packages.db-client.src.persistentSubscription.createPersistentSubscriptionToAll.CreatePersistentSubscriptionToAllOptions→packages.db-client.src.types.Filter
- Direction
- persistentSubscription.createPersistentSubscriptionToAll uses types, so a change to types can break persistentSubscription.createPersistentSubscriptionToAll, while a change to persistentSubscription.createPersistentSubscriptionToAll can't break types.
- Position
- Below the diagonal: persistentSubscription.createPersistentSubscriptionToAll uses a module listed above it, which is the healthy direction.
18→11 persistentSubscription.createPersistentSubscriptionToStream uses persistentSubscription.utils.persistentSubscriptionSettings✕
- Connections
- 1 pair of types, where a type in persistentSubscription.createPersistentSubscriptionToStream uses a type in persistentSubscription.utils.persistentSubscriptionSettings.
- The types involved
packages.db-client.src.persistentSubscription.createPersistentSubscriptionToStream.Client→packages.db-client.src.persistentSubscription.utils.persistentSubscriptionSettings.PersistentSubscriptionToStreamSettings
- Direction
- persistentSubscription.createPersistentSubscriptionToStream uses persistentSubscription.utils.persistentSubscriptionSettings, so a change to persistentSubscription.utils.persistentSubscriptionSettings can break persistentSubscription.createPersistentSubscriptionToStream, while a change to persistentSubscription.createPersistentSubscriptionToStream can't break persistentSubscription.utils.persistentSubscriptionSettings.
- Position
- Below the diagonal: persistentSubscription.createPersistentSubscriptionToStream uses a module listed above it, which is the healthy direction.
18→12 persistentSubscription.createPersistentSubscriptionToStream uses types✕
- Connections
- 1 pair of types, where a type in persistentSubscription.createPersistentSubscriptionToStream uses a type in types.
- The types involved
packages.db-client.src.persistentSubscription.createPersistentSubscriptionToStream.Client→packages.db-client.src.types.BaseOptions
- Direction
- persistentSubscription.createPersistentSubscriptionToStream uses types, so a change to types can break persistentSubscription.createPersistentSubscriptionToStream, while a change to persistentSubscription.createPersistentSubscriptionToStream can't break types.
- Position
- Below the diagonal: persistentSubscription.createPersistentSubscriptionToStream uses a module listed above it, which is the healthy direction.
19→12 persistentSubscription.subscribeToPersistentSubscriptionToAll uses types✕
- Connections
- 1 pair of types, where a type in persistentSubscription.subscribeToPersistentSubscriptionToAll uses a type in types.
- The types involved
packages.db-client.src.persistentSubscription.subscribeToPersistentSubscriptionToAll.Client→packages.db-client.src.types.PersistentSubscriptionToAll
- Direction
- persistentSubscription.subscribeToPersistentSubscriptionToAll uses types, so a change to types can break persistentSubscription.subscribeToPersistentSubscriptionToAll, while a change to persistentSubscription.subscribeToPersistentSubscriptionToAll can't break types.
- Position
- Below the diagonal: persistentSubscription.subscribeToPersistentSubscriptionToAll uses a module listed above it, which is the healthy direction.
20→11 persistentSubscription.updatePersistentSubscriptionToAll uses persistentSubscription.utils.persistentSubscriptionSettings✕
- Connections
- 1 pair of types, where a type in persistentSubscription.updatePersistentSubscriptionToAll uses a type in persistentSubscription.utils.persistentSubscriptionSettings.
- The types involved
packages.db-client.src.persistentSubscription.updatePersistentSubscriptionToAll.Client→packages.db-client.src.persistentSubscription.utils.persistentSubscriptionSettings.PersistentSubscriptionToAllSettings
- Direction
- persistentSubscription.updatePersistentSubscriptionToAll uses persistentSubscription.utils.persistentSubscriptionSettings, so a change to persistentSubscription.utils.persistentSubscriptionSettings can break persistentSubscription.updatePersistentSubscriptionToAll, while a change to persistentSubscription.updatePersistentSubscriptionToAll can't break persistentSubscription.utils.persistentSubscriptionSettings.
- Position
- Below the diagonal: persistentSubscription.updatePersistentSubscriptionToAll uses a module listed above it, which is the healthy direction.
21→11 persistentSubscription.updatePersistentSubscriptionToStream uses persistentSubscription.utils.persistentSubscriptionSettings✕
- Connections
- 1 pair of types, where a type in persistentSubscription.updatePersistentSubscriptionToStream uses a type in persistentSubscription.utils.persistentSubscriptionSettings.
- The types involved
packages.db-client.src.persistentSubscription.updatePersistentSubscriptionToStream.Client→packages.db-client.src.persistentSubscription.utils.persistentSubscriptionSettings.PersistentSubscriptionToStreamSettings
- Direction
- persistentSubscription.updatePersistentSubscriptionToStream uses persistentSubscription.utils.persistentSubscriptionSettings, so a change to persistentSubscription.utils.persistentSubscriptionSettings can break persistentSubscription.updatePersistentSubscriptionToStream, while a change to persistentSubscription.updatePersistentSubscriptionToStream can't break persistentSubscription.utils.persistentSubscriptionSettings.
- Position
- Below the diagonal: persistentSubscription.updatePersistentSubscriptionToStream uses a module listed above it, which is the healthy direction.
21→12 persistentSubscription.updatePersistentSubscriptionToStream uses types✕
- Connections
- 1 pair of types, where a type in persistentSubscription.updatePersistentSubscriptionToStream uses a type in types.
- The types involved
packages.db-client.src.persistentSubscription.updatePersistentSubscriptionToStream.Client→packages.db-client.src.types.BaseOptions
- Direction
- persistentSubscription.updatePersistentSubscriptionToStream uses types, so a change to types can break persistentSubscription.updatePersistentSubscriptionToStream, while a change to persistentSubscription.updatePersistentSubscriptionToStream can't break types.
- Position
- Below the diagonal: persistentSubscription.updatePersistentSubscriptionToStream uses a module listed above it, which is the healthy direction.
22→11 persistentSubscription.utils.mapPersistentSubscriptionInfo uses persistentSubscription.utils.persistentSubscriptionSettings✕
- Connections
- 2 pairs of types, where a type in persistentSubscription.utils.mapPersistentSubscriptionInfo uses a type in persistentSubscription.utils.persistentSubscriptionSettings.
- The types involved
packages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo.PersistentSubscriptionToAllInfo→packages.db-client.src.persistentSubscription.utils.persistentSubscriptionSettings.PersistentSubscriptionToAllSettingspackages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo.PersistentSubscriptionToStreamInfo→packages.db-client.src.persistentSubscription.utils.persistentSubscriptionSettings.PersistentSubscriptionToStreamSettings
- Direction
- persistentSubscription.utils.mapPersistentSubscriptionInfo uses persistentSubscription.utils.persistentSubscriptionSettings, so a change to persistentSubscription.utils.persistentSubscriptionSettings can break persistentSubscription.utils.mapPersistentSubscriptionInfo, while a change to persistentSubscription.utils.mapPersistentSubscriptionInfo can't break persistentSubscription.utils.persistentSubscriptionSettings.
- Position
- Below the diagonal: persistentSubscription.utils.mapPersistentSubscriptionInfo uses a module listed above it, which is the healthy direction.
23→12 projections.createProjection uses types✕
- Connections
- 1 pair of types, where a type in projections.createProjection uses a type in types.
- The types involved
packages.db-client.src.projections.createProjection.CreateProjectionOptions→packages.db-client.src.types.ProjectionEngineVersion
- Direction
- projections.createProjection uses types, so a change to types can break projections.createProjection, while a change to projections.createProjection can't break types.
- Position
- Below the diagonal: projections.createProjection uses a module listed above it, which is the healthy direction.
24→12 projections.getProjectionStatus uses types✕
- Connections
- 1 pair of types, where a type in projections.getProjectionStatus uses a type in types.
- The types involved
packages.db-client.src.projections.getProjectionStatus.Client→packages.db-client.src.types.ProjectionDetails
- Direction
- projections.getProjectionStatus uses types, so a change to types can break projections.getProjectionStatus, while a change to projections.getProjectionStatus can't break types.
- Position
- Below the diagonal: projections.getProjectionStatus uses a module listed above it, which is the healthy direction.
25→12 streams.deleteStream uses types✕
- Connections
- 2 pairs of types, where a type in streams.deleteStream uses a type in types.
- The types involved
packages.db-client.src.streams.deleteStream.Client→packages.db-client.src.types.DeleteResultpackages.db-client.src.streams.deleteStream.DeleteStreamOptions→packages.db-client.src.types.StreamState
- Direction
- streams.deleteStream uses types, so a change to types can break streams.deleteStream, while a change to streams.deleteStream can't break types.
- Position
- Below the diagonal: streams.deleteStream uses a module listed above it, which is the healthy direction.
26→12 streams.readAll uses types✕
- Connections
- 3 pairs of types, where a type in streams.readAll uses a type in types.
- The types involved
packages.db-client.src.streams.readAll.ReadAllOptions→packages.db-client.src.types.Directionpackages.db-client.src.streams.readAll.ReadAllOptions→packages.db-client.src.types.Filterpackages.db-client.src.streams.readAll.ReadAllOptions→packages.db-client.src.types.ReadPosition
- Direction
- streams.readAll uses types, so a change to types can break streams.readAll, while a change to streams.readAll can't break types.
- Position
- Below the diagonal: streams.readAll uses a module listed above it, which is the healthy direction.
26→13 streams.readAll uses types.events✕
- Connections
- 1 pair of types, where a type in streams.readAll uses a type in types.events.
- The types involved
packages.db-client.src.streams.readAll.Client→packages.db-client.src.types.events.AllStreamResolvedEvent
- Direction
- streams.readAll uses types.events, so a change to types.events can break streams.readAll, while a change to streams.readAll can't break types.events.
- Position
- Below the diagonal: streams.readAll uses a module listed above it, which is the healthy direction.
27→12 streams.readStream uses types✕
- Connections
- 2 pairs of types, where a type in streams.readStream uses a type in types.
- The types involved
packages.db-client.src.streams.readStream.ReadStreamOptions→packages.db-client.src.types.Directionpackages.db-client.src.streams.readStream.ReadStreamOptions→packages.db-client.src.types.ReadRevision
- Direction
- streams.readStream uses types, so a change to types can break streams.readStream, while a change to streams.readStream can't break types.
- Position
- Below the diagonal: streams.readStream uses a module listed above it, which is the healthy direction.
27→13 streams.readStream uses types.events✕
- Connections
- 1 pair of types, where a type in streams.readStream uses a type in types.events.
- The types involved
packages.db-client.src.streams.readStream.Client→packages.db-client.src.types.events.ResolvedEvent
- Direction
- streams.readStream uses types.events, so a change to types.events can break streams.readStream, while a change to streams.readStream can't break types.events.
- Position
- Below the diagonal: streams.readStream uses a module listed above it, which is the healthy direction.
28→12 streams.setStreamMetadata uses types✕
- Connections
- 2 pairs of types, where a type in streams.setStreamMetadata uses a type in types.
- The types involved
packages.db-client.src.streams.setStreamMetadata.Client→packages.db-client.src.types.AppendResultpackages.db-client.src.streams.setStreamMetadata.SetStreamMetadataOptions→packages.db-client.src.types.AppendStreamState
- Direction
- streams.setStreamMetadata uses types, so a change to types can break streams.setStreamMetadata, while a change to streams.setStreamMetadata can't break types.
- Position
- Below the diagonal: streams.setStreamMetadata uses a module listed above it, which is the healthy direction.
28→13 streams.setStreamMetadata uses types.events✕
- Connections
- 1 pair of types, where a type in streams.setStreamMetadata uses a type in types.events.
- The types involved
packages.db-client.src.streams.setStreamMetadata.Client→packages.db-client.src.types.events.MetadataType
- Direction
- streams.setStreamMetadata uses types.events, so a change to types.events can break streams.setStreamMetadata, while a change to streams.setStreamMetadata can't break types.events.
- Position
- Below the diagonal: streams.setStreamMetadata uses a module listed above it, which is the healthy direction.
29→12 streams.subscribeToAll uses types✕
- Connections
- 2 pairs of types, where a type in streams.subscribeToAll uses a type in types.
- The types involved
packages.db-client.src.streams.subscribeToAll.SubscribeToAllOptions→packages.db-client.src.types.Filterpackages.db-client.src.streams.subscribeToAll.SubscribeToAllOptions→packages.db-client.src.types.ReadPosition
- Direction
- streams.subscribeToAll uses types, so a change to types can break streams.subscribeToAll, while a change to streams.subscribeToAll can't break types.
- Position
- Below the diagonal: streams.subscribeToAll uses a module listed above it, which is the healthy direction.
30→12 streams.subscribeToStream uses types✕
- Connections
- 1 pair of types, where a type in streams.subscribeToStream uses a type in types.
- The types involved
packages.db-client.src.streams.subscribeToStream.SubscribeToStreamOptions→packages.db-client.src.types.ReadRevision
- Direction
- streams.subscribeToStream uses types, so a change to types can break streams.subscribeToStream, while a change to streams.subscribeToStream can't break types.
- Position
- Below the diagonal: streams.subscribeToStream uses a module listed above it, which is the healthy direction.
31→12 streams.tombstoneStream uses types✕
- Connections
- 2 pairs of types, where a type in streams.tombstoneStream uses a type in types.
- The types involved
packages.db-client.src.streams.tombstoneStream.Client→packages.db-client.src.types.DeleteResultpackages.db-client.src.streams.tombstoneStream.TombstoneStreamOptions→packages.db-client.src.types.StreamState
- Direction
- streams.tombstoneStream uses types, so a change to types can break streams.tombstoneStream, while a change to streams.tombstoneStream can't break types.
- Position
- Below the diagonal: streams.tombstoneStream uses a module listed above it, which is the healthy direction.
32→12 utils uses types✕
- Connections
- 4 pairs of types, where a type in utils uses a type in types.
- The types involved
packages.db-client.src.utils.credentials→packages.db-client.src.types.Credentialspackages.db-client.src.utils.filter→packages.db-client.src.types.Filterpackages.db-client.src.utils.filter→packages.db-client.src.types.FilterOnpackages.db-client.src.utils.filter→packages.db-client.src.types.RegexFilter
- Direction
- utils uses types, so a change to types can break utils, while a change to utils can't break types.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
32→13 utils uses types.events✕
- Connections
- 1 pair of types, where a type in utils uses a type in types.events.
- The types involved
packages.db-client.src.utils.convertRustEvent→packages.db-client.src.types.events.ResolvedEvent
- Direction
- utils uses types.events, so a change to types.events can break utils, while a change to utils can't break types.events.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
33→1 Client uses Client.ServerFeatures✕
- Connections
- 1 pair of types, where a type in Client uses a type in Client.ServerFeatures.
- The types involved
packages.db-client.src.Client.Client→packages.db-client.src.Client.ServerFeatures.ServerFeatures
- Direction
- Client uses Client.ServerFeatures, so a change to Client.ServerFeatures can break Client, while a change to Client can't break Client.ServerFeatures.
- Position
- Below the diagonal: Client uses a module listed above it, which is the healthy direction.
33→12 Client uses types✕
- Connections
- 9 pairs of types, where a type in Client uses a type in types.
- The types involved
packages.db-client.src.Client.Client→packages.db-client.src.types.BaseOptionspackages.db-client.src.Client.Client→packages.db-client.src.types.BasicCredentialspackages.db-client.src.Client.Client→packages.db-client.src.types.Credentialspackages.db-client.src.Client.DNSClusterOptions→packages.db-client.src.types.EndPointpackages.db-client.src.Client.DiscoveryOptions→packages.db-client.src.types.NodePreferencepackages.db-client.src.Client.NextChannelSettings→packages.db-client.src.types.EndPointpackages.db-client.src.Client.discovery→packages.db-client.src.types.EndPointpackages.db-client.src.Client.discovery→packages.db-client.src.types.MemberInfopackages.db-client.src.Client.discovery→packages.db-client.src.types.NodePreference
- Direction
- Client uses types, so a change to types can break Client, while a change to Client can't break types.
- Position
- Below the diagonal: Client uses a module listed above it, which is the healthy direction.
33→15 Client uses Client.http✕
- Connections
- 1 pair of types, where a type in Client uses a type in Client.http.
- The types involved
packages.db-client.src.Client.Client→packages.db-client.src.Client.http.HTTP
- Direction
- Client uses Client.http, so a change to Client.http can break Client, while a change to Client can't break Client.http.
- Position
- Below the diagonal: Client uses a module listed above it, which is the healthy direction.
33→16 Client uses Client.parseConnectionString✕
- Connections
- 2 pairs of types, where a type in Client uses a type in Client.parseConnectionString.
- The types involved
packages.db-client.src.Client.parseConnectionString→packages.db-client.src.Client.parseConnectionString.ConnectionOptionspackages.db-client.src.Client.parseConnectionString→packages.db-client.src.Client.parseConnectionString.RawKeyPair
- Direction
- Client uses Client.parseConnectionString, so a change to Client.parseConnectionString can break Client, while a change to Client can't break Client.parseConnectionString.
- Position
- Below the diagonal: Client uses a module listed above it, which is the healthy direction.
34→22 persistentSubscription.getPersistentSubscriptionToAllInfo uses persistentSubscription.utils.mapPersistentSubscriptionInfo✕
- Connections
- 1 pair of types, where a type in persistentSubscription.getPersistentSubscriptionToAllInfo uses a type in persistentSubscription.utils.mapPersistentSubscriptionInfo.
- The types involved
packages.db-client.src.persistentSubscription.getPersistentSubscriptionToAllInfo.Client→packages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo.PersistentSubscriptionToAllInfo
- Direction
- persistentSubscription.getPersistentSubscriptionToAllInfo uses persistentSubscription.utils.mapPersistentSubscriptionInfo, so a change to persistentSubscription.utils.mapPersistentSubscriptionInfo can break persistentSubscription.getPersistentSubscriptionToAllInfo, while a change to persistentSubscription.getPersistentSubscriptionToAllInfo can't break persistentSubscription.utils.mapPersistentSubscriptionInfo.
- Position
- Below the diagonal: persistentSubscription.getPersistentSubscriptionToAllInfo uses a module listed above it, which is the healthy direction.
35→22 persistentSubscription.getPersistentSubscriptionToStreamInfo uses persistentSubscription.utils.mapPersistentSubscriptionInfo✕
- Connections
- 1 pair of types, where a type in persistentSubscription.getPersistentSubscriptionToStreamInfo uses a type in persistentSubscription.utils.mapPersistentSubscriptionInfo.
- The types involved
packages.db-client.src.persistentSubscription.getPersistentSubscriptionToStreamInfo.Client→packages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo.PersistentSubscriptionToStreamInfo
- Direction
- persistentSubscription.getPersistentSubscriptionToStreamInfo uses persistentSubscription.utils.mapPersistentSubscriptionInfo, so a change to persistentSubscription.utils.mapPersistentSubscriptionInfo can break persistentSubscription.getPersistentSubscriptionToStreamInfo, while a change to persistentSubscription.getPersistentSubscriptionToStreamInfo can't break persistentSubscription.utils.mapPersistentSubscriptionInfo.
- Position
- Below the diagonal: persistentSubscription.getPersistentSubscriptionToStreamInfo uses a module listed above it, which is the healthy direction.
36→11 persistentSubscription.utils uses persistentSubscription.utils.persistentSubscriptionSettings✕
- Connections
- 5 pairs of types, where a type in persistentSubscription.utils uses a type in persistentSubscription.utils.persistentSubscriptionSettings.
- The types involved
packages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo→packages.db-client.src.persistentSubscription.utils.persistentSubscriptionSettings.PersistentSubscriptionSettingsGenericpackages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo→packages.db-client.src.persistentSubscription.utils.persistentSubscriptionSettings.PersistentSubscriptionToAllSettingspackages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo→packages.db-client.src.persistentSubscription.utils.persistentSubscriptionSettings.PersistentSubscriptionToStreamSettingspackages.db-client.src.persistentSubscription.utils.persistentSubscriptionSettings→packages.db-client.src.persistentSubscription.utils.persistentSubscriptionSettings.PersistentSubscriptionToAllSettingspackages.db-client.src.persistentSubscription.utils.persistentSubscriptionSettings→packages.db-client.src.persistentSubscription.utils.persistentSubscriptionSettings.PersistentSubscriptionToStreamSettings
- Direction
- persistentSubscription.utils uses persistentSubscription.utils.persistentSubscriptionSettings, so a change to persistentSubscription.utils.persistentSubscriptionSettings can break persistentSubscription.utils, while a change to persistentSubscription.utils can't break persistentSubscription.utils.persistentSubscriptionSettings.
- Position
- Below the diagonal: persistentSubscription.utils uses a module listed above it, which is the healthy direction.
36→22 persistentSubscription.utils uses persistentSubscription.utils.mapPersistentSubscriptionInfo✕
- Connections
- 9 pairs of types, where a type in persistentSubscription.utils uses a type in persistentSubscription.utils.mapPersistentSubscriptionInfo.
- The types involved
packages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo→packages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo.HTTPConnectionInfopackages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo→packages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo.HTTPSubscriptionInfopackages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo→packages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo.PersistentSubscriptionConnectionInfopackages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo→packages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo.PersistentSubscriptionStatsBasepackages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo→packages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo.PersistentSubscriptionToAllInfopackages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo→packages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo.PersistentSubscriptionToAllStatspackages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo→packages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo.PersistentSubscriptionToEitherInfopackages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo→packages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo.PersistentSubscriptionToStreamInfopackages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo→packages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo.PersistentSubscriptionToStreamStats
- Direction
- persistentSubscription.utils uses persistentSubscription.utils.mapPersistentSubscriptionInfo, so a change to persistentSubscription.utils.mapPersistentSubscriptionInfo can break persistentSubscription.utils, while a change to persistentSubscription.utils can't break persistentSubscription.utils.mapPersistentSubscriptionInfo.
- Position
- Below the diagonal: persistentSubscription.utils uses a module listed above it, which is the healthy direction.
37→2 persistentSubscription uses persistentSubscription.deletePersistentSubscriptionToAll✕
- Connections
- 1 pair of types, where a type in persistentSubscription uses a type in persistentSubscription.deletePersistentSubscriptionToAll.
- The types involved
packages.db-client.src.persistentSubscription.deletePersistentSubscriptionToAll→packages.db-client.src.persistentSubscription.deletePersistentSubscriptionToAll.DeletePersistentSubscriptionToAllOptions
- Direction
- persistentSubscription uses persistentSubscription.deletePersistentSubscriptionToAll, so a change to persistentSubscription.deletePersistentSubscriptionToAll can break persistentSubscription, while a change to persistentSubscription can't break persistentSubscription.deletePersistentSubscriptionToAll.
- Position
- Below the diagonal: persistentSubscription uses a module listed above it, which is the healthy direction.
37→3 persistentSubscription uses persistentSubscription.deletePersistentSubscriptionToStream✕
- Connections
- 1 pair of types, where a type in persistentSubscription uses a type in persistentSubscription.deletePersistentSubscriptionToStream.
- The types involved
packages.db-client.src.persistentSubscription.deletePersistentSubscriptionToStream→packages.db-client.src.persistentSubscription.deletePersistentSubscriptionToStream.DeletePersistentSubscriptionToStreamOptions
- Direction
- persistentSubscription uses persistentSubscription.deletePersistentSubscriptionToStream, so a change to persistentSubscription.deletePersistentSubscriptionToStream can break persistentSubscription, while a change to persistentSubscription can't break persistentSubscription.deletePersistentSubscriptionToStream.
- Position
- Below the diagonal: persistentSubscription uses a module listed above it, which is the healthy direction.
37→4 persistentSubscription uses persistentSubscription.listAllPersistentSubscriptions✕
- Connections
- 1 pair of types, where a type in persistentSubscription uses a type in persistentSubscription.listAllPersistentSubscriptions.
- The types involved
packages.db-client.src.persistentSubscription.listAllPersistentSubscriptions→packages.db-client.src.persistentSubscription.listAllPersistentSubscriptions.ListPersistentSubscriptionsOptions
- Direction
- persistentSubscription uses persistentSubscription.listAllPersistentSubscriptions, so a change to persistentSubscription.listAllPersistentSubscriptions can break persistentSubscription, while a change to persistentSubscription can't break persistentSubscription.listAllPersistentSubscriptions.
- Position
- Below the diagonal: persistentSubscription uses a module listed above it, which is the healthy direction.
37→5 persistentSubscription uses persistentSubscription.listPersistentSubscriptionsToAll✕
- Connections
- 1 pair of types, where a type in persistentSubscription uses a type in persistentSubscription.listPersistentSubscriptionsToAll.
- The types involved
packages.db-client.src.persistentSubscription.listPersistentSubscriptionsToAll→packages.db-client.src.persistentSubscription.listPersistentSubscriptionsToAll.ListPersistentSubscriptionsToAllOptions
- Direction
- persistentSubscription uses persistentSubscription.listPersistentSubscriptionsToAll, so a change to persistentSubscription.listPersistentSubscriptionsToAll can break persistentSubscription, while a change to persistentSubscription can't break persistentSubscription.listPersistentSubscriptionsToAll.
- Position
- Below the diagonal: persistentSubscription uses a module listed above it, which is the healthy direction.
37→6 persistentSubscription uses persistentSubscription.listPersistentSubscriptionsToStream✕
- Connections
- 1 pair of types, where a type in persistentSubscription uses a type in persistentSubscription.listPersistentSubscriptionsToStream.
- The types involved
packages.db-client.src.persistentSubscription.listPersistentSubscriptionsToStream→packages.db-client.src.persistentSubscription.listPersistentSubscriptionsToStream.ListPersistentSubscriptionsToStreamOptions
- Direction
- persistentSubscription uses persistentSubscription.listPersistentSubscriptionsToStream, so a change to persistentSubscription.listPersistentSubscriptionsToStream can break persistentSubscription, while a change to persistentSubscription can't break persistentSubscription.listPersistentSubscriptionsToStream.
- Position
- Below the diagonal: persistentSubscription uses a module listed above it, which is the healthy direction.
37→7 persistentSubscription uses persistentSubscription.replayParkedMessagesToAll✕
- Connections
- 1 pair of types, where a type in persistentSubscription uses a type in persistentSubscription.replayParkedMessagesToAll.
- The types involved
packages.db-client.src.persistentSubscription.replayParkedMessagesToAll→packages.db-client.src.persistentSubscription.replayParkedMessagesToAll.ReplayParkedMessagesToAllOptions
- Direction
- persistentSubscription uses persistentSubscription.replayParkedMessagesToAll, so a change to persistentSubscription.replayParkedMessagesToAll can break persistentSubscription, while a change to persistentSubscription can't break persistentSubscription.replayParkedMessagesToAll.
- Position
- Below the diagonal: persistentSubscription uses a module listed above it, which is the healthy direction.
37→8 persistentSubscription uses persistentSubscription.replayParkedMessagesToStream✕
- Connections
- 1 pair of types, where a type in persistentSubscription uses a type in persistentSubscription.replayParkedMessagesToStream.
- The types involved
packages.db-client.src.persistentSubscription.replayParkedMessagesToStream→packages.db-client.src.persistentSubscription.replayParkedMessagesToStream.ReplayParkedMessagesToStreamOptions
- Direction
- persistentSubscription uses persistentSubscription.replayParkedMessagesToStream, so a change to persistentSubscription.replayParkedMessagesToStream can break persistentSubscription, while a change to persistentSubscription can't break persistentSubscription.replayParkedMessagesToStream.
- Position
- Below the diagonal: persistentSubscription uses a module listed above it, which is the healthy direction.
37→9 persistentSubscription uses persistentSubscription.restartPersistentSubscriptionSubsystem✕
- Connections
- 1 pair of types, where a type in persistentSubscription uses a type in persistentSubscription.restartPersistentSubscriptionSubsystem.
- The types involved
packages.db-client.src.persistentSubscription.restartPersistentSubscriptionSubsystem→packages.db-client.src.persistentSubscription.restartPersistentSubscriptionSubsystem.RestartPersistentSubscriptionSubsystemOptions
- Direction
- persistentSubscription uses persistentSubscription.restartPersistentSubscriptionSubsystem, so a change to persistentSubscription.restartPersistentSubscriptionSubsystem can break persistentSubscription, while a change to persistentSubscription can't break persistentSubscription.restartPersistentSubscriptionSubsystem.
- Position
- Below the diagonal: persistentSubscription uses a module listed above it, which is the healthy direction.
37→10 persistentSubscription uses persistentSubscription.subscribeToPersistentSubscriptionToStream✕
- Connections
- 1 pair of types, where a type in persistentSubscription uses a type in persistentSubscription.subscribeToPersistentSubscriptionToStream.
- The types involved
packages.db-client.src.persistentSubscription.subscribeToPersistentSubscriptionToStream→packages.db-client.src.persistentSubscription.subscribeToPersistentSubscriptionToStream.SubscribeToPersistentSubscriptionToStreamOptions
- Direction
- persistentSubscription uses persistentSubscription.subscribeToPersistentSubscriptionToStream, so a change to persistentSubscription.subscribeToPersistentSubscriptionToStream can break persistentSubscription, while a change to persistentSubscription can't break persistentSubscription.subscribeToPersistentSubscriptionToStream.
- Position
- Below the diagonal: persistentSubscription uses a module listed above it, which is the healthy direction.
37→11 persistentSubscription uses persistentSubscription.utils.persistentSubscriptionSettings✕
- Connections
- 4 pairs of types, where a type in persistentSubscription uses a type in persistentSubscription.utils.persistentSubscriptionSettings.
- The types involved
packages.db-client.src.persistentSubscription.createPersistentSubscriptionToAll→packages.db-client.src.persistentSubscription.utils.persistentSubscriptionSettings.PersistentSubscriptionToAllSettingspackages.db-client.src.persistentSubscription.createPersistentSubscriptionToStream→packages.db-client.src.persistentSubscription.utils.persistentSubscriptionSettings.PersistentSubscriptionToStreamSettingspackages.db-client.src.persistentSubscription.updatePersistentSubscriptionToAll→packages.db-client.src.persistentSubscription.utils.persistentSubscriptionSettings.PersistentSubscriptionToAllSettingspackages.db-client.src.persistentSubscription.updatePersistentSubscriptionToStream→packages.db-client.src.persistentSubscription.utils.persistentSubscriptionSettings.PersistentSubscriptionToStreamSettings
- Direction
- persistentSubscription uses persistentSubscription.utils.persistentSubscriptionSettings, so a change to persistentSubscription.utils.persistentSubscriptionSettings can break persistentSubscription, while a change to persistentSubscription can't break persistentSubscription.utils.persistentSubscriptionSettings.
- Position
- Below the diagonal: persistentSubscription uses a module listed above it, which is the healthy direction.
37→12 persistentSubscription uses types✕
- Connections
- 3 pairs of types, where a type in persistentSubscription uses a type in types.
- The types involved
packages.db-client.src.persistentSubscription.createPersistentSubscriptionToStream→packages.db-client.src.types.BaseOptionspackages.db-client.src.persistentSubscription.subscribeToPersistentSubscriptionToAll→packages.db-client.src.types.PersistentSubscriptionToAllpackages.db-client.src.persistentSubscription.updatePersistentSubscriptionToStream→packages.db-client.src.types.BaseOptions
- Direction
- persistentSubscription uses types, so a change to types can break persistentSubscription, while a change to persistentSubscription can't break types.
- Position
- Below the diagonal: persistentSubscription uses a module listed above it, which is the healthy direction.
37→17 persistentSubscription uses persistentSubscription.createPersistentSubscriptionToAll✕
- Connections
- 1 pair of types, where a type in persistentSubscription uses a type in persistentSubscription.createPersistentSubscriptionToAll.
- The types involved
packages.db-client.src.persistentSubscription.createPersistentSubscriptionToAll→packages.db-client.src.persistentSubscription.createPersistentSubscriptionToAll.CreatePersistentSubscriptionToAllOptions
- Direction
- persistentSubscription uses persistentSubscription.createPersistentSubscriptionToAll, so a change to persistentSubscription.createPersistentSubscriptionToAll can break persistentSubscription, while a change to persistentSubscription can't break persistentSubscription.createPersistentSubscriptionToAll.
- Position
- Below the diagonal: persistentSubscription uses a module listed above it, which is the healthy direction.
37→19 persistentSubscription uses persistentSubscription.subscribeToPersistentSubscriptionToAll✕
- Connections
- 1 pair of types, where a type in persistentSubscription uses a type in persistentSubscription.subscribeToPersistentSubscriptionToAll.
- The types involved
packages.db-client.src.persistentSubscription.subscribeToPersistentSubscriptionToAll→packages.db-client.src.persistentSubscription.subscribeToPersistentSubscriptionToAll.SubscribeToPersistentSubscriptionToAllOptions
- Direction
- persistentSubscription uses persistentSubscription.subscribeToPersistentSubscriptionToAll, so a change to persistentSubscription.subscribeToPersistentSubscriptionToAll can break persistentSubscription, while a change to persistentSubscription can't break persistentSubscription.subscribeToPersistentSubscriptionToAll.
- Position
- Below the diagonal: persistentSubscription uses a module listed above it, which is the healthy direction.
37→20 persistentSubscription uses persistentSubscription.updatePersistentSubscriptionToAll✕
- Connections
- 1 pair of types, where a type in persistentSubscription uses a type in persistentSubscription.updatePersistentSubscriptionToAll.
- The types involved
packages.db-client.src.persistentSubscription.updatePersistentSubscriptionToAll→packages.db-client.src.persistentSubscription.updatePersistentSubscriptionToAll.UpdatePersistentSubscriptionToAllOptions
- Direction
- persistentSubscription uses persistentSubscription.updatePersistentSubscriptionToAll, so a change to persistentSubscription.updatePersistentSubscriptionToAll can break persistentSubscription, while a change to persistentSubscription can't break persistentSubscription.updatePersistentSubscriptionToAll.
- Position
- Below the diagonal: persistentSubscription uses a module listed above it, which is the healthy direction.
37→22 persistentSubscription uses persistentSubscription.utils.mapPersistentSubscriptionInfo✕
- Connections
- 2 pairs of types, where a type in persistentSubscription uses a type in persistentSubscription.utils.mapPersistentSubscriptionInfo.
- The types involved
packages.db-client.src.persistentSubscription.getPersistentSubscriptionToAllInfo→packages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo.PersistentSubscriptionToAllInfopackages.db-client.src.persistentSubscription.getPersistentSubscriptionToStreamInfo→packages.db-client.src.persistentSubscription.utils.mapPersistentSubscriptionInfo.PersistentSubscriptionToStreamInfo
- Direction
- persistentSubscription uses persistentSubscription.utils.mapPersistentSubscriptionInfo, so a change to persistentSubscription.utils.mapPersistentSubscriptionInfo can break persistentSubscription, while a change to persistentSubscription can't break persistentSubscription.utils.mapPersistentSubscriptionInfo.
- Position
- Below the diagonal: persistentSubscription uses a module listed above it, which is the healthy direction.
37→33 persistentSubscription uses Client✕
- Connections
- 16 pairs of types, where a type in persistentSubscription uses a type in Client.
- The types involved
packages.db-client.src.persistentSubscription.createPersistentSubscriptionToAll→packages.db-client.src.Client.Clientpackages.db-client.src.persistentSubscription.createPersistentSubscriptionToStream→packages.db-client.src.Client.Clientpackages.db-client.src.persistentSubscription.deletePersistentSubscriptionToAll→packages.db-client.src.Client.Clientpackages.db-client.src.persistentSubscription.deletePersistentSubscriptionToStream→packages.db-client.src.Client.Clientpackages.db-client.src.persistentSubscription.getPersistentSubscriptionToAllInfo→packages.db-client.src.Client.Clientpackages.db-client.src.persistentSubscription.getPersistentSubscriptionToStreamInfo→packages.db-client.src.Client.Clientpackages.db-client.src.persistentSubscription.listAllPersistentSubscriptions→packages.db-client.src.Client.Clientpackages.db-client.src.persistentSubscription.listPersistentSubscriptionsToAll→packages.db-client.src.Client.Clientpackages.db-client.src.persistentSubscription.listPersistentSubscriptionsToStream→packages.db-client.src.Client.Clientpackages.db-client.src.persistentSubscription.replayParkedMessagesToAll→packages.db-client.src.Client.Clientpackages.db-client.src.persistentSubscription.replayParkedMessagesToStream→packages.db-client.src.Client.Clientpackages.db-client.src.persistentSubscription.restartPersistentSubscriptionSubsystem→packages.db-client.src.Client.Clientpackages.db-client.src.persistentSubscription.subscribeToPersistentSubscriptionToAll→packages.db-client.src.Client.Clientpackages.db-client.src.persistentSubscription.subscribeToPersistentSubscriptionToStream→packages.db-client.src.Client.Clientpackages.db-client.src.persistentSubscription.updatePersistentSubscriptionToAll→packages.db-client.src.Client.Clientpackages.db-client.src.persistentSubscription.updatePersistentSubscriptionToStream→packages.db-client.src.Client.Client
- Direction
- persistentSubscription uses Client, so a change to Client can break persistentSubscription, while a change to persistentSubscription can't break Client.
- Position
- Below the diagonal: persistentSubscription uses a module listed above it, which is the healthy direction.
37→34 persistentSubscription uses persistentSubscription.getPersistentSubscriptionToAllInfo✕
- Connections
- 1 pair of types, where a type in persistentSubscription uses a type in persistentSubscription.getPersistentSubscriptionToAllInfo.
- The types involved
packages.db-client.src.persistentSubscription.getPersistentSubscriptionToAllInfo→packages.db-client.src.persistentSubscription.getPersistentSubscriptionToAllInfo.GetPersistentSubscriptionToAllInfoOptions
- Direction
- persistentSubscription uses persistentSubscription.getPersistentSubscriptionToAllInfo, so a change to persistentSubscription.getPersistentSubscriptionToAllInfo can break persistentSubscription, while a change to persistentSubscription can't break persistentSubscription.getPersistentSubscriptionToAllInfo.
- Position
- Below the diagonal: persistentSubscription uses a module listed above it, which is the healthy direction.
37→35 persistentSubscription uses persistentSubscription.getPersistentSubscriptionToStreamInfo✕
- Connections
- 1 pair of types, where a type in persistentSubscription uses a type in persistentSubscription.getPersistentSubscriptionToStreamInfo.
- The types involved
packages.db-client.src.persistentSubscription.getPersistentSubscriptionToStreamInfo→packages.db-client.src.persistentSubscription.getPersistentSubscriptionToStreamInfo.GetPersistentSubscriptionToStreamInfoOptions
- Direction
- persistentSubscription uses persistentSubscription.getPersistentSubscriptionToStreamInfo, so a change to persistentSubscription.getPersistentSubscriptionToStreamInfo can break persistentSubscription, while a change to persistentSubscription can't break persistentSubscription.getPersistentSubscriptionToStreamInfo.
- Position
- Below the diagonal: persistentSubscription uses a module listed above it, which is the healthy direction.
38→12 projections uses types✕
- Connections
- 1 pair of types, where a type in projections uses a type in types.
- The types involved
packages.db-client.src.projections.getProjectionStatus→packages.db-client.src.types.ProjectionDetails
- Direction
- projections uses types, so a change to types can break projections, while a change to projections can't break types.
- Position
- Below the diagonal: projections uses a module listed above it, which is the healthy direction.
38→23 projections uses projections.createProjection✕
- Connections
- 1 pair of types, where a type in projections uses a type in projections.createProjection.
- The types involved
packages.db-client.src.projections.createProjection→packages.db-client.src.projections.createProjection.CreateProjectionOptions
- Direction
- projections uses projections.createProjection, so a change to projections.createProjection can break projections, while a change to projections can't break projections.createProjection.
- Position
- Below the diagonal: projections uses a module listed above it, which is the healthy direction.
38→24 projections uses projections.getProjectionStatus✕
- Connections
- 1 pair of types, where a type in projections uses a type in projections.getProjectionStatus.
- The types involved
packages.db-client.src.projections.getProjectionStatus→packages.db-client.src.projections.getProjectionStatus.GetProjectionStatusOptions
- Direction
- projections uses projections.getProjectionStatus, so a change to projections.getProjectionStatus can break projections, while a change to projections can't break projections.getProjectionStatus.
- Position
- Below the diagonal: projections uses a module listed above it, which is the healthy direction.
38→33 projections uses Client✕
- Connections
- 11 pairs of types, where a type in projections uses a type in Client.
- The types involved
packages.db-client.src.projections.createProjection→packages.db-client.src.Client.Clientpackages.db-client.src.projections.deleteProjection→packages.db-client.src.Client.Clientpackages.db-client.src.projections.disableProjection→packages.db-client.src.Client.Clientpackages.db-client.src.projections.enableProjection→packages.db-client.src.Client.Clientpackages.db-client.src.projections.getProjectionResult→packages.db-client.src.Client.Clientpackages.db-client.src.projections.getProjectionState→packages.db-client.src.Client.Clientpackages.db-client.src.projections.getProjectionStatus→packages.db-client.src.Client.Clientpackages.db-client.src.projections.listProjections→packages.db-client.src.Client.Clientpackages.db-client.src.projections.resetProjection→packages.db-client.src.Client.Clientpackages.db-client.src.projections.restartSubsystem→packages.db-client.src.Client.Clientpackages.db-client.src.projections.updateProjection→packages.db-client.src.Client.Client
- Direction
- projections uses Client, so a change to Client can break projections, while a change to projections can't break Client.
- Position
- Below the diagonal: projections uses a module listed above it, which is the healthy direction.
39→12 streams.appendToStream uses types✕
- Connections
- 6 pairs of types, where a type in streams.appendToStream uses a type in types.
- The types involved
packages.db-client.src.streams.appendToStream.AppendToStreamOptions→packages.db-client.src.types.AppendStreamStatepackages.db-client.src.streams.appendToStream.Client→packages.db-client.src.types.AppendRecordsResultpackages.db-client.src.streams.appendToStream.Client→packages.db-client.src.types.AppendResultpackages.db-client.src.streams.appendToStream.append→packages.db-client.src.types.AppendResultpackages.db-client.src.streams.appendToStream.appendRecords→packages.db-client.src.types.AppendRecordsResultpackages.db-client.src.streams.appendToStream.batchAppend→packages.db-client.src.types.AppendResult
- Direction
- streams.appendToStream uses types, so a change to types can break streams.appendToStream, while a change to streams.appendToStream can't break types.
- Position
- Below the diagonal: streams.appendToStream uses a module listed above it, which is the healthy direction.
39→33 streams.appendToStream uses Client✕
- Connections
- 4 pairs of types, where a type in streams.appendToStream uses a type in Client.
- The types involved
packages.db-client.src.streams.appendToStream.append→packages.db-client.src.Client.Clientpackages.db-client.src.streams.appendToStream.appendRecords→packages.db-client.src.Client.Clientpackages.db-client.src.streams.appendToStream.batchAppend→packages.db-client.src.Client.Clientpackages.db-client.src.streams.appendToStream.multiStreamAppend→packages.db-client.src.Client.Client
- Direction
- streams.appendToStream uses Client, so a change to Client can break streams.appendToStream, while a change to streams.appendToStream can't break Client.
- Position
- Below the diagonal: streams.appendToStream uses a module listed above it, which is the healthy direction.
40→12 streams uses types✕
- Connections
- 5 pairs of types, where a type in streams uses a type in types.
- The types involved
packages.db-client.src.streams.deleteStream→packages.db-client.src.types.DeleteResultpackages.db-client.src.streams.index→packages.db-client.src.types.AppendRecordsResultpackages.db-client.src.streams.index→packages.db-client.src.types.AppendResultpackages.db-client.src.streams.setStreamMetadata→packages.db-client.src.types.AppendResultpackages.db-client.src.streams.tombstoneStream→packages.db-client.src.types.DeleteResult
- Direction
- streams uses types, so a change to types can break streams, while a change to streams can't break types.
- Position
- Below the diagonal: streams uses a module listed above it, which is the healthy direction.
40→13 streams uses types.events✕
- Connections
- 3 pairs of types, where a type in streams uses a type in types.events.
- The types involved
packages.db-client.src.streams.readAll→packages.db-client.src.types.events.AllStreamResolvedEventpackages.db-client.src.streams.readStream→packages.db-client.src.types.events.ResolvedEventpackages.db-client.src.streams.setStreamMetadata→packages.db-client.src.types.events.MetadataType
- Direction
- streams uses types.events, so a change to types.events can break streams, while a change to streams can't break types.events.
- Position
- Below the diagonal: streams uses a module listed above it, which is the healthy direction.
40→25 streams uses streams.deleteStream✕
- Connections
- 1 pair of types, where a type in streams uses a type in streams.deleteStream.
- The types involved
packages.db-client.src.streams.deleteStream→packages.db-client.src.streams.deleteStream.DeleteStreamOptions
- Direction
- streams uses streams.deleteStream, so a change to streams.deleteStream can break streams, while a change to streams can't break streams.deleteStream.
- Position
- Below the diagonal: streams uses a module listed above it, which is the healthy direction.
40→26 streams uses streams.readAll✕
- Connections
- 1 pair of types, where a type in streams uses a type in streams.readAll.
- The types involved
packages.db-client.src.streams.readAll→packages.db-client.src.streams.readAll.ReadAllOptions
- Direction
- streams uses streams.readAll, so a change to streams.readAll can break streams, while a change to streams can't break streams.readAll.
- Position
- Below the diagonal: streams uses a module listed above it, which is the healthy direction.
40→27 streams uses streams.readStream✕
- Connections
- 1 pair of types, where a type in streams uses a type in streams.readStream.
- The types involved
packages.db-client.src.streams.readStream→packages.db-client.src.streams.readStream.ReadStreamOptions
- Direction
- streams uses streams.readStream, so a change to streams.readStream can break streams, while a change to streams can't break streams.readStream.
- Position
- Below the diagonal: streams uses a module listed above it, which is the healthy direction.
40→28 streams uses streams.setStreamMetadata✕
- Connections
- 1 pair of types, where a type in streams uses a type in streams.setStreamMetadata.
- The types involved
packages.db-client.src.streams.setStreamMetadata→packages.db-client.src.streams.setStreamMetadata.SetStreamMetadataOptions
- Direction
- streams uses streams.setStreamMetadata, so a change to streams.setStreamMetadata can break streams, while a change to streams can't break streams.setStreamMetadata.
- Position
- Below the diagonal: streams uses a module listed above it, which is the healthy direction.
40→29 streams uses streams.subscribeToAll✕
- Connections
- 1 pair of types, where a type in streams uses a type in streams.subscribeToAll.
- The types involved
packages.db-client.src.streams.subscribeToAll→packages.db-client.src.streams.subscribeToAll.SubscribeToAllOptions
- Direction
- streams uses streams.subscribeToAll, so a change to streams.subscribeToAll can break streams, while a change to streams can't break streams.subscribeToAll.
- Position
- Below the diagonal: streams uses a module listed above it, which is the healthy direction.
40→30 streams uses streams.subscribeToStream✕
- Connections
- 1 pair of types, where a type in streams uses a type in streams.subscribeToStream.
- The types involved
packages.db-client.src.streams.subscribeToStream→packages.db-client.src.streams.subscribeToStream.SubscribeToStreamOptions
- Direction
- streams uses streams.subscribeToStream, so a change to streams.subscribeToStream can break streams, while a change to streams can't break streams.subscribeToStream.
- Position
- Below the diagonal: streams uses a module listed above it, which is the healthy direction.
40→31 streams uses streams.tombstoneStream✕
- Connections
- 1 pair of types, where a type in streams uses a type in streams.tombstoneStream.
- The types involved
packages.db-client.src.streams.tombstoneStream→packages.db-client.src.streams.tombstoneStream.TombstoneStreamOptions
- Direction
- streams uses streams.tombstoneStream, so a change to streams.tombstoneStream can break streams, while a change to streams can't break streams.tombstoneStream.
- Position
- Below the diagonal: streams uses a module listed above it, which is the healthy direction.
40→33 streams uses Client✕
- Connections
- 9 pairs of types, where a type in streams uses a type in Client.
- The types involved
packages.db-client.src.streams.deleteStream→packages.db-client.src.Client.Clientpackages.db-client.src.streams.getStreamMetadata→packages.db-client.src.Client.Clientpackages.db-client.src.streams.index→packages.db-client.src.Client.Clientpackages.db-client.src.streams.readAll→packages.db-client.src.Client.Clientpackages.db-client.src.streams.readStream→packages.db-client.src.Client.Clientpackages.db-client.src.streams.setStreamMetadata→packages.db-client.src.Client.Clientpackages.db-client.src.streams.subscribeToAll→packages.db-client.src.Client.Clientpackages.db-client.src.streams.subscribeToStream→packages.db-client.src.Client.Clientpackages.db-client.src.streams.tombstoneStream→packages.db-client.src.Client.Client
- Direction
- streams uses Client, so a change to Client can break streams, while a change to streams can't break Client.
- Position
- Below the diagonal: streams uses a module listed above it, which is the healthy direction.
40→39 streams uses streams.appendToStream✕
- Connections
- 1 pair of types, where a type in streams uses a type in streams.appendToStream.
- The types involved
packages.db-client.src.streams.index→packages.db-client.src.streams.appendToStream.AppendToStreamOptions
- Direction
- streams uses streams.appendToStream, so a change to streams.appendToStream can break streams, while a change to streams can't break streams.appendToStream.
- Position
- Below the diagonal: streams 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 | 69 | High / Critical |
| A05:2025 — Injection | 23 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: 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; Stop accepting every TLS certificate: delete `rejectUnauthorized: false` / `NODE_TLS_REJECT_UNAUTHORIZED=0` so the chain, hostname and expiry are verified, and trust a self-signed or private server by passing its CA (`ca`, or `NODE_EXTRA_CA_CERTS`) — never by switching verification off; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 7 redundant comment finding(s) in Comment Value — start with typedEvents.test.ts (3), importCodePlugin.ts (2), createImportCodeBlockRule.ts. | +1.5 pts | Low | Comment Value |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +2.7 pts | Medium | Architecture documentation |
| Stop accepting every TLS certificate: delete `rejectUnauthorized: false` / `NODE_TLS_REJECT_UNAUTHORIZED=0` so the chain, hostname and expiry are verified, and trust a self-signed or private server by passing its CA (`ca`, or `NODE_EXTRA_CA_CERTS`) — never by switching verification off. | +2.6 pts | Medium | Web-Security Posture |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. | +1.2 pts | Low | Static Analysis (SAST) |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. | +1.2 pts | Low | Static Analysis (SAST) |
| 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. | +2.3 pts | Medium | Security & performance tooling |
| Resolve the 29 Orphaned file finding(s) in Knowledge Freshness — start with mapPersistentSubscriptionInfo.ts, parseConnectionString.ts, events.ts. | +2.2 pts | Medium | Knowledge Freshness |
| Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. | +1.1 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.2 | Mixed | Dependency Vulnerabilities: High vulnerability: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| packages/test/src/extra/dispose.test.ts | 6.0 | Mixed | Explicit Debt: TodoComment |
| packages/test/src/extra/write-after-end.test.ts | 6.0 | Mixed | Explicit Debt: TodoComment |
| packages/test/src/extra/typedEvents.test.ts | 6.9 | Mixed | Test Quality: No assertions: jsonEvent |
| packages/db-client/src/utils/CommandError.ts | 7.2 | Mixed | Cyclomatic Complexity: CommandError.convertToCommandError (cyclomatic 45) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High vulnerability: REDACTED |
| packages/db-client/src/Client/index.ts | 7.4 | Mixed | Cyclomatic Complexity: Client.connectionString (cyclomatic 19) |
| packages/db-client/src/streams/appendToStream/append.ts | 7.4 | Mixed | Cyclomatic Complexity: append.append (cyclomatic 19) |
| packages/db-client/src/streams/appendToStream/multiStreamAppend.ts | 7.8 | Mixed | Cyclomatic Complexity: multiStreamAppend.multiStreamAppend (cyclomatic 19) |
| packages/db-client/src/streams/appendToStream/appendRecords.ts | 7.8 | Mixed | Cyclomatic Complexity: appendRecords.appendRecords (cyclomatic 19) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 74 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 — 74 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, 297 of 330 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 — 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. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for packages/test/ could not reach the package registry on this run (➤ YN0001: │ RequestError: tunneling socket could not be established, statusCode=403), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for packages/test/ could not reach the package registry on this run (➤ YN0001: │ RequestError: tunneling socket could not be established, statusCode=403), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in packages/test/ was NOT MEASURED: the dependency install for packages/test/ could not reach the package registry on this run (➤ YN0001: │ RequestError: tunneling socket could not be established, statusCode=403), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- 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.
- 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these 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.
- D27 Navigability — 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- 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 (the repository): REDACTED has no "dev" script, so `npm run dev` could not start the app. Last output: "npm error Missing script: "dev" / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 2 further occurrence(s) are not listed individually; the score already reflects all 42.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- 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.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was CommandError.convertToCommandError at 45. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being parseConnectionString.verifyKeyValuePair at 20 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/db-client/src/Client/parseConnectionString.ts (parseConnectionString.verifyKeyValuePair at 20). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with CommandError.convertToCommandError (cyclomatic 45). — Refactoring it lifts Cyclomatic Complexity from 8.5 to about 8.9/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
10 method(s) exceeded the cognitive complexity threshold of 15; the worst was Client.connectionString at 32.
What to do
- Bring the 10 bodies over 15 down to 15 or less in Cognitive Complexity — start with Client.connectionString (cognitive 32), CommandError.convertToCommandError (cognitive 28), multiStreamAppend.multiStreamAppend (cognitive 27). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 10 together lifts Cognitive Complexity from 7.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
5 god class(es) detected.
What to do
- Resolve the 3 FunctionTooLong finding(s) in God Classes — start with CommandError.ts, append.ts, batchAppend.ts. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with CommandError.ts. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with index.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
2 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 8 classes have LCOM4 above 3.
D9 · Test Distribution
340 test methods: 340 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 340 `it`/`test` case(s) across 78 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
8 skipped, 7 zero-assertion, 12 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 340 tests.
What to do
- Resolve the 12 Fixed-sleep synchronisation finding(s) in Test Quality — start with getPersistentSubscriptionToAllInfo.test.ts (2), getPersistentSubscriptionToStreamInfo.test.ts (2), write-after-end.test.ts (2). — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 8 Skipped test finding(s) in Test Quality — start with dispose.test.ts (4), readStream.test.ts (2), RecordedEvent-created.test.ts. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 7 No assertions finding(s) in Test Quality — start with updateProjection.test.ts (2), typedEvents.test.ts (2), appendToStream-batch-append-flood.test.ts. — One of this dimension's main actionable groups (7 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D12 · Dependency Hygiene
16 outdated direct production npm dependency(ies) of 22 graded, 0 pinning defect(s), across 6 REDACTED (3 of them the product) and 2 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 1 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 13 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (13). — One of this dimension's main actionable groups (13 recommendation-level).
- Resolve the 3 Outdated (npm) finding(s) in Dependency Hygiene — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 warning-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 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 570 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 573 package(s) this repository's committed lockfile installs for a consumer — its 22 production, optional and peer dependency(ies), across 3 product REDACTED manifest(s), and everything those install in turn. Its 61 `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. A further 3 package(s) the lockfile resolves are not published on the public registry at all — a private scope, a workspace-internal name or a git install — and are outside this verdict. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
3 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/db-client/src/types/index.ts. Counted over 41 of the 93 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
4 deducted task-comment markers across 9728 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 4 TodoComment finding(s) in Explicit Debt — start with dispose.test.ts (3), write-after-end.test.ts. — One of this dimension's main actionable groups (4 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 15 document(s) read across 5 unit(s).
D23 · Boundary Type-Coupling
1 domain type(s) cross context boundaries across 3 contexts; they are measured and withheld (not published, not scored). Contexts: benchmark, db-client, opentelemetry.
D24 · Comment Value
7 of 240 judged comments only repeat the code they sit on (2.9 %). 18 comment(s) in another language or script were not judged.
What to do
- Resolve the 7 redundant comment finding(s) in Comment Value — start with typedEvents.test.ts (3), importCodePlugin.ts (2), createImportCodeBlockRule.ts. — One of this dimension's main actionable groups (7 recommendation-level).
D26 · Project Cohesion
1 of 3 build units (npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
23 finding(s): 0 critical, 22 high, 1 medium, 0 low. 13 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. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- No action in Static Analysis (SAST) — all 13 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 (13 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
57 finding(s): 6 critical, 30 high, 18 medium, 3 low.
What to do
- Resolve the 26 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (26). — One of this dimension's main actionable groups (26 issue-level).
- Resolve the 6 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 4 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
D31 · IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D34 · Knowledge Freshness
29 of 41 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/db-client/src/persistentSubscription/utils/mapPersistentSubscriptionInfo.ts. Counted over 41 of the 93 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 29 Orphaned file finding(s) in Knowledge Freshness — start with mapPersistentSubscriptionInfo.ts, parseConnectionString.ts, events.ts. — One of this dimension's main actionable groups (29 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: readAll.ts↔readStream.ts 55%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with readAll.ts. — One of this dimension's main actionable groups (1 warning-level).
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 — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `StreamingRead` declares 37 required operations under just 8 distinct name(s): `cancel`, `addListener`, `addListener`, `addListener`, `addListener`, `addListener`, `addListener`, `on`, `on`, `on`, `on`, `on`, `on`, `once`, `once`, `once`, `once`, `once`, `once`, `prependListener`, `prependListener`, `prependListener`, `prependListener`, `prependListener`, `prependListener`, `prependOnceListener`, `prependOnceListener`, `prependOnceListener`, `prependOnceListener`, `prependOnceListener`, `prependOnceListener`, `removeListener`, `removeListener`, `removeListener`, `removeListener`, `removeListener`, `[Symbol.asyncIterator]`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 37 separate responsibilities: a caller binds to 8 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 37 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — packages/db-client/src/types/index.ts:373
- `ReadableSubscription` declares 44 required operations under just 8 distinct name(s): `unsubscribe`, `addListener`, `addListener`, `addListener`, `addListener`, `addListener`, `addListener`, `addListener`, `on`, `on`, `on`, `on`, `on`, `on`, `on`, `once`, `once`, `once`, `once`, `once`, `once`, `once`, `prependListener`, `prependListener`, `prependListener`, `prependListener`, `prependListener`, `prependListener`, `prependListener`, `prependOnceListener`, `prependOnceListener`, `prependOnceListener`, `prependOnceListener`, `prependOnceListener`, `prependOnceListener`, `prependOnceListener`, `removeListener`, `removeListener`, `removeListener`, `removeListener`, and 4 more. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 44 separate responsibilities: a caller binds to 8 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 44 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — packages/db-client/src/types/index.ts:432
What to do
- Collapse overload sets (optional/default parameters, or an options object) — these interfaces are wide in SIGNATURES, not in responsibilities, so segregating them would relieve no caller.
AX8 · Test isolation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×11) — packages/test/src/connection/reconnect/all-nodes-down.test.ts:20, packages/test/src/connection/reconnect/mid-stream.test.ts:18, packages/test/src/connection/reconnect/no-reconnection.test.ts:57, …
What to do
- Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 1 of 4 project(s) that lack one — worth up to 0.5 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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 11435 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:3
- `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:24
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 14 duplicated blocks under packages/db-client/src/ have copies in at least two of the sibling directories persistentSubscription, projections, streams, utils — 11 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 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 14 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/db-client/src/persistentSubscription/replayParkedMessagesToStream.ts:22
- packages/db-client/src/persistentSubscription/replayParkedMessagesToStream.ts:22 · packages/db-client/src/projections/createProjection.ts:36 — the two spans are one implementation copied and then locally edited — 314 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/db-client/src/persistentSubscription/replayParkedMessagesToStream.ts:22
- packages/db-client/src/streams/deleteStream.ts:10 · packages/db-client/src/streams/tombstoneStream.ts:10 — the two spans are one implementation copied and then locally edited — 336 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/db-client/src/streams/deleteStream.ts:10
- packages/db-client/src/utils/convertGrpcEvent.ts:83 · packages/db-client/src/utils/convertRustEvent.ts:28 — the two spans are one implementation copied and then locally edited — 247 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/db-client/src/utils/convertGrpcEvent.ts:83
- packages/db-client/src/persistentSubscription/listAllPersistentSubscriptions.ts:59 · packages/db-client/src/persistentSubscription/listPersistentSubscriptionsToStream.ts:76 — the two spans are one implementation copied and then locally edited — 218 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/db-client/src/persistentSubscription/listAllPersistentSubscriptions.ts:59
- packages/db-client/src/persistentSubscription/createPersistentSubscriptionToStream.ts:53 · packages/db-client/src/persistentSubscription/updatePersistentSubscriptionToStream.ts:38 — 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/db-client/src/persistentSubscription/createPersistentSubscriptionToStream.ts:53
- packages/db-client/src/streams/appendToStream/appendRecords.ts:24 · packages/db-client/src/streams/appendToStream/multiStreamAppend.ts:24 — the two spans are one implementation copied and then locally edited — 215 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/db-client/src/streams/appendToStream/appendRecords.ts:24
- packages/db-client/src/projections/getProjectionResult.ts:29 · packages/db-client/src/projections/getProjectionState.ts:29 — 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/db-client/src/projections/getProjectionResult.ts:29
- REDACTED:222 · REDACTED:283 — 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. — REDACTED:222
- packages/db-client/src/streams/appendToStream/append.ts:115 · packages/db-client/src/streams/appendToStream/batchAppend.ts:120 — the two spans are one implementation copied and then locally edited — 231 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/db-client/src/streams/appendToStream/append.ts:115
- packages/db-client/src/projections/enableProjection.ts:24 · packages/db-client/src/projections/resetProjection.ts:25 — 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/db-client/src/projections/enableProjection.ts:24
- packages/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts:108 · packages/db-client/src/streams/subscribeToAll.ts:107 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts:108
- packages/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts:70 · packages/db-client/src/persistentSubscription/updatePersistentSubscriptionToAll.ts:42 — 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/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts:70
- packages/db-client/src/streams/subscribeToAll.ts:59 · packages/db-client/src/streams/subscribeToStream.ts:59 — the two spans are one implementation copied and then locally edited — 122 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/db-client/src/streams/subscribeToAll.ts:59
- packages/db-client/src/persistentSubscription/getPersistentSubscriptionToAllInfo.ts:51 · packages/db-client/src/persistentSubscription/getPersistentSubscriptionToStreamInfo.ts:82 — 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/db-client/src/persistentSubscription/getPersistentSubscriptionToAllInfo.ts:51
- packages/db-client/src/persistentSubscription/getPersistentSubscriptionToStreamInfo.ts:45 · packages/db-client/src/persistentSubscription/replayParkedMessagesToStream.ts:46 — 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/db-client/src/persistentSubscription/getPersistentSubscriptionToStreamInfo.ts:45
- packages/db-client/src/streams/appendToStream/append.ts:27 · packages/db-client/src/streams/appendToStream/batchAppend.ts:172 — 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/db-client/src/streams/appendToStream/append.ts:27
- packages/db-client/src/streams/appendToStream/appendRecords.ts:119 · packages/db-client/src/streams/appendToStream/multiStreamAppend.ts:45 — 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/db-client/src/streams/appendToStream/appendRecords.ts:119
- packages/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts:24 · packages/db-client/src/projections/updateProjection.ts:9 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts:24
- packages/db-client/src/persistentSubscription/createPersistentSubscriptionToStream.ts:13 · packages/db-client/src/persistentSubscription/updatePersistentSubscriptionToStream.ts:12 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/db-client/src/persistentSubscription/createPersistentSubscriptionToStream.ts:13
- packages/db-client/src/streams/subscribeToAll.ts:143 · packages/db-client/src/streams/subscribeToStream.ts:99 — 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/db-client/src/streams/subscribeToAll.ts:143
- packages/db-client/src/streams/utils/ReadStream.ts:62 · packages/db-client/src/streams/utils/Subscription.ts:114 — 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/db-client/src/streams/utils/ReadStream.ts:62
- packages/db-client/src/persistentSubscription/replayParkedMessagesToStream.ts:91 · packages/db-client/src/persistentSubscription/restartPersistentSubscriptionSubsystem.ts:44 · packages/db-client/src/projections/createProjection.ts:102 — the 3 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — packages/db-client/src/persistentSubscription/replayParkedMessagesToStream.ts:91
- packages/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts:148 · packages/db-client/src/persistentSubscription/createPersistentSubscriptionToStream.ts:85 · packages/db-client/src/persistentSubscription/replayParkedMessagesToAll.ts:60 · packages/db-client/src/persistentSubscription/updatePersistentSubscriptionToAll.ts:77 · +5 more site(s) not listed — the 9 copies are spread across 9 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/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts:148
- packages/db-client/src/persistentSubscription/deletePersistentSubscriptionToAll.ts:47 · packages/db-client/src/persistentSubscription/deletePersistentSubscriptionToStream.ts:43 · packages/db-client/src/projections/deleteProjection.ts:69 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/db-client/src/persistentSubscription/deletePersistentSubscriptionToAll.ts:47
- packages/db-client/src/persistentSubscription/deletePersistentSubscriptionToStream.ts:10 · packages/db-client/src/persistentSubscription/replayParkedMessagesToStream.ts:25 · packages/db-client/src/projections/createProjection.ts:39 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/db-client/src/persistentSubscription/deletePersistentSubscriptionToStream.ts:10
- packages/db-client/src/streams/appendToStream/append.ts:74 · packages/db-client/src/utils/CommandError.ts:206 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/db-client/src/streams/appendToStream/append.ts:74
- packages/db-client/src/streams/utils/Subscription.ts:65 · packages/db-client/src/streams/utils/Subscription.ts:85 — 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/db-client/src/streams/utils/Subscription.ts:65
- packages/db-client/src/persistentSubscription/getPersistentSubscriptionToAllInfo.ts:16 · packages/db-client/src/projections/getProjectionStatus.ts:14 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/db-client/src/persistentSubscription/getPersistentSubscriptionToAllInfo.ts:16
- packages/db-client/src/persistentSubscription/utils/PersistentSubscriptionImpl.ts:44 · packages/db-client/src/streams/utils/Subscription.ts:44 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/db-client/src/persistentSubscription/utils/PersistentSubscriptionImpl.ts:44
- packages/db-client/src/persistentSubscription/listAllPersistentSubscriptions.ts:19 · packages/db-client/src/persistentSubscription/listPersistentSubscriptionsToAll.ts:17 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/db-client/src/persistentSubscription/listAllPersistentSubscriptions.ts:19
- packages/db-client/src/utils/CommandError.ts:468 · packages/db-client/src/utils/CommandError.ts:482 · packages/db-client/src/utils/CommandError.ts:496 — all 3 copies are in the same file, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited. — packages/db-client/src/utils/CommandError.ts:468
- packages/db-client/src/utils/convertGrpcEvent.ts:29 · packages/db-client/src/utils/convertGrpcEvent.ts:53 — 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/db-client/src/utils/convertGrpcEvent.ts:29
- packages/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts:154 · packages/db-client/src/persistentSubscription/createPersistentSubscriptionToStream.ts:91 · packages/db-client/src/persistentSubscription/replayParkedMessagesToAll.ts:66 · packages/db-client/src/persistentSubscription/replayParkedMessagesToStream.ts:97 · +9 more site(s) not listed — the 13 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 13 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — packages/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts:154
- REDACTED:203 · REDACTED:267 — 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. — REDACTED:203
- packages/db-client/src/persistentSubscription/replayParkedMessagesToAll.ts:47 · packages/db-client/src/persistentSubscription/replayParkedMessagesToStream.ts:82 — 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/db-client/src/persistentSubscription/replayParkedMessagesToAll.ts:47
- packages/db-client/src/utils/CommandError.ts:175 · packages/db-client/src/utils/CommandError.ts:507 · packages/db-client/src/utils/CommandError.ts:518 — all 3 copies are in the same file, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited. — packages/db-client/src/utils/CommandError.ts:175
- packages/db-client/src/utils/CommandError.ts:511 · packages/db-client/src/utils/CommandError.ts:522 — all 2 copies are in the same file, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited. — packages/db-client/src/utils/CommandError.ts:511
- packages/db-client/src/utils/CommandError.ts:416 · packages/db-client/src/utils/CommandError.ts:470 · packages/db-client/src/utils/CommandError.ts:484 · packages/db-client/src/utils/CommandError.ts:498 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — packages/db-client/src/utils/CommandError.ts:416
- packages/db-client/src/persistentSubscription/listPersistentSubscriptionsToAll.ts:34 · packages/db-client/src/persistentSubscription/subscribeToPersistentSubscriptionToAll.ts:57 · packages/db-client/src/persistentSubscription/updatePersistentSubscriptionToAll.ts:40 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/db-client/src/persistentSubscription/listPersistentSubscriptionsToAll.ts:34
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.
R11 · Import Boundaries
- packages/db-client/src/Client/ServerFeatures.ts:9 imports @grpc/grpc-js/build/src/constants, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/db-client/src/Client/ServerFeatures.ts:9
- packages/db-client/src/Client/index.ts:19 imports @grpc/grpc-js/build/src/call, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/db-client/src/Client/index.ts:19
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
- (anonymous) has cyclomatic complexity 45 and cognitive complexity 28; 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/db-client/src/utils/CommandError.ts:587
- (anonymous) has cyclomatic complexity 28 and cognitive complexity 39; 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/test/src/utils/matchServerVersion.ts:74
- (top-level) has cyclomatic complexity 25 and cognitive complexity 24; 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/db-client/src/types/events.ts:1
- (anonymous) 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/db-client/src/Client/parseConnectionString.ts:276
- connectionString has cyclomatic complexity 19 and cognitive complexity 32; 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/db-client/src/Client/index.ts:168
- createPersistentSubscriptionToAll has cyclomatic complexity 14 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts:51
- (anonymous) has cyclomatic complexity 14 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/test/src/utils/Cluster.ts:218
- unpackToCommandError has cyclomatic complexity 13 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/db-client/src/streams/appendToStream/unpackError.ts:28
- subscribeToAll has cyclomatic complexity 11 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/db-client/src/streams/subscribeToAll.ts:52
- (anonymous) has cyclomatic complexity 11 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — packages/db-client/src/streams/appendToStream/append.ts:66, packages/db-client/src/streams/appendToStream/appendRecords.ts:42
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
- packages/db-client/src/Client/index.ts has 682 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/db-client/src/Client/index.ts:1
- packages/db-client/src/utils/CommandError.ts has 661 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/db-client/src/utils/CommandError.ts:1
- packages/db-client/src/types/index.ts has 616 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/db-client/src/types/index.ts:1
- REDACTED has 487 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
- packages/db-client/src/persistentSubscription/utils/mapPersistentSubscriptionInfo.ts has 403 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/db-client/src/persistentSubscription/utils/mapPersistentSubscriptionInfo.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. — packages/db-client/src/streams/utils/ReadStream.ts:1
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
R7 · Dead Code
- 1 file(s) (~24 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.
- 111 file(s) (~17325 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/test
- Unreachable from the 7 application, 2 tooling and 111 test entry point(s) detected in this repo. Gate removals on `yarn run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (7 application, 2 tooling, 111 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/db-client/src/streams/utils/ReadStream.ts
- Nothing imports this binding — it is safe to review for removal. (×2) — packages/db-client/src/persistentSubscription/utils/mapPersistentSubscriptionInfo.ts:120, packages/db-client/src/persistentSubscription/utils/mapPersistentSubscriptionInfo.ts:124
- Nothing ultimately consumes this binding: its only referrer is the re-export in packages/db-client/src/utils/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/db-client/src/utils/index.ts in the same commit, or the barrel will import a name that no longer exists. (×2) — packages/db-client/src/utils/convertGrpcEvent.ts:16, packages/db-client/src/utils/convertGrpcEvent.ts:17
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
- Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. — packages/test/src/utils/FlakeFinder.js:1
- 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)
- Declared in packages/test/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.
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- packages/db-client/src/utils/CommandError.ts → packages/db-client/src/utils/index.ts → packages/db-client/src/utils/CommandError.ts (one verified cycle inside a mutually-dependent group of 3 files) — packages/db-client/src/utils/CommandError.ts:6
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture
- `rejectUnauthorized: false` is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the option so Node validates the peer. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: pass its CA as `ca` (or set `NODE_EXTRA_CA_CERTS`), which keeps the chain and hostname checks on. A managed database or broker that documents `rejectUnauthorized: false` publishes a CA bundle for exactly this purpose. — packages/db-client/src/Client/index.ts:198
What to do
- Stop accepting every TLS certificate: delete `rejectUnauthorized: false` / `NODE_TLS_REJECT_UNAUTHORIZED=0` so the chain, hostname and expiry are verified, and trust a self-signed or private server by passing its CA (`ca`, or `NODE_EXTRA_CA_CERTS`) — never by switching verification off.
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. (×3) — packages/db-client/src/streams/appendToStream/append.ts:63, packages/db-client/src/streams/appendToStream/batchAppend.ts:155, packages/db-client/src/streams/appendToStream/multiStreamAppend.ts:43
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
- Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `makeRequest` awaits `http.request(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `http.request(url, { signal })`. — packages/db-client/src/Client/http.ts:71
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- 3/4 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
- ~7.0 `!` null assertions per 1k TypeScript source lines — 79 assertion(s) across the 11232 source line(s) of the 105 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/db-client/src/utils/CommandError.ts (20), packages/db-client/src/streams/utils/Subscription.ts (10), packages/db-client/src/Client/http.ts (9). 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 | 66% | Adequate | Acceptable, with room to improve. |
| Architecture | 88% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 59% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 57% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 56% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 91% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 56 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: 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 (the repository): REDACTED has no "dev" script, so `npm run dev` could not start the app. Last output: "npm error Missing script: "dev" / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .ts, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D4 Code Duplication — This repository's production source (.ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (3 domain event(s); its domain events are published by services or handlers — no domain entity raises one)
- 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
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JavaScript/TypeScript source (5 module(s), 94 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- 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.
- R5 Dependency Freshness — uses a yarn 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 — 63 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unlisted import '@jest/test-sequencer' packages/test/src/utils/FlakeFinder.js:1
- Import cycle (2 files) packages/db-client/src/utils/CommandError.ts:6
- TLS certificate validation disabled packages/db-client/src/Client/index.ts:198
Serious — 147 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Fixed-sleep synchronisation: should get info on a persistent subscription to all packages/test/src/persistentSubscription/getPersistentSubscriptionToAllInfo.test.ts:54
- Fixed-sleep synchronisation: should get info on a persistent subscription to all connection packages/test/src/persistentSubscription/getPersistentSubscriptionToAllInfo.test.ts:134
- Fixed-sleep synchronisation: should get info on a persistent subscription packages/test/src/persistentSubscription/getPersistentSubscriptionToStreamInfo.test.ts:31
- Fixed-sleep synchronisation: should get info on a persistent subscription connection packages/test/src/persistentSubscription/getPersistentSubscriptionToStreamInfo.test.ts:113
- Fixed-sleep synchronisation: should list info on a persistent subscription connection packages/test/src/persistentSubscription/listAllPersistentSubscriptions.test.ts:110
- Fixed-sleep synchronisation: should list info on a persistent subscription connection packages/test/src/persistentSubscription/listPersistentSubscriptionsToAll.test.ts:96
- Fixed-sleep synchronisation: should list info on a persistent subscription connection packages/test/src/persistentSubscription/listPersistentSubscriptionsToStream.test.ts:70
- Fixed-sleep synchronisation: Should not write after end packages/test/src/extra/write-after-end.test.ts:37
- Fixed-sleep synchronisation: Should not write after end (batch append) packages/test/src/extra/write-after-end.test.ts:74
- Fixed-sleep synchronisation: UnavailableError packages/test/src/connection/reconnect/UnavailableError.test.ts:18
- Fixed-sleep synchronisation: should reconnect after leader is killed and resurrected as follower packages/test/src/connection/reconnect/leader-failover.test.ts:29
- Fixed-sleep synchronisation: Connection error mid stream should cause a reconnect packages/test/src/connection/reconnect/mid-stream.test.ts:19
- Skipped test: stream not found packages/test/src/streams/readStream.test.ts:238
- Skipped test: stream deleted packages/test/src/streams/readStream.test.ts:282
- Skipped test: Should correctly converted from Ticks packages/test/src/extra/RecordedEvent-created.test.ts:26
- Skipped test: stream set should be cleaned up packages/test/src/extra/dispose.test.ts:41
- Skipped test: stream set should be cleaned up naturally packages/test/src/extra/dispose.test.ts:88
- Skipped test: read $all packages/test/src/extra/dispose.test.ts:240
- Skipped test: read stream packages/test/src/extra/dispose.test.ts:279
- Skipped test: no reconnection for TimeoutError packages/test/src/connection/reconnect/no-reconnection.test.ts:57
- No assertions: Can handle multiple appends within the same event loop packages/test/src/streams/appendToStream-batch-append-flood.test.ts:25
- No assertions: any stream packages/test/src/streams/getStreamMetadata.test.ts:18
- No assertions: resets the projection packages/test/src/projections/resetProjection.test.ts:35
- No assertions: change query packages/test/src/projections/updateProjection.test.ts:36
- No assertions: Emit enabled packages/test/src/projections/updateProjection.test.ts:53
- No assertions: jsonEvent packages/test/src/extra/typedEvents.test.ts:24
- No assertions: binaryEvent packages/test/src/extra/typedEvents.test.ts:86
- TodoComment packages/test/src/extra/dispose.test.ts:53
- TodoComment packages/test/src/extra/dispose.test.ts:253
- TodoComment packages/test/src/extra/dispose.test.ts:294
- TodoComment packages/test/src/extra/write-after-end.test.ts:106
- FunctionTooLong: CommandError.convertToCommandError packages/db-client/src/utils/CommandError.ts:587
- FunctionTooLong: append.append packages/db-client/src/streams/appendToStream/append.ts:19
- FunctionTooLong: batchAppend.batchAppend packages/db-client/src/streams/appendToStream/batchAppend.ts:48
- Duplicated block (18 lines × 2 locations) packages/db-client/src/persistentSubscription/createPersistentSubscriptionToStream.ts:13
- Duplicated block (18 lines × 2 locations) packages/db-client/src/streams/subscribeToAll.ts:143
- Duplicated block (18 lines × 2 locations) packages/db-client/src/streams/utils/ReadStream.ts:62
- `async` Promise executor packages/db-client/src/streams/appendToStream/append.ts:63
- `async` Promise executor packages/db-client/src/streams/appendToStream/batchAppend.ts:155
- `async` Promise executor packages/db-client/src/streams/appendToStream/multiStreamAppend.ts:43
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (22 lines × 2 locations) packages/db-client/src/persistentSubscription/getPersistentSubscriptionToAllInfo.ts:51
- Duplicated block (22 lines × 2 locations) packages/db-client/src/persistentSubscription/getPersistentSubscriptionToStreamInfo.ts:45
- Duplicated block (20 lines × 2 locations) packages/db-client/src/streams/appendToStream/append.ts:27
- Duplicated block (20 lines × 2 locations) packages/db-client/src/streams/appendToStream/appendRecords.ts:119
- Duplicated block (15 lines × 3 locations) packages/db-client/src/persistentSubscription/deletePersistentSubscriptionToAll.ts:47
- Duplicated block (15 lines × 3 locations) packages/db-client/src/persistentSubscription/deletePersistentSubscriptionToStream.ts:10
- Duplicated block (15 lines × 2 locations) packages/db-client/src/streams/appendToStream/append.ts:74
- Duplicated block (15 lines × 2 locations) packages/db-client/src/streams/utils/Subscription.ts:65
- Duplicated block (12 lines × 2 locations) packages/db-client/src/persistentSubscription/listAllPersistentSubscriptions.ts:19
- Duplicated block (12 lines × 2 locations) packages/db-client/src/utils/convertGrpcEvent.ts:29
- Duplicated block (9 lines × 2 locations) packages/db-client/src/persistentSubscription/replayParkedMessagesToAll.ts:47
- Duplicated block (9 lines × 2 locations) packages/db-client/src/utils/CommandError.ts:511
- Boundary violation [package:third-party-deep-import] packages/db-client/src/Client/ServerFeatures.ts:9
- Boundary violation [package:third-party-deep-import] packages/db-client/src/Client/index.ts:19
- Complex function (anonymous) (cyclomatic 11, cognitive 14) packages/db-client/src/streams/appendToStream/append.ts:66
- Complex function (anonymous) (cyclomatic 11, cognitive 14) packages/db-client/src/streams/appendToStream/appendRecords.ts:42
- CommandError.convertToCommandError (cyclomatic 45) packages/db-client/src/utils/CommandError.ts:587
- Client.connectionString (cyclomatic 19) packages/db-client/src/Client/index.ts:168
- append.append (cyclomatic 19) packages/db-client/src/streams/appendToStream/append.ts:19
- multiStreamAppend.multiStreamAppend (cyclomatic 19) packages/db-client/src/streams/appendToStream/multiStreamAppend.ts:18
- appendRecords.appendRecords (cyclomatic 19) packages/db-client/src/streams/appendToStream/appendRecords.ts:18
- Deprecated: eslint REDACTED:31
- Client.connectionString (cognitive 32) packages/db-client/src/Client/index.ts:168
- CommandError.convertToCommandError (cognitive 28) packages/db-client/src/utils/CommandError.ts:587
- multiStreamAppend.multiStreamAppend (cognitive 27) packages/db-client/src/streams/appendToStream/multiStreamAppend.ts:18
- append.append (cognitive 24) packages/db-client/src/streams/appendToStream/append.ts:19
- appendRecords.appendRecords (cognitive 22) packages/db-client/src/streams/appendToStream/appendRecords.ts:18
- createPersistentSubscriptionToAll.Client.createPersistentSubscriptionToAll (cognitive 21) packages/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts:51
- batchAppend.batchAppend (cognitive 19) packages/db-client/src/streams/appendToStream/batchAppend.ts:48
- Subscription._transform (cognitive 18) packages/db-client/src/streams/utils/Subscription.ts:58
- subscribeToAll.Client.subscribeToAll (cognitive 17) packages/db-client/src/streams/subscribeToAll.ts:52
- discovery.discoverEndpoint (cognitive 16) packages/db-client/src/Client/discovery.ts:19
- REDACTED
- FileTooLong: utils/CommandError.ts packages/db-client/src/utils/CommandError.ts
- ClassTooLong: Client packages/db-client/src/Client/index.ts:143
- Change coupling: readAll.ts ↔ readStream.ts packages/db-client/src/streams/readAll.ts:1
- REDACTED
- REDACTED
- REDACTED
- Off the main sequence: @kurrent/kurrentdb-client
- Duplication concentrated across 4 sibling directories (14 clone groups) packages/db-client/src/persistentSubscription/replayParkedMessagesToStream.ts:22
- Duplicated block with local edits (68 matched lines × 2 locations) packages/db-client/src/persistentSubscription/replayParkedMessagesToStream.ts:22
- Duplicated block with local edits (66 matched lines × 2 locations) packages/db-client/src/streams/deleteStream.ts:10
- Duplicated block with local edits (44 matched lines × 2 locations) packages/db-client/src/utils/convertGrpcEvent.ts:83
- Duplicated block with local edits (42 matched lines × 2 locations) packages/db-client/src/persistentSubscription/listAllPersistentSubscriptions.ts:59
- Duplicated block (41 lines × 2 locations) packages/db-client/src/persistentSubscription/createPersistentSubscriptionToStream.ts:53
- Duplicated block with local edits (41 matched lines × 2 locations) packages/db-client/src/streams/appendToStream/appendRecords.ts:24
- Duplicated block (37 lines × 2 locations) packages/db-client/src/projections/getProjectionResult.ts:29
- Duplicated block (35 lines × 2 locations) REDACTED:222
- Duplicated block with local edits (34 matched lines × 2 locations) packages/db-client/src/streams/appendToStream/append.ts:115
- Duplicated block (30 lines × 2 locations) packages/db-client/src/projections/enableProjection.ts:24
- Duplicated block (28 lines × 2 locations) packages/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts:108
- Duplicated block (23 lines × 2 locations) packages/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts:70
- Duplicated block with local edits (23 matched lines × 2 locations) packages/db-client/src/streams/subscribeToAll.ts:59
- Duplicated block (19 lines × 2 locations) packages/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts:24
- Duplicated block (17 lines × 3 locations) packages/db-client/src/persistentSubscription/replayParkedMessagesToStream.ts:91
- Duplicated block (15 lines × 9 locations) packages/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts:148
- Duplicated block (14 lines × 2 locations) packages/db-client/src/persistentSubscription/getPersistentSubscriptionToAllInfo.ts:16
- Duplicated block (13 lines × 2 locations) packages/db-client/src/persistentSubscription/utils/PersistentSubscriptionImpl.ts:44
- Duplicated block (12 lines × 3 locations) packages/db-client/src/utils/CommandError.ts:468
- Duplicated block (10 lines × 13 locations) packages/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts:154
- Duplicated block (10 lines × 2 locations) REDACTED:203
- Duplicated block (9 lines × 3 locations) packages/db-client/src/utils/CommandError.ts:175
- Duplicated block (8 lines × 4 locations) packages/db-client/src/utils/CommandError.ts:416
- Duplicated block (7 lines × 3 locations) packages/db-client/src/persistentSubscription/listPersistentSubscriptionsToAll.ts:34
- Complex function (anonymous) (cyclomatic 45, cognitive 28) packages/db-client/src/utils/CommandError.ts:587
- Complex function (anonymous) (cyclomatic 28, cognitive 39) packages/test/src/utils/matchServerVersion.ts:74
- Complex function (top-level) (cyclomatic 25, cognitive 24) packages/db-client/src/types/events.ts:1
- Complex function (anonymous) (cyclomatic 21, cognitive 9) packages/db-client/src/Client/parseConnectionString.ts:276
- Complex function connectionString (cyclomatic 19, cognitive 32) packages/db-client/src/Client/index.ts:168
- Complex function createPersistentSubscriptionToAll (cyclomatic 14, cognitive 20) packages/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts:51
- Complex function (anonymous) (cyclomatic 14, cognitive 15) packages/test/src/utils/Cluster.ts:218
- Complex function unpackToCommandError (cyclomatic 13, cognitive 13) packages/db-client/src/streams/appendToStream/unpackError.ts:28
- Complex function subscribeToAll (cyclomatic 11, cognitive 17) packages/db-client/src/streams/subscribeToAll.ts:52
- packages/db-client/src/Client/index.ts: 682 lines of code packages/db-client/src/Client/index.ts:1
- packages/db-client/src/utils/CommandError.ts: 661 lines of code packages/db-client/src/utils/CommandError.ts:1
- packages/db-client/src/types/index.ts: 616 lines of code packages/db-client/src/types/index.ts:1
- REDACTED: 487 lines of code REDACTED:1
- packages/db-client/src/persistentSubscription/utils/mapPersistentSubscriptionInfo.ts: 403 lines of code packages/db-client/src/persistentSubscription/utils/mapPersistentSubscriptionInfo.ts:1
- No test reaches this file packages/db-client/src/streams/utils/ReadStream.ts:1
- Dead file (~84 LoC) packages/db-client/src/streams/utils/ReadStream.ts
- Unused dependency 'grpc-tools'
- Unused dependency 'grpc_tools_node_protoc_ts'
- Unused dependency '@opentelemetry/api'
- Async function without AbortSignal: makeRequest packages/db-client/src/Client/http.ts:71
Minor — 106 finding(s)
- Orphaned file packages/db-client/src/persistentSubscription/utils/mapPersistentSubscriptionInfo.ts:1
- Orphaned file packages/db-client/src/Client/parseConnectionString.ts:1
- Orphaned file packages/db-client/src/types/events.ts:1
- Orphaned file packages/db-client/src/Client/discovery.ts:1
- Orphaned file packages/db-client/src/utils/convertGrpcEvent.ts:1
- Orphaned file packages/db-client/src/streams/appendToStream/append.ts:1
- Orphaned file packages/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts:1
- Orphaned file packages/db-client/src/streams/subscribeToAll.ts:1
- Orphaned file packages/db-client/src/streams/utils/streamMetadata.ts:1
- Orphaned file packages/db-client/src/persistentSubscription/utils/PersistentSubscriptionImpl.ts:1
- Orphaned file packages/db-client/src/projections/createProjection.ts:1
- Orphaned file packages/db-client/src/persistentSubscription/utils/persistentSubscriptionSettings.ts:1
- Orphaned file packages/db-client/src/persistentSubscription/listPersistentSubscriptionsToStream.ts:1
- Orphaned file packages/db-client/src/streams/utils/Subscription.ts:1
- Orphaned file packages/db-client/src/persistentSubscription/getPersistentSubscriptionToStreamInfo.ts:1
- Orphaned file packages/db-client/src/persistentSubscription/replayParkedMessagesToStream.ts:1
- Orphaned file packages/db-client/src/persistentSubscription/createPersistentSubscriptionToStream.ts:1
- Orphaned file packages/db-client/src/streams/subscribeToStream.ts:1
- Orphaned file packages/db-client/src/persistentSubscription/listAllPersistentSubscriptions.ts:1
- Orphaned file packages/db-client/src/persistentSubscription/updatePersistentSubscriptionToAll.ts:1
- Orphaned file packages/db-client/src/persistentSubscription/subscribeToPersistentSubscriptionToStream.ts:1
- Orphaned file packages/db-client/src/persistentSubscription/subscribeToPersistentSubscriptionToAll.ts:1
- Orphaned file packages/db-client/src/persistentSubscription/updatePersistentSubscriptionToStream.ts:1
- Orphaned file packages/db-client/src/Client/ServerFeatures.ts:1
- Orphaned file packages/db-client/src/streams/tombstoneStream.ts:1
- Mock-dominated test: after the fact event listeners packages/test/src/streams/subscribeToAll.test.ts:364
- Mock-dominated test: from start packages/test/src/streams/subscribeToStream.test.ts:45
- Mock-dominated test: from end packages/test/src/streams/subscribeToStream.test.ts:97
- Mock-dominated test: from revision packages/test/src/streams/subscribeToStream.test.ts:147
- Mock-dominated test: from start packages/test/src/persistentSubscription/subscribeToPersistentSubscriptionToAll.test.ts:76
- Mock-dominated test: from end packages/test/src/persistentSubscription/subscribeToPersistentSubscriptionToAll.test.ts:188
- Mock-dominated test: after the fact event listeners packages/test/src/persistentSubscription/subscribeToPersistentSubscriptionToAll.test.ts:484
- Mock-dominated test: from start packages/test/src/persistentSubscription/subscribeToPersistentSubscriptionToStream.test.ts:53
- Mock-dominated test: from revision packages/test/src/persistentSubscription/subscribeToPersistentSubscriptionToStream.test.ts:107
- Mock-dominated test: from end packages/test/src/persistentSubscription/subscribeToPersistentSubscriptionToStream.test.ts:159
- Mock-dominated test: nack packages/test/src/persistentSubscription/subscribeToPersistentSubscriptionToStream.test.ts:209
- Mock-dominated test: after the fact event listeners packages/test/src/persistentSubscription/subscribeToPersistentSubscriptionToStream.test.ts:439
- Mock-dominated test: Subscription to stream packages/test/src/extra/dispose.test.ts:106
- Mock-dominated test: Subscription to $all packages/test/src/extra/dispose.test.ts:145
- Mock-dominated test: Persistent subscription to stream packages/test/src/extra/dispose.test.ts:183
- Mock-dominated test: Persistent subscription to $all packages/test/src/extra/dispose.test.ts:333
- Deprecated: @humanwhocodes/config-array REDACTED:697
- Deprecated: @humanwhocodes/object-schema REDACTED:715
- Deprecated: @opentelemetry/propagator-jaeger REDACTED:1490
- Deprecated: @opentelemetry/sdk-trace-base REDACTED:1563
- Deprecated: @opentelemetry/sdk-trace-base REDACTED:1576
- Deprecated: @opentelemetry/sdk-trace-node REDACTED:1589
- Deprecated: @ungap/structured-clone REDACTED:2119
- Deprecated: har-validator REDACTED:5585
- Deprecated: inflight REDACTED:5951
- Deprecated: request REDACTED:9138
- Deprecated: sourcemap-codec REDACTED:9760
- Deprecated: uuid REDACTED:10835
- Deprecated: uuid REDACTED:10844
- Disabled test packages/test/src/connection/reconnect/all-nodes-down.test.ts:20
- Disabled test packages/test/src/connection/reconnect/mid-stream.test.ts:18
- Disabled test packages/test/src/connection/reconnect/no-reconnection.test.ts:57
- Disabled test packages/test/src/extra/RecordedEvent-created.test.ts:26
- Disabled test packages/test/src/extra/dispose.test.ts:41
- Disabled test packages/test/src/extra/dispose.test.ts:88
- Disabled test packages/test/src/extra/dispose.test.ts:240
- Disabled test packages/test/src/extra/dispose.test.ts:279
- Disabled test packages/test/src/extra/write-after-end.test.ts:36
- Disabled test packages/test/src/streams/readStream.test.ts:238
- Disabled test packages/test/src/streams/readStream.test.ts:282
- redundant comment docs/.vuepress/markdown/xode/createImportCodeBlockRule.ts:41
- redundant comment docs/.vuepress/markdown/xode/importCodePlugin.ts:12
- redundant comment docs/.vuepress/markdown/xode/importCodePlugin.ts:22
- redundant comment docs/.vuepress/markdown/xode/resolveImportCode.ts:60
- redundant comment packages/test/src/extra/typedEvents.test.ts:147
- redundant comment packages/test/src/extra/typedEvents.test.ts:196
- redundant comment packages/test/src/extra/typedEvents.test.ts:261
- Outdated (npm): @rollup/plugin-alias docs/REDACTED:33
- Outdated (npm): @types/node REDACTED:26
- Outdated (npm): tinybench packages/benchmark/REDACTED:15
- REDACTED
- REDACTED
- REDACTED
- Fat interface: StreamingRead (37 required operations) packages/db-client/src/types/index.ts:373
- Fat interface: ReadableSubscription (44 required operations) packages/db-client/src/types/index.ts:432
- Duplicated predicate docs/.vuepress/markdown/linkCheck/index.ts:72
- Duplicated predicate packages/db-client/src/persistentSubscription/createPersistentSubscriptionToAll.ts:64
- Off-boarding risk: anonymized user #1
- Projects may be oversized for their cohesion
- REDACTED
- Concentrated knowledge decay
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:3
- No dependency-update automation REDACTED:24
- No release approval gate
- Unused export 'isPersistentSubscriptionToAllInfo' packages/db-client/src/persistentSubscription/utils/mapPersistentSubscriptionInfo.ts:120
- Unused export 'isPersistentSubscriptionToStreamInfo' packages/db-client/src/persistentSubscription/utils/mapPersistentSubscriptionInfo.ts:124
- Unused export 'GRPCReadResp' packages/db-client/src/utils/convertGrpcEvent.ts:16
- Unused export 'GRPCReadEvent' packages/db-client/src/utils/convertGrpcEvent.ts:17
- Not all async functions that make a request accept an AbortSignal
- Strict null checking is not enabled everywhere the repository type-checks
- Null assertions (`!`) reduce the strict null checking score
Minor — 14 finding(s)
- Outdated (npm): @grpc/grpc-js
- Outdated (npm): @opentelemetry/api
- Outdated (npm): @opentelemetry/instrumentation
- Outdated (npm): @types/debug
- Outdated (npm): debug
- Outdated (npm): google-protobuf
- Outdated (npm): iconify-icon
- Outdated (npm): mermaid
- Outdated (npm): sass-loader
- Outdated (npm): semver
- Outdated (npm): vue
- Outdated (npm): vue-router
- Outdated (npm): vuepress-theme-hope
- doc comments repeat the names packages/db-client/src/Client/index.ts:165
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-34a28d380b694d19ae096356668ebc28/history.json --exit-code 0 --source . | 1 | 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-34a28d380b694d19ae096356668ebc28/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude packages/db-client/generated . | 23 | 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 | 57 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 0 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 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 |