Public report of psavelis/enterprise-blockchain, 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, 16:19 UTC · Survey ID cd_379329a5949e4b3294538ff3001e0f44

psavelis/enterprise-blockchain

Measured 22 October 2026, 16:16 UTC, at code version 50c683a

CAI score 62out of 100 At risk 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 Code Health 75 Strong Architecture 71 Adequate Production Readiness 70 Adequate Security and Compliance 64 Adequate Maturity 52 Adequate

A medium codebase: 38,965 lines of product code in 4 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Maturity, 52

Findings by how serious they are

69 critical 216 serious 297 minor

4 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, 16:16 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.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

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 ▸

81of 88 dimensions measured by tools. The other 7 are advisory notes from an AI model, which explain the code but don't count towards the score.
547of 582 findings point to an exact file and line, so you can open each one in the code. The other 35 concern the repository as a whole, such as missing documentation.
88dimensions across 7 lenses, read from 38,965 lines of product code in 4 projects.
Chapters

Executive summary

psavelis/enterprise-blockchain scores 62 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.

The weakest lens counts most in the score, and here that is Maturity, which scores 52 and is rated Adequate. Its Knowledge Freshness dimension scores 0 out of 10, and until that reaches 4, Maturity can't be rated higher than Adequate. The first actions are to resolve the 114 Orphaned file finding(s) in Knowledge Freshness and to reconcile the README with reality: CONTRIBUTING.md names `test/coverage-expansion`, but no file or folder `test/coverage-expansion` exists; CONTRIBUTING.md names `docs/restructure`, but no file or folder `docs/restructure` exists; CONTRIBUTING.md names `infra/terraform`, but no file or folder `infra/terraform` exists; docs/architecture/local-demo-blueprint.md links to `modules/integrations/fabric-gateway/src/index.ts`, but `docs/architecture/modules/integrations/fabric-gateway/src/index.ts` does not exist; docs/architecture/local-demo-blueprint.md links to `contracts/ConsortiumOrderRegistry.sol`, but `docs/architecture/contracts/ConsortiumOrderRegistry.sol` does not exist, and if Maturity rose to 70, the score would rise from 62 to about 68.

69 findings are critical: 42 in Static Analysis (SAST), 23 in Dependency Vulnerabilities and four in IaC & Container Security.

Watchdog couldn't measure 4 dimensions in this code, among them Navigability, Web-Security Posture and Structured logging, so they are left out of the score. The product code is 38,965 lines, which would take an estimated 0.4 person-years, around €60,000, to rebuild.

Code Health 75 Strong Architecture 71 Adequate, capped by Project Cohesion and Import Boundaries Maturity 52 Adequate, capped by Knowledge Freshness and Documentation accuracy Production Readiness 70 Adequate, capped by Test Coverage Security and Compliance 64 Adequate, capped by Static Analysis (SAST), Dependency Vulnerabilities and Supply-chain Provenance & Signing Domain Modelling 100 ★ Exemplary 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 52 · counts for 46%Security and Compliance 64 · counts for 25%Production Readiness 70 · counts for 14%Architecture 71 · counts for 8%Code Health 75 · counts for 4%Domain Modelling 100 · counts for 2%Performance 100 · counts for 1%

If Maturity rose from 52 to 70, the lowest score rated Strong, the score would rise from 62 to about 68.

Code composition: what the lines of code are
Product code 86%Tests 14%
New since the last survey: 49 findings

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

  • Test Quality · Skipped test: (unnamed test) demo/e2e/scenarios.spec.ts
  • Test Quality · Skipped test: (unnamed test) demo/e2e/scenarios.spec.ts
  • Test Quality · Skipped test: (unnamed test) demo/e2e/scenarios.spec.ts
  • Test Quality · Skipped test: (unnamed test) demo/e2e/real-prover.spec.ts
  • Test Quality · Skipped test: (unnamed test) demo/e2e/real-prover.spec.ts
  • Test Quality · Skipped test: (unnamed test) demo/e2e/real-prover.spec.ts
  • Test Quality · Skipped test: (unnamed test) demo/e2e/dashboard.spec.ts
  • Test Quality · Skipped test: (unnamed test) demo/e2e/dashboard.spec.ts
  • Test Quality · Skipped test: (unnamed test) demo/e2e/api.spec.ts
  • Dependency Hygiene · Deprecated: starknet package.json
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Supply-chain Provenance & Signing · REDACTED
  • Import Boundaries · Boundary violation [package:relative-cross-package] modules/p2mr/src/p2mr-output.ts
  • Import Boundaries · Boundary violation [package:relative-cross-package] modules/protocols/besu/src/p2mr-adapter.ts
  • Import Boundaries · Boundary violation [package:relative-cross-package] modules/protocols/besu/src/p2mr-adapter.ts
  • Import Boundaries · Boundary violation [package:relative-cross-package] modules/protocols/corda/src/p2mr-adapter.ts
  • Import Boundaries · Boundary violation [package:relative-cross-package] modules/protocols/corda/src/p2mr-adapter.ts
  • Import Boundaries · Boundary violation [package:relative-cross-package] modules/protocols/fabric/src/p2mr-adapter.ts
  • Import Boundaries · Boundary violation [package:relative-cross-package] modules/protocols/fabric/src/p2mr-adapter.ts
  • Import Boundaries · Boundary violation [package:relative-cross-package] modules/protocols/src/p2mr-port.ts
  • Large Files · modules/p2mr/src/script-interpreter.ts: 621 lines of code modules/p2mr/src/script-interpreter.ts
  • Large Files · packages/enterprise-blockchain/src/p2mr/script-interpreter.ts: 621 lines of code packages/enterprise-blockchain/src/p2mr/script-interpreter.ts
  • Large Files · modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts: 577 lines of code modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts
  • Large Files · modules/stark-settlement/src/domain/ports.ts: 565 lines of code modules/stark-settlement/src/domain/ports.ts
  • Large Files · packages/enterprise-blockchain/src/stark-settlement/domain/ports.ts: 565 lines of code packages/enterprise-blockchain/src/stark-settlement/domain/ports.ts
  • Large Files · modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts: 542 lines of code modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts
  • Large Files · packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/stone-proof-adapter.ts: 542 lines of code packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/stone-proof-adapter.ts
  • Large Files · packages/enterprise-blockchain/src/mpc/index.ts: 521 lines of code packages/enterprise-blockchain/src/mpc/index.ts
  • Large Files · modules/mpc/src/index.ts: 520 lines of code modules/mpc/src/index.ts
  • Large Files · modules/hsm/src/application/asymmetric-key-service.ts: 519 lines of code modules/hsm/src/application/asymmetric-key-service.ts
  • Large Files · modules/stark-settlement/src/domain/value-objects.ts: 499 lines of code modules/stark-settlement/src/domain/value-objects.ts
  • Large Files · packages/enterprise-blockchain/src/stark-settlement/domain/value-objects.ts: 499 lines of code packages/enterprise-blockchain/src/stark-settlement/domain/value-objects.ts
  • Large Files · modules/hsm/src/index.ts: 483 lines of code modules/hsm/src/index.ts
  • Large Files · modules/stark-settlement/src/application/ledger-service.ts: 457 lines of code modules/stark-settlement/src/application/ledger-service.ts
  • Large Files · packages/enterprise-blockchain/src/stark-settlement/application/ledger-service.ts: 457 lines of code packages/enterprise-blockchain/src/stark-settlement/application/ledger-service.ts
  • Large Files · modules/stark-settlement/src/domain/entities.ts: 421 lines of code modules/stark-settlement/src/domain/entities.ts
  • Large Files · packages/enterprise-blockchain/src/stark-settlement/domain/entities.ts: 421 lines of code packages/enterprise-blockchain/src/stark-settlement/domain/entities.ts
  • Large Files · modules/p2mr/src/spend-proof.ts: 415 lines of code modules/p2mr/src/spend-proof.ts
  • Large Files · packages/enterprise-blockchain/src/p2mr/spend-proof.ts: 415 lines of code packages/enterprise-blockchain/src/p2mr/spend-proof.ts
  • Large Files · modules/hsm/src/infrastructure/adapters/simulator-crypto-adapter.ts: 402 lines of code modules/hsm/src/infrastructure/adapters/simulator-crypto-adapter.ts
  • Exception handling · Swallowed exception (empty catch) modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts
  • Exception handling · Swallowed exception (empty catch) modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts
  • Exception handling · Swallowed exception (empty catch) modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts
  • Exception handling · Swallowed exception (empty catch) modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts

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: 121 findings

These 121 critical or serious findings were in the previous survey, on 8 October 2026, and are gone from this one. The first 100 are listed here.

  • Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Code Duplication · Duplicated block with local edits (60 matched lines × 2 locations) modules/hsm/src/infrastructure/audit-log-factory.ts
  • Code Duplication · Duplicated block (59 lines × 2 locations) modules/protocols/src/p2mr-port.ts
  • Code Duplication · Wholesale file copy (58 identical lines × 2 files) modules/p2mr/src/p2mr-output.ts
  • Code Duplication · Duplicated block (57 lines × 2 locations) modules/integrations/besu-client/src/ports.ts
  • Code Duplication · Wholesale file copy (57 identical lines × 2 files) modules/privacy/src/application/view-projector.ts
  • Code Duplication · Duplicated block (55 lines × 2 locations) modules/stark-settlement/src/infrastructure/adapters/clock-adapter.ts
  • Code Duplication · Duplicated block (53 lines × 2 locations) modules/protocols/src/corda-port.ts
  • Code Duplication · Duplicated block (49 lines × 2 locations) modules/p2mr/src/types.ts
  • Code Duplication · Duplicated block (49 lines × 2 locations) modules/protocols/src/fabric-port.ts
  • Code Duplication · Duplicated block (48 lines × 2 locations) modules/shared/src/logger.ts
  • Code Duplication · Duplicated block (46 lines × 2 locations) modules/integrations/fabric-gateway/src/ports.ts
  • Code Duplication · Duplicated block (45 lines × 2 locations) modules/stark-settlement/src/infrastructure/persistence/offset-store.ts
  • Code Duplication · Duplicated block (36 lines × 2 locations) contracts/fabric/FoodTraceContract.ts
  • Code Duplication · Duplicated block (35 lines × 2 locations) modules/integrations/corda-gateway/src/ports.ts
  • Code Duplication · Duplicated block with local edits (33 matched lines × 2 locations) modules/shared/src/telemetry-sdk.ts
  • Code Duplication · Duplicated block (31 lines × 2 locations) modules/hsm/src/domain/entities.ts
  • Code Duplication · Duplicated block (27 lines × 2 locations) modules/shared/src/commit.ts
  • Code Duplication · Duplicated block (27 lines × 2 locations) modules/shared/src/store.ts
  • Code Duplication · Duplicated block (26 lines × 2 locations) modules/mpc/src/adapters.ts
  • Code Duplication · Duplicated block (25 lines × 2 locations) modules/integrations/besu-client/src/error-mapper.ts
  • Code Duplication · Duplicated block (24 lines × 2 locations) modules/protocols/src/besu-port.ts
  • Code Duplication · Duplicated block (23 lines × 3 locations) modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts
  • Code Duplication · Duplicated block (23 lines × 2 locations) modules/traceability/src/infrastructure/in-memory-store.ts
  • Code Duplication · Duplicated block (22 lines × 3 locations) REDACTED
  • Code Duplication · Duplicated block (21 lines × 2 locations) modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts
  • Code Duplication · Duplicated block (21 lines × 2 locations) modules/integrations/shared/src/env.ts
  • Code Duplication · Duplicated block (21 lines × 2 locations) modules/privacy/src/index.ts
  • Code Duplication · Duplicated block (21 lines × 2 locations) modules/shared/src/collection-store.ts
  • Code Duplication · Duplicated block (20 lines × 2 locations) modules/traceability/src/index.ts
  • Code Duplication · Duplicated block (19 lines × 2 locations) modules/hsm/src/index.ts
  • Code Duplication · Duplicated block (18 lines × 2 locations) modules/p2mr/src/adapters.ts
  • Code Duplication · Duplicated block (17 lines × 2 locations) modules/aid-settlement/src/index.ts
  • Code Duplication · Duplicated block (17 lines × 2 locations) modules/credentialing/src/index.ts
  • Code Duplication · Duplicated block (17 lines × 2 locations) modules/hsm/src/application/symmetric-key-service.ts
  • Code Duplication · Duplicated block (17 lines × 3 locations) modules/hsm/src/application/symmetric-key-service.ts
  • Code Duplication · Duplicated block (17 lines × 2 locations) modules/hsm/src/infrastructure/adapters/simulator-crypto-adapter.ts
  • Code Duplication · Duplicated block (17 lines × 2 locations) modules/hsm/src/infrastructure/audit-log.ts
  • Code Duplication · Duplicated block (17 lines × 2 locations) modules/protocols/besu/src/p2mr-adapter.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) modules/aid-settlement/src/infrastructure/in-memory-store.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) modules/credentialing/src/infrastructure/in-memory-store.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) modules/hsm/src/application/symmetric-key-service.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) modules/hsm/src/domain/ports.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) modules/hsm/src/infrastructure/adapters/simulator-crypto-adapter.ts
  • Code Duplication · Duplicated block (14 lines × 2 locations) modules/hsm/src/index.ts
  • Code Duplication · Duplicated block (14 lines × 2 locations) modules/hsm/src/index.ts
  • Code Duplication · Duplicated block (14 lines × 2 locations) modules/mpc/src/ports.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) contracts/fabric/FoodTraceContract.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) modules/hsm/src/application/asymmetric-key-service.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) modules/hsm/src/application/symmetric-key-service.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) modules/hsm/src/index.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) modules/hsm/src/index.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) modules/hsm/src/infrastructure/adapters/simulator-crypto-adapter.ts
  • Code Duplication · Duplicated block (11 lines × 3 locations) modules/hsm/src/application/asymmetric-key-service.ts
  • Code Duplication · Duplicated block (11 lines × 2 locations) modules/hsm/src/index.ts
  • Code Duplication · Duplicated block (11 lines × 2 locations) modules/hsm/src/infrastructure/key-store.ts
  • Code Duplication · Duplicated block (11 lines × 2 locations) modules/traceability/src/domain/ports.ts
  • Code Duplication · Duplicated block (9 lines × 2 locations) modules/hsm/src/application/symmetric-key-service.ts
  • Code Duplication · Duplicated block (9 lines × 2 locations) modules/hsm/src/infrastructure/adapters/simulator-crypto-adapter.ts
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/event-emitter-adapter.ts
  • Import Boundaries · Boundary violation [package:relative-cross-package] modules/protocols/besu/src/p2mr-adapter.ts
  • Import Boundaries · Boundary violation [package:relative-cross-package] modules/protocols/corda/src/p2mr-adapter.ts
  • Import Boundaries · Boundary violation [package:relative-cross-package] modules/protocols/fabric/src/p2mr-adapter.ts
  • Large Files · Large Files
  • Test Coverage · No test reaches this file modules/stark-settlement/src/infrastructure/persistence/outbox-store.ts
  • Test Coverage · No test reaches this file packages/enterprise-blockchain/src/stark-settlement/infrastructure/persistence/outbox-store.ts
  • Test Coverage · No test reaches this file modules/protocols/fabric/src/p2mr-adapter.ts
  • Test Coverage · No test reaches this file packages/enterprise-blockchain/src/mpc/dsa.ts
  • Test Coverage · No test reaches this file modules/protocols/corda/src/p2mr-adapter.ts
  • Test Coverage · No test reaches this file modules/stark-settlement/src/infrastructure/adapters/event-emitter-adapter.ts
  • Test Coverage · No test reaches this file packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/audit-adapter.ts
  • Test Coverage · No test reaches this file modules/stark-settlement/src/infrastructure/adapters/audit-adapter.ts
  • Test Coverage · No test reaches this file packages/enterprise-blockchain/src/hsm/infrastructure/file-audit-log.ts
  • Test Coverage · No test reaches this file packages/enterprise-blockchain/src/hsm/index.ts
  • Test Coverage · No test reaches this file packages/enterprise-blockchain/src/shared/telemetry.ts
  • Test Coverage · No test reaches this file scripts/adapter-projections-demo.ts
  • Test Coverage · No test reaches this file packages/enterprise-blockchain/src/hsm/application/asymmetric-key-service.ts
  • Test Coverage · No test reaches this file modules/stark-settlement/src/infrastructure/adapters/dilithium-adapter.ts
  • Test Coverage · No test reaches this file packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/dilithium-adapter.ts
  • Test Coverage · No test reaches this file packages/enterprise-blockchain/src/aid-settlement/application/reconciler.ts
  • Test Coverage · No test reaches this file packages/enterprise-blockchain/src/hsm/infrastructure/audit-log-factory.ts
  • Test Coverage · No test reaches this file REDACTED
  • Test Coverage · No test reaches this file packages/enterprise-blockchain/src/traceability/application/recall-assessor.ts
  • Test Coverage · No test reaches this file packages/enterprise-blockchain/src/shared/telemetry-sdk.ts
  • Test Coverage · No test reaches this file modules/stark-settlement/src/infrastructure/adapters/clock-adapter.ts
  • Test Coverage · No test reaches this file packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/clock-adapter.ts
  • Test Coverage · No test reaches this file packages/enterprise-blockchain/src/privacy/application/view-projector.ts
  • Test Coverage · No test reaches this file scripts/integration-clients-demo.ts
  • Test Coverage · No test reaches this file packages/enterprise-blockchain/src/credentialing/application/clearance-evaluator.ts
  • Test Coverage · No test reaches this file modules/stark-settlement/src/infrastructure/persistence/offset-store.ts
  • Test Coverage · No test reaches this file packages/enterprise-blockchain/src/stark-settlement/infrastructure/persistence/offset-store.ts
  • Test Coverage · No test reaches this file modules/shared/src/telemetry-sdk.ts
  • Test Coverage · No test reaches this file REDACTED
  • Test Coverage · No test reaches this file packages/enterprise-blockchain/src/shared/logger.ts
Rebuild cost: about €60,000 · Estimate
Cost to rebuild€20,000 to €100,000, for 335 to 1,061 hours of work, about 0.4 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.8 at a score of 62. 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.
SizeMedium: 38,965 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
Resolve the 114 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (15), entities.ts (4), p2mr-adapter.ts (3).
Raises the score by about 8 points · High effort · Knowledge Freshness
2
Reconcile the README with reality: CONTRIBUTING.md names `test/coverage-expansion`, but no file or folder `test/coverage-expansion` exists; CONTRIBUTING.md names `docs/restructure`, but no file or folder `docs/restructure` exists; CONTRIBUTING.md names `infra/terraform`, but no file or folder `infra/terraform` exists; docs/architecture/local-demo-blueprint.md links to `modules/integrations/fabric-gateway/src/index.ts`, but `docs/architecture/modules/integrations/fabric-gateway/src/index.ts` does not exist; docs/architecture/local-demo-blueprint.md links to `contracts/ConsortiumOrderRegistry.sol`, but `docs/architecture/contracts/ConsortiumOrderRegistry.sol` does not exist.
Raises the score by about 7 points · Medium effort · Documentation accuracy
3
Grow the ADR log (currently 6) — reach 8 to raise the maturity tier; document significant decisions as they're made.
Raises the score by about 2 points · Medium effort · Architecture documentation

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 €60,000 to build again, about 0.4 person-years of work. Its weakest lens is Maturity, at 52 (Adequate). 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
Resolve the 114 Orphaned file finding(s) in Knowledge Freshness. Of all the actions in this report, it raises the score most for the work it takes: about 8 points for high effort, because it clears the 114 Knowledge Freshness findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

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.

