Public report of j5ik2o/event-store-adapter-js, published 22 October 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 22 October 2026, 14:16 UTC · Survey ID cd_a22253399a804fcbbd03b3513520d2eb

j5ik2o/event-store-adapter-js

Measured 22 October 2026, 14:10 UTC, at code version a203986

CAI score 49out of 100 Weak
CriticalWeakAdequateStrongExemplary
Down 9 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

Domain Modelling 100 Exemplary Performance 100 Exemplary Architecture 99 Exemplary Code Health 80 Adequate Production Readiness 64 Adequate Security and Compliance 52 Adequate Accessibility 48 Weak Maturity 38 Weak

A small codebase: 5,636 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Maturity, 38

Findings by how serious they are

41 critical 134 serious 51 minor

11 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 14:10 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that implements it, and today Watchdog is the only one that does.

The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

75of 79 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
214of 226 findings point to an exact file and line, so you can open each one in the code. The other 12 concern the repository as a whole, such as missing documentation.
79dimensions across 8 lenses, read from 5,636 lines of product code in 2 projects.
Chapters

Executive summary

j5ik2o/event-store-adapter-js scores 49 out of 100 and is rated Weak, while six of its eight lenses score higher still: Domain Modelling and Performance at 100 and Architecture at 99, all rated Exemplary, and Code Health at 80, Production Readiness at 64 and Security and Compliance at 52, all rated Adequate.

The score is lower than those six because the weakest lens counts most, and here that is Maturity, which scores 38 and is rated Weak. Its Documentation accuracy dimension scores 0 out of 10, and until that reaches 4, Maturity can't be rated higher than Adequate. The first actions are to reconcile the README with reality: conformance/README.md links to `../docs/spec/core-contract.md`, but `docs/spec/core-contract.md` does not exist; conformance/README.md links to `../docs/spec/storage/dynamodb.md`, but `docs/spec/storage/dynamodb.md` does not exist; conformance/README.md links to `../docs/spec/storage/memory.md`, but `docs/spec/storage/memory.md` does not exist; conformance/README.md links to `../docs/spec/storage/sqlite.md`, but `docs/spec/storage/sqlite.md` does not exist; conformance/README.md links to `../docs/spec/storage/spanner.md`, but `docs/spec/storage/spanner.md` does not exist and to record your significant design decisions, and if Maturity rose to 70, the score would rise from 49 to about 56.

41 findings are critical: 34 in Static Analysis (SAST), five in Dependency Vulnerabilities and two in Forms & labels.

Watchdog couldn't measure 10 dimensions in this code, among them Test Reliability, Navigability and Platform End-of-Life, so they are left out of the score. The product code is 5,636 lines, which would take an estimated 0.3 person-years, around €38,000, to rebuild.

Code Health 80 Adequate, capped by Cognitive Complexity Architecture 99 ★ Exemplary Maturity 38 Weak, capped by Architecture documentation and Documentation accuracy Production Readiness 64 Adequate, capped by Security & performance tooling Security and Compliance 52 Adequate, capped by Static Analysis (SAST) and Supply-chain Provenance & Signing Domain Modelling 100 ★ Exemplary Accessibility 48 Weak Performance 100 ★ Exemplary

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Maturity 38 · counts for 45%Accessibility 48 · counts for 25%Security and Compliance 52 · counts for 14%Production Readiness 64 · counts for 8%Code Health 80 · counts for 4%Architecture 99 · counts for 2%Domain Modelling 100 · counts for 1%Performance 100 · counts for 1%

If Maturity rose from 38 to 70, the lowest score rated Strong, the score would rise from 49 to about 56.

Code composition: what the lines of code are
Product code 16%Tests 84%
New since the last survey: 98 findings

These 98 critical or serious findings weren't in the previous survey, on 8 October 2026.

  • Cyclomatic Complexity · memory-event-store.createMemoryEventStoreInternal (cyclomatic 26) packages/library/src/internal/memory-event-store.ts
  • Cyclomatic Complexity · spanner-store-configuration.reconcileSpannerStoreConfiguration (cyclomatic 25) packages/library/src/internal/spanner-store-configuration.ts
  • Cyclomatic Complexity · dynamodb-event-store-input-validation.validateDynamoDBEventStoreInput (cyclomatic 23) packages/library/src/internal/dynamodb-event-store-input-validation.ts
  • Cyclomatic Complexity · event-store-input-validation.validateEventStoreInput (cyclomatic 22) packages/library/src/internal/event-store-input-validation.ts
  • Cyclomatic Complexity · dynamodb-latest-snapshot-restore.restoreDynamoDBLatestSnapshot (cyclomatic 19) packages/library/src/internal/dynamodb-latest-snapshot-restore.ts
  • Cyclomatic Complexity · snapshot-retention-validation.validateSnapshotRetention (cyclomatic 18) packages/library/src/internal/snapshot-retention-validation.ts
  • Cyclomatic Complexity · spanner-persist-event.persistSpannerEvent (cyclomatic 16) packages/library/src/internal/spanner-persist-event.ts
  • Cyclomatic Complexity · spanner-migration-plan.restoreAggregates (cyclomatic 16) packages/library/src/internal/spanner-migration-plan.ts
  • Cyclomatic Complexity · create-release-note-body.render (cyclomatic 16) .github/create-release-note-body.py
  • Cognitive Complexity · create-release-note-body.render (cognitive 33) .github/create-release-note-body.py
  • Cognitive Complexity · spanner-store-configuration.reconcileSpannerStoreConfiguration (cognitive 31) packages/library/src/internal/spanner-store-configuration.ts
  • Cognitive Complexity · dynamodb-snapshot-retention.retainDynamoDBSnapshots (cognitive 29) packages/library/src/internal/dynamodb-snapshot-retention.ts
  • Cognitive Complexity · memory-event-store.createMemoryEventStoreInternal (cognitive 25) packages/library/src/internal/memory-event-store.ts
  • Cognitive Complexity · event-store-input-validation.validateEventStoreInput (cognitive 20) packages/library/src/internal/event-store-input-validation.ts
  • Cognitive Complexity · dynamodb-persist-event-error.classifyDynamoDBPersistEventError (cognitive 19) packages/library/src/internal/dynamodb-persist-event-error.ts
  • Cognitive Complexity · dynamodb-event-store-input-validation.validateDynamoDBEventStoreInput (cognitive 18) packages/library/src/internal/dynamodb-event-store-input-validation.ts
  • Cognitive Complexity · dynamodb-latest-snapshot-restore.restoreDynamoDBLatestSnapshot (cognitive 18) packages/library/src/internal/dynamodb-latest-snapshot-restore.ts
  • Cognitive Complexity · spanner-read-write-transaction.runSpannerReadWriteTransaction (cognitive 18) packages/library/src/internal/spanner-read-write-transaction.ts
  • Cognitive Complexity · spanner-persist-event.persistSpannerEvent (cognitive 18) packages/library/src/internal/spanner-persist-event.ts
  • Cognitive Complexity · dynamodb-stored-integer.dynamoDBStoredInteger (cognitive 17) packages/library/src/internal/dynamodb-stored-integer.ts
  • God Classes · FunctionTooLong: memory-event-store.createMemoryEventStoreInternal packages/library/src/internal/memory-event-store.ts
  • God Classes · FunctionTooLong: dynamodb-persist-event.persistDynamoDBEvent packages/library/src/internal/dynamodb-persist-event.ts
  • God Classes · FunctionTooLong: spanner-persist-event.persistSpannerEvent packages/library/src/internal/spanner-persist-event.ts
  • God Classes · FunctionTooLong: spanner-migration-plan.restoreAggregates packages/library/src/internal/spanner-migration-plan.ts
  • Code Coverage · Low coverage: packages/library/src/event-store.ts packages/library/src/event-store.ts
  • Code Coverage · Low coverage: packages/library/src/internal/dynamodb-batch-get.ts packages/library/src/internal/dynamodb-batch-get.ts
  • Code Coverage · Low coverage: packages/library/src/internal/dynamodb-event-envelope-restore.ts packages/library/src/internal/dynamodb-event-envelope-restore.ts
  • Code Coverage · Low coverage: packages/library/src/internal/dynamodb-event-store-input-validation.ts packages/library/src/internal/dynamodb-event-store-input-validation.ts
  • Code Coverage · Low coverage: packages/library/src/internal/dynamodb-event-store.ts packages/library/src/internal/dynamodb-event-store.ts
  • Code Coverage · Low coverage: packages/library/src/internal/dynamodb-get-events.ts packages/library/src/internal/dynamodb-get-events.ts
  • Code Coverage · Low coverage: packages/library/src/internal/dynamodb-get-latest-snapshot.ts packages/library/src/internal/dynamodb-get-latest-snapshot.ts
  • Code Coverage · Low coverage: packages/library/src/internal/dynamodb-item-size.ts packages/library/src/internal/dynamodb-item-size.ts
  • Code Coverage · Low coverage: packages/library/src/internal/dynamodb-latest-snapshot-restore.ts packages/library/src/internal/dynamodb-latest-snapshot-restore.ts
  • Code Coverage · Low coverage: packages/library/src/internal/dynamodb-persist-event-error.ts packages/library/src/internal/dynamodb-persist-event-error.ts
  • Code Coverage · Low coverage: packages/library/src/internal/dynamodb-persist-event.ts packages/library/src/internal/dynamodb-persist-event.ts
  • Code Coverage · Low coverage: packages/library/src/internal/dynamodb-snapshot-retention.ts packages/library/src/internal/dynamodb-snapshot-retention.ts
  • Code Coverage · Low coverage: packages/library/src/internal/dynamodb-store-configuration.ts packages/library/src/internal/dynamodb-store-configuration.ts
  • Code Coverage · Low coverage: packages/library/src/internal/dynamodb-stored-integer.ts packages/library/src/internal/dynamodb-stored-integer.ts
  • Code Coverage · Low coverage: packages/library/src/internal/retention-failure-notification.ts packages/library/src/internal/retention-failure-notification.ts
  • Code Coverage · Low coverage: packages/library/src/internal/snapshot-retention-validation.ts packages/library/src/internal/snapshot-retention-validation.ts
  • Code Coverage · Low coverage: packages/library/src/internal/validated-event-store.ts packages/library/src/internal/validated-event-store.ts
  • Code Coverage · Low coverage: packages/library/src/internal/dynamodb-persist-event.ts packages/library/src/internal/dynamodb-persist-event.ts
  • Code Coverage · Low coverage: packages/library/src/internal/spanner-migration-read.ts packages/library/src/internal/spanner-migration-read.ts
  • Code Coverage · Low coverage: packages/library/src/internal/spanner-migration.ts packages/library/src/internal/spanner-migration.ts
  • Test Quality · No assertions: built package uses four real DynamoDB operations and domain restoration packages/tests/e2e/workspace-consumption.test.cjs
  • Churn × Complexity Hotspots · Hotspot: packages/library/src/internal/test/dynamodb-persist-event-observation.ts packages/library/src/internal/test/dynamodb-persist-event-observation.ts
  • Churn × Complexity Hotspots · Hotspot: packages/library/src/internal/test/conformance/conformance-case-executor.ts packages/library/src/internal/test/conformance/conformance-case-executor.ts
  • Churn × Complexity Hotspots · Hotspot: packages/library/src/internal/memory-event-store.ts packages/library/src/internal/memory-event-store.ts
  • Churn × Complexity Hotspots · Hotspot: packages/library/src/internal/test/conformance/conformance-data-loader.ts packages/library/src/internal/test/conformance/conformance-data-loader.ts
  • Churn × Complexity Hotspots · Hotspot: packages/library/src/event-envelope.ts packages/library/src/event-envelope.ts
  • Churn × Complexity Hotspots · Hotspot: .github/create-release-note-body.py .github/create-release-note-body.py
  • Boundary Type-Coupling · Cross-context type Result (library → examples) packages/examples/src/run-user-account-example.ts
  • Boundary Type-Coupling · Cross-context type EventStoreError (library → examples) packages/examples/src/run-user-account-example.ts
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Supply-chain Provenance & Signing · REDACTED
  • Supply-chain Provenance & Signing · REDACTED
  • Code Duplication · Duplicated block with local edits (72 matched lines × 2 locations) packages/library/src/internal/dynamodb-event-store-input-validation.ts
  • Code Duplication · Duplicated block with local edits (62 matched lines × 2 locations) packages/library/src/internal/spanner-get-events.ts
  • Code Duplication · Duplicated block with local edits (35 matched lines × 2 locations) packages/library/src/event-envelope.ts
  • Code Duplication · Duplicated block with local edits (33 matched lines × 2 locations) packages/library/src/internal/memory-storage-records.ts
  • Code Duplication · Duplicated block (29 lines × 2 locations) packages/library/src/internal/dynamodb-event-envelope-restore.ts
  • Code Duplication · Duplicated block (21 lines × 2 locations) packages/library/src/internal/dynamodb-latest-snapshot-restore.ts
  • Code Duplication · Duplicated block (19 lines × 2 locations) packages/library/src/internal/event-store-input-validation.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) packages/library/src/event-envelope.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) packages/library/src/internal/memory-event-store.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) packages/library/src/internal/dynamodb-persist-event.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/library/src/internal/dynamodb-persist-event.ts
  • Code Duplication · Duplicated block (11 lines × 2 locations) packages/library/src/internal/memory-storage-records.ts
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/library/src/internal/validated-event-store.ts
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/library/src/internal/dynamodb-get-events.ts
  • Code Duplication · Duplicated block with local edits (6 matched lines × 2 locations) packages/library/src/internal/dynamodb-stored-integer.ts
  • Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 55, cognitive 83) packages/library/src/internal/test/dynamodb-persist-event-observation.ts
  • Cyclomatic Complexity · Complex function checkConstraints (cyclomatic 51, cognitive 66) packages/library/src/internal/test/conformance/conformance-dynamodb-observation.ts
  • Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 34, cognitive 64) packages/library/src/internal/memory-retention.test.ts
  • Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 32, cognitive 54) packages/library/src/internal/test/conformance/conformance-case-executor.ts
  • Cyclomatic Complexity · Complex function reconcileSpannerStoreConfiguration (cyclomatic 26, cognitive 32) packages/library/src/internal/spanner-store-configuration.ts
  • Cyclomatic Complexity · Complex function validateDynamoDBEventStoreInput (cyclomatic 23, cognitive 21) packages/library/src/internal/dynamodb-event-store-input-validation.ts
  • Cyclomatic Complexity · Complex function validateEventStoreInput (cyclomatic 22, cognitive 23) packages/library/src/internal/event-store-input-validation.ts
  • Cyclomatic Complexity · Complex function retainDynamoDBSnapshots (cyclomatic 19, cognitive 34) packages/library/src/internal/dynamodb-snapshot-retention.ts
  • Cyclomatic Complexity · Complex function after (cyclomatic 19, cognitive 28) packages/library/src/internal/test/conformance/conformance-dynamodb-faults.ts
  • Cyclomatic Complexity · Complex function restoreDynamoDBLatestSnapshot (cyclomatic 19, cognitive 18) packages/library/src/internal/dynamodb-latest-snapshot-restore.ts
  • Cyclomatic Complexity · Complex function validateSnapshotRetention (cyclomatic 18, cognitive 16) packages/library/src/internal/snapshot-retention-validation.ts
  • Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 16, cognitive 12) packages/library/src/internal/test/conformance/conformance-data-loader.ts
  • Cyclomatic Complexity · Complex function compareExpectation (cyclomatic 15, cognitive 19) packages/library/src/internal/test/conformance/conformance-expectation.ts
  • Cyclomatic Complexity · Complex function create (cyclomatic 15, cognitive 15) packages/library/src/event-envelope.ts
  • Cyclomatic Complexity · Complex function phase (cyclomatic 15, cognitive 14) packages/library/src/internal/test/conformance/conformance-dynamodb-faults.ts
  • Cyclomatic Complexity · Complex function validateSpannerEventStoreInput (cyclomatic 15, cognitive 13) packages/library/src/internal/spanner-event-store-input-validation.ts
  • Cyclomatic Complexity · Complex function persistDynamoDBEvent (cyclomatic 14, cognitive 17) packages/library/src/internal/dynamodb-persist-event.ts
  • Cyclomatic Complexity · Complex function checkReadEventPages (cyclomatic 14, cognitive 14) packages/library/src/internal/test/conformance/conformance-dynamodb-observation.ts
  • Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 14, cognitive 13) packages/library/src/internal/spanner-get-latest-snapshot.ts
  • Cyclomatic Complexity · Complex function readMigrationInput (cyclomatic 14, cognitive 13) packages/library/src/internal/spanner-migration.ts
  • Large Files · packages/library/src/internal/spanner-migration-plan.ts: 642 lines of code packages/library/src/internal/spanner-migration-plan.ts
  • Exception handling · Swallowed exception (empty catch) packages/library/src/internal/spanner-read-write-transaction.ts
  • Exception handling · Swallowed exception (empty catch) packages/library/src/internal/retention-failure-notification.ts
  • Exception handling · Swallowed exception (empty catch) packages/library/src/internal/memory-storage-records.ts
  • Visual & motion safety · Animation without a prefers-reduced-motion guard .agents/skills/skill-forge/eval-viewer/viewer.html
  • Visual & motion safety · Animation without a prefers-reduced-motion guard .claude/skills/skill-forge/eval-viewer/viewer.html

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 31 findings

These 31 critical or serious findings were in the previous survey, on 8 October 2026, and are gone from this one.

  • Cyclomatic Complexity · spanner-event-store.createSpannerEventStore (cyclomatic 59) packages/library/src/internal/spanner-event-store.ts
  • Cyclomatic Complexity · dynamodb-event-store.createDynamoDBEventStore (cyclomatic 39) packages/library/src/internal/dynamodb-event-store.ts
  • Cyclomatic Complexity · dynamodb-snapshot-retention-executor.createDynamoDBSnapshotRetentionExecutor (cyclomatic 37) packages/library/src/internal/dynamodb-snapshot-retention-executor.ts
  • Cognitive Complexity · spanner-event-store.createSpannerEventStore (cognitive 61) packages/library/src/internal/spanner-event-store.ts
  • Cognitive Complexity · dynamodb-snapshot-retention-executor.createDynamoDBSnapshotRetentionExecutor (cognitive 53) packages/library/src/internal/dynamodb-snapshot-retention-executor.ts
  • Cognitive Complexity · dynamodb-event-store.createDynamoDBEventStore (cognitive 39) packages/library/src/internal/dynamodb-event-store.ts
  • Cognitive Complexity · memory-event-store.createMemoryEventStore (cognitive 16) packages/library/src/internal/memory-event-store.ts
  • God Classes · FunctionTooLong: spanner-event-store.createSpannerEventStore packages/library/src/internal/spanner-event-store.ts
  • God Classes · FunctionTooLong: dynamodb-event-store.createDynamoDBEventStore packages/library/src/internal/dynamodb-event-store.ts
  • God Classes · FunctionTooLong: dynamodb-snapshot-retention-executor.createDynamoDBSnapshotRetentionExecutor packages/library/src/internal/dynamodb-snapshot-retention-executor.ts
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Supply-chain Provenance & Signing REDACTED
  • Supply-chain Provenance & Signing REDACTED
  • Code Duplication · Duplicated block (38 lines × 2 locations) packages/library/src/internal/dynamodb-event-store.ts
  • Code Duplication · Duplicated block with local edits (34 matched lines × 2 locations) packages/library/src/next/event-envelope.ts
  • Code Duplication · Duplicated block (17 lines × 2 locations) packages/library/src/internal/dynamodb-event-store.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) packages/library/src/internal/dynamodb-event-store.ts
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/library/src/internal/dynamodb-event-store.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/library/src/next/internal/validated-event-store.ts
  • Code Duplication · Duplicated block (11 lines × 2 locations) packages/library/src/internal/dynamodb-event-store.ts
  • Code Duplication · Duplicated block (11 lines × 2 locations) packages/library/src/internal/spanner-event-store.ts
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/library/src/internal/dynamodb-event-store.ts
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/library/src/internal/spanner-event-store.ts
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/library/src/internal/dynamodb-event-store.ts
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/library/src/internal/dynamodb-event-store.ts
  • Cyclomatic Complexity · Complex function isUserAccountCreatedDataJson (cyclomatic 18, cognitive 12) packages/library/src/internal/test/user-account-created.ts
  • Cyclomatic Complexity · Complex function isUserAccountRenamedDataJson (cyclomatic 18, cognitive 12) packages/library/src/internal/test/user-account-renamed.ts
  • Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 15, cognitive 11) packages/library/src/next/internal/test/conformance/conformance-data-loader.ts
  • Cyclomatic Complexity · Complex function userAccountEventFromJSON (cyclomatic 14, cognitive 14) packages/library/src/internal/test/user-account-event.ts
  • Cyclomatic Complexity · Complex function create (cyclomatic 13, cognitive 13) packages/library/src/next/event-envelope.ts
  • Cyclomatic Complexity · Complex function isSeqNrPath (cyclomatic 13, cognitive 9) packages/library/src/next/internal/test/conformance/conformance-number-paths.ts
Rebuild cost: about €38,000 · Estimate
Cost to rebuild€13,000 to €63,000, for 210 to 666 hours of work, about 0.3 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 49. 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.
SizeSmall: 5,636 lines of product code

How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Reconcile the README with reality: conformance/README.md links to `../docs/spec/core-contract.md`, but `docs/spec/core-contract.md` does not exist; conformance/README.md links to `../docs/spec/storage/dynamodb.md`, but `docs/spec/storage/dynamodb.md` does not exist; conformance/README.md links to `../docs/spec/storage/memory.md`, but `docs/spec/storage/memory.md` does not exist; conformance/README.md links to `../docs/spec/storage/sqlite.md`, but `docs/spec/storage/sqlite.md` does not exist; conformance/README.md links to `../docs/spec/storage/spanner.md`, but `docs/spec/storage/spanner.md` does not exist.
Raises the score by about 7 points · Medium effort · Documentation accuracy
2
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.
Raises the score by about 6 points · Medium effort · Architecture documentation
3
Resolve the 2 Documentation finding(s) in Documentation Quality — start with MIGRATION_GUIDE_3.0.ja.md, MIGRATION_GUIDE_4.0.md.
Raises the score by about 2 points · Low effort · Documentation Quality

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €38,000 to build again, about 0.3 person-years of work. Its weakest lens is Maturity, at 38 (Weak). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.
Based on: the rebuild estimate · the Maturity grade · how much each lens counts
What to do: Start with the Maturity actions in Top priorities.
If you do one thing first · First action
Reconcile the README with reality: conformance/README.md links to `../docs/spec/core-contract.md`, but `docs/spec/core-contract.md` does not exist; conformance/README.md links to `../docs/spec/storage/dynamodb.md`, but `docs/spec/storage/dynamodb.md` does not exist; conformance/README.md links to `../docs/spec/storage/memory.md`, but `docs/spec/storage/memory.md` does not exist; conformance/README.md links to `../docs/spec/storage/sqlite.md`, but `docs/spec/storage/sqlite.md` does not exist; conformance/README.md links to `../docs/spec/storage/spanner.md`, but `docs/spec/storage/spanner.md` does not exist. Of all the actions in this report, it raises the score most for the work it takes: about 7 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.9 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 3% to 6% on every change. The history of the code shows how much it changes: about 58,937 lines over the last 90 days, which is about 239,022 lines a year. At that pace, the extra work comes to an estimated 16.7 to 100.4 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

54 modules, with 42 dependencies between them. Every module uses only modules listed above it, so there are no loops.