250 modules, with 347 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; 210 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 contracts.fabric.FoodTraceContract2 demo.components.progress3 demo.services.types4 modules.aid-settlement.src.domain.entities5 modules.credentialing.src.domain.entities6 modules.hsm.src.domain.entities7 modules.integrations.shared.src.retry8 modules.mpc.src.field9 modules.mpc.src.ports10 modules.p2mr.src.types11 modules.privacy.src.domain.entities12 modules.shared.src.logger13 modules.shared.src.store14 modules.stark-settlement.src.domain.entities15 modules.stark-settlement.src.domain.value-objects16 modules.traceability.src.domain.entities17 modules.aid-settlement.src.domain.ports18 modules.credentialing.src.domain.ports19 modules.hsm.src.domain.ports20 modules.integrations.besu-client.src.ports21 modules.p2mr.src.merkle-tree22 modules.privacy.src.domain.ports23 modules.protocols.src.p2mr-port24 modules.stark-settlement.src.domain.ports25 modules.traceability.src.domain.ports26 modules.credentialing.src.application.clearance-evaluator27 modules.hsm.src.application.asymmetric-key-service28 modules.hsm.src.application.symmetric-key-service29 modules.hsm.src.infrastructure.syslog-audit-log30 modules.p2mr.src.p2mr-output31 modules.p2mr.src.spend-proof32 modules.stark-settlement.src33 modules.stark-settlement.src.infrastructure.adapters.starknet-proof-adapter34 modules.stark-settlement.src.infrastructure.adapters.stone-proof-adapter35 modules.hsm.src.application.envelope-encryption-service36 modules.p2mr.src37 modules.stark-settlement.src.application.ledger-service38 packages.enterprise-blockchain.src.p2mr39 modules.hsm.src40 modules.privacy.src.application.view-projector
1 contracts.fabric.FoodTraceContract
2 demo.components.progress
3 demo.services.types
4 modules.aid-settlement.src.domain.entities
5 modules.credentialing.src.domain.entities
6 modules.hsm.src.domain.entities
7 modules.integrations.shared.src.retry
8 modules.mpc.src.field
9 modules.mpc.src.ports
10 modules.p2mr.src.types
11 modules.privacy.src.domain.entities
12 modules.shared.src.logger
13 modules.shared.src.store
14 modules.stark-settlement.src.domain.entities
15 modules.stark-settlement.src.domain.value-objects
16 modules.traceability.src.domain.entities
17 modules.aid-settlement.src.domain.ports21
18 modules.credentialing.src.domain.ports21
19 modules.hsm.src.domain.ports1
20 modules.integrations.besu-client.src.ports2
21 modules.p2mr.src.merkle-tree1
22 modules.privacy.src.domain.ports11
23 modules.protocols.src.p2mr-port2
24 modules.stark-settlement.src.domain.ports123
25 modules.traceability.src.domain.ports213
26 modules.credentialing.src.application.clearance-evaluator211
27 modules.hsm.src.application.asymmetric-key-service74
28 modules.hsm.src.application.symmetric-key-service24
29 modules.hsm.src.infrastructure.syslog-audit-log11
30 modules.p2mr.src.p2mr-output21
31 modules.p2mr.src.spend-proof11
32 modules.stark-settlement.src18
33 modules.stark-settlement.src.infrastructure.adapters.starknet-proof-adapter412
34 modules.stark-settlement.src.infrastructure.adapters.stone-proof-adapter412
35 modules.hsm.src.application.envelope-encryption-service311
36 modules.p2mr.src921
37 modules.stark-settlement.src.application.ledger-service811
38 packages.enterprise-blockchain.src.p2mr921
39 modules.hsm.src71221
40 modules.privacy.src.application.view-projector2111
Uses a module listed above itPart of a loopThe module itself
1 contracts.fabric.FoodTraceContract2 demo.components.progress3 demo.services.types4 modules.aid-settlement.src.domain.entities5 modules.credentialing.src.domain.entities6 modules.hsm.src.domain.entities7 modules.integrations.shared.src.retry8 modules.mpc.src.field9 modules.mpc.src.ports10 modules.p2mr.src.types11 modules.privacy.src.domain.entities12 modules.shared.src.logger13 modules.shared.src.store14 modules.stark-settlement.src.domain.entities15 modules.stark-settlement.src.domain.value-objects16 modules.traceability.src.domain.entities17 modules.aid-settlement.src.domain.ports18 modules.credentialing.src.domain.ports19 modules.hsm.src.domain.ports20 modules.integrations.besu-client.src.ports21 modules.p2mr.src.merkle-tree22 modules.privacy.src.domain.ports23 modules.protocols.src.p2mr-port24 modules.stark-settlement.src.domain.ports25 modules.traceability.src.domain.ports26 modules.credentialing.src.application.clearance-evaluator27 modules.hsm.src.application.asymmetric-key-service28 modules.hsm.src.application.symmetric-key-service29 modules.hsm.src.infrastructure.syslog-audit-log30 modules.p2mr.src.p2mr-output31 modules.p2mr.src.spend-proof32 modules.stark-settlement.src33 modules.stark-settlement.src.infrastructure.adapters.starknet-proof-adapter34 modules.stark-settlement.src.infrastructure.adapters.stone-proof-adapter35 modules.hsm.src.application.envelope-encryption-service36 modules.p2mr.src37 modules.stark-settlement.src.application.ledger-service38 packages.enterprise-blockchain.src.p2mr39 modules.hsm.src40 modules.privacy.src.application.view-projectorcontracts.fabric.FoodTraceContract1demo.components.progress2demo.services.types3modules.aid-settlement.src.domain.entities4modules.credentialing.src.domain.entities5modules.hsm.src.domain.entities6modules.integrations.shared.src.retry7modules.mpc.src.field8modules.mpc.src.ports9modules.p2mr.src.types10modules.privacy.src.domain.entities11modules.shared.src.logger12modules.shared.src.store13modules.stark-settlement.src.domain.entities14modules.stark-settlement.src.domain.value-objects15modules.traceability.src.domain.entities16modules.aid-settlement.src.domain.ports17modules.credentialing.src.domain.ports18modules.hsm.src.domain.ports19modules.integrations.besu-client.src.ports20modules.p2mr.src.merkle-tree21modules.privacy.src.domain.ports22modules.protocols.src.p2mr-port23modules.stark-settlement.src.domain.ports24modules.traceability.src.domain.ports25modules.credentialing.src.application.clearance-evaluator26modules.hsm.src.application.asymmetric-key-service27modules.hsm.src.application.symmetric-key-service28modules.hsm.src.infrastructure.syslog-audit-log29modules.p2mr.src.p2mr-output30modules.p2mr.src.spend-proof31modules.stark-settlement.src32modules.stark-settlement.src.infrastructure.adapters.starknet-proof-adapter33modules.stark-settlement.src.infrastructure.adapters.stone-proof-adapter34modules.hsm.src.application.envelope-encryption-service35modules.p2mr.src36modules.stark-settlement.src.application.ledger-service37packages.enterprise-blockchain.src.p2mr38modules.hsm.src39modules.privacy.src.application.view-projector402121121112123213211742411211118412412311921811921712212111+210 more modules (most-connected shown)

At a glance — Code Health · 75% · Strong ·

The Good
D1 · TypeScript Cyclomatic Complexity 9.3 D2 · TypeScript Cognitive Complexity 8.6 D3 · TypeScript God Classes 10.0 D4 · TypeScript Code Duplication 10.0 D17 · TypeScript Explicit Debt 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 10.0 R1 · React / TS Type Safety 10.0 R10 · React / TS Code Duplication 8.6 R2 · React / TS Cyclomatic Complexity 9.6 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 X2 · Repo Cancellation propagation 10.0 X20 · Repo Mistyped argument guard 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 8.4
The Bad
R3 · React / TS Large Files 6.2 R7 · React / TS Dead Code 6.7 X3 · Repo Exception handling 6.3

At a glance — Architecture · 71% · Adequate · gated by D26, R11 ·

The Good
D5 · TypeScript Coupling 10.0 D6 · TypeScript Cohesion (LCOM4) 9.9 D7 · TypeScript Architectural Integrity 10.0 D22 · TypeScript Internal API Consistency 7.0 D35 · TypeScript Change Coupling 10.0 AX10 · Repo Code composition 7.8 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.9 R9 · React / TS Circular Imports 10.0
The Ugly
D26 · TypeScript Project Cohesion 0.0 R11 · React / TS Import Boundaries 2.6

At a glance — Maturity · 52% · Adequate · gated by D34, M4 ·

The Good
D15 · TypeScript Churn × Complexity Hotspots 10.0 D16 · TypeScript Bus Factor 9.8 D19 · TypeScript Documentation Quality 9.6 D20 · TypeScript ADR Quality 9.8 D21 · TypeScript Naming Consistency 10.0 D25 · TypeScript ADR Conformance 10.0 M1 · Repo Documentation (README) 9.2 M2 · Repo Architecture documentation 7.0 M3 · Repo Folder & project structure 10.0
The Ugly
D34 · TypeScript Knowledge Freshness 0.0 M4 · Repo Documentation accuracy 0.0

At a glance — Readiness · 70% · Adequate · gated by R4 ·

The Good
D8 · TypeScript Code Coverage 9.9 D10 · TypeScript Test Quality 9.5 D11 · TypeScript Test Reliability 10.0 D12 · TypeScript Dependency Hygiene 8.7 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 P2 · Repo Observability 9.0 P3 · Repo Security & performance tooling 7.0 P4 · Repo Deployment & Rollback 8.0 P5 · Repo DR & Backup 10.0 P6 · Repo Release Hygiene 10.0 R5 · React / TS Dependency Freshness 7.4 R6 · React / TS Tooling 10.0 R8 · React / TS Dependency Hygiene 10.0
The Bad
D9 · TypeScript Test Distribution 6.4
The Ugly
R4 · React / TS Test Coverage 3.7

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

The Good
D28 · TypeScript Secrets (history) 10.0 D31 · TypeScript IaC & Container Security 7.0 D37 · TypeScript Vulnerability-disclosure Policy 10.0 D43 · TypeScript Malicious Dependencies 10.0 D44 · TypeScript Platform End-of-Life 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0
The Ugly
D29 · TypeScript Static Analysis (SAST) 3.9 D30 · TypeScript Dependency Vulnerabilities 0.0 D36 · TypeScript Supply-chain Provenance & Signing 0.0 X14 · Repo Bypassable address classification 3.5 X17 · Repo Uncapped recursion over a caller-supplied document 2.7

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

The Good
DM6 · Repo Domain ↔ infrastructure boundary 10.0 DM9 · Repo Scattered domain decisions 8.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 — Injection50High / Critical
A03:2025 — Software Supply Chain Failures36High / Critical
A02:2025 — Security Misconfiguration21High / Critical

Roadmap

Begin by resolving the 114 orphaned files in the knowledge base and addressing 19 high-severity dependency vulnerabilities to immediately reduce technical debt and security risk. Next, reconcile documentation inaccuracies and expand the architecture decision record to ensure alignment between written guides and the actual codebase. Finally, enforce import boundaries to eliminate cross-layer violations and maintain clean module structures.

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

Do thisHelpsEffortDimension
Resolve the 114 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (15), entities.ts (4), p2mr-adapter.ts (3).+7.7 ptsHighKnowledge Freshness
Reconcile the README with reality: CONTRIBUTING.md names `test/coverage-expansion`, but no file or folder `test/coverage-expansion` exists; CONTRIBUTING.md names `docs/restructure`, but no file or folder `docs/restructure` exists; CONTRIBUTING.md names `infra/terraform`, but no file or folder `infra/terraform` exists; docs/architecture/local-demo-blueprint.md links to `modules/integrations/fabric-gateway/src/index.ts`, but `docs/architecture/modules/integrations/fabric-gateway/src/index.ts` does not exist; docs/architecture/local-demo-blueprint.md links to `contracts/ConsortiumOrderRegistry.sol`, but `docs/architecture/contracts/ConsortiumOrderRegistry.sol` does not exist.+7.5 ptsMediumDocumentation accuracy
Grow the ADR log (currently 6) — reach 8 to raise the maturity tier; document significant decisions as they're made.+2.4 ptsMediumArchitecture documentation
Resolve the 19 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (19).+1.8 ptsMediumDependency Vulnerabilities
Resolve the 1 Split packages/enterprise-blockchain finding(s) in Project Cohesion.+0.7 ptsLowProject Cohesion
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED.+0.6 ptsLowStatic Analysis (SAST)
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED.+0.6 ptsLowStatic Analysis (SAST)
Resolve the 4 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4).+0.6 ptsLowDependency Vulnerabilities

File quality

Per-file score 0–10 — a quality signature. Of 45 files carrying findings, judged against the Production bar: 9% slop · 58% mixed · 33% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.5SlopIaC & Container Security: High IaC: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.7SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedIaC & Container Security: Medium IaC: REDACTED
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED7.2MixedStatic Analysis (SAST): High: REDACTED
REDACTED7.2MixedStatic Analysis (SAST): High: REDACTED
REDACTED7.2MixedStatic Analysis (SAST): High: REDACTED
demo/e2e/scenarios.spec.ts7.4MixedTest Quality: Skipped test: (unnamed test)
demo/e2e/real-prover.spec.ts7.4MixedTest Quality: Skipped test: (unnamed test)
modules/p2mr/src/script-leaf.ts7.8MixedCyclomatic Complexity: script-leaf.validateScriptLeaf (cyclomatic 20)

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 — 69

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 — 216

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 — 297

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

Could not be resolved — 4

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. 81 of 88 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 7 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 — 88 dimensions across the health lenses
D1D2D3D4D5D6D7D8D9D10D11D12D13D14D15D16D17D19D20D21D22D25D26D28D29D30D31D34D35D36D37D43D44AX10AX3AX4AX5AX6DM6DM9GD1IC1M1M2M3M4P1P10P2P3P4P5P6PF3R1R10R11R2R3R4R5R6R7R8R9X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X5

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, 547 of 582 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 · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ 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 01a16466-4fa1-77b8-9288-df22d3819eba.

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.

  • 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.
  • AXR1 Runtime accessibility — 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. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — prometheus Error context canceled stone-prover Warning context canceled besu-validator-1 Error context canceled corda-notary Error context canceled corda-partya Error context canceled corda-partyb Error context canceled besu-validator-0 Error context canceled otel-collector Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: fabric-peer-org2 Error context canceled corda-partya Error context canceled jaeger Error context canceled otel-collector Error context canceled stone-prover Warning context canceled prometheus Error context canceled WARNING: Some service image(s) must be built from source by running: docker compose build stone-prover Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
  • 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.
  • 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. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
  • P2 Observability — 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. 23 further occurrence(s) are not listed individually; the score already reflects all 63.
  • 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. 61 further occurrence(s) are not listed individually; the score already reflects all 101.
  • R4 Test Coverage — 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. 51 further occurrence(s) are not listed individually; the score already reflects all 91.
  • R7 Dead Code — 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. 12 further occurrence(s) are not listed individually; the score already reflects all 52.
  • 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. 208 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: 7 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

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.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside 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.
  • D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality 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.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • 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.
  • D25 ADR Conformance: ADR conformance is the LLM-scored fraction of sampled code that follows recorded decisions — it checks the decisions that were written down and the slices it sampled, not unrecorded rules or the whole tree.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • 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".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (7): D19, D20, D21, D22, D25, D26, 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 Complexity9.3 / 10Stronggated by 5 serious findings✓ 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 9.3 / 10 · rule-coverage 100% · ceiling Prevented

5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was script-leaf.validateScriptLeaf at 20.

script-leaf.validateScriptLeaf (cyclomatic 20) · ×2modules/p2mr/src/script-leaf.ts:43
spend-proof.validateWitnessStructure (cyclomatic 20) · ×2modules/p2mr/src/spend-proof.ts:370
AsymmetricKeyService.generateKeyPairAsync (cyclomatic 17)modules/hsm/src/application/asymmetric-key-service.ts:207

What to do

  1. Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with script-leaf.validateScriptLeaf (cyclomatic 20), spend-proof.validateWitnessStructure (cyclomatic 20), script-leaf.validateScriptLeaf (cyclomatic 20). — 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 5 together lifts Cyclomatic Complexity from 9.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D2 · Cognitive Complexity8.6 / 10Strong✓ 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 8.6 / 10 · rule-coverage 100% · ceiling Prevented

12 method(s) exceeded the cognitive complexity threshold of 15; the worst was script-leaf.validateScriptLeaf at 24.

script-leaf.validateScriptLeaf (cognitive 24) · ×2modules/p2mr/src/script-leaf.ts:43
spend-proof.validateWitnessStructure (cognitive 23) · ×2modules/p2mr/src/spend-proof.ts:370
MPCEngine.submitShare (cognitive 20) · ×2modules/mpc/src/index.ts:278
QuantumResistantVault.distributeSecret (cognitive 18) · ×2modules/mpc/src/quantum.ts:82
retry.withRetry (cognitive 16) · ×2modules/integrations/shared/src/retry.ts:125

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

What to do

  1. Bring the 12 bodies over 15 down to 15 or less in Cognitive Complexity — start with script-leaf.validateScriptLeaf (cognitive 24), script-leaf.validateScriptLeaf (cognitive 24), spend-proof.validateWitnessStructure (cognitive 23). — 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 12 together lifts Cognitive Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D3 · God Classes10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 god class(es) detected.

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md.

D4 · Code Duplication10.0 / 10Stronggated by 1 serious finding✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Verified

1 duplicated block group(s) detected. Measured on part of this repository only: .ts (92% 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 (17 lines × 2)contracts/corda/ProviderClearanceFlow.kt:81

What to do

  1. Resolve the 1 Duplicated block (17 lines × 2) finding(s) in Code Duplication — start with ProviderClearanceFlow.kt. — One of this dimension's main actionable groups (1 warning-level).
  2. 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.

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

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

3 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)9.9 / 10Stronggated by 1 serious finding✓ 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 9.9 / 10 · rule-coverage 100% · ceiling Verified

1 of 95 classes have LCOM4 above 3.

Low cohesion: SolanaDevnetAdapter (LCOM4 4)modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts:49

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with solana-adapter.ts. — One of this dimension's main actionable groups (1 warning-level).
  2. Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D7 · Architectural Integrity10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the code respects its intended layering / architecture rules.

Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.

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

All 3 mechanizable ADR(s) are enforced: 3 by analyzers, 0 by tests. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).

✓ On the Gold path — maintain.

Detailed fixes: d7_recommendation.md.

D8 · Code Coverage9.9 / 10Exemplary✓ 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 9.9 / 10 · rule-coverage 100% · ceiling Verified

Line coverage 82.1%. Measured from the JavaScript/TypeScript suite (node:test via `npm ci --ignore-scripts` in the repository root).

✓ On the Gold path — maintain.

Detailed fixes: d8_recommendation.md.

D9 · Test Distribution6.4 / 10Adequate✓ 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 6.4 / 10 · rule-coverage 100% · ceiling Documented

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

What to do

  1. Improve Test Distribution — currently 6.4/10. — 410 test methods: 297 unit, 0 integration, 0 BDD, 113 e2e. The JavaScript/TypeScript suite contributes 410 `it`/`test` case(s) across 29 test file(s) declaring at least one; its tier split is read from package names and paths only.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality9.5 / 10Stronggated by 10 serious findings✓ 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 9.5 / 10 · rule-coverage 100% · ceiling Prevented

21 skipped (12 with a documented reason), 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 410 tests.

Skipped test: (unnamed test) · ×9demo/e2e/scenarios.spec.ts:122
No assertions: MPC: allows same nonce in different computationstests/mpc.property.test.ts:364
Skipped (documented): validator-0 responds to health check · ×12tests/e2e-blockchain.e2e.ts:69