The table shows the 40 modules with the most connections; 14 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 .agents.skills.skill-forge.eval-viewer2 .agents.skills.skill-forge.eval-viewer.generate_review3 .agents.skills.skill-forge.scripts4 .github5 packages.examples.src.domain6 packages.examples.src.domain.user-account-event7 packages.library.scripts8 packages.library.src.contract-rule9 packages.library.src.event-store-error10 packages.library.src.internal.spanner-migration-plan11 packages.library.src.internal.test.api-surface12 packages.library.src.internal.test.api-surface.fixtures.constrained-type-parameter13 packages.library.src.internal.test.api-surface.fixtures.events-return-payloads14 packages.library.src.internal.test.api-surface.fixtures.input-manifest-undefined15 packages.library.src.internal.test.api-surface.fixtures.interface-envelope16 packages.library.src.internal.test.api-surface.fixtures.missing-occurred-at17 packages.library.src.internal.test.conformance.conformance-backend18 packages.library.src.internal.test.conformance.conformance-fault-registry19 packages.library.src.internal.test.conformance.conformance-json-value20 packages.library.src.internal.test.conformance.conformance-outcome21 packages.library.src.internal.test.dynamodb-local22 packages.library.src.internal.test.dynamodb-persist-event-observation23 packages.library.src.internal.test.spanner-emulator24 packages.library.src.result25 packages.library.src.spanner-migration-failure26 packages.examples.src27 packages.library.src28 packages.library.src.internal29 packages.library.src.internal.spanner-transaction-rejection30 packages.library.src.internal.test31 packages.library.src.internal.test.conformance.conformance-dynamodb-faults32 packages.library.src.internal.test.conformance.conformance-dynamodb-observation33 packages.library.src.internal.test.conformance.conformance-store34 packages.library.src.internal.test.conformance.conformance-store-binding35 packages.library.src.internal.test.conformance.conformance-hooks36 packages.library.src.internal.test.conformance.conformance-public-binding37 packages.library.src.internal.test.conformance38 packages.library.src.internal.test.conformance.conformance-dynamodb-binding39 packages.library.src.internal.test.conformance.conformance-memory-binding40 packages.library.src.internal.test.conformance.conformance-spanner-binding
1 .agents.skills.skill-forge.eval-viewer
2 .agents.skills.skill-forge.eval-viewer.generate_review
3 .agents.skills.skill-forge.scripts
4 .github
5 packages.examples.src.domain
6 packages.examples.src.domain.user-account-event
7 packages.library.scripts
8 packages.library.src.contract-rule
9 packages.library.src.event-store-error
10 packages.library.src.internal.spanner-migration-plan
11 packages.library.src.internal.test.api-surface
12 packages.library.src.internal.test.api-surface.fixtures.constrained-type-parameter
13 packages.library.src.internal.test.api-surface.fixtures.events-return-payloads
14 packages.library.src.internal.test.api-surface.fixtures.input-manifest-undefined
15 packages.library.src.internal.test.api-surface.fixtures.interface-envelope
16 packages.library.src.internal.test.api-surface.fixtures.missing-occurred-at
17 packages.library.src.internal.test.conformance.conformance-backend
18 packages.library.src.internal.test.conformance.conformance-fault-registry
19 packages.library.src.internal.test.conformance.conformance-json-value
20 packages.library.src.internal.test.conformance.conformance-outcome
21 packages.library.src.internal.test.dynamodb-local
22 packages.library.src.internal.test.dynamodb-persist-event-observation
23 packages.library.src.internal.test.spanner-emulator
24 packages.library.src.result
25 packages.library.src.spanner-migration-failure
26 packages.examples.src111
27 packages.library.src11
28 packages.library.src.internal286291
29 packages.library.src.internal.spanner-transaction-rejection1
30 packages.library.src.internal.test111
31 packages.library.src.internal.test.conformance.conformance-dynamodb-faults11
32 packages.library.src.internal.test.conformance.conformance-dynamodb-observation11
33 packages.library.src.internal.test.conformance.conformance-store1
34 packages.library.src.internal.test.conformance.conformance-store-binding11
35 packages.library.src.internal.test.conformance.conformance-hooks111
36 packages.library.src.internal.test.conformance.conformance-public-binding11111111
37 packages.library.src.internal.test.conformance2112121
38 packages.library.src.internal.test.conformance.conformance-dynamodb-binding11
39 packages.library.src.internal.test.conformance.conformance-memory-binding1
40 packages.library.src.internal.test.conformance.conformance-spanner-binding11
Uses a module listed above itPart of a loopThe module itself
1 .agents.skills.skill-forge.eval-viewer2 .agents.skills.skill-forge.eval-viewer.generate_review3 .agents.skills.skill-forge.scripts4 .github5 packages.examples.src.domain6 packages.examples.src.domain.user-account-event7 packages.library.scripts8 packages.library.src.contract-rule9 packages.library.src.event-store-error10 packages.library.src.internal.spanner-migration-plan11 packages.library.src.internal.test.api-surface12 packages.library.src.internal.test.api-surface.fixtures.constrained-type-parameter13 packages.library.src.internal.test.api-surface.fixtures.events-return-payloads14 packages.library.src.internal.test.api-surface.fixtures.input-manifest-undefined15 packages.library.src.internal.test.api-surface.fixtures.interface-envelope16 packages.library.src.internal.test.api-surface.fixtures.missing-occurred-at17 packages.library.src.internal.test.conformance.conformance-backend18 packages.library.src.internal.test.conformance.conformance-fault-registry19 packages.library.src.internal.test.conformance.conformance-json-value20 packages.library.src.internal.test.conformance.conformance-outcome21 packages.library.src.internal.test.dynamodb-local22 packages.library.src.internal.test.dynamodb-persist-event-observation23 packages.library.src.internal.test.spanner-emulator24 packages.library.src.result25 packages.library.src.spanner-migration-failure26 packages.examples.src27 packages.library.src28 packages.library.src.internal29 packages.library.src.internal.spanner-transaction-rejection30 packages.library.src.internal.test31 packages.library.src.internal.test.conformance.conformance-dynamodb-faults32 packages.library.src.internal.test.conformance.conformance-dynamodb-observation33 packages.library.src.internal.test.conformance.conformance-store34 packages.library.src.internal.test.conformance.conformance-store-binding35 packages.library.src.internal.test.conformance.conformance-hooks36 packages.library.src.internal.test.conformance.conformance-public-binding37 packages.library.src.internal.test.conformance38 packages.library.src.internal.test.conformance.conformance-dynamodb-binding39 packages.library.src.internal.test.conformance.conformance-memory-binding40 packages.library.src.internal.test.conformance.conformance-spanner-binding.agents.skills.skill-forge.eval-viewer1.agents.skills.skill-forge.eval-viewer.generate_review2.agents.skills.skill-forge.scripts3.github4packages.examples.src.domain5packages.examples.src.domain.user-account-event6packages.library.scripts7packages.library.src.contract-rule8packages.library.src.event-store-error9packages.library.src.internal.spanner-migration-plan10packages.library.src.internal.test.api-surface11packages.library.src.internal.test.api-surface.fixtures.constrained-type-parameter12packages.library.src.internal.test.api-surface.fixtures.events-return-payloads13packages.library.src.internal.test.api-surface.fixtures.input-manifest-undefined14packages.library.src.internal.test.api-surface.fixtures.interface-envelope15packages.library.src.internal.test.api-surface.fixtures.missing-occurred-at16packages.library.src.internal.test.conformance.conformance-backend17packages.library.src.internal.test.conformance.conformance-fault-registry18packages.library.src.internal.test.conformance.conformance-json-value19packages.library.src.internal.test.conformance.conformance-outcome20packages.library.src.internal.test.dynamodb-local21packages.library.src.internal.test.dynamodb-persist-event-observation22packages.library.src.internal.test.spanner-emulator23packages.library.src.result24packages.library.src.spanner-migration-failure25packages.examples.src26packages.library.src27packages.library.src.internal28packages.library.src.internal.spanner-transaction-rejection29packages.library.src.internal.test30packages.library.src.internal.test.conformance.conformance-dynamodb-faults31packages.library.src.internal.test.conformance.conformance-dynamodb-observation32packages.library.src.internal.test.conformance.conformance-store33packages.library.src.internal.test.conformance.conformance-store-binding34packages.library.src.internal.test.conformance.conformance-hooks35packages.library.src.internal.test.conformance.conformance-public-binding36packages.library.src.internal.test.conformance37packages.library.src.internal.test.conformance.conformance-dynamodb-binding38packages.library.src.internal.test.conformance.conformance-memory-binding39packages.library.src.internal.test.conformance.conformance-spanner-binding40111112862911111111111111111111111211212111111+14 more modules (most-connected shown)

At a glance — Code Health · 80% · Adequate · gated by D2 ·

The Good
D3 · TypeScript God Classes 7.4 D4 · TypeScript Code Duplication 9.7 D17 · TypeScript Explicit Debt 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 10.0 R1 · React / TS Type Safety 9.8 R10 · React / TS Code Duplication 8.6 R2 · React / TS Cyclomatic Complexity 9.3 R3 · React / TS Large Files 9.5 R7 · React / TS Dead Code 10.0 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X5 · Repo Nullable reference types 9.9
The Bad
D1 · TypeScript Cyclomatic Complexity 5.8 X3 · Repo Exception handling 6.4
The Ugly
D2 · TypeScript Cognitive Complexity 2.0

At a glance — Architecture · 99% · Exemplary ·

The Good
D6 · TypeScript Cohesion (LCOM4) 10.0 D22 · TypeScript Internal API Consistency 10.0 D23 · TypeScript Boundary Type-Coupling 9.5 D26 · TypeScript Project Cohesion 10.0 D35 · TypeScript Change Coupling 9.8 AX10 · Repo Code composition 10.0 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX6 · Repo Interface segregation 10.0 AX8 · Repo Test isolation 10.0 R9 · React / TS Circular Imports 10.0

At a glance — Maturity · 38% · Weak · gated by M2, M4 ·

The Good
D15 · TypeScript Churn × Complexity Hotspots 9.8 D19 · TypeScript Documentation Quality 9.0 D21 · TypeScript Naming Consistency 10.0 D34 · TypeScript Knowledge Freshness 10.0 M3 · Repo Folder & project structure 10.0
The Bad
M1 · Repo Documentation (README) 5.0
The Ugly
M2 · Repo Architecture documentation 2.0 M4 · Repo Documentation accuracy 0.0

At a glance — Readiness · 64% · Adequate · gated by P3 ·

The Good
D9 · TypeScript Test Distribution 9.9 D10 · TypeScript Test Quality 10.0 D12 · TypeScript Dependency Hygiene 9.9 D13 · TypeScript Secret Scanning 10.0 D14 · TypeScript License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P9 · Repo Domain vs controller coverage 9.9 R4 · React / TS Test Coverage 9.8 R6 · React / TS Tooling 10.0 R8 · React / TS Dependency Hygiene 10.0
The Bad
D8 · TypeScript Code Coverage 6.7 P4 · Repo Deployment & Rollback 5.0 P6 · Repo Release Hygiene 5.0
The Ugly
P3 · Repo Security & performance tooling 3.0

At a glance — Security · 52% · Adequate · gated by D29, D36 ·

The Good
D28 · TypeScript Secrets (history) 10.0 D43 · TypeScript Malicious Dependencies 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0
The Bad
D30 · TypeScript Dependency Vulnerabilities 5.8
The Ugly
D29 · TypeScript Static Analysis (SAST) 0.1 D36 · TypeScript Supply-chain Provenance & Signing 0.0

At a glance — Domain Modelling · 100% · Exemplary ·

The Good
DM6 · Repo Domain ↔ infrastructure boundary 10.0 DM9 · Repo Scattered domain decisions 10.0

At a glance — Accessibility · 48% · Weak ·

The Bad
AC2 · Repo Forms & labels 5.3 AC3 · Repo Page structure 5.1 AC6 · Repo Visual & motion safety 5.6
The Ugly
AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 100% · Exemplary ·

The Good
PF3 · Repo Async & latency hygiene 10.0

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A05:2025 — Injection37High / Critical
A03:2025 — Software Supply Chain Failures18High / Critical

Roadmap

First, reconcile the README with reality by fixing broken links and removing references to non-existent specification files. Next, establish a clear record of design decisions by creating an ADR folder and expand the main README with a getting-started guide, architecture overview, and project map. Then, resolve the identified documentation quality issues, starting with the migration guides. Finally, enforce accessibility by enabling linting rules, adding test assertions, and gating checks in CI.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Reconcile the README with reality: conformance/README.md links to `../docs/spec/core-contract.md`, but `docs/spec/core-contract.md` does not exist; conformance/README.md links to `../docs/spec/storage/dynamodb.md`, but `docs/spec/storage/dynamodb.md` does not exist; conformance/README.md links to `../docs/spec/storage/memory.md`, but `docs/spec/storage/memory.md` does not exist; conformance/README.md links to `../docs/spec/storage/sqlite.md`, but `docs/spec/storage/sqlite.md` does not exist; conformance/README.md links to `../docs/spec/storage/spanner.md`, but `docs/spec/storage/spanner.md` does not exist.+6.8 ptsMediumDocumentation accuracy
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.+5.9 ptsMediumArchitecture documentation
Resolve the 2 Documentation finding(s) in Documentation Quality — start with MIGRATION_GUIDE_3.0.ja.md, MIGRATION_GUIDE_4.0.md.+2.3 ptsLowDocumentation Quality
Expand the README with getting-started, architecture overview and a project map.+4.2 ptsMediumDocumentation (README)
Enforce accessibility in the toolchain you already use: enable Biome's a11y rule group in your biome.json `linter.rules` (it is off whenever `recommended` is false and the group is unlisted), then assert with jest-axe in tests, then gate axe/pa11y/Lighthouse in CI.+2.1 ptsMediumA11y enforcement
Resolve the 17 REDACTED finding(s) charged to Static Analysis (SAST) — the other 10 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once.+1.7 ptsMediumStatic Analysis (SAST)
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.+1.5 ptsMediumPage structure
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.+1.4 ptsMediumForms & labels

File quality

Per-file score 0–10 — a quality signature. Of 55 files carrying findings, judged against the Production bar: 7% slop · 62% mixed · 31% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED1.4SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
packages/library/src/internal/dynamodb-event-store-input-validation.ts6.3MixedCyclomatic Complexity: dynamodb-event-store-input-validation.validateDynamoDBEventStoreInput (cyclomatic 23)
packages/library/src/internal/dynamodb-latest-snapshot-restore.ts6.3MixedCyclomatic Complexity: dynamodb-latest-snapshot-restore.restoreDynamoDBLatestSnapshot (cyclomatic 19)
packages/library/src/internal/dynamodb-persist-event.ts6.3MixedGod Classes: FunctionTooLong: dynamodb-persist-event.persistDynamoDBEvent
REDACTED6.9MixedDependency Vulnerabilities: Medium CVE: REDACTED
packages/library/src/internal/snapshot-retention-validation.ts7.0MixedCyclomatic Complexity: snapshot-retention-validation.validateSnapshotRetention (cyclomatic 18)
packages/library/src/internal/dynamodb-snapshot-retention.ts7.0MixedCognitive Complexity: dynamodb-snapshot-retention.retainDynamoDBSnapshots (cognitive 29)
packages/library/src/internal/dynamodb-persist-event-error.ts7.0MixedCognitive Complexity: dynamodb-persist-event-error.classifyDynamoDBPersistEventError (cognitive 19)
packages/library/src/internal/dynamodb-stored-integer.ts7.0MixedCognitive Complexity: dynamodb-stored-integer.dynamoDBStoredInteger (cognitive 17)
packages/library/src/internal/dynamodb-event-store.ts7.0MixedCode Coverage: Low coverage: packages/library/src/internal/dynamodb-event-store.ts
.agents/skills/skill-forge/scripts/run_eval_claude.py7.2MixedCyclomatic Complexity: run_eval_claude.run_single_query_claude (cyclomatic 34)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 41

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.

Serious — 134

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.

Minor — 51

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 11

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