What to do

  1. Resolve the 9 Skipped test finding(s) in Test Quality — start with scenarios.spec.ts (3), real-prover.spec.ts (3), dashboard.spec.ts (2). — One of this dimension's main actionable groups (9 warning-level).
  2. Resolve the 1 No assertions finding(s) in Test Quality — start with mpc.property.test.ts. — One of this dimension's main actionable groups (1 warning-level).

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

D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests pass reliably, with no flakiness.

Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.

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

0 flaky across 1 measured tier(s). JavaScript/TypeScript (node:test via `npm ci --ignore-scripts` in the repository root (266 tests); vitest via `npm ci --ignore-scripts` in demo/ (33 tests)): measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

D12 · Dependency Hygiene8.7 / 10Strong✓ 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 8.7 / 10 · rule-coverage 100% · ceiling Verified

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

Deprecated: starknetpackage.json:68
Deprecated: glob · ×2REDACTED:5600
Outdated (npm): @grpc/grpc-js · ×17

What to do

  1. Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
  2. Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with package.json. — One of this dimension's main actionable groups (1 warning-level).

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 21 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 21 production dependency(ies) this repository's committed lockfile resolves, across 3 product package.json manifest(s). Its 35 `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 Apache-2.0, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Stronggated by 1 serious finding✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: modules/mpc/src/quantum.ts (6×15=90)

Hotspot: modules/mpc/src/quantum.tsmodules/mpc/src/quantum.ts:82

What to do

  1. Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with quantum.ts. — One of this dimension's main actionable groups (1 warning-level).

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

D16 · Bus Factor9.8 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

7 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is modules/hsm/src/application/asymmetric-key-service.ts. Counted over 117 of the 211 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Small-team knowledge concentration

✓ On the Gold path — maintain.

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

D17 · Explicit Debt10.0 / 10Stronggated by 2 serious findings✓ Tool-verified

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

2 deducted task-comment markers across 38849 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.

TodoComment · ×2modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts:233

What to do

  1. Resolve the 2 TodoComment finding(s) in Explicit Debt — start with starknet-proof-adapter.ts (2). — One of this dimension's main actionable groups (2 warning-level).
  2. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.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

Enterprise Blockchain documentation is clear and complete for its repository root README (overview + npm install/usage), four architecture/design docs (cairo/, contracts/fabric/, skills/, docs/adr/) covering the full project scope, and seven subdirectories (contracts/solidity/, demo/, infra/, skills/, docs/presentation/) each documenting their own directories. The visible content is exemplary: a README that states what it documents (the enterprise blockchain case studies) rather than the repository as a whole; an architecture diagram for Cairo's 3-tier recursive aggregation pipeline; runnable example catalogs; and a companion-resources section linking domain-specific skills to the main package. The repository's READMEs and architecture/Docs markdown files are exemplary documentation for a software project focused on cross-border financial settlement systems (HSM envelopes, hybrid KEM key exchange, HSM ceremonies), with each document clearly stating what it demonstrates and showing run commands. The visible content is complete: the aid-voucher-reconciliation examples give an overview; the hybrid-KEM example explains why hybrid instead of pure ML-KEM, lists real-world deployments, shows construction code, and ends in a clipped wire-format section that the outline confirms exists.

Documentation: no project overviewexamples/hybrid-kem-settlement/README.md

✓ On the Gold path — maintain.

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

D20 · ADR QualityExemplary◐ Sampled · advisory

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

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

Evaluated 5 ADR(s) individually; mean quality 9.8/10 (consistently complete and clear). 0 flagged with a specific gap.

✓ On the Gold path — maintain.

Detailed fixes: d20_recommendation.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 ConsistencyStrong◐ 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 Strong / 10 · rule-coverage 100% · ceiling Verified

3 API inconsistencies across a 400-member sample of 322 exposed types.

Redundant verification methods with overlapping intent. `verify` computes the hash of the leaf internally, while `verifyHash` expects the hash. This forces callers to either duplicate hashing logic or choose between two nearly identical methods based on an implementation detail.
Inconsistent naming and scope of verification methods. `validateSpendProofStructure` and `verifySpendProofStructure` appear to do similar structural checks but have different names and potentially different inputs (one takes just proof, the other takes proof + output). `verifyMerkleProof` is a specific subset. The distinction between 'validate' and 'verify' is unclear and inconsistent with other parts of the API (e.g., `MerkleTree.verify` vs `MerkleTree.verifyHash`).
Multiple entry points for SHA-256 hashing with inconsistent naming and signatures. `crypto.sha256hex` and `HashingPort.sha256hex` are identical. `CommitmentProvider` also exposes `sha256hex`. This creates confusion about which utility to use and duplicates functionality across different modules (shared, p2mr, mpc).

What to do

  1. Resolve the 1 Redundant verification methods with overlapping intent. `verify`… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Inconsistent naming and scope of verification methods.… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Multiple entry points for SHA-256 hashing with inconsistent naming and… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).

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

D25 · ADR ConformanceExemplary◐ Sampled · advisory

What it measures: Whether the code actually follows the decisions recorded in the project's ADRs.

Method: Judged by language model at low temperature against ADRs plus a deterministic structural code summary; findings linked to repo-rooted ADR paths for traceability. Advisory.

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

4 conform / 0 violate across 5 ADRs.

✓ On the Gold path — maintain.

Detailed fixes: d25_recommendation.md.

D26 · Project Cohesion0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

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

Split packages/enterprise-blockchain

What to do

  1. Resolve the 1 Split packages/enterprise-blockchain finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.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)3.9 / 10Weak✓ 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 3.9 / 10 · rule-coverage 100% · ceiling Documented

50 finding(s): 0 critical, 42 high, 8 medium, 0 low. 39 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

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 Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. No action in Static Analysis (SAST) — all 39 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (39 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

30 finding(s): 4 critical, 19 high, 6 medium, 1 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

D31 · IaC & Container Security7.0 / 10Adequategated by 4 critical findings✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

21 finding(s): 0 critical, 4 high, 16 medium, 1 low.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 16 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (11), REDACTED (5). — One of this dimension's main actionable groups (16 warning-level).
  2. Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
  3. Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

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

D34 · Knowledge Freshness0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

117 of 117 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/enterprise-blockchain/src/stark-settlement/domain/ports.ts. Counted over 117 of the 211 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×114packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/stone-proof-adapter.ts:1
Most significant orphaned file · ×3packages/enterprise-blockchain/src/stark-settlement/domain/ports.ts:1
Dormant codebase

What to do

  1. Resolve the 114 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (15), entities.ts (4), p2mr-adapter.ts (3). — One of this dimension's main actionable groups (114 recommendation-level).
  2. Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with ports.ts (2), pkcs11-crypto-adapter.ts. — One of this dimension's main actionable groups (3 recommendation-level).
  3. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.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. — One of this dimension's main actionable groups (1 recommendation-level).

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

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.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.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 11 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AX10 · Code composition7.8 / 10Strong✓ 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.

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

AX6 · Interface segregation9.9 / 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.

  • `LedgerPersistencePort` declares 19 required operations: `createAccount`, `getAccount`, `getAccountByAddress`, `updateAccountBalance`, `getAccountsByAssetType`, `appendTransaction`, `getTransaction`, `getTransactionsByIdempotencyKey`, `getPendingTransactions`, `updateTransactionStatus`, `saveBaseProof`, `getBaseProof`, `getUnaggregatedBaseProofs`, `saveTier1Proof`, `getTier1Proof`, `getUnaggregatedTier1Proofs`, `saveTier2Proof`, `getTier2Proof`, `getLatestBlockProof`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — modules/stark-settlement/src/domain/ports.ts:102, packages/enterprise-blockchain/src/stark-settlement/domain/ports.ts:102

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
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 decisions8.0 / 10Strong✓ 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.

  • contracts.fabric.FoodTraceContract.TelemetryEntry's [metric, value] are judged in contracts.fabric.FoodTraceContract.FoodTraceContract, contracts.fabric.FoodTraceContractDeployable.FoodTraceContractDeployable — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
  • modules.p2mr.src.types.SpendWitness's [publicKeys, signatures] are judged in modules.p2mr.src.script-interpreter, modules.p2mr.src.spend-proof, packages.enterprise-blockchain.src.p2mr.script-interpreter, packages.enterprise-blockchain.src.p2mr.spend-proof — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
  • modules.stark-settlement.src.domain.entities.OutboxEntry's [maxRetries, retryCount, status] are judged in modules.stark-settlement.src.infrastructure.persistence.outbox-store.InMemoryOutboxStore, packages.enterprise-blockchain.src.stark-settlement.infrastructure.persistence.outbox-store.InMemoryOutboxStore — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
  • modules.stark-settlement.src.domain.entities.Tier2BlockProof's [finalProof, stateRoot, tier1ProofIds] are judged in modules.stark-settlement.src.infrastructure.adapters.mock-stark-adapter.FlexibleMockStarkAdapter, packages.enterprise-blockchain.src.stark-settlement.infrastructure.adapters.mock-stark-adapter.FlexibleMockStarkAdapter — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
  • modules.stark-settlement.src.domain.entities.Tier2BlockProof's [finalProof, stateRoot, tier1ProofIds, txCount] are judged in modules.stark-settlement.src.infrastructure.adapters.mock-stark-adapter.MockStarkAdapter, packages.enterprise-blockchain.src.stark-settlement.infrastructure.adapters.mock-stark-adapter.MockStarkAdapter — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.

What to do

  • Move each repeated judgement onto the type that owns the members it reads, so the rule has one home and cannot drift.
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.

  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×9) — demo/e2e/api.spec.ts:187, demo/e2e/dashboard.spec.ts:130, demo/e2e/dashboard.spec.ts:161, …
  • `info` has an empty body — confirm it's an intentional no-op and not an unfinished method. (×2) — modules/shared/src/logger.ts:27, packages/enterprise-blockchain/src/shared/logger.ts:27
  • `warn` has an empty body — confirm it's an intentional no-op and not an unfinished method. (×2) — modules/shared/src/logger.ts:28, packages/enterprise-blockchain/src/shared/logger.ts:28
  • `error` has an empty body — confirm it's an intentional no-op and not an unfinished method. (×2) — modules/shared/src/logger.ts:29, packages/enterprise-blockchain/src/shared/logger.ts:29

What to do

  • Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
M1 · Documentation (README)9.2 / 10Exemplary✓ 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.

What to do

  • Add a README to the 2 of 5 project(s) that lack one — worth up to 0.8 pts.
M2 · Architecture documentation7.0 / 10Strong✓ 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.

What to do

  • Grow the ADR log (currently 6) — reach 8 to raise the maturity tier; document significant decisions as they're made.
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.

  • CONTRIBUTING.md names `test/coverage-expansion`, but no file or folder `test/coverage-expansion` 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. — CONTRIBUTING.md:23
  • CONTRIBUTING.md names `docs/restructure`, but no file or folder `docs/restructure` 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. — CONTRIBUTING.md:24
  • CONTRIBUTING.md names `infra/terraform`, but no file or folder `infra/terraform` 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. — CONTRIBUTING.md:25
  • docs/architecture/local-demo-blueprint.md links to `modules/integrations/fabric-gateway/src/index.ts`, but `docs/architecture/modules/integrations/fabric-gateway/src/index.ts` 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. — docs/architecture/local-demo-blueprint.md:10
  • docs/architecture/local-demo-blueprint.md links to `contracts/ConsortiumOrderRegistry.sol`, but `docs/architecture/contracts/ConsortiumOrderRegistry.sol` 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. — docs/architecture/local-demo-blueprint.md:15
  • docs/architecture/local-demo-blueprint.md links to `modules/integrations/besu-client/src/index.ts`, but `docs/architecture/modules/integrations/besu-client/src/index.ts` 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. — docs/architecture/local-demo-blueprint.md:17
  • docs/architecture/local-demo-blueprint.md links to `modules/integrations/corda-gateway/src/index.ts`, but `docs/architecture/modules/integrations/corda-gateway/src/index.ts` 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. — docs/architecture/local-demo-blueprint.md:22
  • docs/architecture/scenario-to-protocol-mapping.md links to `modules/traceability/src/index.ts`, but `docs/architecture/modules/traceability/src/index.ts` 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. — docs/architecture/scenario-to-protocol-mapping.md:8
  • docs/architecture/scenario-to-protocol-mapping.md links to `modules/protocols/fabric/src/index.ts`, but `docs/architecture/modules/protocols/fabric/src/index.ts` 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. — docs/architecture/scenario-to-protocol-mapping.md:9
  • docs/architecture/scenario-to-protocol-mapping.md links to `modules/privacy/src/index.ts`, but `docs/architecture/modules/privacy/src/index.ts` 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. — docs/architecture/scenario-to-protocol-mapping.md:24
  • docs/architecture/scenario-to-protocol-mapping.md links to `modules/protocols/besu/src/index.ts`, but `docs/architecture/modules/protocols/besu/src/index.ts` 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. — docs/architecture/scenario-to-protocol-mapping.md:25
  • docs/architecture/scenario-to-protocol-mapping.md links to `modules/credentialing/src/index.ts`, but `docs/architecture/modules/credentialing/src/index.ts` 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. — docs/architecture/scenario-to-protocol-mapping.md:40
  • docs/architecture/scenario-to-protocol-mapping.md links to `modules/protocols/corda/src/index.ts`, but `docs/architecture/modules/protocols/corda/src/index.ts` 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. — docs/architecture/scenario-to-protocol-mapping.md:41
  • docs/presentation/enterprise-blockchain-deck.md installs `#` (`npm install # install dependencies`), but no package.json declares 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/presentation/enterprise-blockchain-deck.md:509
  • docs/presentation/enterprise-blockchain-deck.md installs `install` (`npm install # install dependencies`), but no package.json declares 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/presentation/enterprise-blockchain-deck.md:509
  • docs/presentation/enterprise-blockchain-deck.md installs `dependencies` (`npm install # install dependencies`), but no package.json declares 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/presentation/enterprise-blockchain-deck.md:509
  • docs/research/initial-usage-research.md runs `./install-fabric.sh`, but `install-fabric.sh` 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. — docs/research/initial-usage-research.md:1398
  • docs/research/initial-usage-research.md runs `./network.sh up createChannel -ca -s couchdb`, but `network.sh` 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. — docs/research/initial-usage-research.md:1402
  • docs/research/initial-usage-research.md documents the environment variable `FABRIC_CFG_PATH`, 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/research/initial-usage-research.md:1410

What to do

  • Reconcile the README with reality: CONTRIBUTING.md names `test/coverage-expansion`, but no file or folder `test/coverage-expansion` exists; CONTRIBUTING.md names `docs/restructure`, but no file or folder `docs/restructure` exists; CONTRIBUTING.md names `infra/terraform`, but no file or folder `infra/terraform` exists; docs/architecture/local-demo-blueprint.md links to `modules/integrations/fabric-gateway/src/index.ts`, but `docs/architecture/modules/integrations/fabric-gateway/src/index.ts` does not exist; docs/architecture/local-demo-blueprint.md links to `contracts/ConsortiumOrderRegistry.sol`, but `docs/architecture/contracts/ConsortiumOrderRegistry.sol` 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.

  • `echo "Terraform files are not formatted. Run 'terraform fmt -recursive' in the infra/ directory."` invokes terraform fmt in the mode that REWRITES the files it reformats and exits 0 whatever it changed. The rewrite happens inside the runner's throwaway checkout and is then discarded, so the step passes on a badly-formatted change exactly as it passes on a clean one — it enforces nothing, and no other step in this file reads the result. `-check` is the flag that turns the same invocation into a gate: it leaves the files alone and exits non-zero when anything would have been reformatted. — REDACTED:75

What to do

  • Add `-check` to the terraform fmt step in `REDACTED` so a change that is not formatted fails CI, instead of being silently reformatted into a checkout that is thrown away — or, if reformatting the branch is the intent, commit the result back so the fix reaches the repository.
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.

P2 · Observability9.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • `modules/hsm/src/infrastructure/syslog-audit-log.ts` reports through `console.*` at line 225 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/hsm/src/infrastructure/syslog-audit-log.ts:225
  • `modules/shared/src/telemetry-sdk.ts` reports through `console.*` at line 63 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/shared/src/telemetry-sdk.ts:63
  • `modules/shared/src/telemetry-sdk.ts` reports through `console.*` at line 66 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/shared/src/telemetry-sdk.ts:66
  • `modules/shared/src/telemetry-sdk.ts` reports through `console.*` at line 73 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/shared/src/telemetry-sdk.ts:73
  • `modules/shared/src/telemetry-sdk.ts` reports through `console.*` at line 77 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/shared/src/telemetry-sdk.ts:77
  • `modules/stark-settlement/src/application/settlement-service.ts` reports through `console.*` at line 244 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/application/settlement-service.ts:244
  • `modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts` reports through `console.*` at line 122 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:122
  • `modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts` reports through `console.*` at line 142 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:142
  • `modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts` reports through `console.*` at line 156 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:156
  • `modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts` reports through `console.*` at line 189 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:189
  • `modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts` reports through `console.*` at line 255 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:255
  • `modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts` reports through `console.*` at line 328 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:328
  • `modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts` reports through `console.*` at line 378 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:378
  • `modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts` reports through `console.*` at line 448 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:448
  • `modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts` reports through `console.*` at line 453 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:453
  • `modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts` reports through `console.*` at line 84 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts:84
  • `modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts` reports through `console.*` at line 136 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts:136
  • `modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts` reports through `console.*` at line 194 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts:194
  • `modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts` reports through `console.*` at line 245 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts:245
  • `modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts` reports through `console.*` at line 98 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts:98
  • `modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts` reports through `console.*` at line 101 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts:101
  • `modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts` reports through `console.*` at line 102 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts:102
  • `modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts` reports through `console.*` at line 125 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts:125
  • `modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts` reports through `console.*` at line 132 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts:132
  • `modules/stark-settlement/src/infrastructure/adapters/fiat-adapter.ts` reports through `console.*` at line 98 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/fiat-adapter.ts:98
  • `modules/stark-settlement/src/infrastructure/adapters/fiat-adapter.ts` reports through `console.*` at line 99 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/fiat-adapter.ts:99
  • `modules/stark-settlement/src/infrastructure/adapters/fiat-adapter.ts` reports through `console.*` at line 100 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/fiat-adapter.ts:100
  • `modules/stark-settlement/src/infrastructure/adapters/fiat-adapter.ts` reports through `console.*` at line 101 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/fiat-adapter.ts:101
  • `modules/stark-settlement/src/infrastructure/adapters/event-emitter-adapter.ts` reports through `console.*` at line 42 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/event-emitter-adapter.ts:42
  • `modules/stark-settlement/src/infrastructure/adapters/event-emitter-adapter.ts` reports through `console.*` at line 53 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/event-emitter-adapter.ts:53
  • `modules/stark-settlement/src/infrastructure/adapters/event-emitter-adapter.ts` reports through `console.*` at line 150 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/event-emitter-adapter.ts:150
  • `modules/stark-settlement/src/infrastructure/adapters/bitcoin-adapter.ts` reports through `console.*` at line 110 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/bitcoin-adapter.ts:110
  • `modules/stark-settlement/src/infrastructure/adapters/bitcoin-adapter.ts` reports through `console.*` at line 111 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/bitcoin-adapter.ts:111
  • `modules/stark-settlement/src/infrastructure/adapters/bitcoin-adapter.ts` reports through `console.*` at line 112 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/bitcoin-adapter.ts:112
  • `modules/stark-settlement/src/infrastructure/adapters/bitcoin-adapter.ts` reports through `console.*` at line 136 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/bitcoin-adapter.ts:136
  • `modules/stark-settlement/src/infrastructure/adapters/bitcoin-adapter.ts` reports through `console.*` at line 145 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — modules/stark-settlement/src/infrastructure/adapters/bitcoin-adapter.ts:145
  • `packages/enterprise-blockchain/src/hsm/infrastructure/syslog-audit-log.ts` reports through `console.*` at line 257 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/enterprise-blockchain/src/hsm/infrastructure/syslog-audit-log.ts:257
  • `packages/enterprise-blockchain/src/p2mr/script-interpreter.ts` reports through `console.*` at line 113 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/enterprise-blockchain/src/p2mr/script-interpreter.ts:113
  • `packages/enterprise-blockchain/src/shared/telemetry-sdk.ts` reports through `console.*` at line 46 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/enterprise-blockchain/src/shared/telemetry-sdk.ts:46
  • `packages/enterprise-blockchain/src/shared/telemetry-sdk.ts` reports through `console.*` at line 51 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/enterprise-blockchain/src/shared/telemetry-sdk.ts:51