Watchdog 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. 75 of 79 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 1.0 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 79 dimensions across the health lenses
D1D2D3D4D6D8D9D10D12D13D14D15D17D19D21D22D23D26D28D29D30D34D35D36D43AC2AC3AC6AC7AX10AX3AX4AX6AX8DM6DM9GD1IC1M1M2M3M4P1P10P3P4P6P9PF3R1R10R2R3R4R6R7R8R9X1X12X13X14X15X16X17X18X19X21X22X23X24X25X26X27X28X29X3X30X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. 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, 214 of 226 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. 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.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a163f2-c726-7e3f-bbf6-c4147b4aa7bd.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D11 Test Reliability — evaluation did not complete — Test Reliability not included (check did not complete) — excluded from the score.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 3378 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
  • D27 Navigability — not measured this run — Watchdog 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D28 Secrets (history) — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A filesystem error ended D28's config-credential walk (FileNotFoundException: Could not find file '.mcp.json'.); configs after that point were not read for credential bindings.
  • D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/library/src/internal/dynamodb-event-store-input-validation.ts`, `packages/library/src/internal/dynamodb-event-store.ts`, `packages/library/src/internal/dynamodb-get-events.ts`, `packages/library/src/internal/dynamodb-persist-event.ts`, `packages/library/src/internal/spanner-event-store-input-validation.ts`, … (+5 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D44 Platform End-of-Life — not measured this run — Watchdog 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.
  • AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 4 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • C1 Data Protection — not measured this run — Watchdog 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. '@aws-sdk/client-dynamodb' is imported (packages/library/src/dynamodb-event-store-input.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • C3 Audit Trail — not measured this run — Watchdog 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. '@aws-sdk/client-dynamodb' is imported (packages/library/src/dynamodb-event-store-input.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • C4 Data Retention — not measured this run — Watchdog 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. '@aws-sdk/client-dynamodb' is imported (packages/library/src/dynamodb-event-store-input.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • C5 Data-Subject Rights — not measured this run — Watchdog 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. '@aws-sdk/client-dynamodb' is imported (packages/library/src/dynamodb-event-store-input.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. The filesystem refused the listing or the read of: .mcp.json. Every other path was read.
  • S1 Web-Security Posture — not measured this run — Watchdog 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. 76 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation and obsolete TLS versions, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
  • X4 Structured logging — not measured this run — Watchdog 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.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • 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.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
  • D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • 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.

The LLM boundary

LLM-set scores this run (4): D19, D21, D22, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity5.8 / 10Adequate✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 5.8 / 10 · rule-coverage 100% · ceiling Prevented

17 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was run_eval_claude.run_single_query_claude at 34.

run_eval_claude.run_single_query_claude (cyclomatic 34).agents/skills/skill-forge/scripts/run_eval_claude.py:48
run_loop.run_loop (cyclomatic 28).agents/skills/skill-forge/scripts/run_loop.py:47
memory-event-store.createMemoryEventStoreInternal (cyclomatic 26)packages/library/src/internal/memory-event-store.ts:30
spanner-store-configuration.reconcileSpannerStoreConfiguration (cyclomatic 25)packages/library/src/internal/spanner-store-configuration.ts:109
aggregate_benchmark.load_run_results (cyclomatic 24).agents/skills/skill-forge/scripts/aggregate_benchmark.py:70

+ 12 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with run_eval_claude.run_single_query_claude (cyclomatic 34). — Refactoring it lifts Cyclomatic Complexity from 5.8 to about 6.2/10.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity2.0 / 10Critical✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 2.0 / 10 · rule-coverage 100% · ceiling Prevented

21 method(s) exceeded the cognitive complexity threshold of 15; the worst was run_eval_claude.run_single_query_claude at 93.

run_eval_claude.run_single_query_claude (cognitive 93).agents/skills/skill-forge/scripts/run_eval_claude.py:48
aggregate_benchmark.load_run_results (cognitive 61).agents/skills/skill-forge/scripts/aggregate_benchmark.py:70
run_loop.run_loop (cognitive 55).agents/skills/skill-forge/scripts/run_loop.py:47
generate_review.build_run (cognitive 44).agents/skills/skill-forge/eval-viewer/generate_review.py:85
generate_report.generate_html (cognitive 40).agents/skills/skill-forge/scripts/generate_report.py:16

+ 16 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with run_eval_claude.run_single_query_claude (cognitive 93), aggregate_benchmark.load_run_results (cognitive 61). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 2.0 to about 3.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
  2. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes7.4 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 7.4 / 10 · rule-coverage 100% · ceiling Prevented

4 over-large unit(s) detected — types, modules or files that carry too much.

FunctionTooLong: memory-event-store.createMemoryEventStoreInternal · ×4packages/library/src/internal/memory-event-store.ts:30

What to do

  1. Resolve the 4 FunctionTooLong finding(s) in God Classes — start with memory-event-store.ts, dynamodb-persist-event.ts, spanner-persist-event.ts. — One of this dimension's main actionable groups (4 warning-level).
  2. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication9.7 / 10Stronggated by 4 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Verified

4 duplicated block group(s) detected. Measured on part of this repository only: .ts (99% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.

Duplicated block (29 lines × 2).agents/skills/skill-forge/scripts/run_eval_claude.py:108
Duplicated block (11 lines × 2).agents/skills/skill-forge/scripts/run_eval_claude.py:204
Duplicated block (10 lines × 2).agents/skills/skill-forge/scripts/run_eval.py:160
Duplicated block (6 lines × 2).agents/skills/skill-forge/scripts/run_eval.py:149

What to do

  1. Resolve the 1 Duplicated block (29 lines × 2) finding(s) in Code Duplication — start with run_eval_claude.py. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with run_eval_claude.py. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with run_eval.py. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 8 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D8 · Code Coverage6.7 / 10Adequate✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

Maturity: Documented → Verified → Prevented · effective 6.7 / 10 · rule-coverage 100% · ceiling Verified

Line coverage 31.9% — 21 file(s) below 50%. Measured from the JavaScript/TypeScript suite (node:test via `pnpm install --frozen-lockfile --ignore-scripts` in packages/examples/; jest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/library/; node:test via `pnpm install --frozen-lockfile --ignore-scripts` in packages/tests/).

Low coverage: packages/library/src/event-store.ts · ×20packages/library/src/event-store.ts:1

What to do

  1. Resolve the 20 Low coverage finding(s) in Code Coverage — start with dynamodb-persist-event.ts (2), event-store.ts, dynamodb-batch-get.ts. — One of this dimension's main actionable groups (20 warning-level).
  2. Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.

D9 · Test Distribution9.9 / 10Exemplary✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Documented

775 test methods: 772 unit, 0 integration, 0 BDD, 3 e2e. The JavaScript/TypeScript suite contributes 775 `it`/`test` case(s) across 85 test file(s) declaring at least one; its tier split is read from package names and paths only.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality10.0 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 775 tests.

No assertions: built package uses four real DynamoDB operations and domain restorationpackages/tests/e2e/workspace-consumption.test.cjs:6
Mock-dominated test: logs a retention failure and sends the same failure to the additional callbackpackages/library/src/internal/retention-failure-notification.test.ts:5

What to do

  1. Resolve the 1 No assertions finding(s) in Test Quality — start with workspace-consumption.test.cjs. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Mock-dominated test finding(s) in Test Quality — start with retention-failure-notification.test.ts. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.

D12 · Dependency Hygiene9.9 / 10Exemplary✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Verified

1 outdated direct production npm dependency(ies) of 3 graded, 0 pinning defect(s), across 3 package.json (1 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 0 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.

Deprecated: glob · ×2REDACTED:1878
Outdated (npm): @aws-sdk/client-dynamodb

✓ On the Gold path — maintain.

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 3 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 3 production dependency(ies) this repository's committed lockfile resolves, across 1 product package.json manifest(s). Its 21 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under MIT, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.8 / 10Stronggated by 6 serious findings✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: packages/library/src/internal/test/dynamodb-persist-event-observation.ts (5×55=275); packages/library/src/internal/test/conformance/conformance-case-executor.ts (3×32=96); packages/library/src/internal/memory-event-store.ts (2×26=52)

Hotspot: packages/library/src/internal/test/dynamodb-persist-event-observation.ts · ×6packages/library/src/internal/test/dynamodb-persist-event-observation.ts:168

What to do

  1. Resolve the 6 Hotspot finding(s) in Churn × Complexity Hotspots — start with dynamodb-persist-event-observation.ts, conformance-case-executor.ts, memory-event-store.ts. — One of this dimension's main actionable groups (6 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

D17 · Explicit Debt10.0 / 10Exemplary○ Nothing flagged

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 deducted task-comment markers across 5595 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

D19 · Documentation QualityExemplary◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Documented

The repository's root README (event-store-adapter-js) is a clear one-line description of the workspace plus pnpm workspaces and an overview of packages, development commands, and library documentation. The api-surface/README documents its own directory (API surface照合), covering surface.json, js.json, test steps, matching criteria, and conformance testing with detailed test output. The conformance/README is a long data-and-test document describing the expected shape of values/* JSON schemas for 169 value records across 75 rules plus an exhaustive list of what it confirms and does not confirm. packages/examples/README documents its own directory (event-store-adapter-js examples). packages/library/README is the largest single file, covering installation, usage, DynamoDB/Spanner APIs, serializers, migration guidance, and a full architecture review document for the next major version (5.0.0), with an outline of every section present. All four READMEs are well written and scoped to their directories; the only unstructured element is the packages/library/README's own shell block in the middle of its prose. This is a well-structured migration and schema reference documentation set for an adapter library. The READMEs are thin but each document clearly states what it covers (e.g., 'Migration Guide 3.0', 'Cloud Spanner schema') and the outline sections exist; there is no single unshown section to flag as missing, so clipping does not penalize this quality. All documents are internal-facing or reference an external migration guide, which is consistent with the internal-focused review criteria.

Documentation: written for insiders · ×2packages/library/docs/MIGRATION_GUIDE_3.0.ja.md

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Verified

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

D22 · Internal API ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether the internal API surface is consistent and coherent.

Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Verified

0 API inconsistencies across 5 exposed types.

✓ On the Gold path — maintain.

Detailed fixes: d22_recommendation.md.

D23 · Boundary Type-Coupling9.5 / 10Stronggated by 2 serious findings✓ Tool-verified

What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.

Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.

Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.

Maturity: Documented → Verified → Prevented · effective 9.5 / 10 · rule-coverage 100% · ceiling Verified

2 domain type(s) cross context boundaries across 2 contexts.

Cross-context type Result (library → examples)packages/examples/src/run-user-account-example.ts:34
Cross-context type EventStoreError (library → examples)packages/examples/src/run-user-account-example.ts:34

What to do

  1. Resolve the 1 Cross-context type Result (library → examples) finding(s) in Boundary Type-Coupling — start with run-user-account-example.ts. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Cross-context type EventStoreError (library → examples) finding(s) in Boundary Type-Coupling — start with run-user-account-example.ts. — One of this dimension's main actionable groups (1 warning-level).
  3. Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d23_recommendation.md · top locations in Appendix A, every location in findings.md.

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 of 2 build units (npm) flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)0.1 / 10Critical✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 0.1 / 10 · rule-coverage 100% · ceiling Documented

37 finding(s): 0 critical, 34 high, 3 medium, 0 low. 10 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 20 file(s) — `.takt/workflows/ddd-implement.yaml`, `.takt/workflows/ddd-remediation.yaml`, `.takt/workflows/ddd-rust-default.yaml`, `.takt/workflows/ddd-typescript-default.yaml`, `packages/examples/src/domain/user-account-created.ts` (line 1), … (+15 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 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.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 5 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 17 REDACTED finding(s) charged to Static Analysis (SAST) — the other 10 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (27 issue-level, 17 of them charged here).
  2. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
  3. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities5.8 / 10Adequate✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

Maturity: Documented → Verified → Prevented · effective 5.8 / 10 · rule-coverage 100% · ceiling Documented

12 finding(s): 0 critical, 5 high, 5 medium, 2 low.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
  2. Resolve the 5 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 2 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 24 of the 77 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling9.8 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: dynamodb-event-store.ts↔memory-event-store.ts 60%

Change coupling: dynamodb-event-store.ts ↔ memory-event-store.tspackages/library/src/internal/dynamodb-event-store.ts:1

What to do

  1. Resolve the 1 Change coupling finding(s) in Change Coupling — start with dynamodb-event-store.ts. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 1 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AC2 · Forms & labels5.3 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×2) — .agents/skills/skill-forge/eval-viewer/viewer.html:604, .claude/skills/skill-forge/eval-viewer/viewer.html:604

What to do

  • Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure5.1 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×4) — .agents/skills/skill-forge/assets/eval_review.html:2, .agents/skills/skill-forge/eval-viewer/viewer.html:2, .claude/skills/skill-forge/assets/eval_review.html:2, …

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety5.6 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • `.grades-toggle .arrow` moves (`transition: transform 0.15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — .agents/skills/skill-forge/eval-viewer/viewer.html:275, .claude/skills/skill-forge/eval-viewer/viewer.html:275

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.

Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.

Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.

  • No accessibility enforcement found — your Biome config enables no a11y rules and there's no axe/pa11y/Lighthouse in tests or CI. Start by turning on Biome's own a11y rule group to catch issues at author time. What was searched, so you can tell an absence from a miss: the 4 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

  • Enforce accessibility in the toolchain you already use: enable Biome's a11y rule group in your biome.json `linter.rules` (it is off whenever `recommended` is false and the group is unlisted), then assert with jest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

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 cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

DM6 · Domain ↔ infrastructure boundary10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (TypeORM/Prisma/MikroORM/Sequelize/Mongoose) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

DM9 · Scattered domain decisions10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.

Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

M1 · Documentation (README)5.0 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

  • The root README is 89 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.

What to do

  • Expand the README with getting-started, architecture overview and a project map.
  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 2 of 4 project(s) that lack one — worth up to 1 pts.