What to do

  • Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
  • Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling7.0 / 10Strong✓ 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.

What to do

  • Dependabot is configured but does not watch `gitsubmodule` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback8.0 / 10Strong✓ 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.

  • Deployment 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 reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.

What to do

  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

P6 · Release Hygiene10.0 / 10Exemplary✓ 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.

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 Safety10.0 / 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.

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.

  • 95 duplicated blocks under the repository root have copies in at least two of the sibling directories modules, packages — 87 of them are reported below, and 8 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 95 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 95 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 95 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — modules/p2mr/src/script-interpreter.ts:17
  • modules/p2mr/src/script-interpreter.ts:17 · packages/enterprise-blockchain/src/p2mr/script-interpreter.ts:17 — these 2 files are line-for-line copies of one another — 363 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/p2mr/src/script-interpreter.ts:17
  • modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:27 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/stone-proof-adapter.ts:27 — these 2 files are line-for-line copies of one another — 304 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:27
  • modules/mpc/src/index.ts:8 · packages/enterprise-blockchain/src/mpc/index.ts:8 — these 2 files are line-for-line copies of one another — 287 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/mpc/src/index.ts:8
  • modules/integrations/shared/src/retry.ts:14 · packages/enterprise-blockchain/src/integrations/shared/retry.ts:14 — these 2 files are line-for-line copies of one another — 258 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/integrations/shared/src/retry.ts:14
  • modules/integrations/besu-client/src/index.ts:7 · packages/enterprise-blockchain/src/integrations/besu-client/index.ts:7 — these 2 files are line-for-line copies of one another — 224 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/integrations/besu-client/src/index.ts:7
  • modules/stark-settlement/src/domain/value-objects.ts:16 · packages/enterprise-blockchain/src/stark-settlement/domain/value-objects.ts:16 — these 2 files are line-for-line copies of one another — 207 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/stark-settlement/src/domain/value-objects.ts:16
  • modules/stark-settlement/src/application/settlement-service.ts:15 · packages/enterprise-blockchain/src/stark-settlement/application/settlement-service.ts:15 — these 2 files are line-for-line copies of one another — 194 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/stark-settlement/src/application/settlement-service.ts:15
  • modules/p2mr/src/spend-proof.ts:10 · packages/enterprise-blockchain/src/p2mr/spend-proof.ts:10 — these 2 files are line-for-line copies of one another — 193 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/p2mr/src/spend-proof.ts:10
  • modules/stark-settlement/src/infrastructure/adapters/mock-stark-adapter.ts:14 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/mock-stark-adapter.ts:14 — these 2 files are line-for-line copies of one another — 191 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/stark-settlement/src/infrastructure/adapters/mock-stark-adapter.ts:14
  • modules/integrations/fabric-gateway/src/index.ts:1 · packages/enterprise-blockchain/src/integrations/fabric-gateway/index.ts:1 — these 2 files are line-for-line copies of one another — 183 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/integrations/fabric-gateway/src/index.ts:1
  • modules/stark-settlement/src/infrastructure/persistence/ledger-store.ts:12 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/persistence/ledger-store.ts:12 — these 2 files are line-for-line copies of one another — 175 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/stark-settlement/src/infrastructure/persistence/ledger-store.ts:12
  • modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts:18 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/starknet-proof-adapter.ts:18 — these 2 files are line-for-line copies of one another — 168 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts:18
  • modules/stark-settlement/src/application/aggregator-service.ts:14 · packages/enterprise-blockchain/src/stark-settlement/application/aggregator-service.ts:14 — these 2 files are line-for-line copies of one another — 158 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/stark-settlement/src/application/aggregator-service.ts:14
  • modules/stark-settlement/src/domain/entities.ts:26 · packages/enterprise-blockchain/src/stark-settlement/domain/entities.ts:26 — these 2 files are line-for-line copies of one another — 147 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/stark-settlement/src/domain/entities.ts:26
  • modules/stark-settlement/src/domain/ports.ts:15 · packages/enterprise-blockchain/src/stark-settlement/domain/ports.ts:15 — these 2 files are line-for-line copies of one another — 146 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/stark-settlement/src/domain/ports.ts:15
  • modules/integrations/corda-gateway/src/index.ts:31 · packages/enterprise-blockchain/src/integrations/corda-gateway/index.ts:31 — the two spans are one implementation copied and then locally edited — 819 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. — modules/integrations/corda-gateway/src/index.ts:31
  • modules/stark-settlement/src/infrastructure/adapters/bitcoin-adapter.ts:19 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/bitcoin-adapter.ts:19 — these 2 files are line-for-line copies of one another — 140 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/stark-settlement/src/infrastructure/adapters/bitcoin-adapter.ts:19
  • modules/mpc/src/quantum.ts:1 · packages/enterprise-blockchain/src/mpc/quantum.ts:1 — these 2 files are line-for-line copies of one another — 131 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/mpc/src/quantum.ts:1
  • modules/stark-settlement/src/infrastructure/adapters/event-emitter-adapter.ts:17 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/event-emitter-adapter.ts:35 — the two spans are one implementation copied and then locally edited — 915 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. — modules/stark-settlement/src/infrastructure/adapters/event-emitter-adapter.ts:17
  • modules/stark-settlement/src/infrastructure/adapters/fiat-adapter.ts:18 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/fiat-adapter.ts:18 — these 2 files are line-for-line copies of one another — 130 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/stark-settlement/src/infrastructure/adapters/fiat-adapter.ts:18
  • modules/hsm/src/infrastructure/syslog-audit-log.ts:1 · packages/enterprise-blockchain/src/hsm/infrastructure/syslog-audit-log.ts:1 — these 2 files are line-for-line copies of one another — 116 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/hsm/src/infrastructure/syslog-audit-log.ts:1
  • modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts:19 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/solana-adapter.ts:19 — these 2 files are line-for-line copies of one another — 108 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts:19
  • modules/stark-settlement/src/infrastructure/persistence/outbox-store.ts:18 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/persistence/outbox-store.ts:18 — these 2 files are line-for-line copies of one another — 105 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/stark-settlement/src/infrastructure/persistence/outbox-store.ts:18
  • modules/stark-settlement/src/index.ts:254 · packages/enterprise-blockchain/src/stark-settlement/index.ts:254 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — modules/stark-settlement/src/index.ts:254
  • modules/protocols/corda/src/p2mr-adapter.ts:13 · modules/protocols/fabric/src/p2mr-adapter.ts:13 — these 2 files are line-for-line copies of one another — 99 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/protocols/corda/src/p2mr-adapter.ts:13
  • modules/hsm/src/infrastructure/file-audit-log.ts:1 · packages/enterprise-blockchain/src/hsm/infrastructure/file-audit-log.ts:1 — these 2 files are line-for-line copies of one another — 89 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/hsm/src/infrastructure/file-audit-log.ts:1
  • modules/p2mr/src/merkle-tree.ts:27 · packages/enterprise-blockchain/src/p2mr/merkle-tree.ts:32 — these 2 files are line-for-line copies of one another — 87 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/p2mr/src/merkle-tree.ts:27
  • modules/p2mr/src/script-leaf.ts:20 · packages/enterprise-blockchain/src/p2mr/script-leaf.ts:20 — these 2 files are line-for-line copies of one another — 85 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/p2mr/src/script-leaf.ts:20
  • modules/stark-settlement/src/infrastructure/adapters/audit-adapter.ts:12 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/audit-adapter.ts:12 — these 2 files are line-for-line copies of one another — 84 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/stark-settlement/src/infrastructure/adapters/audit-adapter.ts:12
  • modules/mpc/src/field.ts:15 · packages/enterprise-blockchain/src/mpc/field.ts:16 — these 2 files are line-for-line copies of one another — 76 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/mpc/src/field.ts:15
  • modules/mpc/src/kyber.ts:24 · packages/enterprise-blockchain/src/mpc/kyber.ts:24 — these 2 files are line-for-line copies of one another — 76 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/mpc/src/kyber.ts:24
  • modules/hsm/src/application/asymmetric-key-service.ts:66 · packages/enterprise-blockchain/src/hsm/application/asymmetric-key-service.ts:31 — the two spans are one implementation copied and then locally edited — 467 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. — modules/hsm/src/application/asymmetric-key-service.ts:66
  • modules/shared/src/telemetry.ts:22 · packages/enterprise-blockchain/src/shared/telemetry.ts:29 — these 2 files are line-for-line copies of one another — 75 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/shared/src/telemetry.ts:22
  • modules/aid-settlement/src/application/reconciler.ts:1 · packages/enterprise-blockchain/src/aid-settlement/application/reconciler.ts:1 — these 2 files are line-for-line copies of one another — 74 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/aid-settlement/src/application/reconciler.ts:1
  • modules/credentialing/src/application/clearance-evaluator.ts:17 · packages/enterprise-blockchain/src/credentialing/application/clearance-evaluator.ts:20 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — modules/credentialing/src/application/clearance-evaluator.ts:17
  • modules/traceability/src/application/recall-assessor.ts:6 · packages/enterprise-blockchain/src/traceability/application/recall-assessor.ts:6 — these 2 files are line-for-line copies of one another — 70 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/traceability/src/application/recall-assessor.ts:6
  • modules/mpc/src/dsa.ts:27 · packages/enterprise-blockchain/src/mpc/dsa.ts:27 — these 2 files are line-for-line copies of one another — 65 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/mpc/src/dsa.ts:27
  • modules/mpc/src/hybrid-kem.ts:32 · packages/enterprise-blockchain/src/mpc/hybrid-kem.ts:32 — these 2 files are line-for-line copies of one another — 62 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/mpc/src/hybrid-kem.ts:32
  • modules/stark-settlement/src/infrastructure/adapters/dilithium-adapter.ts:13 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/dilithium-adapter.ts:13 — these 2 files are line-for-line copies of one another — 61 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — modules/stark-settlement/src/infrastructure/adapters/dilithium-adapter.ts:13

What to do

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

React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).

Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.

  • modules/p2mr/src/adapters.ts:10 reaches into another package with a relative path (../../mpc/src/dsa) — import the package by name instead. — modules/p2mr/src/adapters.ts:10
  • modules/p2mr/src/adapters.ts:11 reaches into another package with a relative path (../../shared/src/crypto) — import the package by name instead. — modules/p2mr/src/adapters.ts:11
  • modules/p2mr/src/merkle-tree.ts:14 reaches into another package with a relative path (../../shared/src/crypto) — import the package by name instead. — modules/p2mr/src/merkle-tree.ts:14
  • modules/p2mr/src/p2mr-output.ts:10 reaches into another package with a relative path (../../shared/src/store) — import the package by name instead. — modules/p2mr/src/p2mr-output.ts:10
  • modules/p2mr/src/p2mr-output.ts:11 reaches into another package with a relative path (../../shared/src/store) — import the package by name instead. — modules/p2mr/src/p2mr-output.ts:11
  • modules/protocols/besu/src/p2mr-adapter.ts:27 reaches into another package with a relative path (../../../p2mr/src/types) — import the package by name instead. — modules/protocols/besu/src/p2mr-adapter.ts:27
  • modules/protocols/besu/src/p2mr-adapter.ts:28 reaches into another package with a relative path (../../../p2mr/src/index) — import the package by name instead. — modules/protocols/besu/src/p2mr-adapter.ts:28
  • modules/protocols/corda/src/p2mr-adapter.ts:20 reaches into another package with a relative path (../../../p2mr/src/types) — import the package by name instead. — modules/protocols/corda/src/p2mr-adapter.ts:20
  • modules/protocols/corda/src/p2mr-adapter.ts:21 reaches into another package with a relative path (../../../p2mr/src/merkle-tree) — import the package by name instead. — modules/protocols/corda/src/p2mr-adapter.ts:21
  • modules/protocols/fabric/src/p2mr-adapter.ts:20 reaches into another package with a relative path (../../../p2mr/src/types) — import the package by name instead. — modules/protocols/fabric/src/p2mr-adapter.ts:20
  • modules/protocols/fabric/src/p2mr-adapter.ts:21 reaches into another package with a relative path (../../../p2mr/src/merkle-tree) — import the package by name instead. — modules/protocols/fabric/src/p2mr-adapter.ts:21
  • modules/protocols/src/p2mr-port.ts:13 reaches into another package with a relative path (../../p2mr/src/types) — import the package by name instead. — modules/protocols/src/p2mr-port.ts:13
  • packages/enterprise-blockchain/src/integrations/besu-client/index.ts:12 reaches into another package with a relative path (../../../../../contracts/ConsortiumOrderRegistry.json) — import the package by name instead. — packages/enterprise-blockchain/src/integrations/besu-client/index.ts:12
  • tests/contracts.test.ts:3 reaches past another workspace package's public entry into its internals with a relative path (../contracts/fabric/FoodTraceContract) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — tests/contracts.test.ts:3

What to do

  • Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity9.6 / 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.

  • validateScriptLeaf has cyclomatic complexity 21 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — modules/p2mr/src/script-leaf.ts:43, packages/enterprise-blockchain/src/p2mr/script-leaf.ts:43
  • validateWitnessStructure has cyclomatic complexity 21 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — modules/p2mr/src/spend-proof.ts:370, packages/enterprise-blockchain/src/p2mr/spend-proof.ts:370
  • generateKeyPairAsync has cyclomatic complexity 20 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — modules/hsm/src/application/asymmetric-key-service.ts:207
  • distributeSecret has cyclomatic complexity 15 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — modules/mpc/src/quantum.ts:82, packages/enterprise-blockchain/src/mpc/quantum.ts:82
  • submitShare has cyclomatic complexity 13 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — modules/mpc/src/index.ts:278, packages/enterprise-blockchain/src/mpc/index.ts:279
  • createFromEnv has cyclomatic complexity 13 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/enterprise-blockchain/src/hsm/infrastructure/audit-log-factory.ts:85
  • validateGatewayUrl has cyclomatic complexity 12 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/enterprise-blockchain/src/integrations/corda-gateway/index.ts:134
  • createDefaultContext has cyclomatic complexity 12 and cognitive complexity 11; 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. (×2) — modules/stark-settlement/src/index.ts:317, packages/enterprise-blockchain/src/stark-settlement/index.ts:317
  • compute has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — modules/mpc/src/index.ts:388, packages/enterprise-blockchain/src/mpc/index.ts:389
  • evaluate has cyclomatic complexity 11 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — modules/credentialing/src/application/clearance-evaluator.ts:17, packages/enterprise-blockchain/src/credentialing/application/clearance-evaluator.ts:20

What to do

  • Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files6.2 / 10Adequate✓ 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.

  • modules/p2mr/src/script-interpreter.ts has 621 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — modules/p2mr/src/script-interpreter.ts:1
  • packages/enterprise-blockchain/src/p2mr/script-interpreter.ts has 621 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/enterprise-blockchain/src/p2mr/script-interpreter.ts:1
  • modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts has 577 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts:1
  • modules/stark-settlement/src/domain/ports.ts has 565 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — modules/stark-settlement/src/domain/ports.ts:1
  • packages/enterprise-blockchain/src/stark-settlement/domain/ports.ts has 565 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/enterprise-blockchain/src/stark-settlement/domain/ports.ts:1
  • modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts has 542 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:1
  • packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/stone-proof-adapter.ts has 542 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/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/stone-proof-adapter.ts:1
  • packages/enterprise-blockchain/src/mpc/index.ts has 521 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/enterprise-blockchain/src/mpc/index.ts:1
  • modules/mpc/src/index.ts has 520 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — modules/mpc/src/index.ts:1
  • modules/hsm/src/application/asymmetric-key-service.ts has 519 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — modules/hsm/src/application/asymmetric-key-service.ts:1
  • modules/stark-settlement/src/domain/value-objects.ts has 499 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — modules/stark-settlement/src/domain/value-objects.ts:1
  • packages/enterprise-blockchain/src/stark-settlement/domain/value-objects.ts has 499 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/enterprise-blockchain/src/stark-settlement/domain/value-objects.ts:1
  • modules/hsm/src/index.ts has 483 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — modules/hsm/src/index.ts:1
  • modules/stark-settlement/src/application/ledger-service.ts has 457 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — modules/stark-settlement/src/application/ledger-service.ts:1
  • packages/enterprise-blockchain/src/stark-settlement/application/ledger-service.ts has 457 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/enterprise-blockchain/src/stark-settlement/application/ledger-service.ts:1
  • modules/stark-settlement/src/domain/entities.ts has 421 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — modules/stark-settlement/src/domain/entities.ts:1
  • packages/enterprise-blockchain/src/stark-settlement/domain/entities.ts has 421 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/enterprise-blockchain/src/stark-settlement/domain/entities.ts:1
  • modules/p2mr/src/spend-proof.ts has 415 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — modules/p2mr/src/spend-proof.ts:1
  • packages/enterprise-blockchain/src/p2mr/spend-proof.ts has 415 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/enterprise-blockchain/src/p2mr/spend-proof.ts:1
  • modules/hsm/src/infrastructure/adapters/simulator-crypto-adapter.ts has 402 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — modules/hsm/src/infrastructure/adapters/simulator-crypto-adapter.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 Coverage3.7 / 10Weak✓ 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. (×40) — packages/enterprise-blockchain/src/p2mr/script-interpreter.ts:1, modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:1, packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/stone-proof-adapter.ts:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness7.4 / 10Strong✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

What to do

  • Bump outdated dependencies to current versions to limit upgrade debt.
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 Code6.7 / 10Adequate✓ 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.

  • Unreachable from the 37 application, 2 tooling and 17 test entry point(s) detected in this repo. Gate removals on `npm run typecheck` — an undetected custom entry would make these reachable.
  • no import path from any entry point (37 application, 2 tooling, 17 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×7) — modules/protocols/besu/src/p2mr-adapter.ts, modules/protocols/fabric/src/p2mr-adapter.ts, modules/protocols/corda/src/p2mr-adapter.ts, …
  • no import path from any entry point (37 application, 2 tooling, 17 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (modules/protocols/besu/src/p2mr-adapter.ts, modules/protocols/corda/src/p2mr-adapter.ts, modules/protocols/fabric/src/p2mr-adapter.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — modules/protocols/src/p2mr-port.ts
  • Nothing ultimately consumes this binding: its only referrer is the re-export in modules/hsm/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/hsm/src/index.ts in the same commit, or the barrel will import a name that no longer exists. — modules/hsm/src/infrastructure/audit-log-factory.ts:47
  • Nothing imports this binding — it is safe to review for removal. (×3) — modules/integrations/shared/src/retry.ts:66, modules/mpc/src/field.ts:36, packages/enterprise-blockchain/src/integrations/shared/retry.ts:66
  • Nothing ultimately consumes this binding: its only referrer is the re-export in modules/mpc/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/mpc/src/index.ts in the same commit, or the barrel will import a name that no longer exists. (×2) — modules/mpc/src/field.ts:235, modules/mpc/src/field.ts:239
  • Nothing ultimately consumes this binding: its only referrer is the re-export in modules/shared/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/shared/src/index.ts in the same commit, or the barrel will import a name that no longer exists. (×3) — modules/shared/src/telemetry.ts:38, modules/shared/src/telemetry.ts:44, modules/shared/src/telemetry.ts:140
  • Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists. (×22) — modules/stark-settlement/src/application/aggregator-service.ts:51, modules/stark-settlement/src/application/settlement-service.ts:65, modules/stark-settlement/src/domain/entities.ts:44, …

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency 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 classification3.5 / 10Weak✓ Tool-verified

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.

  • This function unwraps IPv4-MAPPED IPv6 (`::ffff:`, line 99) and then rejects `10.0.0.0/8` on its IPv4 path — but the IPv6 decision at line 105 classifies the address as written, and IPv4 reaches IPv6 through three MORE embeddings this function never mentions: IPv4-compatible (`::a.b.c.d`), 6to4 (`2002::/16`) and NAT64 (`64:ff9b::/96`). So `::10.0.0.1`, `2002:0a00:0001::` and `64:ff9b::10.0.0.0` all name a host inside `10.0.0.0/8` — the range this same function declares non-public — and all reach the IPv6 decision un-unwrapped, taking the opposite verdict. Unwrap every embedding to its IPv4 form before classifying, or reject any IPv6 address carrying an embedded IPv4 outright. — packages/enterprise-blockchain/src/integrations/corda-gateway/index.ts:105

What to do

  • Each finding names the IPv4 branch that rejects the host and the IPv6 branch that accepts the same host in another notation. Confirm from the two, then unwrap every IPv4-in-IPv6 embedding before classifying, or reject non-native IPv6 outright.
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 document2.7 / 10Weak✓ Tool-verified

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.

  • `canonicalJSON` is exported and takes `obj: unknown` from its caller, and it calls itself at line 33 (`canonicalJSON`) with a piece of `obj` (and at line 45) — and nowhere in `canonicalJSON` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `canonicalJSON` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — modules/p2mr/src/merkle-tree.ts:33
  • `canonicalJSON` is exported and takes `obj: unknown` from its caller, and it calls itself at line 38 (`canonicalJSON`) with a piece of `obj` (and at line 50) — and nowhere in `canonicalJSON` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `canonicalJSON` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/enterprise-blockchain/src/p2mr/merkle-tree.ts:38

What to do

  • Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern 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.

X2 · Cancellation propagation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. 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 question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). 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 (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements 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.3 / 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. (×4) — modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts:141, modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts:146, modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts:155, …

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 types8.4 / 10Strong✓ 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.

  • ~4.1 `!` null assertions per 1k TypeScript source lines — 152 assertion(s) across the 37432 source line(s) of the 208 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: modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts (24), modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts (11), packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/starknet-proof-adapter.ts (11). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

What to do

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

Reference — by lens

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 Health75%StrongSolid.
Architecture71%Adequate — gated by D26, R11Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity52%Adequate — gated by D34, M4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness70%Adequate — gated by R4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security64%Adequate — gated by D29, D30, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling100%ExemplaryStrongest area.
Performance100%ExemplarySolid.
Unscored — 2 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.

  • P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 50 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 web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. 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).
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — prometheus Error context canceled stone-prover Warning context canceled besu-validator-1 Error context canceled corda-notary Error context canceled corda-partya Error context canceled corda-partyb Error context canceled besu-validator-0 Error context canceled otel-collector Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: fabric-peer-org2 Error context canceled corda-partya Error context canceled jaeger Error context canceled otel-collector Error context canceled stone-prover Warning context canceled prometheus Error context canceled WARNING: Some service image(s) must be built from source by running: docker compose build stone-prover Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
  • C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
  • 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.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — No inline comments to assess — comment value is not applicable here.
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.js,.ts,.tsx), 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.
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • 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.
  • DM1 Aggregate boundaries — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • DM10 One transaction, one aggregate — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • DM2 Strongly-typed ids — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • DM4 Rich vs anemic model — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • DM5 Encapsulated state — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • 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
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage data present for 58 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
  • 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: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Kotlin code has 410 production line(s), 0 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
  • S1 Web-Security Posture — Not assessed: 208 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.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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 — 69 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
  • + 14 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · High CVE · ×19
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · High IaC · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 216 finding(s)
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file packages/enterprise-blockchain/src/p2mr/script-interpreter.ts: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.
  • No test reaches this file modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts: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.
  • No test reaches this file packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/stone-proof-adapter.ts: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.
  • No test reaches this file packages/enterprise-blockchain/src/mpc/index.ts: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.
  • No test reaches this file modules/stark-settlement/src/domain/value-objects.ts: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.
  • No test reaches this file packages/enterprise-blockchain/src/stark-settlement/domain/value-objects.ts: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.
  • No test reaches this file packages/enterprise-blockchain/src/p2mr/spend-proof.ts: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.
  • No test reaches this file packages/enterprise-blockchain/src/integrations/shared/retry.ts: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.
  • No test reaches this file packages/enterprise-blockchain/src/integrations/besu-client/index.ts: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.
  • No test reaches this file modules/stark-settlement/src/index.ts: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.
  • No test reaches this file packages/enterprise-blockchain/src/stark-settlement/index.ts: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.
  • No test reaches this file modules/stark-settlement/src/infrastructure/adapters/mock-stark-adapter.ts: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.
  • No test reaches this file packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/mock-stark-adapter.ts: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.
  • No test reaches this file modules/protocols/besu/src/p2mr-adapter.ts: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.
  • No test reaches this file modules/stark-settlement/src/application/settlement-service.ts: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.
  • No test reaches this file packages/enterprise-blockchain/src/stark-settlement/application/settlement-service.ts: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.
  • No test reaches this file modules/stark-settlement/src/application/aggregator-service.ts: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.
  • No test reaches this file packages/enterprise-blockchain/src/stark-settlement/application/aggregator-service.ts: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.
  • No test reaches this file modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts: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.
  • No test reaches this file packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/starknet-proof-adapter.ts: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.
  • No test reaches this file packages/enterprise-blockchain/src/integrations/fabric-gateway/index.ts: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.
  • No test reaches this file modules/stark-settlement/src/infrastructure/persistence/ledger-store.ts: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.
  • No test reaches this file packages/enterprise-blockchain/src/stark-settlement/infrastructure/persistence/ledger-store.ts: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.
  • No test reaches this file packages/enterprise-blockchain/src/integrations/corda-gateway/index.ts: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.
  • No test reaches this file contracts/fabric/FoodTraceContractDeployable.ts: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.
  • + 15 more in this group — see findings.md.
D31 · IaC & Container Security · Medium IaC · ×16
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R11 · Import Boundaries · Boundary violation [package · ×14
  • Boundary violation [package:relative-cross-package] modules/p2mr/src/adapters.ts:10 — modules/p2mr/src/adapters.ts:10 reaches into another package with a relative path (../../mpc/src/dsa) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] modules/p2mr/src/adapters.ts:11 — modules/p2mr/src/adapters.ts:11 reaches into another package with a relative path (../../shared/src/crypto) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] modules/p2mr/src/merkle-tree.ts:14 — modules/p2mr/src/merkle-tree.ts:14 reaches into another package with a relative path (../../shared/src/crypto) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] modules/p2mr/src/p2mr-output.ts:10 — modules/p2mr/src/p2mr-output.ts:10 reaches into another package with a relative path (../../shared/src/store) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] modules/p2mr/src/p2mr-output.ts:11 — modules/p2mr/src/p2mr-output.ts:11 reaches into another package with a relative path (../../shared/src/store) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] modules/protocols/besu/src/p2mr-adapter.ts:27 — modules/protocols/besu/src/p2mr-adapter.ts:27 reaches into another package with a relative path (../../../p2mr/src/types) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] modules/protocols/besu/src/p2mr-adapter.ts:28 — modules/protocols/besu/src/p2mr-adapter.ts:28 reaches into another package with a relative path (../../../p2mr/src/index) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] modules/protocols/corda/src/p2mr-adapter.ts:20 — modules/protocols/corda/src/p2mr-adapter.ts:20 reaches into another package with a relative path (../../../p2mr/src/types) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] modules/protocols/corda/src/p2mr-adapter.ts:21 — modules/protocols/corda/src/p2mr-adapter.ts:21 reaches into another package with a relative path (../../../p2mr/src/merkle-tree) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] modules/protocols/fabric/src/p2mr-adapter.ts:20 — modules/protocols/fabric/src/p2mr-adapter.ts:20 reaches into another package with a relative path (../../../p2mr/src/types) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] modules/protocols/fabric/src/p2mr-adapter.ts:21 — modules/protocols/fabric/src/p2mr-adapter.ts:21 reaches into another package with a relative path (../../../p2mr/src/merkle-tree) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] modules/protocols/src/p2mr-port.ts:13 — modules/protocols/src/p2mr-port.ts:13 reaches into another package with a relative path (../../p2mr/src/types) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] packages/enterprise-blockchain/src/integrations/besu-client/index.ts:12 — packages/enterprise-blockchain/src/integrations/besu-client/index.ts:12 reaches into another package with a relative path (../../../../../contracts/ConsortiumOrderRegistry.json) — import the package by name instead.
  • Boundary violation [package:test-cross-package-internals] tests/contracts.test.ts:3 — tests/contracts.test.ts:3 reaches past another workspace package's public entry into its internals with a relative path (../contracts/fabric/FoodTraceContract) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
D10 · Test Quality · Skipped test · ×9
  • Skipped test: (unnamed test) demo/e2e/scenarios.spec.ts:122 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) demo/e2e/scenarios.spec.ts:143 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) demo/e2e/scenarios.spec.ts:160 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) demo/e2e/real-prover.spec.ts:69 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) demo/e2e/real-prover.spec.ts:145 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) demo/e2e/real-prover.spec.ts:193 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) demo/e2e/dashboard.spec.ts:130 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) demo/e2e/dashboard.spec.ts:161 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) demo/e2e/api.spec.ts:187 — Skipped — switched off by test.skip
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium CVE · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X3 · Exception handling · Swallowed exception (empty catch) · ×4
  • Swallowed exception (empty catch) modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts:141 — 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) modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.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.
  • Swallowed exception (empty catch) modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts:155 — 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) modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts:160 — 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.
D1 · Cyclomatic Complexity · script-leaf.validateScriptLeaf (cyclomatic 20) · ×2
  • script-leaf.validateScriptLeaf (cyclomatic 20) modules/p2mr/src/script-leaf.ts:43 — script-leaf.validateScriptLeaf 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.
  • script-leaf.validateScriptLeaf (cyclomatic 20) packages/enterprise-blockchain/src/p2mr/script-leaf.ts:43 — script-leaf.validateScriptLeaf 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 · spend-proof.validateWitnessStructure (cyclomatic 20) · ×2
  • spend-proof.validateWitnessStructure (cyclomatic 20) modules/p2mr/src/spend-proof.ts:370 — spend-proof.validateWitnessStructure 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.
  • spend-proof.validateWitnessStructure (cyclomatic 20) packages/enterprise-blockchain/src/p2mr/spend-proof.ts:370 — spend-proof.validateWitnessStructure 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.
D17 · Explicit Debt · TodoComment · ×2
  • TodoComment modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts:233 — // TODO: Implement full proof verification when Cairo circuits are deployed. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/starknet-proof-adapter.ts:233 — // TODO: Implement full proof verification when Cairo circuits are deployed. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D2 · Cognitive Complexity · script-leaf.validateScriptLeaf (cognitive 24) · ×2
  • script-leaf.validateScriptLeaf (cognitive 24) modules/p2mr/src/script-leaf.ts:43 — script-leaf.validateScriptLeaf has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 4, loops 1, match/switch 1 (nesting depth added 8). 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.
  • script-leaf.validateScriptLeaf (cognitive 24) packages/enterprise-blockchain/src/p2mr/script-leaf.ts:43 — script-leaf.validateScriptLeaf has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 4, loops 1, match/switch 1 (nesting depth added 8). 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 · spend-proof.validateWitnessStructure (cognitive 23) · ×2
  • spend-proof.validateWitnessStructure (cognitive 23) modules/p2mr/src/spend-proof.ts:370 — spend-proof.validateWitnessStructure has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 6, match/switch 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.
  • spend-proof.validateWitnessStructure (cognitive 23) packages/enterprise-blockchain/src/p2mr/spend-proof.ts:370 — spend-proof.validateWitnessStructure has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 6, match/switch 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 · MPCEngine.submitShare (cognitive 20) · ×2
  • MPCEngine.submitShare (cognitive 20) modules/mpc/src/index.ts:278 — MPCEngine.submitShare has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (20 pts) (nesting depth added 8). 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.
  • MPCEngine.submitShare (cognitive 20) packages/enterprise-blockchain/src/mpc/index.ts:279 — MPCEngine.submitShare has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (20 pts) (nesting depth added 8). 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 · QuantumResistantVault.distributeSecret (cognitive 18) · ×2
  • QuantumResistantVault.distributeSecret (cognitive 18) modules/mpc/src/quantum.ts:82 — QuantumResistantVault.distributeSecret has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 2 (4 pts), loops 3, boolean chains 2 (nesting depth added 4). 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.
  • QuantumResistantVault.distributeSecret (cognitive 18) packages/enterprise-blockchain/src/mpc/quantum.ts:82 — QuantumResistantVault.distributeSecret has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 2 (4 pts), loops 3, boolean chains 2 (nesting depth added 4). 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 · retry.withRetry (cognitive 16) · ×2
  • retry.withRetry (cognitive 16) modules/integrations/shared/src/retry.ts:125 — retry.withRetry has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), ternaries 1 (3 pts), error handling 1 (2 pts), loops 1 (nesting depth added 9). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to one function literal inside it that branches (line 143). 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.
  • retry.withRetry (cognitive 16) packages/enterprise-blockchain/src/integrations/shared/retry.ts:125 — retry.withRetry has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), ternaries 1 (3 pts), error handling 1 (2 pts), loops 1 (nesting depth added 9). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to one function literal inside it that branches (line 143). 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.
R10 · Code Duplication · Wholesale file copy (76 identical lines × 2 files) · ×2
  • Wholesale file copy (76 identical lines × 2 files) modules/mpc/src/field.ts:15 — modules/mpc/src/field.ts:15 · packages/enterprise-blockchain/src/mpc/field.ts:16 — these 2 files are line-for-line copies of one another — 76 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
  • Wholesale file copy (76 identical lines × 2 files) modules/mpc/src/kyber.ts:24 — modules/mpc/src/kyber.ts:24 · packages/enterprise-blockchain/src/mpc/kyber.ts:24 — these 2 files are line-for-line copies of one another — 76 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R2 · Cyclomatic Complexity · Complex function validateScriptLeaf (cyclomatic 21, cognitive 25) · ×2
  • Complex function validateScriptLeaf (cyclomatic 21, cognitive 25) modules/p2mr/src/script-leaf.ts:43 — validateScriptLeaf has cyclomatic complexity 21 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function validateScriptLeaf (cyclomatic 21, cognitive 25) packages/enterprise-blockchain/src/p2mr/script-leaf.ts:43 — validateScriptLeaf has cyclomatic complexity 21 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function validateWitnessStructure (cyclomatic 21, cognitive 24) · ×2
  • Complex function validateWitnessStructure (cyclomatic 21, cognitive 24) modules/p2mr/src/spend-proof.ts:370 — validateWitnessStructure has cyclomatic complexity 21 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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.
  • Complex function validateWitnessStructure (cyclomatic 21, cognitive 24) packages/enterprise-blockchain/src/p2mr/spend-proof.ts:370 — validateWitnessStructure has cyclomatic complexity 21 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 distributeSecret (cyclomatic 15, cognitive 18) · ×2
  • Complex function distributeSecret (cyclomatic 15, cognitive 18) modules/mpc/src/quantum.ts:82 — distributeSecret has cyclomatic complexity 15 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 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.
  • Complex function distributeSecret (cyclomatic 15, cognitive 18) packages/enterprise-blockchain/src/mpc/quantum.ts:82 — distributeSecret has cyclomatic complexity 15 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 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 submitShare (cyclomatic 13, cognitive 20) · ×2
  • Complex function submitShare (cyclomatic 13, cognitive 20) modules/mpc/src/index.ts:278 — submitShare has cyclomatic complexity 13 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function submitShare (cyclomatic 13, cognitive 20) packages/enterprise-blockchain/src/mpc/index.ts:279 — submitShare has cyclomatic complexity 13 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function createDefaultContext (cyclomatic 12, cognitive 11) · ×2
  • Complex function createDefaultContext (cyclomatic 12, cognitive 11) modules/stark-settlement/src/index.ts:317 — createDefaultContext has cyclomatic complexity 12 and cognitive complexity 11; 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.
  • Complex function createDefaultContext (cyclomatic 12, cognitive 11) packages/enterprise-blockchain/src/stark-settlement/index.ts:317 — createDefaultContext has cyclomatic complexity 12 and cognitive complexity 11; 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 compute (cyclomatic 11, cognitive 13) · ×2
  • Complex function compute (cyclomatic 11, cognitive 13) modules/mpc/src/index.ts:388 — compute has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function compute (cyclomatic 11, cognitive 13) packages/enterprise-blockchain/src/mpc/index.ts:389 — compute has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function evaluate (cyclomatic 11, cognitive 12) · ×2
  • Complex function evaluate (cyclomatic 11, cognitive 12) modules/credentialing/src/application/clearance-evaluator.ts:17 — evaluate has cyclomatic complexity 11 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 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.
  • Complex function evaluate (cyclomatic 11, cognitive 12) packages/enterprise-blockchain/src/credentialing/application/clearance-evaluator.ts:20 — evaluate has cyclomatic complexity 11 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 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.
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×2
  • Recursive walk over a caller-supplied document has no depth cap modules/p2mr/src/merkle-tree.ts:33 — `canonicalJSON` is exported and takes `obj: unknown` from its caller, and it calls itself at line 33 (`canonicalJSON`) with a piece of `obj` (and at line 45) — and nowhere in `canonicalJSON` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `canonicalJSON` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/enterprise-blockchain/src/p2mr/merkle-tree.ts:38 — `canonicalJSON` is exported and takes `obj: unknown` from its caller, and it calls itself at line 38 (`canonicalJSON`) with a piece of `obj` (and at line 50) — and nowhere in `canonicalJSON` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `canonicalJSON` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
D1 · Cyclomatic Complexity · AsymmetricKeyService.generateKeyPairAsync (cyclomatic 17) · ×1
  • AsymmetricKeyService.generateKeyPairAsync (cyclomatic 17) modules/hsm/src/application/asymmetric-key-service.ts:207 — AsymmetricKeyService.generateKeyPairAsync has cyclomatic complexity 17 (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.
D10 · Test Quality · No assertions · ×1
  • No assertions: MPC: allows same nonce in different computations tests/mpc.property.test.ts:364 — 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.
D12 · Dependency Hygiene · Deprecated · ×1
  • Deprecated: starknet package.json:68 — starknet 9.4.2, declared in package.json, is marked deprecated by its publisher: "starknet <10 is end-of-life and no longer receives security fixes. Upgrade to starknet@10 (10.8.0 or later).". Replace it with the package or version that message names, or record why this one must stay.
D15 · Churn × Complexity Hotspots · Hotspot · ×1
  • Hotspot: modules/mpc/src/quantum.ts modules/mpc/src/quantum.ts:82 — modules/mpc/src/quantum.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in QuantumResistantVault.distributeSecret at line 82. 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-01-14..2026-04-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-01-14 09:03:33 -03:00' --until='2026-04-14 09:03:33 -03:00' --full-history --no-merges -- modules/mpc/src/quantum.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.
D2 · Cognitive Complexity · AsymmetricKeyService.generateKeyPairAsync (cognitive 18) · ×1
  • AsymmetricKeyService.generateKeyPairAsync (cognitive 18) modules/hsm/src/application/asymmetric-key-service.ts:207 — AsymmetricKeyService.generateKeyPairAsync has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 2). 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 · AuditLogFactory.createFromEnv (cognitive 17) · ×1
  • AuditLogFactory.createFromEnv (cognitive 17) packages/enterprise-blockchain/src/hsm/infrastructure/audit-log-factory.ts:85 — AuditLogFactory.createFromEnv has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 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.