M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy0.0 / 10Critical◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

  • conformance/README.md links to `../docs/spec/core-contract.md`, but `docs/spec/core-contract.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — conformance/README.md:3
  • conformance/README.md links to `../docs/spec/storage/dynamodb.md`, but `docs/spec/storage/dynamodb.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — conformance/README.md:3
  • conformance/README.md links to `../docs/spec/storage/memory.md`, but `docs/spec/storage/memory.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — conformance/README.md:3
  • conformance/README.md links to `../docs/spec/storage/sqlite.md`, but `docs/spec/storage/sqlite.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — conformance/README.md:3
  • conformance/README.md links to `../docs/spec/storage/spanner.md`, but `docs/spec/storage/spanner.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — conformance/README.md:3
  • conformance/README.md links to `../docs/spec/storage/bigtable.md`, but `docs/spec/storage/bigtable.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — conformance/README.md:3
  • conformance/README.md links to `../docs/spec/storage/hash.md`, but `docs/spec/storage/hash.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — conformance/README.md:3
  • conformance/README.md names `tools/conformance/data.py`, but no file or folder `tools/conformance/data.py` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — conformance/README.md:54
  • conformance/README.md names `tools/conformance/uv.lock`, but no file or folder `tools/conformance/uv.lock` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — conformance/README.md:264
  • conformance/README.md names `tools/conformance/reference_model.py`, but no file or folder `tools/conformance/reference_model.py` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — conformance/README.md:285
  • docs/design/next-major.md names `docs/spec/core-contract.md`, but no file or folder `docs/spec/core-contract.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design/next-major.md:5
  • docs/design/next-major.md names `docs/spec/storage/dynamodb.md`, but no file or folder `docs/spec/storage/dynamodb.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design/next-major.md:5
  • docs/design/next-major.md names `docs/spec/storage/memory.md`, but no file or folder `docs/spec/storage/memory.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design/next-major.md:5
  • docs/design/next-major.md names `docs/plan/implementation-plan.md`, but no file or folder `docs/plan/implementation-plan.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design/next-major.md:5
  • docs/design/next-major.md names `docs/adr/`, but no file or folder `docs/adr` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design/next-major.md:5
  • docs/design/next-major.md names `packages/library/src/next/`, but no file or folder `packages/library/src/next` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design/next-major.md:57
  • docs/design/next-major.md names `src/next/`, but no file or folder `src/next` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design/next-major.md:57
  • docs/design/next-major.md documents the environment variable `DEFAULT_SHARD_COUNT`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design/next-major.md:361
  • docs/design/next-major.md names `packages/library/src/next/internal/memory-event-store.ts`, but no file or folder `packages/library/src/next/internal/memory-event-store.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design/next-major.md:371
  • docs/design/next-major.md names `packages/library/src/next/internal/dynamodb-event-store.ts`, but no file or folder `packages/library/src/next/internal/dynamodb-event-store.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design/next-major.md:396
  • docs/design/next-major.md names `dynamodb.md`, but no file or folder `dynamodb.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design/next-major.md:442
  • docs/design/next-major.md names `dynamodb-snapshot-retention-executor.ts`, but no file or folder `dynamodb-snapshot-retention-executor.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design/next-major.md:463
  • docs/design/next-major.md names `packages/library/src/next/internal/test/conformance/`, but no file or folder `packages/library/src/next/internal/test/conformance` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design/next-major.md:474
  • docs/design/next-major.md names `src/next/internal/test/`, but no file or folder `src/next/internal/test` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design/next-major.md:474
  • docs/design/next-major.md names `tools/conformance/data.py`, but no file or folder `tools/conformance/data.py` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design/next-major.md:490
  • docs/design/next-major.md names `src/next/internal/test/conformance/`, but no file or folder `src/next/internal/test/conformance` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design/next-major.md:645
  • docs/design/next-major.md names `default-serializer.ts`, but no file or folder `default-serializer.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/design/next-major.md:670

What to do

  • Reconcile the README with reality: conformance/README.md links to `../docs/spec/core-contract.md`, but `docs/spec/core-contract.md` does not exist; conformance/README.md links to `../docs/spec/storage/dynamodb.md`, but `docs/spec/storage/dynamodb.md` does not exist; conformance/README.md links to `../docs/spec/storage/memory.md`, but `docs/spec/storage/memory.md` does not exist; conformance/README.md links to `../docs/spec/storage/sqlite.md`, but `docs/spec/storage/sqlite.md` does not exist; conformance/README.md links to `../docs/spec/storage/spanner.md`, but `docs/spec/storage/spanner.md` does not exist.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • 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 33372 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.

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.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

  • 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 Hygiene5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P9 · Domain vs controller coverage9.9 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether test coverage concentrates on the domain (business rules) rather than the trivial web/controller layer — a focus check a generic tool can't make.

Method: Roslyn plus test-execution analysis: domain-layer versus trivial web/controller coverage ratio. Computed metric, deterministic.

What to do

  • Raise domain coverage toward 100% — cover the remaining aggregates / value objects / domain services where the business invariants and costly bugs live.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

R1 · Type Safety9.8 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

What to do

  • Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication8.6 / 10Strong✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.

  • packages/library/src/internal/dynamodb-event-store-input-validation.ts:19 · packages/library/src/internal/spanner-event-store-input-validation.ts:83 — the two spans are one implementation copied and then locally edited — 319 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/library/src/internal/dynamodb-event-store-input-validation.ts:19
  • packages/library/src/internal/spanner-get-events.ts:13 · packages/library/src/internal/spanner-get-latest-snapshot.ts:11 — the two spans are one implementation copied and then locally edited — 367 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/library/src/internal/spanner-get-events.ts:13
  • packages/library/src/event-envelope.ts:11 · packages/library/src/snapshot-envelope.ts:7 — the two spans are one implementation copied and then locally edited — 213 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/library/src/event-envelope.ts:11
  • packages/library/src/internal/memory-storage-records.ts:133 · packages/library/src/internal/retention-failure-notification.ts:4 — the two spans are one implementation copied and then locally edited — 129 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/library/src/internal/memory-storage-records.ts:133
  • packages/library/src/internal/dynamodb-event-envelope-restore.ts:36 · packages/library/src/internal/spanner-get-events.ts:114 — 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/library/src/internal/dynamodb-event-envelope-restore.ts:36
  • packages/library/src/internal/dynamodb-latest-snapshot-restore.ts:90 · packages/library/src/internal/spanner-get-latest-snapshot.ts:97 — 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/library/src/internal/dynamodb-latest-snapshot-restore.ts:90
  • packages/library/src/internal/event-store-input-validation.ts:52 · packages/library/src/internal/memory-storage-input-validation.ts:11 — 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/library/src/internal/event-store-input-validation.ts:52
  • packages/library/src/event-envelope.ts:65 · packages/library/src/snapshot-envelope.ts:40 — 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/library/src/event-envelope.ts:65
  • packages/library/src/internal/memory-event-store.ts:100 · packages/library/src/internal/memory-event-store.ts:149 — 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/library/src/internal/memory-event-store.ts:100
  • packages/library/src/internal/dynamodb-persist-event.ts:37 · packages/library/src/internal/spanner-persist-event.ts:40 — 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/library/src/internal/dynamodb-persist-event.ts:37
  • packages/library/src/internal/dynamodb-persist-event.ts:82 · packages/library/src/internal/dynamodb-persist-event.ts:100 — 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/library/src/internal/dynamodb-persist-event.ts:82
  • packages/library/src/internal/memory-storage-records.ts:246 · packages/library/src/internal/validated-event-store.ts:62 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/library/src/internal/memory-storage-records.ts:246
  • packages/library/src/internal/validated-event-store.ts:85 · packages/library/src/internal/validated-event-store.ts:102 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/library/src/internal/validated-event-store.ts:85
  • packages/library/src/internal/dynamodb-get-events.ts:17 · packages/library/src/internal/spanner-get-events.ts:25 — 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/library/src/internal/dynamodb-get-events.ts:17
  • packages/library/src/internal/dynamodb-stored-integer.ts:32 · packages/library/src/internal/spanner-stored-integer.ts:26 — the two spans are one implementation copied and then locally edited — 51 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/library/src/internal/dynamodb-stored-integer.ts:32

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity9.3 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

  • (anonymous) has cyclomatic complexity 55 and cognitive complexity 83; 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/library/src/internal/test/dynamodb-persist-event-observation.ts:168
  • checkConstraints has cyclomatic complexity 51 and cognitive complexity 66; 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/library/src/internal/test/conformance/conformance-dynamodb-observation.ts:251
  • (anonymous) has cyclomatic complexity 34 and cognitive complexity 64; 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/library/src/internal/memory-retention.test.ts:709
  • (anonymous) has cyclomatic complexity 32 and cognitive complexity 54; 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/library/src/internal/test/conformance/conformance-case-executor.ts:200
  • reconcileSpannerStoreConfiguration has cyclomatic complexity 26 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/library/src/internal/spanner-store-configuration.ts:109
  • validateDynamoDBEventStoreInput has cyclomatic complexity 23 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/library/src/internal/dynamodb-event-store-input-validation.ts:7
  • validateEventStoreInput has cyclomatic complexity 22 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/library/src/internal/event-store-input-validation.ts:46
  • retainDynamoDBSnapshots has cyclomatic complexity 19 and cognitive complexity 34; 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/library/src/internal/dynamodb-snapshot-retention.ts:30
  • after has cyclomatic complexity 19 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 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/library/src/internal/test/conformance/conformance-dynamodb-faults.ts:236
  • restoreDynamoDBLatestSnapshot has cyclomatic complexity 19 and cognitive complexity 18; 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/library/src/internal/dynamodb-latest-snapshot-restore.ts:13
  • validateSnapshotRetention has cyclomatic complexity 18 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/library/src/internal/snapshot-retention-validation.ts:5
  • (anonymous) has cyclomatic complexity 16 and cognitive complexity 12; 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/library/src/internal/test/conformance/conformance-data-loader.ts:23
  • compareExpectation has cyclomatic complexity 15 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/library/src/internal/test/conformance/conformance-expectation.ts:7
  • create has cyclomatic complexity 15 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/library/src/event-envelope.ts:17
  • phase has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/library/src/internal/test/conformance/conformance-dynamodb-faults.ts:63
  • validateSpannerEventStoreInput has cyclomatic complexity 15 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 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/library/src/internal/spanner-event-store-input-validation.ts:73
  • persistDynamoDBEvent has cyclomatic complexity 14 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/library/src/internal/dynamodb-persist-event.ts:53
  • checkReadEventPages has cyclomatic complexity 14 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. — packages/library/src/internal/test/conformance/conformance-dynamodb-observation.ts:589
  • (anonymous) has cyclomatic complexity 14 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 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/library/src/internal/spanner-get-latest-snapshot.ts:24
  • readMigrationInput has cyclomatic complexity 14 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 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/library/src/internal/spanner-migration.ts:38

What to do

  • Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files9.5 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

  • packages/library/src/internal/spanner-migration-plan.ts has 642 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/library/src/internal/spanner-migration-plan.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 Coverage9.8 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • 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/library/scripts/remove-test-artifacts.mjs:1

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

  • 5 file(s) (~321 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/tests
R8 · Dependency Hygiene10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling6.4 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×3) — packages/library/src/internal/spanner-read-write-transaction.ts:83, packages/library/src/internal/retention-failure-notification.ts:17, packages/library/src/internal/memory-storage-records.ts:146

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X5 · Nullable reference types9.9 / 10Exemplary✓ Tool-verified

Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • ~0.2 `!` null assertions per 1k TypeScript source lines — 1 assertion(s) across the 5536 source line(s) of the 76 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/library/src/internal/memory-storage-records.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

What to do

  • The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).

WCAG coverage — what static analysis assessed

Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only
AC7 · A11y enforcementenforcement — no page criterionEnforcement posture (process)