D22 · Internal API Consistency · Redundant verification methods with overlapping intent. `verify` computes the hash of the leaf internally, while `verifyHash` expects the hash. This forces callers to either duplicate hashing logic or choose between two nearly identical methods based on an implementation detail. · ×1
  • Redundant verification methods with overlapping intent. `verify` computes the hash of the leaf internally, while `verifyHash` expects the hash. This forces callers to either duplicate hashing logic or choose between two nearly identical methods based on an implementation detail. — Remove `verifyHash` and have `verify` accept a pre-computed hash as an optional parameter, or rename `verify` to `verifyLeaf` and keep `verifyHash` if the distinction is critical for performance, but document clearly. Ideally, unify into one method with an overload or optional argument. (signatures: modules.p2mr.src.merkle-tree.MerkleTree.verify(leaf: ScriptLeaf, proof: MerkleProofNode[], expectedRoot: string): boolean | modules.p2mr.src.merkle-tree.MerkleTree.verifyHash(leafHash: string, proof: MerkleProofNode[], expectedRoot: string): boolean)
D22 · Internal API Consistency · Inconsistent naming and scope of verification methods. `validateSpendProofStructure` and `verifySpendProofStructure` appear to do similar structural checks but have different names and potentially different inputs (one takes just proof, the other takes proof + output). `verifyMerkleProof` is a specific subset. The distinction between 'validate' and 'verify' is unclear and inconsistent with other parts of the API (e.g., `MerkleTree.verify` vs `MerkleTree.verifyHash`). · ×1
  • Inconsistent naming and scope of verification methods. `validateSpendProofStructure` and `verifySpendProofStructure` appear to do similar structural checks but have different names and potentially different inputs (one takes just proof, the other takes proof + output). `verifyMerkleProof` is a specific subset. The distinction between 'validate' and 'verify' is unclear and inconsistent with other parts of the API (e.g., `MerkleTree.verify` vs `MerkleTree.verifyHash`). — Unify naming convention. Use 'verify' for all verification operations. Clarify if `validateSpendProofStructure` and `verifySpendProofStructure` are distinct; if so, rename one to reflect its specific scope (e.g., `verifySpendProofIntegrity`). Consider a single `verifySpendProof` method that takes all necessary context. (signatures: modules.p2mr.src.spend-proof.validateSpendProofStructure(proof: SpendProof): SpendVerificationResult | modules.p2mr.src.spend-proof.verifyMerkleProof(proof: SpendProof, expectedRoot: string): SpendVerificationResult | modules.p2mr.src.spend-proof.verifySpendProofStructure(proof: SpendProof, output: P2MROutput): SpendVerificationResult)
D22 · Internal API Consistency · Multiple entry points for SHA-256 hashing with inconsistent naming and signatures. `crypto.sha256hex` and `HashingPort.sha256hex` are identical. `CommitmentProvider` also exposes `sha256hex`. This creates confusion about which utility to use and duplicates functionality across different modules (shared, p2mr, mpc). · ×1
  • Multiple entry points for SHA-256 hashing with inconsistent naming and signatures. `crypto.sha256hex` and `HashingPort.sha256hex` are identical. `CommitmentProvider` also exposes `sha256hex`. This creates confusion about which utility to use and duplicates functionality across different modules (shared, p2mr, mpc). — Consolidate SHA-256 hashing into a single, well-documented utility module (e.g., `shared/crypto` or `shared/hashing`). Remove `sha256hex` from `CommitmentProvider` and `HashingPort` if they are just wrappers, or ensure `HashingPort` is the only public interface for hashing in the p2mr domain, with `crypto` being the global fallback. (signatures: packages.enterprise-blockchain.src.shared.crypto.sha256hex(value: string): string | modules.p2mr.src.merkle-tree.hashScriptLeaf(leaf: ScriptLeaf): string | modules.p2mr.src.ports.HashingPort.sha256hex(data: string): string | packages.enterprise-blockchain.src.mpc.ports.CommitmentProvider.sha256hex(data: string): string)
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Medium vulnerability · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) contracts/corda/ProviderClearanceFlow.kt:81 — contracts/corda/ProviderClearanceFlow.kt:81-97 | contracts/corda/ProviderClearanceFlow.kt:229-245 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `contracts/corda/ProviderClearanceFlow.kt:81` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: SolanaDevnetAdapter (LCOM4 4) modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts:49 — SolanaDevnetAdapter's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
P1 · CI/CD gates · CI formatting step cannot fail · ×1
  • CI formatting step cannot fail REDACTED:75 — `echo "Terraform files are not formatted. Run 'terraform fmt -recursive' in the infra/ directory."` invokes terraform fmt in the mode that REWRITES the files it reformats and exits 0 whatever it changed. The rewrite happens inside the runner's throwaway checkout and is then discarded, so the step passes on a badly-formatted change exactly as it passes on a clean one — it enforces nothing, and no other step in this file reads the result. `-check` is the flag that turns the same invocation into a gate: it leaves the files alone and exits non-zero when anything would have been reformatted.
P12 · CI test-gate honesty · Test failure does not fail the CI gate · ×1
  • Test failure does not fail the CI gate REDACTED:61 — `continue-on-error: true` lets the step or job that runs `node --import tsx --test tests/**/*.test.ts --test-reporter tap 2>&1 | tee test-output.tap` fail without failing the pipeline — the suite can go red and the change still merges. Remove it from the test step, or quarantine the specific failing tests instead.
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (95 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (95 clone groups) modules/p2mr/src/script-interpreter.ts:17 — 95 duplicated blocks under the repository root have copies in at least two of the sibling directories modules, packages — 87 of them are reported below, and 8 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 95 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 95 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 95 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Wholesale file copy (363 identical lines × 2 files) · ×1
  • Wholesale file copy (363 identical lines × 2 files) modules/p2mr/src/script-interpreter.ts:17 — modules/p2mr/src/script-interpreter.ts:17 · packages/enterprise-blockchain/src/p2mr/script-interpreter.ts:17 — these 2 files are line-for-line copies of one another — 363 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (304 identical lines × 2 files) · ×1
  • Wholesale file copy (304 identical lines × 2 files) modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:27 — modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:27 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/stone-proof-adapter.ts:27 — these 2 files are line-for-line copies of one another — 304 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (287 identical lines × 2 files) · ×1
  • Wholesale file copy (287 identical lines × 2 files) modules/mpc/src/index.ts:8 — modules/mpc/src/index.ts:8 · packages/enterprise-blockchain/src/mpc/index.ts:8 — these 2 files are line-for-line copies of one another — 287 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (258 identical lines × 2 files) · ×1
  • Wholesale file copy (258 identical lines × 2 files) modules/integrations/shared/src/retry.ts:14 — modules/integrations/shared/src/retry.ts:14 · packages/enterprise-blockchain/src/integrations/shared/retry.ts:14 — these 2 files are line-for-line copies of one another — 258 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (224 identical lines × 2 files) · ×1
  • Wholesale file copy (224 identical lines × 2 files) modules/integrations/besu-client/src/index.ts:7 — modules/integrations/besu-client/src/index.ts:7 · packages/enterprise-blockchain/src/integrations/besu-client/index.ts:7 — these 2 files are line-for-line copies of one another — 224 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (207 identical lines × 2 files) · ×1
  • Wholesale file copy (207 identical lines × 2 files) modules/stark-settlement/src/domain/value-objects.ts:16 — modules/stark-settlement/src/domain/value-objects.ts:16 · packages/enterprise-blockchain/src/stark-settlement/domain/value-objects.ts:16 — these 2 files are line-for-line copies of one another — 207 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (194 identical lines × 2 files) · ×1
  • Wholesale file copy (194 identical lines × 2 files) modules/stark-settlement/src/application/settlement-service.ts:15 — modules/stark-settlement/src/application/settlement-service.ts:15 · packages/enterprise-blockchain/src/stark-settlement/application/settlement-service.ts:15 — these 2 files are line-for-line copies of one another — 194 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (193 identical lines × 2 files) · ×1
  • Wholesale file copy (193 identical lines × 2 files) modules/p2mr/src/spend-proof.ts:10 — modules/p2mr/src/spend-proof.ts:10 · packages/enterprise-blockchain/src/p2mr/spend-proof.ts:10 — these 2 files are line-for-line copies of one another — 193 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (191 identical lines × 2 files) · ×1
  • Wholesale file copy (191 identical lines × 2 files) modules/stark-settlement/src/infrastructure/adapters/mock-stark-adapter.ts:14 — modules/stark-settlement/src/infrastructure/adapters/mock-stark-adapter.ts:14 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/mock-stark-adapter.ts:14 — these 2 files are line-for-line copies of one another — 191 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (183 identical lines × 2 files) · ×1
  • Wholesale file copy (183 identical lines × 2 files) modules/integrations/fabric-gateway/src/index.ts:1 — modules/integrations/fabric-gateway/src/index.ts:1 · packages/enterprise-blockchain/src/integrations/fabric-gateway/index.ts:1 — these 2 files are line-for-line copies of one another — 183 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (175 identical lines × 2 files) · ×1
  • Wholesale file copy (175 identical lines × 2 files) modules/stark-settlement/src/infrastructure/persistence/ledger-store.ts:12 — modules/stark-settlement/src/infrastructure/persistence/ledger-store.ts:12 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/persistence/ledger-store.ts:12 — these 2 files are line-for-line copies of one another — 175 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (168 identical lines × 2 files) · ×1
  • Wholesale file copy (168 identical lines × 2 files) modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts:18 — modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts:18 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/starknet-proof-adapter.ts:18 — these 2 files are line-for-line copies of one another — 168 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (158 identical lines × 2 files) · ×1
  • Wholesale file copy (158 identical lines × 2 files) modules/stark-settlement/src/application/aggregator-service.ts:14 — modules/stark-settlement/src/application/aggregator-service.ts:14 · packages/enterprise-blockchain/src/stark-settlement/application/aggregator-service.ts:14 — these 2 files are line-for-line copies of one another — 158 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (147 identical lines × 2 files) · ×1
  • Wholesale file copy (147 identical lines × 2 files) modules/stark-settlement/src/domain/entities.ts:26 — modules/stark-settlement/src/domain/entities.ts:26 · packages/enterprise-blockchain/src/stark-settlement/domain/entities.ts:26 — these 2 files are line-for-line copies of one another — 147 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (146 identical lines × 2 files) · ×1
  • Wholesale file copy (146 identical lines × 2 files) modules/stark-settlement/src/domain/ports.ts:15 — modules/stark-settlement/src/domain/ports.ts:15 · packages/enterprise-blockchain/src/stark-settlement/domain/ports.ts:15 — these 2 files are line-for-line copies of one another — 146 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (141 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (141 matched lines × 2 locations) modules/integrations/corda-gateway/src/index.ts:31 — modules/integrations/corda-gateway/src/index.ts:31 · packages/enterprise-blockchain/src/integrations/corda-gateway/index.ts:31 — the two spans are one implementation copied and then locally edited — 819 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 · Wholesale file copy (140 identical lines × 2 files) · ×1
  • Wholesale file copy (140 identical lines × 2 files) modules/stark-settlement/src/infrastructure/adapters/bitcoin-adapter.ts:19 — modules/stark-settlement/src/infrastructure/adapters/bitcoin-adapter.ts:19 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/bitcoin-adapter.ts:19 — these 2 files are line-for-line copies of one another — 140 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (131 identical lines × 2 files) · ×1
  • Wholesale file copy (131 identical lines × 2 files) modules/mpc/src/quantum.ts:1 — modules/mpc/src/quantum.ts:1 · packages/enterprise-blockchain/src/mpc/quantum.ts:1 — these 2 files are line-for-line copies of one another — 131 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (131 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (131 matched lines × 2 locations) modules/stark-settlement/src/infrastructure/adapters/event-emitter-adapter.ts:17 — modules/stark-settlement/src/infrastructure/adapters/event-emitter-adapter.ts:17 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/event-emitter-adapter.ts:35 — the two spans are one implementation copied and then locally edited — 915 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 · Wholesale file copy (130 identical lines × 2 files) · ×1
  • Wholesale file copy (130 identical lines × 2 files) modules/stark-settlement/src/infrastructure/adapters/fiat-adapter.ts:18 — modules/stark-settlement/src/infrastructure/adapters/fiat-adapter.ts:18 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/fiat-adapter.ts:18 — these 2 files are line-for-line copies of one another — 130 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (116 identical lines × 2 files) · ×1
  • Wholesale file copy (116 identical lines × 2 files) modules/hsm/src/infrastructure/syslog-audit-log.ts:1 — modules/hsm/src/infrastructure/syslog-audit-log.ts:1 · packages/enterprise-blockchain/src/hsm/infrastructure/syslog-audit-log.ts:1 — these 2 files are line-for-line copies of one another — 116 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (108 identical lines × 2 files) · ×1
  • Wholesale file copy (108 identical lines × 2 files) modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts:19 — modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts:19 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/solana-adapter.ts:19 — these 2 files are line-for-line copies of one another — 108 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (105 identical lines × 2 files) · ×1
  • Wholesale file copy (105 identical lines × 2 files) modules/stark-settlement/src/infrastructure/persistence/outbox-store.ts:18 — modules/stark-settlement/src/infrastructure/persistence/outbox-store.ts:18 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/persistence/outbox-store.ts:18 — these 2 files are line-for-line copies of one another — 105 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block (101 lines × 2 locations) · ×1
  • Duplicated block (101 lines × 2 locations) modules/stark-settlement/src/index.ts:254 — modules/stark-settlement/src/index.ts:254 · packages/enterprise-blockchain/src/stark-settlement/index.ts:254 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Wholesale file copy (99 identical lines × 2 files) · ×1
  • Wholesale file copy (99 identical lines × 2 files) modules/protocols/corda/src/p2mr-adapter.ts:13 — modules/protocols/corda/src/p2mr-adapter.ts:13 · modules/protocols/fabric/src/p2mr-adapter.ts:13 — these 2 files are line-for-line copies of one another — 99 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (89 identical lines × 2 files) · ×1
  • Wholesale file copy (89 identical lines × 2 files) modules/hsm/src/infrastructure/file-audit-log.ts:1 — modules/hsm/src/infrastructure/file-audit-log.ts:1 · packages/enterprise-blockchain/src/hsm/infrastructure/file-audit-log.ts:1 — these 2 files are line-for-line copies of one another — 89 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (87 identical lines × 2 files) · ×1
  • Wholesale file copy (87 identical lines × 2 files) modules/p2mr/src/merkle-tree.ts:27 — modules/p2mr/src/merkle-tree.ts:27 · packages/enterprise-blockchain/src/p2mr/merkle-tree.ts:32 — these 2 files are line-for-line copies of one another — 87 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (85 identical lines × 2 files) · ×1
  • Wholesale file copy (85 identical lines × 2 files) modules/p2mr/src/script-leaf.ts:20 — modules/p2mr/src/script-leaf.ts:20 · packages/enterprise-blockchain/src/p2mr/script-leaf.ts:20 — these 2 files are line-for-line copies of one another — 85 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (84 identical lines × 2 files) · ×1
  • Wholesale file copy (84 identical lines × 2 files) modules/stark-settlement/src/infrastructure/adapters/audit-adapter.ts:12 — modules/stark-settlement/src/infrastructure/adapters/audit-adapter.ts:12 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/audit-adapter.ts:12 — these 2 files are line-for-line copies of one another — 84 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (75 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (75 matched lines × 2 locations) modules/hsm/src/application/asymmetric-key-service.ts:66 — modules/hsm/src/application/asymmetric-key-service.ts:66 · packages/enterprise-blockchain/src/hsm/application/asymmetric-key-service.ts:31 — the two spans are one implementation copied and then locally edited — 467 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 · Wholesale file copy (75 identical lines × 2 files) · ×1
  • Wholesale file copy (75 identical lines × 2 files) modules/shared/src/telemetry.ts:22 — modules/shared/src/telemetry.ts:22 · packages/enterprise-blockchain/src/shared/telemetry.ts:29 — these 2 files are line-for-line copies of one another — 75 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (74 identical lines × 2 files) · ×1
  • Wholesale file copy (74 identical lines × 2 files) modules/aid-settlement/src/application/reconciler.ts:1 — modules/aid-settlement/src/application/reconciler.ts:1 · packages/enterprise-blockchain/src/aid-settlement/application/reconciler.ts:1 — these 2 files are line-for-line copies of one another — 74 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block (71 lines × 2 locations) · ×1
  • Duplicated block (71 lines × 2 locations) modules/credentialing/src/application/clearance-evaluator.ts:17 — modules/credentialing/src/application/clearance-evaluator.ts:17 · packages/enterprise-blockchain/src/credentialing/application/clearance-evaluator.ts:20 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Wholesale file copy (70 identical lines × 2 files) · ×1
  • Wholesale file copy (70 identical lines × 2 files) modules/traceability/src/application/recall-assessor.ts:6 — modules/traceability/src/application/recall-assessor.ts:6 · packages/enterprise-blockchain/src/traceability/application/recall-assessor.ts:6 — these 2 files are line-for-line copies of one another — 70 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (65 identical lines × 2 files) · ×1
  • Wholesale file copy (65 identical lines × 2 files) modules/mpc/src/dsa.ts:27 — modules/mpc/src/dsa.ts:27 · packages/enterprise-blockchain/src/mpc/dsa.ts:27 — these 2 files are line-for-line copies of one another — 65 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (62 identical lines × 2 files) · ×1
  • Wholesale file copy (62 identical lines × 2 files) modules/mpc/src/hybrid-kem.ts:32 — modules/mpc/src/hybrid-kem.ts:32 · packages/enterprise-blockchain/src/mpc/hybrid-kem.ts:32 — these 2 files are line-for-line copies of one another — 62 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (61 identical lines × 2 files) · ×1
  • Wholesale file copy (61 identical lines × 2 files) modules/stark-settlement/src/infrastructure/adapters/dilithium-adapter.ts:13 — modules/stark-settlement/src/infrastructure/adapters/dilithium-adapter.ts:13 · packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/dilithium-adapter.ts:13 — these 2 files are line-for-line copies of one another — 61 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R2 · Cyclomatic Complexity · Complex function generateKeyPairAsync (cyclomatic 20, cognitive 21) · ×1
  • Complex function generateKeyPairAsync (cyclomatic 20, cognitive 21) modules/hsm/src/application/asymmetric-key-service.ts:207 — generateKeyPairAsync has cyclomatic complexity 20 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function createFromEnv (cyclomatic 13, cognitive 17) · ×1
  • Complex function createFromEnv (cyclomatic 13, cognitive 17) packages/enterprise-blockchain/src/hsm/infrastructure/audit-log-factory.ts:85 — createFromEnv has cyclomatic complexity 13 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 validateGatewayUrl (cyclomatic 12, cognitive 15) · ×1
  • Complex function validateGatewayUrl (cyclomatic 12, cognitive 15) packages/enterprise-blockchain/src/integrations/corda-gateway/index.ts:134 — validateGatewayUrl has cyclomatic complexity 12 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.
R3 · Large Files · modules/p2mr/src/script-interpreter.ts · ×1
  • modules/p2mr/src/script-interpreter.ts: 621 lines of code modules/p2mr/src/script-interpreter.ts:1 — modules/p2mr/src/script-interpreter.ts has 621 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/enterprise-blockchain/src/p2mr/script-interpreter.ts · ×1
  • packages/enterprise-blockchain/src/p2mr/script-interpreter.ts: 621 lines of code packages/enterprise-blockchain/src/p2mr/script-interpreter.ts:1 — packages/enterprise-blockchain/src/p2mr/script-interpreter.ts has 621 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts · ×1
  • modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts: 577 lines of code modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts:1 — modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts has 577 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · modules/stark-settlement/src/domain/ports.ts · ×1
  • modules/stark-settlement/src/domain/ports.ts: 565 lines of code modules/stark-settlement/src/domain/ports.ts:1 — modules/stark-settlement/src/domain/ports.ts has 565 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/enterprise-blockchain/src/stark-settlement/domain/ports.ts · ×1
  • packages/enterprise-blockchain/src/stark-settlement/domain/ports.ts: 565 lines of code packages/enterprise-blockchain/src/stark-settlement/domain/ports.ts:1 — packages/enterprise-blockchain/src/stark-settlement/domain/ports.ts has 565 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts · ×1
  • modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts: 542 lines of code modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:1 — modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts has 542 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/stone-proof-adapter.ts · ×1
  • packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/stone-proof-adapter.ts: 542 lines of code packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/stone-proof-adapter.ts:1 — packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/stone-proof-adapter.ts has 542 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/enterprise-blockchain/src/mpc/index.ts · ×1
  • packages/enterprise-blockchain/src/mpc/index.ts: 521 lines of code packages/enterprise-blockchain/src/mpc/index.ts:1 — packages/enterprise-blockchain/src/mpc/index.ts has 521 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · modules/mpc/src/index.ts · ×1
  • modules/mpc/src/index.ts: 520 lines of code modules/mpc/src/index.ts:1 — modules/mpc/src/index.ts has 520 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · modules/hsm/src/application/asymmetric-key-service.ts · ×1
  • modules/hsm/src/application/asymmetric-key-service.ts: 519 lines of code modules/hsm/src/application/asymmetric-key-service.ts:1 — modules/hsm/src/application/asymmetric-key-service.ts has 519 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · modules/stark-settlement/src/domain/value-objects.ts · ×1
  • modules/stark-settlement/src/domain/value-objects.ts: 499 lines of code modules/stark-settlement/src/domain/value-objects.ts:1 — modules/stark-settlement/src/domain/value-objects.ts has 499 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/enterprise-blockchain/src/stark-settlement/domain/value-objects.ts · ×1
  • packages/enterprise-blockchain/src/stark-settlement/domain/value-objects.ts: 499 lines of code packages/enterprise-blockchain/src/stark-settlement/domain/value-objects.ts:1 — packages/enterprise-blockchain/src/stark-settlement/domain/value-objects.ts has 499 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · modules/hsm/src/index.ts · ×1
  • modules/hsm/src/index.ts: 483 lines of code modules/hsm/src/index.ts:1 — modules/hsm/src/index.ts has 483 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · modules/stark-settlement/src/application/ledger-service.ts · ×1
  • modules/stark-settlement/src/application/ledger-service.ts: 457 lines of code modules/stark-settlement/src/application/ledger-service.ts:1 — modules/stark-settlement/src/application/ledger-service.ts has 457 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/enterprise-blockchain/src/stark-settlement/application/ledger-service.ts · ×1
  • packages/enterprise-blockchain/src/stark-settlement/application/ledger-service.ts: 457 lines of code packages/enterprise-blockchain/src/stark-settlement/application/ledger-service.ts:1 — packages/enterprise-blockchain/src/stark-settlement/application/ledger-service.ts has 457 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · modules/stark-settlement/src/domain/entities.ts · ×1
  • modules/stark-settlement/src/domain/entities.ts: 421 lines of code modules/stark-settlement/src/domain/entities.ts:1 — modules/stark-settlement/src/domain/entities.ts has 421 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/enterprise-blockchain/src/stark-settlement/domain/entities.ts · ×1
  • packages/enterprise-blockchain/src/stark-settlement/domain/entities.ts: 421 lines of code packages/enterprise-blockchain/src/stark-settlement/domain/entities.ts:1 — packages/enterprise-blockchain/src/stark-settlement/domain/entities.ts has 421 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · modules/p2mr/src/spend-proof.ts · ×1
  • modules/p2mr/src/spend-proof.ts: 415 lines of code modules/p2mr/src/spend-proof.ts:1 — modules/p2mr/src/spend-proof.ts has 415 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/enterprise-blockchain/src/p2mr/spend-proof.ts · ×1
  • packages/enterprise-blockchain/src/p2mr/spend-proof.ts: 415 lines of code packages/enterprise-blockchain/src/p2mr/spend-proof.ts:1 — packages/enterprise-blockchain/src/p2mr/spend-proof.ts has 415 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · modules/hsm/src/infrastructure/adapters/simulator-crypto-adapter.ts · ×1
  • modules/hsm/src/infrastructure/adapters/simulator-crypto-adapter.ts: 402 lines of code modules/hsm/src/infrastructure/adapters/simulator-crypto-adapter.ts:1 — modules/hsm/src/infrastructure/adapters/simulator-crypto-adapter.ts has 402 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R7 · Dead Code · Dead file (~404 LoC) · ×1
  • Dead file (~404 LoC) modules/protocols/besu/src/p2mr-adapter.ts — no import path from any entry point (37 application, 2 tooling, 17 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~223 LoC) · ×1
  • Dead file (~223 LoC) modules/protocols/fabric/src/p2mr-adapter.ts — no import path from any entry point (37 application, 2 tooling, 17 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~217 LoC) · ×1
  • Dead file (~217 LoC) modules/protocols/corda/src/p2mr-adapter.ts — no import path from any entry point (37 application, 2 tooling, 17 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~203 LoC) · ×1
  • Dead file (~203 LoC) modules/protocols/src/p2mr-port.ts — no import path from any entry point (37 application, 2 tooling, 17 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (modules/protocols/besu/src/p2mr-adapter.ts, modules/protocols/corda/src/p2mr-adapter.ts, modules/protocols/fabric/src/p2mr-adapter.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~120 LoC) · ×1
  • Dead file (~120 LoC) modules/protocols/src/corda-port.ts — no import path from any entry point (37 application, 2 tooling, 17 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~113 LoC) · ×1
  • Dead file (~113 LoC) modules/protocols/src/fabric-port.ts — no import path from any entry point (37 application, 2 tooling, 17 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~89 LoC) · ×1
  • Dead file (~89 LoC) modules/protocols/src/besu-port.ts — no import path from any entry point (37 application, 2 tooling, 17 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~82 LoC) · ×1
  • Dead file (~82 LoC) modules/shared/src/telemetry-sdk.ts — no import path from any entry point (37 application, 2 tooling, 17 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
X14 · Bypassable address classification · IP classification is bypassable through an IPv4-in-IPv6 embedding · ×1
  • IP classification is bypassable through an IPv4-in-IPv6 embedding packages/enterprise-blockchain/src/integrations/corda-gateway/index.ts:105 — This function unwraps IPv4-MAPPED IPv6 (`::ffff:`, line 99) and then rejects `10.0.0.0/8` on its IPv4 path — but the IPv6 decision at line 105 classifies the address as written, and IPv4 reaches IPv6 through three MORE embeddings this function never mentions: IPv4-compatible (`::a.b.c.d`), 6to4 (`2002::/16`) and NAT64 (`64:ff9b::/96`). So `::10.0.0.1`, `2002:0a00:0001::` and `64:ff9b::10.0.0.0` all name a host inside `10.0.0.0/8` — the range this same function declares non-public — and all reach the IPv6 decision un-unwrapped, taking the opposite verdict. Unwrap every embedding to its IPv4 form before classifying, or reject any IPv6 address carrying an embedded IPv4 outright.
Minor — 268 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×114
  • Orphaned file packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/stone-proof-adapter.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/enterprise-blockchain/src/p2mr/script-interpreter.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/p2mr/src/script-interpreter.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/enterprise-blockchain/src/mpc/index.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/stark-settlement/src/domain/entities.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/enterprise-blockchain/src/stark-settlement/domain/entities.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/mpc/src/index.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/stark-settlement/src/domain/value-objects.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/enterprise-blockchain/src/stark-settlement/domain/value-objects.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/hsm/src/application/asymmetric-key-service.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/hsm/src/index.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/enterprise-blockchain/src/stark-settlement/index.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/stark-settlement/src/index.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file contracts/corda/ProviderClearanceFlow.kt:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/hsm/src/infrastructure/adapters/simulator-crypto-adapter.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/integrations/besu-client/src/index.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/enterprise-blockchain/src/integrations/besu-client/index.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/integrations/shared/src/retry.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/enterprise-blockchain/src/integrations/shared/retry.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/protocols/besu/src/p2mr-adapter.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/enterprise-blockchain/src/stark-settlement/application/aggregator-service.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/stark-settlement/src/application/aggregator-service.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/mock-stark-adapter.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file modules/stark-settlement/src/infrastructure/adapters/mock-stark-adapter.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 89 more in this group — see findings.md.
P2 · Observability · Console output used as the logging channel · ×40
  • Console output used as the logging channel modules/hsm/src/infrastructure/syslog-audit-log.ts:225 — `modules/hsm/src/infrastructure/syslog-audit-log.ts` reports through `console.*` at line 225 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/shared/src/telemetry-sdk.ts:63 — `modules/shared/src/telemetry-sdk.ts` reports through `console.*` at line 63 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/shared/src/telemetry-sdk.ts:66 — `modules/shared/src/telemetry-sdk.ts` reports through `console.*` at line 66 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/shared/src/telemetry-sdk.ts:73 — `modules/shared/src/telemetry-sdk.ts` reports through `console.*` at line 73 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/shared/src/telemetry-sdk.ts:77 — `modules/shared/src/telemetry-sdk.ts` reports through `console.*` at line 77 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/stark-settlement/src/application/settlement-service.ts:244 — `modules/stark-settlement/src/application/settlement-service.ts` reports through `console.*` at line 244 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:122 — `modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts` reports through `console.*` at line 122 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:142 — `modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts` reports through `console.*` at line 142 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:156 — `modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts` reports through `console.*` at line 156 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:189 — `modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts` reports through `console.*` at line 189 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:255 — `modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts` reports through `console.*` at line 255 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:328 — `modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts` reports through `console.*` at line 328 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:378 — `modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts` reports through `console.*` at line 378 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:448 — `modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts` reports through `console.*` at line 448 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:453 — `modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts` reports through `console.*` at line 453 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts:84 — `modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts` reports through `console.*` at line 84 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts:136 — `modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts` reports through `console.*` at line 136 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts:194 — `modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts` reports through `console.*` at line 194 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts:245 — `modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts` reports through `console.*` at line 245 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts:98 — `modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts` reports through `console.*` at line 98 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts:101 — `modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts` reports through `console.*` at line 101 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts:102 — `modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts` reports through `console.*` at line 102 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts:125 — `modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts` reports through `console.*` at line 125 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts:132 — `modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts` reports through `console.*` at line 132 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel modules/stark-settlement/src/infrastructure/adapters/fiat-adapter.ts:98 — `modules/stark-settlement/src/infrastructure/adapters/fiat-adapter.ts` reports through `console.*` at line 98 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • + 15 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×25
  • Duplicated predicate modules/p2mr/src/script-leaf.ts:57 — `!Array.isArray(leaf.publicKeyHashes) || leaf.publicKeyHashes.length === 0` appears character-identically in 2 files — modules/p2mr/src/script-leaf.ts, packages/enterprise-blockchain/src/p2mr/script-leaf.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 modules/p2mr/src/spend-proof.ts:375 — `!Array.isArray(witness.publicKeys) || witness.publicKeys.length === 0` appears character-identically in 2 files — modules/p2mr/src/spend-proof.ts, packages/enterprise-blockchain/src/p2mr/spend-proof.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 modules/p2mr/src/spend-proof.ts:382 — `!Array.isArray(witness.signatures) || witness.signatures.length === 0` appears character-identically in 2 files — modules/p2mr/src/spend-proof.ts, packages/enterprise-blockchain/src/p2mr/spend-proof.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 modules/stark-settlement/src/infrastructure/persistence/ledger-store.ts:273 — `!latest || proof.blockNumber > latest.blockNumber` appears character-identically in 2 files — modules/stark-settlement/src/infrastructure/persistence/ledger-store.ts, packages/enterprise-blockchain/src/stark-settlement/infrastructure/persistence/ledger-store.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 modules/p2mr/src/spend-proof.ts:124 — `!proof.outputId || proof.outputId.length === 0` appears character-identically in 2 files — modules/p2mr/src/spend-proof.ts, packages/enterprise-blockchain/src/p2mr/spend-proof.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 modules/stark-settlement/src/application/aggregator-service.ts:233 — `!result.blockGenerated && result.baseProofsProcessed > 0` appears character-identically in 2 files — modules/stark-settlement/src/application/aggregator-service.ts, packages/enterprise-blockchain/src/stark-settlement/application/aggregator-service.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 modules/hsm/src/infrastructure/audit-log-factory.ts:86 — `(env[AUDIT_LOG_ENV.TYPE] as AuditLogType) || "memory"` appears character-identically in 2 files — modules/hsm/src/infrastructure/audit-log-factory.ts, packages/enterprise-blockchain/src/hsm/infrastructure/audit-log-factory.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 modules/privacy/src/index.ts:43 — `(hsm && !signerKeyLabel) || (!hsm && signerKeyLabel)` appears character-identically in 2 files — modules/privacy/src/index.ts, packages/enterprise-blockchain/src/privacy/index.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 modules/stark-settlement/src/infrastructure/adapters/mock-stark-adapter.ts:218 — `blockProof.finalProof.length > 0 && blockProof.tier1ProofIds.length === 64 && blockProof.txCount === 128 * 64 && blockProof.stateRoot.length…` appears character-identically in 2 files — modules/stark-settlement/src/infrastructure/adapters/mock-stark-adapter.ts, packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/mock-stark-adapter.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 modules/stark-settlement/src/infrastructure/adapters/mock-stark-adapter.ts:389 — `blockProof.finalProof.length > 0 && blockProof.tier1ProofIds.length === this.tier2BatchSize && blockProof.stateRoot.length === 64` appears character-identically in 2 files — modules/stark-settlement/src/infrastructure/adapters/mock-stark-adapter.ts, packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/mock-stark-adapter.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 modules/credentialing/src/application/clearance-evaluator.ts:41 — `c.type === required && c.jurisdictions.includes(assignment.jurisdiction)` appears character-identically in 2 files — modules/credentialing/src/application/clearance-evaluator.ts, packages/enterprise-blockchain/src/credentialing/application/clearance-evaluator.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 modules/integrations/besu-client/src/error-mapper.ts:27 — `code === "INSUFFICIENT_FUNDS" || msg.includes("insufficient funds")` appears character-identically in 2 files — modules/integrations/besu-client/src/error-mapper.ts, packages/enterprise-blockchain/src/integrations/besu-client/error-mapper.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 modules/integrations/besu-client/src/error-mapper.ts:33 — `code === "NONCE_TOO_LOW" || msg.includes("nonce too low")` appears character-identically in 2 files — modules/integrations/besu-client/src/error-mapper.ts, packages/enterprise-blockchain/src/integrations/besu-client/error-mapper.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 modules/p2mr/src/merkle-tree.ts:250 — `currentLevel.length % 2 === 1 && currentLevel.length > 1` appears character-identically in 2 files — modules/p2mr/src/merkle-tree.ts, packages/enterprise-blockchain/src/p2mr/merkle-tree.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 modules/mpc/src/field.ts:75 — `effectiveMode === "demo" && !isDevelopment` appears character-identically in 2 files — modules/mpc/src/field.ts, packages/enterprise-blockchain/src/mpc/field.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 modules/stark-settlement/src/infrastructure/persistence/outbox-store.ts:150 — `entry && entry.status === "failed" && entry.retryCount < entry.maxRetries` appears character-identically in 2 files — modules/stark-settlement/src/infrastructure/persistence/outbox-store.ts, packages/enterprise-blockchain/src/stark-settlement/infrastructure/persistence/outbox-store.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 modules/stark-settlement/src/infrastructure/persistence/outbox-store.ts:80 — `entry.status !== "pending" && entry.status !== "failed"` appears character-identically in 2 files — modules/stark-settlement/src/infrastructure/persistence/outbox-store.ts, packages/enterprise-blockchain/src/stark-settlement/infrastructure/persistence/outbox-store.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 modules/integrations/corda-gateway/src/index.ts:216 — `err.name === "TimeoutError" || err.message.includes("timeout")` appears character-identically in 2 files — modules/integrations/corda-gateway/src/index.ts, packages/enterprise-blockchain/src/integrations/corda-gateway/index.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 modules/p2mr/src/spend-proof.ts:82 — `leafIndex < 0 || leafIndex >= leaves.length` appears character-identically in 2 files — modules/p2mr/src/spend-proof.ts, packages/enterprise-blockchain/src/p2mr/spend-proof.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 modules/p2mr/src/merkle-tree.ts:157 — `leafIndex < 0 || leafIndex >= this.#leaves.length` appears character-identically in 2 files — modules/p2mr/src/merkle-tree.ts, packages/enterprise-blockchain/src/p2mr/merkle-tree.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 modules/p2mr/src/spend-proof.ts:361 — `n.position !== "left" && n.position !== "right"` appears character-identically in 2 files — modules/p2mr/src/spend-proof.ts, packages/enterprise-blockchain/src/p2mr/spend-proof.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 modules/mpc/src/field.ts:70 — `nodeEnv === "development" || nodeEnv === "test"` appears character-identically in 2 files — modules/mpc/src/field.ts, packages/enterprise-blockchain/src/mpc/field.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 modules/mpc/src/field.ts:61 — `rawMode !== "demo" && rawMode !== "production"` appears character-identically in 2 files — modules/mpc/src/field.ts, packages/enterprise-blockchain/src/mpc/field.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 modules/credentialing/src/application/clearance-evaluator.ts:68 — `reasons.length === 0 && missingCredentials.length === 0 && provider.sanctionStatus === "clear"` appears character-identically in 2 files — modules/credentialing/src/application/clearance-evaluator.ts, packages/enterprise-blockchain/src/credentialing/application/clearance-evaluator.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 modules/mpc/src/quantum.ts:120 — `secretBigint < 0n || secretBigint >= this.field.prime` appears character-identically in 2 files — modules/mpc/src/quantum.ts, packages/enterprise-blockchain/src/mpc/quantum.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.
M4 · Documentation accuracy · README/code drift · ×19
  • README/code drift CONTRIBUTING.md:23 — CONTRIBUTING.md names `test/coverage-expansion`, but no file or folder `test/coverage-expansion` 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 CONTRIBUTING.md:24 — CONTRIBUTING.md names `docs/restructure`, but no file or folder `docs/restructure` 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 CONTRIBUTING.md:25 — CONTRIBUTING.md names `infra/terraform`, but no file or folder `infra/terraform` 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/architecture/local-demo-blueprint.md:10 — docs/architecture/local-demo-blueprint.md links to `modules/integrations/fabric-gateway/src/index.ts`, but `docs/architecture/modules/integrations/fabric-gateway/src/index.ts` 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 docs/architecture/local-demo-blueprint.md:15 — docs/architecture/local-demo-blueprint.md links to `contracts/ConsortiumOrderRegistry.sol`, but `docs/architecture/contracts/ConsortiumOrderRegistry.sol` 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 docs/architecture/local-demo-blueprint.md:17 — docs/architecture/local-demo-blueprint.md links to `modules/integrations/besu-client/src/index.ts`, but `docs/architecture/modules/integrations/besu-client/src/index.ts` 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 docs/architecture/local-demo-blueprint.md:22 — docs/architecture/local-demo-blueprint.md links to `modules/integrations/corda-gateway/src/index.ts`, but `docs/architecture/modules/integrations/corda-gateway/src/index.ts` 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 docs/architecture/scenario-to-protocol-mapping.md:8 — docs/architecture/scenario-to-protocol-mapping.md links to `modules/traceability/src/index.ts`, but `docs/architecture/modules/traceability/src/index.ts` 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 docs/architecture/scenario-to-protocol-mapping.md:9 — docs/architecture/scenario-to-protocol-mapping.md links to `modules/protocols/fabric/src/index.ts`, but `docs/architecture/modules/protocols/fabric/src/index.ts` 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 docs/architecture/scenario-to-protocol-mapping.md:24 — docs/architecture/scenario-to-protocol-mapping.md links to `modules/privacy/src/index.ts`, but `docs/architecture/modules/privacy/src/index.ts` 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 docs/architecture/scenario-to-protocol-mapping.md:25 — docs/architecture/scenario-to-protocol-mapping.md links to `modules/protocols/besu/src/index.ts`, but `docs/architecture/modules/protocols/besu/src/index.ts` 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 docs/architecture/scenario-to-protocol-mapping.md:40 — docs/architecture/scenario-to-protocol-mapping.md links to `modules/credentialing/src/index.ts`, but `docs/architecture/modules/credentialing/src/index.ts` 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 docs/architecture/scenario-to-protocol-mapping.md:41 — docs/architecture/scenario-to-protocol-mapping.md links to `modules/protocols/corda/src/index.ts`, but `docs/architecture/modules/protocols/corda/src/index.ts` 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 docs/presentation/enterprise-blockchain-deck.md:509 — docs/presentation/enterprise-blockchain-deck.md installs `#` (`npm install # install dependencies`), but no package.json declares 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/presentation/enterprise-blockchain-deck.md:509 — docs/presentation/enterprise-blockchain-deck.md installs `install` (`npm install # install dependencies`), but no package.json declares 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/presentation/enterprise-blockchain-deck.md:509 — docs/presentation/enterprise-blockchain-deck.md installs `dependencies` (`npm install # install dependencies`), but no package.json declares 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/research/initial-usage-research.md:1398 — docs/research/initial-usage-research.md runs `./install-fabric.sh`, but `install-fabric.sh` 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 docs/research/initial-usage-research.md:1402 — docs/research/initial-usage-research.md runs `./network.sh up createChannel -ca -s couchdb`, but `network.sh` 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 docs/research/initial-usage-research.md:1410 — docs/research/initial-usage-research.md documents the environment variable `FABRIC_CFG_PATH`, 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.
IC1 · Incompleteness & stubs · Disabled test · ×9
  • Disabled test demo/e2e/api.spec.ts:187 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test demo/e2e/dashboard.spec.ts:130 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test demo/e2e/dashboard.spec.ts:161 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test demo/e2e/real-prover.spec.ts:69 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test demo/e2e/real-prover.spec.ts:145 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test demo/e2e/real-prover.spec.ts:193 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test demo/e2e/scenarios.spec.ts:122 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test demo/e2e/scenarios.spec.ts:143 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test demo/e2e/scenarios.spec.ts:160 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
IC1 · Incompleteness & stubs · Empty method body · ×6
  • Empty method body modules/shared/src/logger.ts:27 — `info` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body modules/shared/src/logger.ts:28 — `warn` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body modules/shared/src/logger.ts:29 — `error` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/enterprise-blockchain/src/shared/logger.ts:27 — `info` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/enterprise-blockchain/src/shared/logger.ts:28 — `warn` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/enterprise-blockchain/src/shared/logger.ts:29 — `error` has an empty body — confirm it's an intentional no-op and not an unfinished method.
D34 · Knowledge Freshness · Most significant orphaned file · ×3
  • Most significant orphaned file packages/enterprise-blockchain/src/stark-settlement/domain/ports.ts:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file modules/stark-settlement/src/domain/ports.ts:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
AX6 · Interface segregation · Fat interface · ×2
  • Fat interface: LedgerPersistencePort (19 required operations) modules/stark-settlement/src/domain/ports.ts:102 — `LedgerPersistencePort` declares 19 required operations: `createAccount`, `getAccount`, `getAccountByAddress`, `updateAccountBalance`, `getAccountsByAssetType`, `appendTransaction`, `getTransaction`, `getTransactionsByIdempotencyKey`, `getPendingTransactions`, `updateTransactionStatus`, `saveBaseProof`, `getBaseProof`, `getUnaggregatedBaseProofs`, `saveTier1Proof`, `getTier1Proof`, `getUnaggregatedTier1Proofs`, `saveTier2Proof`, `getTier2Proof`, `getLatestBlockProof`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LedgerPersistencePort (19 required operations) packages/enterprise-blockchain/src/stark-settlement/domain/ports.ts:102 — `LedgerPersistencePort` declares 19 required operations: `createAccount`, `getAccount`, `getAccountByAddress`, `updateAccountBalance`, `getAccountsByAssetType`, `appendTransaction`, `getTransaction`, `getTransactionsByIdempotencyKey`, `getPendingTransactions`, `updateTransactionStatus`, `saveBaseProof`, `getBaseProof`, `getUnaggregatedBaseProofs`, `saveTier1Proof`, `getTier1Proof`, `getUnaggregatedTier1Proofs`, `saveTier2Proof`, `getTier2Proof`, `getLatestBlockProof`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D12 · Dependency Hygiene · Deprecated · ×2
  • Deprecated: glob REDACTED:5600 — 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: prebuild-install REDACTED:9683 — prebuild-install 7.1.3 is resolved in REDACTED and is marked deprecated by its publisher: "No longer maintained. Please contact the author of the relevant native addon; alternatives are available.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
R7 · Dead Code · Unused export 'DEFAULT_RETRY_POLICY' · ×2
  • Unused export 'DEFAULT_RETRY_POLICY' modules/integrations/shared/src/retry.ts:66 — Nothing imports this binding — it is safe to review for removal.
  • Unused export 'DEFAULT_RETRY_POLICY' packages/enterprise-blockchain/src/integrations/shared/retry.ts:66 — Nothing imports this binding — it is safe to review for removal.
D16 · Bus Factor · Small-team knowledge concentration · ×1
  • Small-team knowledge concentration — 7 file(s) are concentrated to one author — the ambient state with 2 active author(s), not 7 separate risks. The signal becomes meaningful as ownership spreads; no per-file action implied now.
D19 · Documentation Quality · Documentation · ×1
  • Documentation: no project overview examples/hybrid-kem-settlement/README.md — The hybrid-KEM example is long and well-structured, but the visible text does not state what this directory is for — it documents only one of the many cross-border settlement scenarios covered in its outline. Add an overview line stating that this directory demonstrates a production-grade cross-border FX settlement key exchange using Hybrid KEM.
D26 · Project Cohesion · Split packages/enterprise-blockchain · ×1
  • Split packages/enterprise-blockchain — At 15k LoC the enterprise-blockchain package is large and spans 33 namespaces across Stark settlement, MPC, protocols, integrations, shared, and traceability domains. Suggested:
D30 · Dependency Vulnerabilities · Low vulnerability · ×1
  • REDACTED
D31 · IaC & Container Security · Low IaC · ×1
  • REDACTED
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 117 of 117 significant files have no living knowledge — the codebase as a whole is dormant, not 117 separate risks. Counted over 117 of the 211 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
DM9 · Scattered domain decisions · Rule about [metric, value] decided in 2 places · ×1
  • Rule about [metric, value] decided in 2 places — contracts.fabric.FoodTraceContract.TelemetryEntry's [metric, value] are judged in contracts.fabric.FoodTraceContract.FoodTraceContract, contracts.fabric.FoodTraceContractDeployable.FoodTraceContractDeployable — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
DM9 · Scattered domain decisions · Rule about [publicKeys, signatures] decided in 4 places · ×1
  • Rule about [publicKeys, signatures] decided in 4 places — modules.p2mr.src.types.SpendWitness's [publicKeys, signatures] are judged in modules.p2mr.src.script-interpreter, modules.p2mr.src.spend-proof, packages.enterprise-blockchain.src.p2mr.script-interpreter, packages.enterprise-blockchain.src.p2mr.spend-proof — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
DM9 · Scattered domain decisions · Rule about [maxRetries, retryCount, status] decided in 2 places · ×1
  • Rule about [maxRetries, retryCount, status] decided in 2 places — modules.stark-settlement.src.domain.entities.OutboxEntry's [maxRetries, retryCount, status] are judged in modules.stark-settlement.src.infrastructure.persistence.outbox-store.InMemoryOutboxStore, packages.enterprise-blockchain.src.stark-settlement.infrastructure.persistence.outbox-store.InMemoryOutboxStore — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
DM9 · Scattered domain decisions · Rule about [finalProof, stateRoot, tier1ProofIds] decided in 2 places · ×1
  • Rule about [finalProof, stateRoot, tier1ProofIds] decided in 2 places — modules.stark-settlement.src.domain.entities.Tier2BlockProof's [finalProof, stateRoot, tier1ProofIds] are judged in modules.stark-settlement.src.infrastructure.adapters.mock-stark-adapter.FlexibleMockStarkAdapter, packages.enterprise-blockchain.src.stark-settlement.infrastructure.adapters.mock-stark-adapter.FlexibleMockStarkAdapter — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
DM9 · Scattered domain decisions · Rule about [finalProof, stateRoot, tier1ProofIds, txCount] decided in 2 places · ×1
  • Rule about [finalProof, stateRoot, tier1ProofIds, txCount] decided in 2 places — modules.stark-settlement.src.domain.entities.Tier2BlockProof's [finalProof, stateRoot, tier1ProofIds, txCount] are judged in modules.stark-settlement.src.infrastructure.adapters.mock-stark-adapter.MockStarkAdapter, packages.enterprise-blockchain.src.stark-settlement.infrastructure.adapters.mock-stark-adapter.MockStarkAdapter — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate — Deployment 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 reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
R7 · Dead Code · Unused export 'AuditLogFactory' · ×1
  • Unused export 'AuditLogFactory' modules/hsm/src/infrastructure/audit-log-factory.ts:47 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/hsm/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/hsm/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'CURVE25519_PRIME' · ×1
  • Unused export 'CURVE25519_PRIME' modules/mpc/src/field.ts:36 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'demoField' · ×1
  • Unused export 'demoField' modules/mpc/src/field.ts:235 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/mpc/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/mpc/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'productionField' · ×1
  • Unused export 'productionField' modules/mpc/src/field.ts:239 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/mpc/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/mpc/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'SERVICE_NAME' · ×1
  • Unused export 'SERVICE_NAME' modules/shared/src/telemetry.ts:38 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/shared/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/shared/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'isTelemetryEnabled' · ×1
  • Unused export 'isTelemetryEnabled' modules/shared/src/telemetry.ts:44 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/shared/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/shared/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'withSpanSync' · ×1
  • Unused export 'withSpanSync' modules/shared/src/telemetry.ts:140 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/shared/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/shared/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'AggregatorService' · ×1
  • Unused export 'AggregatorService' modules/stark-settlement/src/application/aggregator-service.ts:51 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'SettlementService' · ×1
  • Unused export 'SettlementService' modules/stark-settlement/src/application/settlement-service.ts:65 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'ASSET_CONFIGS' · ×1
  • Unused export 'ASSET_CONFIGS' modules/stark-settlement/src/domain/entities.ts:44 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'STARK_GENERATOR' · ×1
  • Unused export 'STARK_GENERATOR' modules/stark-settlement/src/domain/value-objects.ts:32 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'sha256' · ×1
  • Unused export 'sha256' modules/stark-settlement/src/domain/value-objects.ts:545 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'sha256Bytes' · ×1
  • Unused export 'sha256Bytes' modules/stark-settlement/src/domain/value-objects.ts:552 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'pedersenHash' · ×1
  • Unused export 'pedersenHash' modules/stark-settlement/src/domain/value-objects.ts:561 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'defaultAuditLog' · ×1
  • Unused export 'defaultAuditLog' modules/stark-settlement/src/infrastructure/adapters/audit-adapter.ts:187 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'BitcoinTestnetAdapter' · ×1
  • Unused export 'BitcoinTestnetAdapter' modules/stark-settlement/src/infrastructure/adapters/bitcoin-adapter.ts:46 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'MockBitcoinAdapter' · ×1
  • Unused export 'MockBitcoinAdapter' modules/stark-settlement/src/infrastructure/adapters/bitcoin-adapter.ts:238 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'FixedClock' · ×1
  • Unused export 'FixedClock' modules/stark-settlement/src/infrastructure/adapters/clock-adapter.ts:32 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'defaultClock' · ×1
  • Unused export 'defaultClock' modules/stark-settlement/src/infrastructure/adapters/clock-adapter.ts:105 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'MockDilithiumAdapter' · ×1
  • Unused export 'MockDilithiumAdapter' modules/stark-settlement/src/infrastructure/adapters/dilithium-adapter.ts:91 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'createTransactionSigningAdapter' · ×1
  • Unused export 'createTransactionSigningAdapter' modules/stark-settlement/src/infrastructure/adapters/dilithium-adapter.ts:139 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'AsyncEventEmitter' · ×1
  • Unused export 'AsyncEventEmitter' modules/stark-settlement/src/infrastructure/adapters/event-emitter-adapter.ts:138 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'defaultEventEmitter' · ×1
  • Unused export 'defaultEventEmitter' modules/stark-settlement/src/infrastructure/adapters/event-emitter-adapter.ts:202 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'FiatMockAdapter' · ×1
  • Unused export 'FiatMockAdapter' modules/stark-settlement/src/infrastructure/adapters/fiat-adapter.ts:44 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'MockFiatAdapter' · ×1
  • Unused export 'MockFiatAdapter' modules/stark-settlement/src/infrastructure/adapters/fiat-adapter.ts:254 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'SolanaDevnetAdapter' · ×1
  • Unused export 'SolanaDevnetAdapter' modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts:49 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'MockSolanaAdapter' · ×1
  • Unused export 'MockSolanaAdapter' modules/stark-settlement/src/infrastructure/adapters/solana-adapter.ts:208 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'createStarknetProofAdapter' · ×1
  • Unused export 'createStarknetProofAdapter' modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts:363 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'createStoneProofAdapter' · ×1
  • Unused export 'createStoneProofAdapter' modules/stark-settlement/src/infrastructure/adapters/stone-proof-adapter.ts:620 — Nothing ultimately consumes this binding: its only referrer is the re-export in modules/stark-settlement/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in modules/stark-settlement/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
X5 · Nullable reference types · Null assertions (`!`) reduce the strict null checking score · ×1
  • Null assertions (`!`) reduce the strict null checking score — ~4.1 `!` null assertions per 1k TypeScript source lines — 152 assertion(s) across the 37432 source line(s) of the 208 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: modules/hsm/src/infrastructure/adapters/pkcs11-crypto-adapter.ts (24), modules/stark-settlement/src/infrastructure/adapters/starknet-proof-adapter.ts (11), packages/enterprise-blockchain/src/stark-settlement/infrastructure/adapters/starknet-proof-adapter.ts (11). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Minor — 29 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×17
  • Outdated (npm): @grpc/grpc-js — @grpc/grpc-js is pinned at 1.14.3; registry.npmjs.org publishes 1.14.6 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.
  • Outdated (npm): @grpc/proto-loader — @grpc/proto-loader is pinned at 0.8.0; registry.npmjs.org publishes 0.8.1 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.
  • Outdated (npm): @hyperledger/fabric-gateway — @hyperledger/fabric-gateway is pinned at 1.10.1; registry.npmjs.org publishes 1.13.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.
  • Outdated (npm): @noble/post-quantum — @noble/post-quantum is pinned at 0.6.1; registry.npmjs.org publishes 0.7.1 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.
  • Outdated (npm): @opentelemetry/api — @opentelemetry/api is pinned at 1.9.1; registry.npmjs.org publishes 1.10.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.
  • Outdated (npm): @opentelemetry/exporter-metrics-otlp-http — @opentelemetry/exporter-metrics-otlp-http is pinned at 0.214.0; registry.npmjs.org publishes 0.300.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.
  • Outdated (npm): @opentelemetry/exporter-trace-otlp-http — @opentelemetry/exporter-trace-otlp-http is pinned at 0.214.0; registry.npmjs.org publishes 0.300.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.
  • Outdated (npm): @opentelemetry/sdk-node — @opentelemetry/sdk-node is pinned at 0.214.0; registry.npmjs.org publishes 0.300.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.
  • Outdated (npm): @opentelemetry/semantic-conventions — @opentelemetry/semantic-conventions is pinned at 1.40.0; registry.npmjs.org publishes 1.43.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.
  • Outdated (npm): ethers — ethers is pinned at 6.16.0; registry.npmjs.org publishes 6.17.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.
  • Outdated (npm): lucide-react — lucide-react is pinned at 1.7.0; registry.npmjs.org publishes 1.61.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.
  • Outdated (npm): next — next is pinned at 16.2.3; registry.npmjs.org publishes 16.4.2 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.
  • Outdated (npm): react — react is pinned at 19.2.4; registry.npmjs.org publishes 19.3.1 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.
  • Outdated (npm): react-dom — react-dom is pinned at 19.2.4; registry.npmjs.org publishes 19.3.1 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.
  • Outdated (npm): starknet — starknet is pinned at 9.4.2; registry.npmjs.org publishes 10.8.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.
  • Outdated (npm): tailwind-merge — tailwind-merge is pinned at 3.5.0; registry.npmjs.org publishes 3.7.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.
  • Outdated (npm): zod — zod is pinned at 4.3.6; registry.npmjs.org publishes 4.6.7 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.
D10 · Test Quality · Skipped (documented) · ×12
  • Skipped (documented): validator-0 responds to health check tests/e2e-blockchain.e2e.ts:69 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
  • Skipped (documented): validator-1 responds to health check tests/e2e-blockchain.e2e.ts:89 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
  • Skipped (documented): both validators are on the same chain tests/e2e-blockchain.e2e.ts:105 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
  • Skipped (documented): blocks are being produced tests/e2e-blockchain.e2e.ts:125 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call It synchronises against work it did not wait for (`provider`, still running when the sleep starts) with `new Promise((resolve) => setTimeout(resolve, 3000))` — a fixed wait rather than a signal, which is the usual cause of exactly this kind of randomness.
  • Skipped (documented): can retrieve block details tests/e2e-blockchain.e2e.ts:145 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
  • Skipped (documented): eth_chainId returns correct chain ID tests/e2e-blockchain.e2e.ts:163 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
  • Skipped (documented): eth_gasPrice returns a value tests/e2e-blockchain.e2e.ts:179 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
  • Skipped (documented): eth_syncing returns false (not syncing) tests/e2e-blockchain.e2e.ts:192 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
  • Skipped (documented): net_version returns the network ID tests/e2e-blockchain.e2e.ts:206 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
  • Skipped (documented): eth_accounts returns available accounts tests/e2e-blockchain.e2e.ts:222 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
  • Skipped (documented): both validators report consistent chain state tests/e2e-blockchain.e2e.ts:278 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
  • Skipped (documented): health check works with real node tests/e2e-blockchain.e2e.ts:334 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call

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-ee0743d69b4043ccbf26ef0a74a96f70/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-ee0743d69b4043ccbf26ef0a74a96f70/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 .50artifacts/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-update30artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .21artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.0—
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 01a16466-4fa1-77b8-9288-df22d3819eba · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 69 · Warnings: 216 · Recommendations: 268 · Info: 29 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 16:16 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