Not statically assessed — these 45 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.1, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health80%Adequate — gated by D2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture99%ExemplarySolid.
Maturity38%Weak — gated by M2, M4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness64%Adequate — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security52%Adequate — gated by D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling100%ExemplaryStrongest area.
Accessibility48%WeakBelow par — needs attention.
Performance100%ExemplarySolid.
Unscored — 1 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • X10 Duplicated predicate — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Not assessed: this repository stores data through '@aws-sdk/client-dynamodb' (packages/library/src/dynamodb-event-store-input.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
  • C4 Data Retention — Not assessed: this repository stores data through '@aws-sdk/client-dynamodb' (packages/library/src/dynamodb-event-store-input.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
  • C5 Data-Subject Rights — Not assessed: this repository stores data through '@aws-sdk/client-dynamodb' (packages/library/src/dynamodb-event-store-input.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
  • 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

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
  • AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
  • AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
  • AX1 Captive dependencies — Not applicable: 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 — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. 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
  • AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — Not assessed: this repository stores data through '@aws-sdk/client-dynamodb' (packages/library/src/dynamodb-event-store-input.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
  • C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • D11 Test Reliability — Test Reliability not included (check did not complete)
  • D16 Bus Factor — single-contributor repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
  • D24 Comment Value — No inline comments to assess — comment value is not applicable here.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.cjs,.mjs,.ts), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 10 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • 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
  • D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
  • DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
  • DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
  • DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
  • DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
  • DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • P2 Observability — This repository's JavaScript/TypeScript source (2 module(s), 88 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, Python source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • S1 Web-Security Posture — Not assessed: 76 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
  • X2 Cancellation propagation — no C# was loaded; this repository's Python was read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
  • 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.
  • 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)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 41 finding(s)
D29 · Static Analysis (SAST) · 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
  • + 2 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · High CVE · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <textarea> without a programmatic label · ×2
  • <textarea> without a programmatic label .agents/skills/skill-forge/eval-viewer/viewer.html:604 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <textarea> without a programmatic label .claude/skills/skill-forge/eval-viewer/viewer.html:604 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 134 finding(s)
D8 · Code Coverage · Low coverage · ×20
  • Low coverage: packages/library/src/event-store.ts packages/library/src/event-store.ts:1 — 47.4% line coverage (18/38).
  • Low coverage: packages/library/src/internal/dynamodb-batch-get.ts packages/library/src/internal/dynamodb-batch-get.ts:1 — 18.0% line coverage (9/50).
  • Low coverage: packages/library/src/internal/dynamodb-event-envelope-restore.ts packages/library/src/internal/dynamodb-event-envelope-restore.ts:1 — 22.5% line coverage (9/40).
  • Low coverage: packages/library/src/internal/dynamodb-event-store-input-validation.ts packages/library/src/internal/dynamodb-event-store-input-validation.ts:1 — 8.2% line coverage (7/85).
  • Low coverage: packages/library/src/internal/dynamodb-event-store.ts packages/library/src/internal/dynamodb-event-store.ts:1 — 32.4% line coverage (12/37).
  • Low coverage: packages/library/src/internal/dynamodb-get-events.ts packages/library/src/internal/dynamodb-get-events.ts:1 — 17.7% line coverage (11/62).
  • Low coverage: packages/library/src/internal/dynamodb-get-latest-snapshot.ts packages/library/src/internal/dynamodb-get-latest-snapshot.ts:1 — 22.2% line coverage (8/36).
  • Low coverage: packages/library/src/internal/dynamodb-item-size.ts packages/library/src/internal/dynamodb-item-size.ts:1 — 16.0% line coverage (4/25).
  • Low coverage: packages/library/src/internal/dynamodb-latest-snapshot-restore.ts packages/library/src/internal/dynamodb-latest-snapshot-restore.ts:1 — 13.8% line coverage (9/65).
  • Low coverage: packages/library/src/internal/dynamodb-persist-event-error.ts packages/library/src/internal/dynamodb-persist-event-error.ts:1 — 10.4% line coverage (5/48).
  • Low coverage: packages/library/src/internal/dynamodb-persist-event.ts packages/library/src/internal/dynamodb-persist-event.ts:1 — 8.9% line coverage (14/157).
  • Low coverage: packages/library/src/internal/dynamodb-snapshot-retention.ts packages/library/src/internal/dynamodb-snapshot-retention.ts:1 — 10.0% line coverage (8/80).
  • Low coverage: packages/library/src/internal/dynamodb-store-configuration.ts packages/library/src/internal/dynamodb-store-configuration.ts:1 — 9.9% line coverage (11/111).
  • Low coverage: packages/library/src/internal/dynamodb-stored-integer.ts packages/library/src/internal/dynamodb-stored-integer.ts:1 — 13.5% line coverage (5/37).
  • Low coverage: packages/library/src/internal/retention-failure-notification.ts packages/library/src/internal/retention-failure-notification.ts:1 — 10.4% line coverage (5/48).
  • Low coverage: packages/library/src/internal/snapshot-retention-validation.ts packages/library/src/internal/snapshot-retention-validation.ts:1 — 28.8% line coverage (15/52).
  • Low coverage: packages/library/src/internal/validated-event-store.ts packages/library/src/internal/validated-event-store.ts:1 — 40.5% line coverage (47/116).
  • Low coverage: packages/library/src/internal/dynamodb-persist-event.ts packages/library/src/internal/dynamodb-persist-event.ts:1 — 28.6% line coverage (16/56).
  • Low coverage: packages/library/src/internal/spanner-migration-read.ts packages/library/src/internal/spanner-migration-read.ts:1 — 23.5% line coverage (4/17).
  • Low coverage: packages/library/src/internal/spanner-migration.ts packages/library/src/internal/spanner-migration.ts:1 — 12.9% line coverage (11/85).
D15 · Churn × Complexity Hotspots · Hotspot · ×6
  • Hotspot: packages/library/src/internal/test/dynamodb-persist-event-observation.ts packages/library/src/internal/test/dynamodb-persist-event-observation.ts:168 — packages/library/src/internal/test/dynamodb-persist-event-observation.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in (anonymous) at line 168. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 19:27:15 +00:00' --until='2026-10-21 19:27:15 +00:00' --full-history --no-merges -- packages/library/src/internal/test/dynamodb-persist-event-observation.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/library/src/internal/test/conformance/conformance-case-executor.ts packages/library/src/internal/test/conformance/conformance-case-executor.ts:200 — packages/library/src/internal/test/conformance/conformance-case-executor.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in (anonymous) at line 200. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 19:27:15 +00:00' --until='2026-10-21 19:27:15 +00:00' --full-history --no-merges -- packages/library/src/internal/test/conformance/conformance-case-executor.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/library/src/internal/memory-event-store.ts packages/library/src/internal/memory-event-store.ts:30 — packages/library/src/internal/memory-event-store.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in memory-event-store.createMemoryEventStoreInternal at line 30. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 19:27:15 +00:00' --until='2026-10-21 19:27:15 +00:00' --full-history --no-merges -- packages/library/src/internal/memory-event-store.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/library/src/internal/test/conformance/conformance-data-loader.ts packages/library/src/internal/test/conformance/conformance-data-loader.ts:23 — packages/library/src/internal/test/conformance/conformance-data-loader.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in (anonymous) at line 23. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 19:27:15 +00:00' --until='2026-10-21 19:27:15 +00:00' --full-history --no-merges -- packages/library/src/internal/test/conformance/conformance-data-loader.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/library/src/event-envelope.ts packages/library/src/event-envelope.ts:17 — packages/library/src/event-envelope.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in create at line 17. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 19:27:15 +00:00' --until='2026-10-21 19:27:15 +00:00' --full-history --no-merges -- packages/library/src/event-envelope.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: .github/create-release-note-body.py .github/create-release-note-body.py:91 — .github/create-release-note-body.py changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in create-release-note-body.render at line 91. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 19:27:15 +00:00' --until='2026-10-21 19:27:15 +00:00' --full-history --no-merges -- .github/create-release-note-body.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D30 · Dependency Vulnerabilities · Medium CVE · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC3 · Page structure · Page without a main landmark · ×4
  • Page without a main landmark .agents/skills/skill-forge/assets/eval_review.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark .agents/skills/skill-forge/eval-viewer/viewer.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark .claude/skills/skill-forge/assets/eval_review.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark .claude/skills/skill-forge/eval-viewer/viewer.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D3 · God Classes · FunctionTooLong · ×4
  • FunctionTooLong: memory-event-store.createMemoryEventStoreInternal packages/library/src/internal/memory-event-store.ts:30 — FunctionTooLong — createMemoryEventStoreInternal runs 161 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 61 over it, 1.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: dynamodb-persist-event.persistDynamoDBEvent packages/library/src/internal/dynamodb-persist-event.ts:53 — FunctionTooLong — persistDynamoDBEvent runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: spanner-persist-event.persistSpannerEvent packages/library/src/internal/spanner-persist-event.ts:77 — FunctionTooLong — persistSpannerEvent runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: spanner-migration-plan.restoreAggregates packages/library/src/internal/spanner-migration-plan.ts:215 — FunctionTooLong — restoreAggregates runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
X3 · Exception handling · Swallowed exception (empty catch) · ×3
  • Swallowed exception (empty catch) packages/library/src/internal/spanner-read-write-transaction.ts:83 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/library/src/internal/retention-failure-notification.ts:17 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/library/src/internal/memory-storage-records.ts:146 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×2
  • Animation without a prefers-reduced-motion guard .agents/skills/skill-forge/eval-viewer/viewer.html:275 — `.grades-toggle .arrow` moves (`transition: transform 0.15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard .claude/skills/skill-forge/eval-viewer/viewer.html:275 — `.grades-toggle .arrow` moves (`transition: transform 0.15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
R10 · Code Duplication · Duplicated block (16 lines × 2 locations) · ×2
  • Duplicated block (16 lines × 2 locations) packages/library/src/event-envelope.ts:65 — packages/library/src/event-envelope.ts:65 · packages/library/src/snapshot-envelope.ts:40 — 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.
  • Duplicated block (16 lines × 2 locations) packages/library/src/internal/memory-event-store.ts:100 — packages/library/src/internal/memory-event-store.ts:100 · packages/library/src/internal/memory-event-store.ts:149 — 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.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — No accessibility enforcement found — your Biome config enables no a11y rules and there's no axe/pa11y/Lighthouse in tests or CI. Start by turning on Biome's own a11y rule group to catch issues at author time. What was searched, so you can tell an absence from a miss: the 4 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
D1 · Cyclomatic Complexity · run_eval_claude.run_single_query_claude (cyclomatic 34) · ×1
  • run_eval_claude.run_single_query_claude (cyclomatic 34) .agents/skills/skill-forge/scripts/run_eval_claude.py:48 — run_eval_claude.run_single_query_claude has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · run_loop.run_loop (cyclomatic 28) · ×1
  • run_loop.run_loop (cyclomatic 28) .agents/skills/skill-forge/scripts/run_loop.py:47 — run_loop.run_loop has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · memory-event-store.createMemoryEventStoreInternal (cyclomatic 26) · ×1
  • memory-event-store.createMemoryEventStoreInternal (cyclomatic 26) packages/library/src/internal/memory-event-store.ts:30 — memory-event-store.createMemoryEventStoreInternal has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · spanner-store-configuration.reconcileSpannerStoreConfiguration (cyclomatic 25) · ×1
  • spanner-store-configuration.reconcileSpannerStoreConfiguration (cyclomatic 25) packages/library/src/internal/spanner-store-configuration.ts:109 — spanner-store-configuration.reconcileSpannerStoreConfiguration has cyclomatic complexity 25 (threshold 15). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · aggregate_benchmark.load_run_results (cyclomatic 24) · ×1
  • aggregate_benchmark.load_run_results (cyclomatic 24) .agents/skills/skill-forge/scripts/aggregate_benchmark.py:70 — aggregate_benchmark.load_run_results has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · dynamodb-event-store-input-validation.validateDynamoDBEventStoreInput (cyclomatic 23) · ×1
  • dynamodb-event-store-input-validation.validateDynamoDBEventStoreInput (cyclomatic 23) packages/library/src/internal/dynamodb-event-store-input-validation.ts:7 — dynamodb-event-store-input-validation.validateDynamoDBEventStoreInput has cyclomatic complexity 23 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · quick_validate.validate_skill (cyclomatic 23) · ×1
  • quick_validate.validate_skill (cyclomatic 23) .agents/skills/skill-forge/scripts/quick_validate.py:12 — quick_validate.validate_skill has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · event-store-input-validation.validateEventStoreInput (cyclomatic 22) · ×1
  • event-store-input-validation.validateEventStoreInput (cyclomatic 22) packages/library/src/internal/event-store-input-validation.ts:46 — event-store-input-validation.validateEventStoreInput has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · generate_report.generate_html (cyclomatic 22) · ×1
  • generate_report.generate_html (cyclomatic 22) .agents/skills/skill-forge/scripts/generate_report.py:16 — generate_report.generate_html has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · generate_review.build_run (cyclomatic 20) · ×1
  • generate_review.build_run (cyclomatic 20) .agents/skills/skill-forge/eval-viewer/generate_review.py:85 — generate_review.build_run has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · dynamodb-latest-snapshot-restore.restoreDynamoDBLatestSnapshot (cyclomatic 19) · ×1
  • dynamodb-latest-snapshot-restore.restoreDynamoDBLatestSnapshot (cyclomatic 19) packages/library/src/internal/dynamodb-latest-snapshot-restore.ts:13 — dynamodb-latest-snapshot-restore.restoreDynamoDBLatestSnapshot has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · run_eval_codex.run_single_query_codex (cyclomatic 19) · ×1
  • run_eval_codex.run_single_query_codex (cyclomatic 19) .agents/skills/skill-forge/scripts/run_eval_codex.py:15 — run_eval_codex.run_single_query_codex has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · snapshot-retention-validation.validateSnapshotRetention (cyclomatic 18) · ×1
  • snapshot-retention-validation.validateSnapshotRetention (cyclomatic 18) packages/library/src/internal/snapshot-retention-validation.ts:5 — snapshot-retention-validation.validateSnapshotRetention has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · improve_description._build_prompt (cyclomatic 18) · ×1
  • improve_description._build_prompt (cyclomatic 18) .agents/skills/skill-forge/scripts/improve_description.py:25 — improve_description._build_prompt has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · spanner-persist-event.persistSpannerEvent (cyclomatic 16) · ×1
  • spanner-persist-event.persistSpannerEvent (cyclomatic 16) packages/library/src/internal/spanner-persist-event.ts:77 — spanner-persist-event.persistSpannerEvent has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · spanner-migration-plan.restoreAggregates (cyclomatic 16) · ×1
  • spanner-migration-plan.restoreAggregates (cyclomatic 16) packages/library/src/internal/spanner-migration-plan.ts:215 — spanner-migration-plan.restoreAggregates has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 221, 220, 341, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · create-release-note-body.render (cyclomatic 16) · ×1
  • create-release-note-body.render (cyclomatic 16) .github/create-release-note-body.py:91 — create-release-note-body.render has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D10 · Test Quality · No assertions · ×1
  • No assertions: built package uses four real DynamoDB operations and domain restoration packages/tests/e2e/workspace-consumption.test.cjs:6 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D2 · Cognitive Complexity · run_eval_claude.run_single_query_claude (cognitive 93) · ×1
  • run_eval_claude.run_single_query_claude (cognitive 93) .agents/skills/skill-forge/scripts/run_eval_claude.py:48 — run_eval_claude.run_single_query_claude has cognitive complexity 93 (threshold 15). Drivers by points: if/else 20 (67 pts), error handling 3 (15 pts), loops 3 (7 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 64). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · aggregate_benchmark.load_run_results (cognitive 61) · ×1
  • aggregate_benchmark.load_run_results (cognitive 61) .agents/skills/skill-forge/scripts/aggregate_benchmark.py:70 — aggregate_benchmark.load_run_results has cognitive complexity 61 (threshold 15). Drivers by points: if/else 12 (32 pts), error handling 4 (15 pts), loops 4 (10 pts), boolean chains 3, ternaries 1 (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · run_loop.run_loop (cognitive 55) · ×1
  • run_loop.run_loop (cognitive 55) .agents/skills/skill-forge/scripts/run_loop.py:47 — run_loop.run_loop has cognitive complexity 55 (threshold 15). Drivers by points: if/else 23 (44 pts), ternaries 5 (9 pts), boolean chains 1, loops 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · generate_review.build_run (cognitive 44) · ×1
  • generate_review.build_run (cognitive 44) .agents/skills/skill-forge/eval-viewer/generate_review.py:85 — generate_review.build_run has cognitive complexity 44 (threshold 15). Drivers by points: if/else 11 (27 pts), error handling 3 (10 pts), loops 4 (6 pts), boolean chains 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · generate_report.generate_html (cognitive 40) · ×1
  • generate_report.generate_html (cognitive 40) .agents/skills/skill-forge/scripts/generate_report.py:16 — generate_report.generate_html has cognitive complexity 40 (threshold 15). Drivers by points: ternaries 11 (23 pts), loops 7 (12 pts), if/else 4 (5 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · run_eval_codex.run_single_query_codex (cognitive 37) · ×1
  • run_eval_codex.run_single_query_codex (cognitive 37) .agents/skills/skill-forge/scripts/run_eval_codex.py:15 — run_eval_codex.run_single_query_codex has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (28 pts), error handling 1 (3 pts), loops 2 (3 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · improve_description._build_prompt (cognitive 36) · ×1
  • improve_description._build_prompt (cognitive 36) .agents/skills/skill-forge/scripts/improve_description.py:25 — improve_description._build_prompt has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (19 pts), loops 4 (10 pts), ternaries 1 (5 pts), boolean chains 2 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · create-release-note-body.render (cognitive 33) · ×1
  • create-release-note-body.render (cognitive 33) .github/create-release-note-body.py:91 — create-release-note-body.render has cognitive complexity 33 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 3 (5 pts), ternaries 2 (5 pts), boolean chains 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · spanner-store-configuration.reconcileSpannerStoreConfiguration (cognitive 31) · ×1
  • spanner-store-configuration.reconcileSpannerStoreConfiguration (cognitive 31) packages/library/src/internal/spanner-store-configuration.ts:109 — spanner-store-configuration.reconcileSpannerStoreConfiguration has cognitive complexity 31 (threshold 15). Drivers by points: if/else 18 (24 pts), boolean chains 5, loops 1, ternaries 1 (nesting depth added 6). Of this number, 30 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · dynamodb-snapshot-retention.retainDynamoDBSnapshots (cognitive 29) · ×1
  • dynamodb-snapshot-retention.retainDynamoDBSnapshots (cognitive 29) packages/library/src/internal/dynamodb-snapshot-retention.ts:30 — dynamodb-snapshot-retention.retainDynamoDBSnapshots has cognitive complexity 29 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 5 (9 pts), error handling 1 (2 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · quick_validate.validate_skill (cognitive 29) · ×1
  • quick_validate.validate_skill (cognitive 29) .agents/skills/skill-forge/scripts/quick_validate.py:12 — quick_validate.validate_skill has cognitive complexity 29 (threshold 15). Drivers by points: if/else 19 (26 pts), boolean chains 2, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · memory-event-store.createMemoryEventStoreInternal (cognitive 25) · ×1
  • memory-event-store.createMemoryEventStoreInternal (cognitive 25) packages/library/src/internal/memory-event-store.ts:30 — memory-event-store.createMemoryEventStoreInternal has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15, error handling 7, ternaries 2, boolean chains 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · run_eval.run_eval (cognitive 22) · ×1
  • run_eval.run_eval (cognitive 22) .agents/skills/skill-forge/scripts/run_eval.py:46 — run_eval.run_eval has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 4 (5 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · event-store-input-validation.validateEventStoreInput (cognitive 20) · ×1
  • event-store-input-validation.validateEventStoreInput (cognitive 20) packages/library/src/internal/event-store-input-validation.ts:46 — event-store-input-validation.validateEventStoreInput has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 8, ternaries 2, error handling 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · dynamodb-persist-event-error.classifyDynamoDBPersistEventError (cognitive 19) · ×1
  • dynamodb-persist-event-error.classifyDynamoDBPersistEventError (cognitive 19) packages/library/src/internal/dynamodb-persist-event-error.ts:4 — dynamodb-persist-event-error.classifyDynamoDBPersistEventError has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · dynamodb-event-store-input-validation.validateDynamoDBEventStoreInput (cognitive 18) · ×1
  • dynamodb-event-store-input-validation.validateDynamoDBEventStoreInput (cognitive 18) packages/library/src/internal/dynamodb-event-store-input-validation.ts:7 — dynamodb-event-store-input-validation.validateDynamoDBEventStoreInput has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 6, error handling 1, loops 1, ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · dynamodb-latest-snapshot-restore.restoreDynamoDBLatestSnapshot (cognitive 18) · ×1
  • dynamodb-latest-snapshot-restore.restoreDynamoDBLatestSnapshot (cognitive 18) packages/library/src/internal/dynamodb-latest-snapshot-restore.ts:13 — dynamodb-latest-snapshot-restore.restoreDynamoDBLatestSnapshot has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13, boolean chains 4, error handling 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · spanner-read-write-transaction.runSpannerReadWriteTransaction (cognitive 18) · ×1
  • spanner-read-write-transaction.runSpannerReadWriteTransaction (cognitive 18) packages/library/src/internal/spanner-read-write-transaction.ts:20 — spanner-read-write-transaction.runSpannerReadWriteTransaction has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (13 pts), error handling 2 (4 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · spanner-persist-event.persistSpannerEvent (cognitive 18) · ×1
  • spanner-persist-event.persistSpannerEvent (cognitive 18) packages/library/src/internal/spanner-persist-event.ts:77 — spanner-persist-event.persistSpannerEvent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 2, ternaries 2 (nesting depth added 3). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 108). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · utils.parse_skill_md (cognitive 18) · ×1
  • utils.parse_skill_md (cognitive 18) .agents/skills/skill-forge/scripts/utils.py:106 — utils.parse_skill_md has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · dynamodb-stored-integer.dynamoDBStoredInteger (cognitive 17) · ×1
  • dynamodb-stored-integer.dynamoDBStoredInteger (cognitive 17) packages/library/src/internal/dynamodb-stored-integer.ts:4 — dynamodb-stored-integer.dynamoDBStoredInteger has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 1, ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D23 · Boundary Type-Coupling · Cross-context type Result (library → examples) · ×1
  • Cross-context type Result (library → examples) packages/examples/src/run-user-account-example.ts:34 — Result (context library) is exposed in examples's public surface via run-user-account-example.unwrap — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type EventStoreError (library → examples) · ×1
  • Cross-context type EventStoreError (library → examples) packages/examples/src/run-user-account-example.ts:34 — EventStoreError (context library) is exposed in examples's public surface via run-user-account-example.unwrap — couples the contexts.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D35 · Change Coupling · Change coupling · ×1
  • Change coupling: dynamodb-event-store.ts ↔ memory-event-store.ts packages/library/src/internal/dynamodb-event-store.ts:1 — `packages/library/src/internal/dynamodb-event-store.ts` and `packages/library/src/internal/memory-event-store.ts` change together 60% of the time (18 of the 30 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 18 shared commits counted here, the most recent 3 are `6345a9b5` fix: clarify shared serializer and ttl checks (at that commit the files were still `src/internal/dynamodb-event-store.ts` and `src/internal/memory-event-store.ts`); `6dee0dfe` fix: apply latest review simplifications (at that commit the files were still `src/internal/dynamodb-event-store.ts` and `src/internal/memory-event-store.ts`); `8729cb22` fix: address review consistency checks (at that commit the files were still `src/internal/dynamodb-event-store.ts` and `src/internal/memory-event-store.ts`) — run `git show` on any of them.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×1
  • Duplicated block (29 lines × 2) .agents/skills/skill-forge/scripts/run_eval_claude.py:108 — .agents/skills/skill-forge/scripts/run_eval_claude.py:108-136 | .agents/skills/skill-forge/scripts/run_eval_codex.py:68-96 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1
  • Duplicated block (11 lines × 2) .agents/skills/skill-forge/scripts/run_eval_claude.py:204 — .agents/skills/skill-forge/scripts/run_eval_claude.py:204-214 | .agents/skills/skill-forge/scripts/run_eval_codex.py:109-119 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `.agents/skills/skill-forge/scripts/run_eval_claude.py:204` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×1
  • Duplicated block (10 lines × 2) .agents/skills/skill-forge/scripts/run_eval.py:160 — .agents/skills/skill-forge/scripts/run_eval.py:160-169 | .agents/skills/skill-forge/scripts/run_loop.py:267-276 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `.agents/skills/skill-forge/scripts/run_eval.py:159` calls `add_argument` and `.agents/skills/skill-forge/scripts/run_loop.py:266` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) .agents/skills/skill-forge/scripts/run_eval.py:149 — .agents/skills/skill-forge/scripts/run_eval.py:149-154 | .agents/skills/skill-forge/scripts/run_loop.py:252-257 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
R10 · Code Duplication · Duplicated block with local edits (72 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (72 matched lines × 2 locations) packages/library/src/internal/dynamodb-event-store-input-validation.ts:19 — packages/library/src/internal/dynamodb-event-store-input-validation.ts:19 · packages/library/src/internal/spanner-event-store-input-validation.ts:83 — the two spans are one implementation copied and then locally edited — 319 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.
R10 · Code Duplication · Duplicated block with local edits (62 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (62 matched lines × 2 locations) packages/library/src/internal/spanner-get-events.ts:13 — packages/library/src/internal/spanner-get-events.ts:13 · packages/library/src/internal/spanner-get-latest-snapshot.ts:11 — the two spans are one implementation copied and then locally edited — 367 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.
R10 · Code Duplication · Duplicated block with local edits (35 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (35 matched lines × 2 locations) packages/library/src/event-envelope.ts:11 — packages/library/src/event-envelope.ts:11 · packages/library/src/snapshot-envelope.ts:7 — the two spans are one implementation copied and then locally edited — 213 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.
R10 · Code Duplication · Duplicated block with local edits (33 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (33 matched lines × 2 locations) packages/library/src/internal/memory-storage-records.ts:133 — packages/library/src/internal/memory-storage-records.ts:133 · packages/library/src/internal/retention-failure-notification.ts:4 — the two spans are one implementation copied and then locally edited — 129 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.
R10 · Code Duplication · Duplicated block (29 lines × 2 locations) · ×1
  • Duplicated block (29 lines × 2 locations) packages/library/src/internal/dynamodb-event-envelope-restore.ts:36 — packages/library/src/internal/dynamodb-event-envelope-restore.ts:36 · packages/library/src/internal/spanner-get-events.ts:114 — 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.
R10 · Code Duplication · Duplicated block (21 lines × 2 locations) · ×1
  • Duplicated block (21 lines × 2 locations) packages/library/src/internal/dynamodb-latest-snapshot-restore.ts:90 — packages/library/src/internal/dynamodb-latest-snapshot-restore.ts:90 · packages/library/src/internal/spanner-get-latest-snapshot.ts:97 — 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.
R10 · Code Duplication · Duplicated block (19 lines × 2 locations) · ×1
  • Duplicated block (19 lines × 2 locations) packages/library/src/internal/event-store-input-validation.ts:52 — packages/library/src/internal/event-store-input-validation.ts:52 · packages/library/src/internal/memory-storage-input-validation.ts:11 — 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.
R10 · Code Duplication · Duplicated block (15 lines × 2 locations) · ×1
  • Duplicated block (15 lines × 2 locations) packages/library/src/internal/dynamodb-persist-event.ts:37 — packages/library/src/internal/dynamodb-persist-event.ts:37 · packages/library/src/internal/spanner-persist-event.ts:40 — 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.
R10 · Code Duplication · Duplicated block (13 lines × 2 locations) · ×1
  • Duplicated block (13 lines × 2 locations) packages/library/src/internal/dynamodb-persist-event.ts:82 — packages/library/src/internal/dynamodb-persist-event.ts:82 · packages/library/src/internal/dynamodb-persist-event.ts:100 — 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.
R10 · Code Duplication · Duplicated block (11 lines × 2 locations) · ×1
  • Duplicated block (11 lines × 2 locations) packages/library/src/internal/memory-storage-records.ts:246 — packages/library/src/internal/memory-storage-records.ts:246 · packages/library/src/internal/validated-event-store.ts:62 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (9 lines × 2 locations) · ×1
  • Duplicated block (9 lines × 2 locations) packages/library/src/internal/validated-event-store.ts:85 — packages/library/src/internal/validated-event-store.ts:85 · packages/library/src/internal/validated-event-store.ts:102 — 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.
R10 · Code Duplication · Duplicated block (8 lines × 2 locations) · ×1
  • Duplicated block (8 lines × 2 locations) packages/library/src/internal/dynamodb-get-events.ts:17 — packages/library/src/internal/dynamodb-get-events.ts:17 · packages/library/src/internal/spanner-get-events.ts:25 — 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.
R10 · Code Duplication · Duplicated block with local edits (6 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (6 matched lines × 2 locations) packages/library/src/internal/dynamodb-stored-integer.ts:32 — packages/library/src/internal/dynamodb-stored-integer.ts:32 · packages/library/src/internal/spanner-stored-integer.ts:26 — the two spans are one implementation copied and then locally edited — 51 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 55, cognitive 83) · ×1
  • Complex function (anonymous) (cyclomatic 55, cognitive 83) packages/library/src/internal/test/dynamodb-persist-event-observation.ts:168 — (anonymous) has cyclomatic complexity 55 and cognitive complexity 83; 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.
R2 · Cyclomatic Complexity · Complex function checkConstraints (cyclomatic 51, cognitive 66) · ×1
  • Complex function checkConstraints (cyclomatic 51, cognitive 66) packages/library/src/internal/test/conformance/conformance-dynamodb-observation.ts:251 — checkConstraints has cyclomatic complexity 51 and cognitive complexity 66; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 34, cognitive 64) · ×1
  • Complex function (anonymous) (cyclomatic 34, cognitive 64) packages/library/src/internal/memory-retention.test.ts:709 — (anonymous) has cyclomatic complexity 34 and cognitive complexity 64; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 32, cognitive 54) · ×1
  • Complex function (anonymous) (cyclomatic 32, cognitive 54) packages/library/src/internal/test/conformance/conformance-case-executor.ts:200 — (anonymous) has cyclomatic complexity 32 and cognitive complexity 54; 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.
R2 · Cyclomatic Complexity · Complex function reconcileSpannerStoreConfiguration (cyclomatic 26, cognitive 32) · ×1
  • Complex function reconcileSpannerStoreConfiguration (cyclomatic 26, cognitive 32) packages/library/src/internal/spanner-store-configuration.ts:109 — reconcileSpannerStoreConfiguration has cyclomatic complexity 26 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.
R2 · Cyclomatic Complexity · Complex function validateDynamoDBEventStoreInput (cyclomatic 23, cognitive 21) · ×1
  • Complex function validateDynamoDBEventStoreInput (cyclomatic 23, cognitive 21) packages/library/src/internal/dynamodb-event-store-input-validation.ts:7 — validateDynamoDBEventStoreInput has cyclomatic complexity 23 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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.
R2 · Cyclomatic Complexity · Complex function validateEventStoreInput (cyclomatic 22, cognitive 23) · ×1
  • Complex function validateEventStoreInput (cyclomatic 22, cognitive 23) packages/library/src/internal/event-store-input-validation.ts:46 — validateEventStoreInput has cyclomatic complexity 22 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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.
R2 · Cyclomatic Complexity · Complex function retainDynamoDBSnapshots (cyclomatic 19, cognitive 34) · ×1
  • Complex function retainDynamoDBSnapshots (cyclomatic 19, cognitive 34) packages/library/src/internal/dynamodb-snapshot-retention.ts:30 — retainDynamoDBSnapshots has cyclomatic complexity 19 and cognitive complexity 34; 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.
R2 · Cyclomatic Complexity · Complex function after (cyclomatic 19, cognitive 28) · ×1
  • Complex function after (cyclomatic 19, cognitive 28) packages/library/src/internal/test/conformance/conformance-dynamodb-faults.ts:236 — after has cyclomatic complexity 19 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 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.
R2 · Cyclomatic Complexity · Complex function restoreDynamoDBLatestSnapshot (cyclomatic 19, cognitive 18) · ×1
  • Complex function restoreDynamoDBLatestSnapshot (cyclomatic 19, cognitive 18) packages/library/src/internal/dynamodb-latest-snapshot-restore.ts:13 — restoreDynamoDBLatestSnapshot has cyclomatic complexity 19 and cognitive complexity 18; 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.
R2 · Cyclomatic Complexity · Complex function validateSnapshotRetention (cyclomatic 18, cognitive 16) · ×1
  • Complex function validateSnapshotRetention (cyclomatic 18, cognitive 16) packages/library/src/internal/snapshot-retention-validation.ts:5 — validateSnapshotRetention has cyclomatic complexity 18 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 16, cognitive 12) · ×1
  • Complex function (anonymous) (cyclomatic 16, cognitive 12) packages/library/src/internal/test/conformance/conformance-data-loader.ts:23 — (anonymous) has cyclomatic complexity 16 and cognitive complexity 12; 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.
R2 · Cyclomatic Complexity · Complex function compareExpectation (cyclomatic 15, cognitive 19) · ×1
  • Complex function compareExpectation (cyclomatic 15, cognitive 19) packages/library/src/internal/test/conformance/conformance-expectation.ts:7 — compareExpectation has cyclomatic complexity 15 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function create (cyclomatic 15, cognitive 15) · ×1
  • Complex function create (cyclomatic 15, cognitive 15) packages/library/src/event-envelope.ts:17 — create has cyclomatic complexity 15 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.
R2 · Cyclomatic Complexity · Complex function phase (cyclomatic 15, cognitive 14) · ×1
  • Complex function phase (cyclomatic 15, cognitive 14) packages/library/src/internal/test/conformance/conformance-dynamodb-faults.ts:63 — phase has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function validateSpannerEventStoreInput (cyclomatic 15, cognitive 13) · ×1
  • Complex function validateSpannerEventStoreInput (cyclomatic 15, cognitive 13) packages/library/src/internal/spanner-event-store-input-validation.ts:73 — validateSpannerEventStoreInput has cyclomatic complexity 15 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 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.
R2 · Cyclomatic Complexity · Complex function persistDynamoDBEvent (cyclomatic 14, cognitive 17) · ×1
  • Complex function persistDynamoDBEvent (cyclomatic 14, cognitive 17) packages/library/src/internal/dynamodb-persist-event.ts:53 — persistDynamoDBEvent has cyclomatic complexity 14 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function checkReadEventPages (cyclomatic 14, cognitive 14) · ×1
  • Complex function checkReadEventPages (cyclomatic 14, cognitive 14) packages/library/src/internal/test/conformance/conformance-dynamodb-observation.ts:589 — checkReadEventPages has cyclomatic complexity 14 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 14, cognitive 13) · ×1
  • Complex function (anonymous) (cyclomatic 14, cognitive 13) packages/library/src/internal/spanner-get-latest-snapshot.ts:24 — (anonymous) has cyclomatic complexity 14 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 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.
R2 · Cyclomatic Complexity · Complex function readMigrationInput (cyclomatic 14, cognitive 13) · ×1
  • Complex function readMigrationInput (cyclomatic 14, cognitive 13) packages/library/src/internal/spanner-migration.ts:38 — readMigrationInput has cyclomatic complexity 14 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 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.
R3 · Large Files · packages/library/src/internal/spanner-migration-plan.ts · ×1
  • packages/library/src/internal/spanner-migration-plan.ts: 642 lines of code packages/library/src/internal/spanner-migration-plan.ts:1 — packages/library/src/internal/spanner-migration-plan.ts has 642 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R4 · Test Coverage · No test reaches this file · ×1
  • No test reaches this file packages/library/scripts/remove-test-artifacts.mjs:1 — 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.
Minor — 50 finding(s)
M4 · Documentation accuracy · README/code drift · ×27
  • README/code drift conformance/README.md:3 — conformance/README.md links to `../docs/spec/core-contract.md`, but `docs/spec/core-contract.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift conformance/README.md:3 — conformance/README.md links to `../docs/spec/storage/dynamodb.md`, but `docs/spec/storage/dynamodb.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift conformance/README.md:3 — conformance/README.md links to `../docs/spec/storage/memory.md`, but `docs/spec/storage/memory.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift conformance/README.md:3 — conformance/README.md links to `../docs/spec/storage/sqlite.md`, but `docs/spec/storage/sqlite.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift conformance/README.md:3 — conformance/README.md links to `../docs/spec/storage/spanner.md`, but `docs/spec/storage/spanner.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift conformance/README.md:3 — conformance/README.md links to `../docs/spec/storage/bigtable.md`, but `docs/spec/storage/bigtable.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift conformance/README.md:3 — conformance/README.md links to `../docs/spec/storage/hash.md`, but `docs/spec/storage/hash.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift conformance/README.md:54 — conformance/README.md names `tools/conformance/data.py`, but no file or folder `tools/conformance/data.py` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift conformance/README.md:264 — conformance/README.md names `tools/conformance/uv.lock`, but no file or folder `tools/conformance/uv.lock` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift conformance/README.md:285 — conformance/README.md names `tools/conformance/reference_model.py`, but no file or folder `tools/conformance/reference_model.py` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design/next-major.md:5 — docs/design/next-major.md names `docs/spec/core-contract.md`, but no file or folder `docs/spec/core-contract.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design/next-major.md:5 — docs/design/next-major.md names `docs/spec/storage/dynamodb.md`, but no file or folder `docs/spec/storage/dynamodb.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design/next-major.md:5 — docs/design/next-major.md names `docs/spec/storage/memory.md`, but no file or folder `docs/spec/storage/memory.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design/next-major.md:5 — docs/design/next-major.md names `docs/plan/implementation-plan.md`, but no file or folder `docs/plan/implementation-plan.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design/next-major.md:5 — docs/design/next-major.md names `docs/adr/`, but no file or folder `docs/adr` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design/next-major.md:57 — docs/design/next-major.md names `packages/library/src/next/`, but no file or folder `packages/library/src/next` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design/next-major.md:57 — docs/design/next-major.md names `src/next/`, but no file or folder `src/next` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design/next-major.md:361 — docs/design/next-major.md documents the environment variable `DEFAULT_SHARD_COUNT`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design/next-major.md:371 — docs/design/next-major.md names `packages/library/src/next/internal/memory-event-store.ts`, but no file or folder `packages/library/src/next/internal/memory-event-store.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design/next-major.md:396 — docs/design/next-major.md names `packages/library/src/next/internal/dynamodb-event-store.ts`, but no file or folder `packages/library/src/next/internal/dynamodb-event-store.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design/next-major.md:442 — docs/design/next-major.md names `dynamodb.md`, but no file or folder `dynamodb.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design/next-major.md:463 — docs/design/next-major.md names `dynamodb-snapshot-retention-executor.ts`, but no file or folder `dynamodb-snapshot-retention-executor.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design/next-major.md:474 — docs/design/next-major.md names `packages/library/src/next/internal/test/conformance/`, but no file or folder `packages/library/src/next/internal/test/conformance` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design/next-major.md:474 — docs/design/next-major.md names `src/next/internal/test/`, but no file or folder `src/next/internal/test` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/design/next-major.md:490 — docs/design/next-major.md names `tools/conformance/data.py`, but no file or folder `tools/conformance/data.py` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • + 2 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×7
  • Duplicated predicate packages/library/src/internal/dynamodb-get-events.ts:49 — `cursor !== undefined && Object.keys(cursor).length !== 0` appears character-identically in 2 files — packages/library/src/internal/dynamodb-get-events.ts, packages/library/src/internal/dynamodb-snapshot-retention.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/library/src/internal/event-store-input-validation.ts:60 — `input === null || (input !== undefined && (typeof input !== "object" || Array.isArray(input)))` appears character-identically in 2 files — packages/library/src/internal/event-store-input-validation.ts, packages/library/src/internal/memory-storage-input-validation.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/library/src/internal/dynamodb-event-store-input-validation.ts:27 — `input === null || typeof input !== "object" || Array.isArray(input)` appears character-identically in 2 files — packages/library/src/internal/dynamodb-event-store-input-validation.ts, packages/library/src/internal/spanner-event-store-input-validation.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/library/src/event-envelope.ts:69 — `manifest !== undefined && typeof manifest !== "string"` appears character-identically in 2 files — packages/library/src/event-envelope.ts, packages/library/src/snapshot-envelope.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/library/src/internal/snapshot-retention-validation.ts:17 — `retention === null || typeof retention !== "object" || Array.isArray(retention)` appears character-identically in 2 files — packages/library/src/internal/snapshot-retention-validation.ts, packages/library/src/internal/spanner-event-store-input-validation.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/library/src/internal/dynamodb-event-envelope-restore.ts:37 — `typeof manifest !== "string" || !(bytes instanceof Uint8Array)` appears character-identically in 4 files — packages/library/src/internal/dynamodb-event-envelope-restore.ts, packages/library/src/internal/dynamodb-latest-snapshot-restore.ts, packages/library/src/internal/spanner-get-events.ts, packages/library/src/internal/spanner-get-latest-snapshot.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate .agents/skills/skill-forge/scripts/run_eval_claude.py:210 — `not killed and process.returncode and process.returncode != 0` appears character-identically in 2 files — .agents/skills/skill-forge/scripts/run_eval_claude.py, .agents/skills/skill-forge/scripts/run_eval_codex.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D12 · Dependency Hygiene · Deprecated · ×2
  • Deprecated: glob REDACTED:1878 — glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: node-domexception REDACTED:2315 — node-domexception 1.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native DOMException instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
D19 · Documentation Quality · Documentation · ×2
  • Documentation: written for insiders packages/library/docs/MIGRATION_GUIDE_3.0.ja.md — The 'Shard 選択 API' section names `KeyResolver`, `SpannerShardSelector`, and `selectShardId` but does not explain what each type is or how to use it for a reader who cannot read the adapter's source. Add an overview paragraph explaining what each ShardSelector type represents (e.g., its contract) so readers can match them without referencing the code.
  • Documentation: written for insiders packages/library/docs/MIGRATION_GUIDE_4.0.md — The 'AggregateId の値' section describes `createAggregateIdValue(...)` and removes `AggregateIdValue` but does not explain what domain value type is now used or how to validate plain strings. Add a short paragraph mapping the new string-only aggregate id to its shape (typeName, readonly fields) so readers can construct it.
D30 · Dependency Vulnerabilities · Low CVE · ×2
  • REDACTED
  • REDACTED
D10 · Test Quality · Mock-dominated test · ×1
  • Mock-dominated test: logs a retention failure and sends the same failure to the additional callback packages/library/src/internal/retention-failure-notification.test.ts:5 — This test sets up 5 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M1 · Documentation (README) · Thin README · ×1
  • Thin README — The root README is 89 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — 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.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — 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 33372 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.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate — 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.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X5 · Nullable reference types · Null assertions (`!`) reduce the strict null checking score · ×1
  • Null assertions (`!`) reduce the strict null checking score — ~0.2 `!` null assertions per 1k TypeScript source lines — 1 assertion(s) across the 5536 source line(s) of the 76 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/library/src/internal/memory-storage-records.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Minor — 1 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×1
  • Outdated (npm): @aws-sdk/client-dynamodb — @aws-sdk/client-dynamodb is pinned at 3.1154.0; registry.npmjs.org publishes 3.1155.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9ffd88344b9842d0ac12222b839dfd3c/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9ffd88344b9842d0ac12222b839dfd3c/tree.json --exit-code 0 --source .0artifacts/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/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .37artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update12artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 10 file(s) — `packages/library/src/internal/dynamodb-event-store-input-validation.ts`, `packages/library/src/internal/dynamodb-event-store.ts`, `packages/library/src/internal/dynamodb-get-events.ts`, `packages/library/src/internal/dynamodb-persist-event.ts`, `packages/library/src/internal/spanner-event-store-input-validation.ts`, … (+5 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—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 Confinementruntime-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 Confinementruntime-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 Enforcementruntime-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 Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a163f2-c726-7e3f-bbf6-c4147b4aa7bd · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 41 · Warnings: 134 · Recommendations: 50 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 14:10 UTC.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md