dogganidhal/noddde

Executive summary

dogganidhal/noddde scores 52 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 Production Readiness, which scores 43 and is rated Weak. Its Security & performance tooling dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 15 Deprecated finding(s) in Dependency Hygiene and to add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing, and if Production Readiness rose to 70, the score would rise from 52 to about 59.

81 findings are critical: 42 in Dependency Vulnerabilities, 35 in Static Analysis (SAST), two in Dependency Hygiene, one in Domain ↔ infrastructure boundary and one in Test Quality.

Watchdog couldn't measure 5 dimensions in this code, among them Navigability, Platform End-of-Life and Cancellation propagation, so they are left out of the score. The product code is 29,330 lines, which would take an estimated 0.4 person-years, around €56,000, to rebuild.

Code Health 61 Adequate, capped by Nullable reference types Architecture 87 Strong Maturity 49 Weak, capped by Documentation accuracy Production Readiness 43 Weak, capped by Dependency Hygiene, Security & performance tooling and Schema migrations Security and Compliance 73 Adequate, capped by Dependency Vulnerabilities Domain Modelling 79 Strong Accessibility 71 Strong Performance 85 Strong

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.

Production Readiness 43 · counts for 45%Maturity 49 · counts for 25%Code Health 61 · counts for 14%Accessibility 71 · counts for 8%Security and Compliance 73 · counts for 4%Domain Modelling 79 · counts for 2%Performance 85 · counts for 1%Architecture 87 · counts for 1%

If Production Readiness rose from 43 to 70, the lowest score rated Strong, the score would rise from 52 to about 59.

Code composition: what the lines of code are

Product code 45%Tests 55%

New since the last survey: 95 findings

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

Test Quality · Fixed-sleep synchronisation: recovers and delivers after a full broker outage mid-consume packages/adapters/nats/src/__tests__/integration/nats.reconnect.integration.test.ts
Test Quality · Fixed-sleep synchronisation: recovers from a connection reset injected mid-flow packages/adapters/nats/src/__tests__/integration/nats.reconnect.integration.test.ts
Test Quality · Fixed-sleep synchronisation: recovers and delivers after a full broker outage mid-consume packages/adapters/rabbitmq/src/__tests__/integration/rabbitmq.reconnect.integration.test.ts
Test Quality · Fixed-sleep synchronisation: recovers from a connection reset injected mid-flow packages/adapters/rabbitmq/src/__tests__/integration/rabbitmq.reconnect.integration.test.ts
Test Quality · Fixed-sleep synchronisation: survives an outage while a handler is still in flight, without a silent ack-loss or a wedged consumer packages/adapters/rabbitmq/src/__tests__/integration/rabbitmq.reconnect.integration.test.ts
Test Quality · Fixed-sleep synchronisation: second acquire on same key blocks until first release packages/engine/src/__tests__/engine/implementations/in-memory-aggregate-locker.test.ts
Dependency Hygiene · Deprecated: eslint packages/adapters/drizzle/REDACTED
Dependency Hygiene · Deprecated: eslint packages/adapters/kafka/REDACTED
Dependency Hygiene · Deprecated: eslint packages/adapters/nats/REDACTED
Dependency Hygiene · Deprecated: nats packages/adapters/nats/REDACTED
Dependency Hygiene · Deprecated: eslint packages/adapters/prisma/REDACTED
Dependency Hygiene · Deprecated: eslint packages/adapters/rabbitmq/REDACTED
Dependency Hygiene · Deprecated: eslint packages/adapters/typeorm/REDACTED
Dependency Hygiene · Deprecated: eslint packages/cli/REDACTED
Dependency Hygiene · Deprecated: eslint packages/core/REDACTED
Dependency Hygiene · Deprecated: @opentelemetry/sdk-trace-base packages/engine/REDACTED
Dependency Hygiene · Deprecated: @opentelemetry/sdk-trace-node packages/engine/REDACTED
Dependency Hygiene · Deprecated: eslint packages/engine/REDACTED
Dependency Hygiene · Deprecated: eslint packages/integrations/nestjs/REDACTED
Dependency Hygiene · Deprecated: eslint packages/testing-integration/REDACTED
Dependency Hygiene · Deprecated: eslint packages/testing/REDACTED
Boundary Type-Coupling · Cross-context type PersistenceConfiguration (core → engine) packages/engine/src/aggregate-persistence-resolver.ts
Boundary Type-Coupling · Cross-context type PersistenceConfiguration (core → engine) packages/engine/src/aggregate-persistence-resolver.ts
Boundary Type-Coupling · Cross-context type PersistenceConfiguration (core → engine) packages/engine/src/aggregate-persistence-resolver.ts
Boundary Type-Coupling · Cross-context type PersistenceConfiguration (core → engine) packages/engine/src/aggregate-persistence-resolver.ts
Boundary Type-Coupling · Cross-context type PersistenceConfiguration (core → engine) packages/engine/src/aggregate-persistence-resolver.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/concurrency-strategy.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/concurrency-strategy.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/concurrency-strategy.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/concurrency-strategy.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/concurrency-strategy.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/concurrency-strategy.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/concurrency-strategy.ts
Boundary Type-Coupling · Cross-context type LogLevel (core → engine) packages/engine/src/logger.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-aggregate-persistence.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-aggregate-persistence.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-aggregate-persistence.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-aggregate-persistence.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-aggregate-persistence.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-saga-persistence.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-saga-persistence.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/executors/metadata-enricher.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/domain.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-aggregate-locker.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-aggregate-locker.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-idempotency-store.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-idempotency-store.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-snapshot-store.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-snapshot-store.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-view-store.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-view-store.ts
Boundary Type-Coupling · Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-view-store.ts
Boundary Type-Coupling · Cross-context type ID (core → testing) packages/testing/src/metadata-helpers.ts
Boundary Type-Coupling · Cross-context type ID (core → testing) packages/testing/src/metadata-helpers.ts
Boundary Type-Coupling · Cross-context type ID (core → testing) packages/testing/src/metadata-helpers.ts
Boundary Type-Coupling · Cross-context type ID (core → sample-hotel-booking) samples/sample-hotel-booking/src/infrastructure/persistence/drizzle-view-store.ts
Boundary Type-Coupling · Cross-context type ID (core → sample-hotel-booking) samples/sample-hotel-booking/src/infrastructure/persistence/drizzle-view-store.ts
Boundary Type-Coupling · Cross-context type ID (core → sample-hotel-booking) samples/sample-hotel-booking/src/infrastructure/persistence/drizzle-view-store.ts
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Supply-chain Provenance & Signing · REDACTED
Supply-chain Provenance & Signing · REDACTED
Supply-chain Provenance & Signing · REDACTED
Large Files · packages/engine/src/domain.ts: 1741 lines of code packages/engine/src/domain.ts
Large Files · packages/adapters/kafka/src/kafka-event-bus.ts: 810 lines of code packages/adapters/kafka/src/kafka-event-bus.ts
Large Files · packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts: 717 lines of code packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts
Large Files · packages/testing-integration/src/contracts/persistence-contract.ts: 536 lines of code packages/testing-integration/src/contracts/persistence-contract.ts
Large Files · packages/adapters/drizzle/src/persistence.ts: 477 lines of code packages/adapters/drizzle/src/persistence.ts
Large Files · packages/adapters/nats/src/nats-event-bus.ts: 449 lines of code packages/adapters/nats/src/nats-event-bus.ts
Large Files · packages/adapters/typeorm/src/persistence.ts: 423 lines of code packages/adapters/typeorm/src/persistence.ts
Dependency Hygiene · Unused dependency 'mssql'
Dependency Hygiene · Unused dependency '@nestjs/platform-express'
Documentation (README) · README may be stale
Exception handling · Swallowed exception (empty catch) packages/adapters/drizzle/src/unit-of-work.ts
Exception handling · Swallowed exception (empty catch) packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts
Exception handling · Swallowed exception (empty catch) packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts
Exception handling · Swallowed exception (empty catch) packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts
Exception handling · Swallowed exception (empty catch) packages/adapters/typeorm/src/mssql/advisory-locker.ts
Exception handling · Swallowed exception (empty catch) packages/cli/src/utils/discovery.ts
Exception handling · Swallowed exception (empty catch) packages/cli/src/utils/discovery.ts
Exception handling · Swallowed exception (empty catch) packages/cli/src/utils/cli-version.ts
Exception handling · Swallowed exception (empty catch) packages/engine/src/domain.ts
Exception handling · Swallowed exception (empty catch) packages/engine/src/domain.ts
Exception handling · Swallowed exception (empty catch) packages/engine/src/domain.ts
Exception handling · Swallowed exception (empty catch) packages/engine/src/domain.ts
Exception handling · Swallowed exception (empty catch) packages/engine/src/executors/saga-executor.ts
Exception handling · Swallowed exception (empty catch) packages/engine/src/executors/saga-executor.ts
Exception handling · Swallowed exception (empty catch) packages/engine/src/executors/command-lifecycle-executor.ts
Exception handling · Swallowed exception (empty catch) packages/engine/src/executors/command-lifecycle-executor.ts
Exception handling · Swallowed exception (empty catch) packages/engine/src/executors/command-lifecycle-executor.ts
Exception handling · Swallowed exception (empty catch) packages/engine/src/executors/command-lifecycle-executor.ts
Schema migrations · Schema created by TypeORM synchronize: true (no migration path) samples/sample-flash-sale/src/main-optimistic.ts
Domain ↔ infrastructure boundary · Domain depends on infrastructure: run-type-perf packages/core/scripts/run-type-perf.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: 78 findings

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

Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Supply-chain Provenance & Signing REDACTED
Supply-chain Provenance & Signing REDACTED
Code Duplication · Duplicated block (16 lines × 2 locations) packages/adapters/drizzle/src/mysql/schema.ts
Code Duplication · Duplicated block (16 lines × 2 locations) packages/adapters/drizzle/src/persistence.ts
Code Duplication · Duplicated block (16 lines × 2 locations) packages/adapters/drizzle/src/persistence.ts
Code Duplication · Duplicated block (16 lines × 2 locations) packages/core/src/ddd/aggregate-root.ts
Code Duplication · Duplicated block (16 lines × 2 locations) packages/testing-integration/src/containers/nats.ts
Code Duplication · Duplicated block (15 lines × 3 locations) packages/adapters/drizzle/src/pg/advisory-locker.ts
Code Duplication · Duplicated block (15 lines × 3 locations) packages/adapters/drizzle/src/unit-of-work.ts
Code Duplication · Duplicated block (15 lines × 3 locations) packages/adapters/drizzle/vitest.integration.config.mts
Code Duplication · Duplicated block (15 lines × 3 locations) packages/adapters/prisma/src/unit-of-work.ts
Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) scripts/check-spec-docs-links.mjs
Code Duplication · Duplicated block (14 lines × 2 locations) packages/adapters/typeorm/src/persistence.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/engine/src/implementations/in-memory-aggregate-persistence.ts
Code Duplication · Duplicated block (14 lines × 3 locations) packages/testing-integration/src/containers/mssql.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/testing-integration/src/contracts/outbox-contract.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/adapters/drizzle/src/dedicated-state-persistence.ts
Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) packages/adapters/kafka/vitest.config.mts
Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) packages/adapters/nats/vitest.config.mts
Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) packages/adapters/rabbitmq/vitest.config.mts
Code Duplication · Duplicated block (13 lines × 3 locations) packages/adapters/typeorm/src/dedicated-state-persistence.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/core/src/ddd/domain-definition.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/testing-integration/src/contracts/persistence-contract.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/testing-integration/src/contracts/unit-of-work-contract.ts
Code Duplication · Duplicated block (12 lines × 2 locations) packages/adapters/drizzle/src/advisory-locker.ts
Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) packages/adapters/kafka/vitest.config.mts
Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) packages/adapters/nats/vitest.config.mts
Code Duplication · Duplicated block (12 lines × 2 locations) packages/adapters/prisma/src/pg/advisory-locker.ts
Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) packages/adapters/rabbitmq/vitest.config.mts
Code Duplication · Duplicated block (12 lines × 2 locations) packages/adapters/typeorm/src/event-reader.ts
Code Duplication · Duplicated block (12 lines × 2 locations) packages/engine/src/executors/saga-executor.ts
Code Duplication · Duplicated block (11 lines × 5 locations) packages/adapters/drizzle/src/persistence.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/adapters/drizzle/src/pg/advisory-locker.ts
Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) packages/adapters/kafka/vitest.config.mts
Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) packages/adapters/nats/vitest.config.mts
Code Duplication · Duplicated block (11 lines × 3 locations) packages/adapters/typeorm/src/mssql/advisory-locker.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/adapters/typeorm/src/mssql/advisory-locker.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/adapters/typeorm/src/persistence.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/cli/src/generators/aggregate.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/core/src/infrastructure/closeable.ts
Code Duplication · Duplicated block (11 lines × 4 locations) packages/testing-integration/src/contracts/event-reader-contract.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/testing-integration/src/contracts/persistence-contract.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/adapters/drizzle/src/persistence.ts
Code Duplication · Duplicated block (10 lines × 3 locations) packages/adapters/drizzle/src/persistence.ts
Code Duplication · Duplicated block (10 lines × 4 locations) packages/adapters/prisma/src/persistence.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/cli/src/commands/add.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/engine/src/concurrency-strategy.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/engine/src/executors/command-lifecycle-executor.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/engine/src/implementations/in-memory-command-bus.ts
Code Duplication · Duplicated block (10 lines × 3 locations) packages/testing-integration/src/contracts/event-bus-contract.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/adapters/drizzle/src/pg/schema.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/adapters/prisma/src/persistence.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/adapters/typeorm/src/entities.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/cli/src/commands/diagram.ts
Code Duplication · Duplicated block (9 lines × 8 locations) packages/testing-integration/src/contracts/advisory-locker-contract.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/testing-integration/src/contracts/event-bus-contract.ts
Code Duplication · Duplicated block (9 lines × 3 locations) packages/testing-integration/src/contracts/outbox-contract.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/testing-integration/src/contracts/persistence-contract.ts
Code Duplication · Duplicated block (8 lines × 2 locations) packages/adapters/drizzle/src/mysql/advisory-locker.ts
Code Duplication · Duplicated block (8 lines × 3 locations) packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts
Code Duplication · Duplicated block (8 lines × 2 locations) packages/adapters/typeorm/src/persistence.ts
Code Duplication · Duplicated block (8 lines × 2 locations) packages/cli/src/diagram/emit-dot.ts
Code Duplication · Duplicated block (8 lines × 2 locations) packages/testing-integration/src/contracts/outbox-contract.ts
Code Duplication · Duplicated block (8 lines × 2 locations) packages/testing-integration/src/contracts/persistence-contract.ts
Code Duplication · Duplicated block (8 lines × 2 locations) packages/testing-integration/src/contracts/scale-contract.ts
Code Duplication · Duplicated block (7 lines × 2 locations) packages/adapters/drizzle/src/dedicated-state-persistence.ts
Code Duplication · Duplicated block (7 lines × 3 locations) packages/adapters/prisma/src/persistence.ts
Code Duplication · Duplicated block (7 lines × 2 locations) packages/cli/src/diagram/build-graph.ts
Code Duplication · Duplicated block (7 lines × 2 locations) packages/cli/src/utils/file-modifier.ts
Code Duplication · Duplicated block (7 lines × 2 locations) packages/core/src/ddd/aggregate-root.ts
Code Duplication · Duplicated block with local edits (6 matched lines × 2 locations) packages/adapters/drizzle/src/errors.ts
Code Duplication · Duplicated block (6 lines × 3 locations) packages/adapters/drizzle/src/persistence.ts
Code Duplication · Duplicated block (5 lines × 2 locations) packages/adapters/typeorm/src/persistence.ts
Code Duplication · Duplicated block with local edits (5 matched lines × 2 locations) packages/core/src/infrastructure/logger.ts

Rebuild cost: about €56,000 · Estimate

Cost to rebuild	€19,000 to €94,000, for 311 to 988 hours of work, about 0.4 person-years for one engineer
Difficulty of the problem	Low, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor	×0.7 at a score of 52. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size	Medium: 29,330 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.

Resolve the 15 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (15).

Raises the score by about 6 points · Medium effort · Dependency Hygiene

Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.

Raises the score by about 5 points · Medium effort · Security & performance tooling

Reconcile the README with reality: specs/README.md names `packages/docs/content/docs/`, but no file or folder `packages/docs/content/docs` exists; docs/content/docs/index.mdx links to `/docs/getting-started/why-noddde`, but `docs/getting-started/why-noddde` does not exist; docs/content/docs/index.mdx links to `/docs/getting-started/quick-start`, but `docs/getting-started/quick-start` does not exist; docs/content/docs/index.mdx links to `/docs/core-concepts/messages-and-types`, but `docs/core-concepts/messages-and-types` does not exist; docs/content/docs/index.mdx links to `/docs/modeling/defining-aggregates`, but `docs/modeling/defining-aggregates` does not exist.

Raises the score by about 5 points · Medium effort · Documentation accuracy

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.

Files that change often carry extra risk · Combined risk

4 files are changed often and are hard to read, which makes them the likeliest places for a mistake. They also have under half their code tested, or were written almost entirely by one person, so a mistake there is less likely to be caught, or only one person knows the code well enough to avoid it. A change to these files therefore carries more risk than the overall score suggests.

Based on: Churn × Complexity Hotspots (9 files) · Code Coverage (16 files under half tested) · The files: persistence.ts, advisory-locker.ts and unit-of-work.ts

What to do: Add tests to these files and have a second person review every change to them, starting with persistence.ts, advisory-locker.ts and unit-of-work.ts.

Where the investment is most exposed · Value at risk

This code would cost about €56,000 to build again, about 0.4 person-years of work. Its weakest lens is Production Readiness, at 43 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.

Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts

What to do: Start with the Production Readiness actions in Top priorities.

If you do one thing first · First action

Resolve the 15 Deprecated finding(s) in Dependency Hygiene. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for medium effort, because it clears the 15 Dependency Hygiene 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 — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

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.

265 modules, with 317 dependencies between them. 2 loops run through 6 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 225 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 packages.cli.src.utils.context	2 packages.cli.src.utils.persistence	3 packages.core.src.edd.event	4 packages.core.src.edd.event-bus	6 packages.core.src.id	7 packages.core.src.infrastructure.instrumentation	8 packages.core.src.infrastructure.logger	9 packages.core.src.persistence.unit-of-work	12 packages.adapters.prisma.src.unit-of-work	13 packages.adapters.typeorm.src.unit-of-work	15 packages.core.src.cqrs.command.command	16 packages.core.src.infrastructure	17 packages.core.src.persistence.aggregate-locker	18 packages.core.src.persistence.event-reader	19 packages.core.src.persistence.outbox	20 packages.core.src.persistence.snapshot	21 packages.core.src.persistence.view-store	22 packages.adapters.drizzle.src.advisory-locker	23 packages.core.src.ddd.projection	24 packages.core.src.persistence	25 packages.engine.src.concurrency-strategy	27 packages.adapters.drizzle.src	34 packages.engine.src.executors.command-lifecycle-executor	35 packages.engine.src.executors.saga-executor	37 packages.engine.src.projection-rebuild	40 packages.engine.src.domain
1 packages.cli.src.utils.context
2 packages.cli.src.utils.persistence
3 packages.core.src.edd.event
4 packages.core.src.edd.event-bus
5 packages.core.src.edd.event-idempotency
6 packages.core.src.id
7 packages.core.src.infrastructure.instrumentation
8 packages.core.src.infrastructure.logger
9 packages.core.src.persistence.unit-of-work
10 packages.testing-integration.src.containers
11 packages.adapters.kafka.src.kafka-event-bus			1	1		2	2
12 packages.adapters.prisma.src.unit-of-work								1
13 packages.adapters.typeorm.src.unit-of-work								1
14 packages.cli.src.utils	1	1
15 packages.core.src.cqrs.command.command					1
16 packages.core.src.infrastructure				1			1
17 packages.core.src.persistence.aggregate-locker					1
18 packages.core.src.persistence.event-reader			1
19 packages.core.src.persistence.outbox			1
20 packages.core.src.persistence.snapshot					2
21 packages.core.src.persistence.view-store					1
22 packages.adapters.drizzle.src.advisory-locker							1						1
23 packages.core.src.ddd.projection																	1
24 packages.core.src.persistence					3												1
25 packages.engine.src.concurrency-strategy					4		2	3					1
26 samples.sample-hotel-booking.src.infrastructure.types																	1
27 packages.adapters.drizzle.src			1												1	1		1		3
28 packages.adapters.prisma.src									1						1	1				3
29 packages.adapters.prisma.src.persistence									5						1	3				3
30 packages.adapters.prisma.src.prisma-adapter		1							1				1	1	1	1				3
31 packages.adapters.typeorm.src			1							1					1	1				3
32 packages.adapters.typeorm.src.typeorm-adapter		1								1			1	1	1	1				3
33 packages.core.src.persistence.adapter													1	1	1	1				3
34 packages.engine.src.executors.command-lifecycle-executor						1	1	1			1									1	1
35 packages.engine.src.executors.saga-executor			1			1	1	1												1						1
36 packages.engine.src.implementations.in-memory-aggregate-persistence			1		2									2		1				2
37 packages.engine.src.projection-rebuild				1			2							1			2		1
38 packages.testing.src			1									1							1
39 packages.adapters.drizzle.src.drizzle-adapter		1											1	1	1	1		1		3		1
40 packages.engine.src.domain				1	1	1									1		1		1				1	1	2

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 61% · Adequate · gated by X5 ·

The Good

D1 · TypeScript Cyclomatic Complexity 7.2 D3 · TypeScript God Classes 8.7 D17 · TypeScript Explicit Debt 9.7 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 10.0 R1 · React / TS Type Safety 9.9 R10 · React / TS Code Duplication 7.9 R2 · React / TS Cyclomatic Complexity 9.5 R3 · React / TS Large Files 8.7 R7 · React / TS Dead Code 10.0 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X25 · Repo Inert configuration knob 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

The Bad

D2 · TypeScript Cognitive Complexity 5.8 X23 · Repo Unguarded diagnostic materialisation 6.1 X3 · Repo Exception handling 5.1

The Ugly

X5 · Repo Nullable reference types 1.8

At a glance — Architecture · 87% · Strong ·

The Good

D5 · TypeScript Coupling 9.4 D6 · TypeScript Cohesion (LCOM4) 10.0 D7 · TypeScript Architectural Integrity 10.0 D22 · TypeScript Internal API Consistency 9.0 D23 · TypeScript Boundary Type-Coupling 7.6 D26 · TypeScript Project Cohesion 10.0 D35 · TypeScript Change Coupling 9.9 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0 R9 · React / TS Circular Imports 10.0

The Bad

AX10 · Repo Code composition 6.5

At a glance — Maturity · 49% · Weak · gated by M4 ·

The Good

D15 · TypeScript Churn × Complexity Hotspots 9.8 D19 · TypeScript Documentation Quality 9.3 D20 · TypeScript ADR Quality 7.0 D21 · TypeScript Naming Consistency 10.0 D34 · TypeScript Knowledge Freshness 10.0 M1 · Repo Documentation (README) 8.3 M3 · Repo Folder & project structure 10.0

The Ugly

M2 · Repo Architecture documentation 4.0 M4 · Repo Documentation accuracy 0.0

At a glance — Readiness · 43% · Weak · gated by R8, P3, P8 ·

The Good

D8 · TypeScript Code Coverage 9.7 D9 · TypeScript Test Distribution 10.0 D10 · TypeScript Test Quality 9.8 D11 · TypeScript Test Reliability 10.0 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 8.1 P4 · Repo Deployment & Rollback 7.0 P6 · Repo Release Hygiene 10.0 P9 · Repo Domain vs controller coverage 10.0 R4 · React / TS Test Coverage 9.8 R6 · React / TS Tooling 10.0

The Bad

D12 · TypeScript Dependency Hygiene 6.9

The Ugly

P3 · Repo Security & performance tooling 0.0 P8 · Repo Schema migrations 3.0 R8 · React / TS Dependency Hygiene 2.5

At a glance — Security · 73% · Adequate · gated by D30 ·

The Good

D28 · TypeScript Secrets (history) 10.0 D31 · TypeScript IaC & Container Security 10.0 D43 · TypeScript Malicious Dependencies 10.0 S1 · Repo Web-Security Posture 8.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0

The Bad

D29 · TypeScript Static Analysis (SAST) 5.4 D36 · TypeScript Supply-chain Provenance & Signing 5.0

The Ugly

D30 · TypeScript Dependency Vulnerabilities 0.0

At a glance — Domain Modelling · 79% · Strong ·

The Good

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

At a glance — Accessibility · 71% · Strong ·

The Good

AC1 · Repo Text alternatives 10.0 AC2 · Repo Forms & labels 10.0 AC5 · Repo ARIA correctness 10.0 AC6 · Repo Visual & motion safety 10.0

The Bad

AC3 · Repo Page structure 5.4

The Ugly

AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 85% · Strong ·

The Good

PF3 · Repo Async & latency hygiene 8.5

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 category	Findings	Severity
A03:2025 — Software Supply Chain Failures	77	High / Critical
A05:2025 — Injection	37	High / Critical

Roadmap

First, resolve the fifteen deprecated dependencies in REDACTED and remove unused or misclassified packages to ensure a clean dependency tree. Next, integrate a SAST step into the CI pipeline to automatically block security regressions before they land. Finally, correct the broken links and inaccuracies in the documentation and organize architecture decision records under a dedicated docs folder for better discoverability.

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

Do this	Helps	Effort	Dimension
Resolve the 15 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (15).	+5.8 pts	Medium	Dependency Hygiene
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.	+5.0 pts	Medium	Security & performance tooling
Reconcile the README with reality: specs/README.md names `packages/docs/content/docs/`, but no file or folder `packages/docs/content/docs` exists; docs/content/docs/index.mdx links to `/docs/getting-started/why-noddde`, but `docs/getting-started/why-noddde` does not exist; docs/content/docs/index.mdx links to `/docs/getting-started/quick-start`, but `docs/getting-started/quick-start` does not exist; docs/content/docs/index.mdx links to `/docs/core-concepts/messages-and-types`, but `docs/core-concepts/messages-and-types` does not exist; docs/content/docs/index.mdx links to `/docs/modeling/defining-aggregates`, but `docs/modeling/defining-aggregates` does not exist.	+4.6 pts	Medium	Documentation accuracy
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with typed-dispatch.test.ts.	+2.3 pts	Low	Test Quality
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.	+3.4 pts	Medium	Dependency Hygiene
Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find.	+3.2 pts	Medium	Architecture documentation
Replace TypeORM synchronize: true with TypeORM migrations (`typeorm migration:generate` + `migrationsRun`) so the production schema can evolve safely and reproducibly.	+3.1 pts	Medium	Schema migrations
Improve ADR Quality — currently 7.0/10.	+2.5 pts	Medium	ADR Quality

File quality

Per-file score 0–10 — a quality signature. Of 133 files carrying findings, judged against the Production bar: 3% slop · 32% mixed · 65% near-clean.

File	Score	Band	Worst signal
REDACTED	0.0	Slop	Dependency Vulnerabilities: Critical vulnerability: REDACTED
REDACTED	2.3	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	2.4	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	2.7	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	4.6	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.6	Mixed	Static Analysis (SAST): High: REDACTED
packages/engine/src/__tests__/engine/typed-dispatch.test.ts	5.1	Mixed	Test Quality: No assertions (empty test): should dispatch standalone commands at runtime
packages/engine/src/domain.ts	5.5	Mixed	Cyclomatic Complexity: Domain.init (cyclomatic 113)
packages/engine/src/executors/command-lifecycle-executor.ts	5.6	Mixed	Cyclomatic Complexity: CommandLifecycleExecutor.executeLifecycle (cyclomatic 22)
packages/testing/src/metadata-helpers.ts	5.9	Mixed	Code Coverage: Low coverage: packages/testing/src/metadata-helpers.ts
packages/cli/src/templates/domain/domain-wiring.ts	6.4	Mixed	Explicit Debt: TodoComment
packages/cli/src/templates/saga/saga.ts	6.6	Mixed	Explicit Debt: TodoComment
packages/cli/src/templates/add/command.ts	6.9	Mixed	Explicit Debt: TodoComment
packages/cli/src/templates/aggregate/aggregate.ts	6.9	Mixed	Explicit Debt: TodoComment
packages/cli/src/templates/domain/saga-transition-handlers.ts	6.9	Mixed	Explicit Debt: TodoComment
packages/cli/src/templates/domain/projection.ts	6.9	Mixed	Explicit Debt: TodoComment
samples/sample-flash-sale/src/main-optimistic.ts	6.9	Mixed	Explicit Debt: TodoComment
REDACTED	6.9	Mixed	Static Analysis (SAST): Medium: REDACTED
packages/adapters/typeorm/src/entities.ts	7.0	Mixed	God Classes: FunctionTooLong: entities.buildEntities
packages/engine/src/concurrency-strategy.ts	7.0	Mixed	Boundary Type-Coupling: Cross-context type ID (core → engine)

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

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

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

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

Could not be resolved — 6

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

D1D2D3D5D6D7D8D9D10D11D12D13D14D15D17D19D20D21D22D23D26D28D29D30D31D34D35D36D43AC1AC2AC3AC5AC6AC7AX10AX3AX5AX6DM6DM9GD1IC1M1M2M3M4P1P10P2P3P4P6P8P9PF3R1R10R2R3R4R6R7R8R9S1X1X12X13X14X15X16X17X18X19X21X22X23X24X25X28X29X3X30X5

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

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, 740 of 780 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.)
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.
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.

Method	Backs	Version	Evaluator
Roslyn static analysis	Complexity, cohesion, coupling, dead code, API surface, layering	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy · checkov	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3 · 3.2.533	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a163e4-8b17-71a1-9aaf-8963447a8c3b.

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.

D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 458 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 2 hold 0.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
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.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/adapters/drizzle/src/builder.ts`, `packages/adapters/nats/src/nats-event-bus.ts`, `packages/adapters/prisma/src/builder.ts`, `packages/adapters/typeorm/src/builder.ts`, `packages/core/src/cqrs/query/query.ts`, … (+3 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
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 (samples/sample-hotel-booking/docker-compose.yml). compose up failed (exit 18 — an image could not be pulled) — rabbitmq Pulling postgres Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden rabbitmq Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: postgres Pulling rabbitmq Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden rabbitmq Error Get "https://registry-1.docker.io/v2/": Forbidden 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.
M4 Documentation accuracy — 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. 282 further occurrence(s) are not listed individually; the score already reflects all 322.
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. 72 further occurrence(s) are not listed individually; the score already reflects all 112.
X2 Cancellation propagation — 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, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

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

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
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.
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.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
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.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

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

Dimensions

D1 · Cyclomatic Complexity7.2 / 10Strong✓ 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 7.2 / 10 · rule-coverage 100% · ceiling Prevented

8 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Domain.init at 113.

Domain.init (cyclomatic 113)packages/engine/src/domain.ts:443

SagaExecutor.execute (cyclomatic 23)packages/engine/src/executors/saga-executor.ts:55

CommandLifecycleExecutor.executeLifecycle (cyclomatic 22)packages/engine/src/executors/command-lifecycle-executor.ts:229

projection-rebuild.rebuildProjectionImpl (cyclomatic 20)packages/engine/src/projection-rebuild.ts:179

KafkaEventBus._handleMessage (cyclomatic 19)packages/adapters/kafka/src/kafka-event-bus.ts:683

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

What to do

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

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

Do you agree with this assessment?

D2 · Cognitive Complexity5.8 / 10Adequate✓ 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 5.8 / 10 · rule-coverage 100% · ceiling Prevented

16 method(s) exceeded the cognitive complexity threshold of 15; the worst was Domain.init at 228.

Domain.init (cognitive 228)packages/engine/src/domain.ts:443

CommandLifecycleExecutor.execute (cognitive 36)packages/engine/src/executors/command-lifecycle-executor.ts:71

SagaExecutor.execute (cognitive 34)packages/engine/src/executors/saga-executor.ts:55

CommandLifecycleExecutor.executeLifecycle (cognitive 29)packages/engine/src/executors/command-lifecycle-executor.ts:229

projection-rebuild.rebuildProjectionImpl (cognitive 29)packages/engine/src/projection-rebuild.ts:179

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

What to do

Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with Domain.init (cognitive 228). — Refactoring it lifts Cognitive Complexity from 5.8 to about 7.2/10.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D3 · God Classes8.7 / 10Strong✓ Tool-verified

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

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

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

10 god class(es) detected.

FunctionTooLong: persistence-contract.definePersistenceContract · ×5packages/testing-integration/src/contracts/persistence-contract.ts:87

MethodTooLong: Domain.init · ×3packages/engine/src/domain.ts:443

FileTooLong: src/domain.tspackages/engine/src/domain.ts

ClassTooLong: Domainpackages/engine/src/domain.ts:380

What to do

Resolve the 5 FunctionTooLong finding(s) in God Classes — start with persistence-contract.ts, event-bus-contract.ts, unit-of-work-contract.ts. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 3 MethodTooLong finding(s) in God Classes — start with domain.ts, saga-executor.ts, command-lifecycle-executor.ts. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 FileTooLong finding(s) in God Classes — start with domain.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D5 · Coupling9.4 / 10Stronggated by 1 serious finding✓ 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 9.4 / 10 · rule-coverage 100% · ceiling Prevented

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

Off the main sequence: @noddde/engine

What to do

Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

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

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

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

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

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

0 of 63 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

Do you agree with this assessment?

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 1 mechanizable ADR(s) are enforced: 1 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.

Do you agree with this assessment?

D8 · Code Coverage9.7 / 10Stronggated by 28 serious findings✓ 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.7 / 10 · rule-coverage 100% · ceiling Verified

Line coverage 72.1% — 28 file(s) below 50%. Measured from the JavaScript/TypeScript suite (vitest + @vitest/coverage-v8 via `yarn install --frozen-lockfile --ignore-scripts` in packages/adapters/drizzle/; vitest + @vitest/coverage-v8 via `yarn install --frozen-lockfile --ignore-scripts` in packages/adapters/kafka/; vitest + @vitest/coverage-v8 via `yarn install --frozen-lockfile --ignore-scripts` in packages/adapters/nats/; vitest + @vitest/coverage-v8 via `yarn install --frozen-lockfile --ignore-scripts` in packages/adapters/prisma/; vitest + @vitest/coverage-v8 via `yarn install --frozen-lockfile --ignore-scripts` in packages/adapters/rabbitmq/; vitest + @vitest/coverage-v8 via `yarn install --frozen-lockfile --ignore-scripts` in packages/adapters/typeorm/; vitest + @vitest/coverage-v8 via `yarn install --frozen-lockfile --ignore-scripts` in packages/cli/; vitest + @vitest/coverage-v8 via `yarn install --frozen-lockfile --ignore-scripts` in packages/core/; vitest + @vitest/coverage-v8 via `yarn install --frozen-lockfile --ignore-scripts` in packages/engine/; vitest + @vitest/coverage-v8 via `yarn install --frozen-lockfile --ignore-scripts` in packages/integrations/nestjs/; vitest + @vitest/coverage-v8 via `yarn install --frozen-lockfile --ignore-scripts` in packages/testing/; vitest in packages/testing-integration/: not run).

Low coverage: packages/adapters/drizzle/src/advisory-locker.ts · ×28packages/adapters/drizzle/src/advisory-locker.ts:1

What to do

Resolve the 28 Low coverage finding(s) in Code Coverage — start with advisory-locker.ts (5), builder.ts (2), dedicated-state-persistence.ts (2). — One of this dimension's main actionable groups (28 warning-level).
Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality9.8 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

0 skipped, 268 zero-assertion, 6 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1577 tests (1 harness-style project(s) excluded from the assertion penalty).

No assertions (empty test): should dispatch standalone commands at runtimepackages/engine/src/__tests__/engine/typed-dispatch.test.ts:192

No assertions: typed-column mapper: TS rejects mappers with mismatched row keys · ×19packages/adapters/drizzle/src/__tests__/builder.test.ts:459

Fixed-sleep synchronisation: recovers and delivers after a full broker outage mid-consume · ×6packages/adapters/nats/src/__tests__/integration/nats.reconnect.integration.test.ts:52

No direct assertions: should accept string · ×248packages/core/src/__tests__/id.test.ts:5

Mock-dominated test: should explicitly commit offsets after handling · ×28packages/adapters/kafka/src/__tests__/kafka-event-bus.test.ts:451

What to do

Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with typed-dispatch.test.ts. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 19 No assertions finding(s) in Test Quality — start with typed-dispatch.test.ts (6), wire-domain-at-scale.test.ts (5), builder.test.ts (3). — One of this dimension's main actionable groups (19 warning-level).
Resolve the 6 Fixed-sleep synchronisation finding(s) in Test Quality — start with rabbitmq.reconnect.integration.test.ts (3), nats.reconnect.integration.test.ts (2), in-memory-aggregate-locker.test.ts. — One of this dimension's main actionable groups (6 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

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 (vitest via `yarn install --frozen-lockfile --ignore-scripts` in packages/adapters/drizzle/ (77 tests); vitest via `yarn install --frozen-lockfile --ignore-scripts` in packages/adapters/kafka/ (42 tests); vitest via `yarn install --frozen-lockfile --ignore-scripts` in packages/adapters/nats/ (32 tests); vitest via `yarn install --frozen-lockfile --ignore-scripts` in packages/adapters/prisma/ (14 tests); vitest via `yarn install --frozen-lockfile --ignore-scripts` in packages/adapters/rabbitmq/ (42 tests); vitest via `yarn install --frozen-lockfile --ignore-scripts` in packages/adapters/typeorm/ (73 tests); vitest via `yarn install --frozen-lockfile --ignore-scripts` in packages/cli/ (203 tests); vitest via `yarn install --frozen-lockfile --ignore-scripts` in packages/core/ (351 tests); vitest via `yarn install --frozen-lockfile --ignore-scripts` in packages/engine/ (414 tests); vitest via `yarn install --frozen-lockfile --ignore-scripts` in packages/integrations/nestjs/ (14 tests); vitest via `yarn install --frozen-lockfile --ignore-scripts` in packages/testing/ (45 tests); vitest via `yarn install --frozen-lockfile --ignore-scripts` in packages/testing-integration/ (0 tests)): measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

Do you agree with this assessment?

D12 · Dependency Hygiene6.9 / 10Adequate✓ 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 6.9 / 10 · rule-coverage 100% · ceiling Verified

22 outdated direct production npm dependency(ies) of 24 graded, 0 pinning defect(s), across 18 REDACTED (14 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 4 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: eslint · ×15packages/adapters/drizzle/REDACTED:97

Deprecated: @humanwhocodes/config-array · ×10REDACTED:1111

Outdated (npm): @inquirer/prompts · ×22

What to do

Resolve the 15 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (15). — One of this dimension's main actionable groups (15 warning-level).
Resolve the 10 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (10). — One of this dimension's main actionable groups (10 recommendation-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

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.

Do you agree with this assessment?

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

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

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

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

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

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

Top hotspots: packages/engine/src/domain.ts (3×113=339); packages/adapters/kafka/src/kafka-event-bus.ts (10×19=190); packages/engine/src/executors/saga-executor.ts (4×23=92) Repeated repair below the complexity floor: packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts (5 of 5 changes were fixes); packages/testing-integration/src/contracts/persistence-contract.ts (4 of 6 changes were fixes); packages/adapters/typeorm/src/persistence.ts (4 of 5 changes were fixes)

Repeated repair: packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts · ×10packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts:539

Hotspot: packages/engine/src/domain.ts · ×3packages/engine/src/domain.ts:443

What to do

Resolve the 10 Repeated repair finding(s) in Churn × Complexity Hotspots — start with persistence.ts (3), advisory-locker.ts (3), rabbitmq-event-bus.ts. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with domain.ts, kafka-event-bus.ts, saga-executor.ts. — One of this dimension's main actionable groups (3 warning-level).

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

Do you agree with this assessment?

D17 · Explicit Debt9.7 / 10Stronggated by 41 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 9.7 / 10 · rule-coverage 100% · ceiling Prevented

41 deducted task-comment markers across 28752 LoC (0.1/KLoC) → score 9.7. 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 · ×41packages/cli/src/templates/add/event-handler.ts:17

What to do

Resolve the 41 TodoComment finding(s) in Explicit Debt — start with domain-wiring.ts (9), aggregate.ts (5), saga.ts (4). — One of this dimension's main actionable groups (41 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D19 · Documentation QualityExemplary◐ Sampled · advisory

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

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

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

The repository's root README and the packages/core README give a strong overview of noddde as a TypeScript framework for domain modeling, event sourcing, CQRS, and testing. The architecture/Docs markdown files (20+ entries) cover design docs, adapter directories, test harnesses, and detailed usage of each package, making this an enterprise-grade documentation set. All visible documents are well-structured with headings, examples, and a consistent overview; the only unshown element is the full CI/release process for the main branch. The repository is well documented: the READMEs for each package directory (e.g. samples/sample-flash-sale/README.md) describe what the directory contains and give a quick start with test-running commands; architecture/design docs are also present (81 markdown files). The root README gives an overview of the project, installation, usage, contribution guidance, and licence. The repository is well documented: the READMEs for each packages/integrations/nestjs directory and the architecture/design docs are complete. The root README gives an overview of what noddde is (a TypeScript framework for DDD/CQRS/Event Sourcing using the functional Decider pattern) and links to a full guide, while the architecture doc explains what noddde is, its target audience, design priorities, anti-goals, and covers competitive context. The API docs are comprehensive: each class, interface, type alias, constructor, accessor, method, and their signatures are listed with links to the source.

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

Do you agree with this assessment?

D20 · ADR QualityStrong◐ 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 Strong / 10 · rule-coverage 100% · ceiling Documented

Evaluated 1 ADR(s) individually; mean quality 7.0/10 (mixed — many ADRs miss context or consequences). 0 flagged with a specific gap.

What to do

Improve ADR Quality — currently 7.0/10. — Evaluated 1 ADR(s) individually; mean quality 7.0/10 (mixed — many ADRs miss context or consequences). 0 flagged with a specific gap.

Detailed fixes: d20_recommendation.md.

Do you agree with this assessment?

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.

Do you agree with this assessment?

D22 · Internal API ConsistencyStronggated by 3 serious findings◐ 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 186 exposed types.

Duplicate intent with different naming and parameter types. Both interfaces check for the existence of a processed key/command. One uses 'hasProcessed' with a string key, the other uses 'exists' with an ID type.

Duplicate intent with different signatures. Both mark an item as processed. One takes a simple key string, the other takes a full record object.

Duplicate intent. Both interfaces define the same method for cleaning up expired entries.

What to do

Resolve the 1 Duplicate intent with different naming and parameter types. Both… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Duplicate intent with different signatures. Both mark an item as… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Duplicate intent. Both interfaces define the same method for cleaning up… 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.

Do you agree with this assessment?

D23 · Boundary Type-Coupling7.6 / 10Strong✓ Tool-verified

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

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

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

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

37 domain type(s) cross context boundaries across 16 contexts.

Cross-context type ID (core → engine) · ×25packages/engine/src/concurrency-strategy.ts:30

Cross-context type PersistenceConfiguration (core → engine) · ×5packages/engine/src/aggregate-persistence-resolver.ts:19

Cross-context type ID (core → testing) · ×3packages/testing/src/metadata-helpers.ts:98

Cross-context type ID (core → sample-hotel-booking) · ×3samples/sample-hotel-booking/src/infrastructure/persistence/drizzle-view-store.ts:44

Cross-context type LogLevel (core → engine)packages/engine/src/logger.ts:97

What to do

Resolve the 25 Cross-context type ID (core → engine) finding(s) in Boundary Type-Coupling — start with concurrency-strategy.ts (7), in-memory-aggregate-persistence.ts (5), in-memory-view-store.ts (3). — One of this dimension's main actionable groups (25 warning-level).
Resolve the 5 Cross-context type PersistenceConfiguration (core → engine) finding(s) in Boundary Type-Coupling — start with aggregate-persistence-resolver.ts (5). — One of this dimension's main actionable groups (5 warning-level).
Resolve the 3 Cross-context type ID (core → testing) finding(s) in Boundary Type-Coupling — start with metadata-helpers.ts (3). — One of this dimension's main actionable groups (3 warning-level).
Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

Do you agree with this assessment?

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.

Do you agree with this assessment?

D29 · Static Analysis (SAST)5.4 / 10Adequate✓ 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 5.4 / 10 · rule-coverage 100% · ceiling Documented

37 finding(s): 0 critical, 35 high, 2 medium, 0 low. 32 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 12 file(s) — `packages/adapters/drizzle/src/builder.ts` (line 168), `packages/adapters/nats/src/nats-event-bus.ts` (line 415), `packages/adapters/prisma/src/__tests__/ga-hardening.test.ts` (line 12), `packages/adapters/prisma/src/builder.ts` (line 154), `packages/adapters/typeorm/src/builder.ts` (line 156), … (+7 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 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

What to do

Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
No action in Static Analysis (SAST) — all 32 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 (32 issue-level, 0 of them charged here).

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

Do you agree with this assessment?

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

71 finding(s): 3 critical, 39 high, 24 medium, 5 low.

REDACTED

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

What to do

Resolve the 39 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (39). — One of this dimension's main actionable groups (39 issue-level).
Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

Do you agree with this assessment?

D31 · IaC & Container Security10.0 / 10Exemplary○ Nothing flagged

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

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

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

trivy and checkov found no infrastructure-as-code or container misconfigurations.

✓ On the Gold path — maintain.

Detailed fixes: d31_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

Strongest change-coupling: command-lifecycle-executor.ts↔saga-executor.ts 55%

Change coupling: command-lifecycle-executor.ts ↔ saga-executor.tspackages/engine/src/executors/command-lifecycle-executor.ts:1

What to do

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

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

Do you agree with this assessment?

D36 · Supply-chain Provenance & Signing5.0 / 10Adequate✓ 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 5.0 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED

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

What to do

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

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

Do you agree with this assessment?

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.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

Do you agree with this assessment?

AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged

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

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

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

Do you agree with this assessment?

AC3 · Page structure5.4 / 10Adequate✓ Tool-verified

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

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

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

No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — docs/src/app/layout.tsx:59

What to do

Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.

Do you agree with this assessment?

AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

Do you agree with this assessment?

AC6 · Visual & motion safety10.0 / 10Exemplary○ Nothing flagged

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

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

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

Do you agree with this assessment?

AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

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

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

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

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

What to do

Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.

Do you agree with this assessment?

AX10 · Code composition6.5 / 10Adequate✓ 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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

DM6 · Domain ↔ infrastructure boundary7.9 / 10Strong✓ 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.

`packages/core/scripts/run-type-perf.ts` (domain layer) depends on `node:fs` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it. — packages/core/scripts/run-type-perf.ts:13

What to do

Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository).

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

M1 · Documentation (README)8.3 / 10Strong✓ 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.

189 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.

What to do

Add a README to the 2 of 18 project(s) that lack one — worth up to 0.2 pts.
Review the README against recent changes; refresh the parts that drifted.

Do you agree with this assessment?

M2 · Architecture documentation4.0 / 10Weak✓ 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.

1 ADR-shaped document(s) detected by content — `specs/api-freeze.spec.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.

What to do

Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

specs/README.md names `packages/docs/content/docs/`, but no file or folder `packages/docs/content/docs` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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. — specs/README.md:199
docs/content/docs/index.mdx links to `/docs/getting-started/why-noddde`, but `docs/getting-started/why-noddde` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/index.mdx:14
docs/content/docs/index.mdx links to `/docs/getting-started/quick-start`, but `docs/getting-started/quick-start` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/index.mdx:15
docs/content/docs/index.mdx links to `/docs/core-concepts/messages-and-types`, but `docs/core-concepts/messages-and-types` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/index.mdx:16
docs/content/docs/index.mdx links to `/docs/modeling/defining-aggregates`, but `docs/modeling/defining-aggregates` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/index.mdx:24
docs/content/docs/index.mdx links to `/docs/running/domain-configuration`, but `docs/running/domain-configuration` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/index.mdx:25
docs/content/docs/index.mdx links to `/docs/running/persistence-adapters`, but `docs/running/persistence-adapters` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/index.mdx:26
docs/content/docs/index.mdx links to `/docs/design-decisions/why-decider`, but `docs/design-decisions/why-decider` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/index.mdx:27
docs/content/docs/core-concepts/cqrs-and-event-sourcing.mdx links to `/docs/process-managers/sagas`, but `docs/process-managers/sagas` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/cqrs-and-event-sourcing.mdx:32
docs/content/docs/core-concepts/cqrs-and-event-sourcing.mdx links to `/docs/modeling/defining-aggregates`, but `docs/modeling/defining-aggregates` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/cqrs-and-event-sourcing.mdx:62
docs/content/docs/core-concepts/cqrs-and-event-sourcing.mdx links to `/docs/read-model/projections`, but `docs/read-model/projections` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/cqrs-and-event-sourcing.mdx:90
docs/content/docs/core-concepts/cqrs-and-event-sourcing.mdx links to `/docs/running/domain-configuration`, but `docs/running/domain-configuration` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/cqrs-and-event-sourcing.mdx:334
docs/content/docs/core-concepts/decider-pattern.mdx links to `/docs/modeling/defining-aggregates`, but `docs/modeling/defining-aggregates` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/decider-pattern.mdx:335
docs/content/docs/core-concepts/decider-pattern.mdx links to `/docs/design-decisions/why-decider`, but `docs/design-decisions/why-decider` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/decider-pattern.mdx:336
docs/content/docs/core-concepts/decider-pattern.mdx links to `/docs/running/infrastructure`, but `docs/running/infrastructure` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/decider-pattern.mdx:337
docs/content/docs/core-concepts/messages-and-types.mdx links to `/docs/running/idempotent-commands`, but `docs/running/idempotent-commands` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/messages-and-types.mdx:42
docs/content/docs/core-concepts/messages-and-types.mdx links to `/docs/getting-started/quick-start`, but `docs/getting-started/quick-start` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/messages-and-types.mdx:625
docs/content/docs/core-concepts/messages-and-types.mdx links to `/docs/modeling/defining-aggregates`, but `docs/modeling/defining-aggregates` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/messages-and-types.mdx:626
docs/content/docs/core-concepts/messages-and-types.mdx links to `/docs/core-concepts/decider-pattern`, but `docs/core-concepts/decider-pattern` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/messages-and-types.mdx:627
docs/content/docs/core-concepts/messages-and-types.mdx links to `/docs/design-decisions/why-aggregate-types`, but `docs/design-decisions/why-aggregate-types` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/messages-and-types.mdx:628
docs/content/docs/core-concepts/messages-and-types.mdx links to `/docs/design-decisions/why-define-commands-events`, but `docs/design-decisions/why-define-commands-events` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/messages-and-types.mdx:629
docs/content/docs/design-decisions/why-decider.mdx links to `/docs/core-concepts/decider-pattern#decider-vs-oop-aggregates`, but `docs/core-concepts/decider-pattern` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/design-decisions/why-decider.mdx:12
docs/content/docs/design-decisions/why-injectable-infrastructure.mdx links to `/docs/running/infrastructure`, but `docs/running/infrastructure` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/design-decisions/why-injectable-infrastructure.mdx:106
docs/content/docs/design-decisions/why-sagas-return-commands.mdx links to `/docs/process-managers/sagas#atomicity`, but `docs/process-managers/sagas` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/design-decisions/why-sagas-return-commands.mdx:64
docs/content/docs/design-decisions/why-two-persistence-strategies.mdx links to `/docs/running/persistence#decision-matrix`, but `docs/running/persistence` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/design-decisions/why-two-persistence-strategies.mdx:74
docs/content/docs/event-bus/kafka.mdx links to `/docs/running/event-bus-adapters#handler-error-isolation`, but `docs/running/event-bus-adapters` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/event-bus/kafka.mdx:49
docs/content/docs/event-bus/nats.mdx links to `/docs/running/event-bus-adapters#handler-error-isolation`, but `docs/running/event-bus-adapters` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/event-bus/nats.mdx:42
docs/content/docs/event-bus/rabbitmq.mdx links to `/docs/running/event-bus-adapters#handler-error-isolation`, but `docs/running/event-bus-adapters` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/event-bus/rabbitmq.mdx:50
docs/content/docs/getting-started/cli.mdx links to `/docs/getting-started/project-structure`, but `docs/getting-started/project-structure` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/getting-started/cli.mdx:57
docs/content/docs/getting-started/introduction.mdx links to `/docs/getting-started/quick-start`, but `docs/getting-started/quick-start` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/getting-started/introduction.mdx:6
docs/content/docs/getting-started/introduction.mdx links to `/docs/modeling/defining-aggregates`, but `docs/modeling/defining-aggregates` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/getting-started/introduction.mdx:32
docs/content/docs/getting-started/introduction.mdx links to `/docs/core-concepts/messages-and-types`, but `docs/core-concepts/messages-and-types` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/getting-started/introduction.mdx:45
docs/content/docs/getting-started/introduction.mdx links to `/docs/read-model/projections`, but `docs/read-model/projections` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/getting-started/introduction.mdx:80
docs/content/docs/getting-started/introduction.mdx links to `/docs/process-managers/sagas`, but `docs/process-managers/sagas` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/getting-started/introduction.mdx:102
docs/content/docs/getting-started/introduction.mdx links to `/docs/running/persistence-adapters`, but `docs/running/persistence-adapters` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/getting-started/introduction.mdx:118
docs/content/docs/getting-started/introduction.mdx links to `/docs/getting-started/why-noddde`, but `docs/getting-started/why-noddde` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/getting-started/introduction.mdx:124
docs/content/docs/getting-started/quick-start.mdx runs `npx tsx account.ts`, but `account.ts` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/getting-started/quick-start.mdx:184
docs/content/docs/getting-started/quick-start.mdx links to `/docs/design-decisions/why-id-not-in-state`, but `docs/design-decisions/why-id-not-in-state` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/getting-started/quick-start.mdx:251
docs/content/docs/getting-started/quick-start.mdx links to `/docs/design-decisions/why-aggregate-types`, but `docs/design-decisions/why-aggregate-types` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/getting-started/quick-start.mdx:269
docs/content/docs/getting-started/quick-start.mdx links to `/docs/running/persistence-adapters`, but `docs/running/persistence-adapters` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/getting-started/quick-start.mdx:321

What to do

Reconcile the README with reality: specs/README.md names `packages/docs/content/docs/`, but no file or folder `packages/docs/content/docs` exists; docs/content/docs/index.mdx links to `/docs/getting-started/why-noddde`, but `docs/getting-started/why-noddde` does not exist; docs/content/docs/index.mdx links to `/docs/getting-started/quick-start`, but `docs/getting-started/quick-start` does not exist; docs/content/docs/index.mdx links to `/docs/core-concepts/messages-and-types`, but `docs/core-concepts/messages-and-types` does not exist; docs/content/docs/index.mdx links to `/docs/modeling/defining-aggregates`, but `docs/modeling/defining-aggregates` does not exist.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

P2 · Observability8.1 / 10Strong✓ 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.

Only 5/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `docs`, `packages/cli`.

What to do

Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.

Do you agree with this assessment?

P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 16396 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

P4 · Deployment & Rollback7.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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

P8 · Schema migrations3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.

TypeORM synchronize: true builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt TypeORM migrations (`typeorm migration:generate` + `migrationsRun`), so every schema change is a versioned file applied the same way in every environment. (×2) — samples/sample-flash-sale/src/main-pessimistic.ts:71, samples/sample-flash-sale/src/main-optimistic.ts:72

What to do

Replace TypeORM synchronize: true with TypeORM migrations (`typeorm migration:generate` + `migrationsRun`) so the production schema can evolve safely and reproducibly.

Do you agree with this assessment?

P9 · Domain vs controller coverage10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

PF3 · Async & latency hygiene8.5 / 10Strong✓ 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.

`fs.writeFileSync` in `callback to action` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/cli/src/commands/diagram.ts:81

What to do

TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.

Do you agree with this assessment?

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

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

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

What to do

Migrate the remaining .js/.jsx files to TypeScript.

Do you agree with this assessment?

R10 · Code Duplication7.9 / 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.

38 duplicated blocks under packages/adapters/ have copies in at least two of the sibling directories drizzle, kafka, nats, prisma, rabbitmq, typeorm — 26 of them are reported below, and 12 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 38 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 38 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 38 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/adapters/prisma/src/persistence.ts:47
7 duplicated blocks under packages/ have copies in at least two of the sibling directories adapters, cli, core, engine, integrations, testing — 4 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/core/src/ddd/domain-definition.ts:17
5 of the duplicated blocks reported below have copies in at least two of the sibling directories mysql, pg, sqlite under packages/adapters/drizzle/src/. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/adapters/drizzle/src/pg/schema.ts:29
packages/adapters/prisma/src/persistence.ts:47 · packages/adapters/typeorm/src/persistence.ts:90 — the two spans are one implementation copied and then locally edited — 1313 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/adapters/prisma/src/persistence.ts:47
packages/cli/src/generators/domain.ts:60 · packages/cli/src/generators/project.ts:65 — the two spans are one implementation copied and then locally edited — 416 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/cli/src/generators/domain.ts:60
packages/adapters/prisma/src/builder.ts:59 · packages/adapters/typeorm/src/builder.ts:59 — the two spans are one implementation copied and then locally edited — 436 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/adapters/prisma/src/builder.ts:59
packages/adapters/prisma/src/mysql/advisory-locker.ts:20 · packages/adapters/prisma/src/pg/advisory-locker.ts:20 — the two spans are one implementation copied and then locally edited — 371 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/adapters/prisma/src/mysql/advisory-locker.ts:20
packages/adapters/prisma/src/unit-of-work.ts:14 · packages/adapters/typeorm/src/unit-of-work.ts:15 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/adapters/prisma/src/unit-of-work.ts:14
packages/adapters/drizzle/src/pg/schema.ts:29 · packages/adapters/drizzle/src/sqlite/schema.ts:24 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/adapters/drizzle/src/pg/schema.ts:29
packages/adapters/typeorm/src/mysql/advisory-locker.ts:16 · packages/adapters/typeorm/src/pg/advisory-locker.ts:16 — the two spans are one implementation copied and then locally edited — 294 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/adapters/typeorm/src/mysql/advisory-locker.ts:16
packages/adapters/drizzle/src/mysql/advisory-locker.ts:17 · packages/adapters/drizzle/src/pg/advisory-locker.ts:19 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/adapters/drizzle/src/mysql/advisory-locker.ts:17
packages/testing-integration/src/contracts/saga-contract.ts:5 · packages/testing-integration/src/contracts/snapshot-contract.ts:4 — the two spans are one implementation copied and then locally edited — 286 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/testing-integration/src/contracts/saga-contract.ts:5
packages/integrations/nestjs/src/noddde.module.ts:180 · packages/integrations/nestjs/src/noddde.module.ts:240 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/integrations/nestjs/src/noddde.module.ts:180
packages/adapters/kafka/src/kafka-event-bus.ts:716 · packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts:554 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/adapters/kafka/src/kafka-event-bus.ts:716
packages/testing-integration/src/containers/mysql.ts:8 · packages/testing-integration/src/containers/postgres.ts:7 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/testing-integration/src/containers/mysql.ts:8
packages/cli/src/utils/discovery.ts:96 · packages/cli/src/utils/discovery.ts:135 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/cli/src/utils/discovery.ts:96
packages/adapters/prisma/src/persistence.ts:123 · packages/adapters/prisma/src/persistence.ts:201 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/adapters/prisma/src/persistence.ts:123
packages/adapters/drizzle/src/builder.ts:243 · packages/adapters/typeorm/src/builder.ts:191 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/adapters/drizzle/src/builder.ts:243
packages/cli/src/generators/add-command.ts:67 · packages/cli/src/generators/add-query.ts:52 — the two spans are one implementation copied and then locally edited — 198 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/cli/src/generators/add-command.ts:67
packages/adapters/drizzle/src/persistence.ts:167 · packages/adapters/drizzle/src/persistence.ts:262 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/adapters/drizzle/src/persistence.ts:167
packages/adapters/prisma/src/index.ts:47 · packages/adapters/typeorm/src/index.ts:50 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/adapters/prisma/src/index.ts:47
packages/adapters/prisma/src/keyed-mutex.ts:12 · packages/adapters/typeorm/src/keyed-mutex.ts:11 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/adapters/prisma/src/keyed-mutex.ts:12
packages/cli/src/generators/aggregate.ts:47 · packages/cli/src/generators/projection.ts:50 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/cli/src/generators/aggregate.ts:47
packages/adapters/prisma/src/persistence.ts:175 · packages/adapters/prisma/src/persistence.ts:239 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/adapters/prisma/src/persistence.ts:175
packages/adapters/drizzle/src/mysql/schema.ts:69 · packages/adapters/drizzle/src/pg/schema.ts:70 · packages/adapters/drizzle/src/sqlite/schema.ts:62 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/adapters/drizzle/src/mysql/schema.ts:69
packages/adapters/typeorm/src/entities.ts:237 · packages/adapters/typeorm/src/entities.ts:270 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/adapters/typeorm/src/entities.ts:237
packages/cli/src/utils/discovery.ts:22 · packages/cli/src/utils/discovery.ts:59 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/cli/src/utils/discovery.ts:22
packages/adapters/prisma/src/advisory-locker.ts:181 · packages/adapters/typeorm/src/advisory-locker.ts:92 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/adapters/prisma/src/advisory-locker.ts:181
packages/testing-integration/src/contracts/unit-of-work-contract.ts:140 · packages/testing-integration/src/contracts/unit-of-work-contract.ts:187 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/testing-integration/src/contracts/unit-of-work-contract.ts:140
packages/adapters/drizzle/src/dedicated-state-persistence.ts:85 · packages/adapters/drizzle/src/persistence.ts:214 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/adapters/drizzle/src/dedicated-state-persistence.ts:85
packages/adapters/nats/src/nats-event-bus.ts:244 · packages/engine/src/implementations/ee-event-bus.ts:109 — the two spans are one implementation copied and then locally edited — 137 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/adapters/nats/src/nats-event-bus.ts:244
packages/cli/src/generators/add-query.ts:48 · packages/cli/src/generators/aggregate.ts:51 · packages/cli/src/generators/projection.ts:54 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/cli/src/generators/add-query.ts:48
packages/cli/src/generators/domain.ts:171 · packages/cli/src/generators/saga.ts:28 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/cli/src/generators/domain.ts:171
packages/core/src/ddd/domain-definition.ts:17 · packages/engine/src/domain.ts:135 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/core/src/ddd/domain-definition.ts:17
packages/adapters/prisma/src/dedicated-state-persistence.ts:54 · packages/adapters/prisma/src/persistence.ts:57 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/adapters/prisma/src/dedicated-state-persistence.ts:54
packages/adapters/typeorm/src/dedicated-state-persistence.ts:79 · packages/adapters/typeorm/src/persistence.ts:218 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/adapters/typeorm/src/dedicated-state-persistence.ts:79
packages/adapters/prisma/src/dedicated-state-persistence.ts:81 · packages/adapters/prisma/src/persistence.ts:166 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/adapters/prisma/src/dedicated-state-persistence.ts:81
packages/cli/src/generators/add-command.ts:45 · packages/cli/src/generators/add-query.ts:34 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/cli/src/generators/add-command.ts:45
packages/testing-integration/src/contracts/persistence-contract.ts:149 · packages/testing-integration/src/contracts/persistence-contract.ts:168 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/testing-integration/src/contracts/persistence-contract.ts:149
packages/adapters/drizzle/src/advisory-locker.ts:129 · packages/adapters/prisma/src/advisory-locker.ts:182 · packages/adapters/typeorm/src/advisory-locker.ts:93 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/adapters/drizzle/src/advisory-locker.ts:129

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.

Do you agree with this assessment?

R2 · Cyclomatic Complexity9.5 / 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.

init has cyclomatic complexity 94 and cognitive complexity 183; 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/engine/src/domain.ts:443
executeLifecycle has cyclomatic complexity 23 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/engine/src/executors/command-lifecycle-executor.ts:229
_handleMessage has cyclomatic complexity 23 and cognitive complexity 31; 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/adapters/kafka/src/kafka-event-bus.ts:683
rebuildProjectionImpl has cyclomatic complexity 22 and cognitive complexity 31; 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/engine/src/projection-rebuild.ts:179
introspectDomain has cyclomatic complexity 21 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/cli/src/diagram/introspect.ts:23
rebuildProjection has cyclomatic complexity 19 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. — packages/engine/src/domain.ts:1594
buildDomainGraph has cyclomatic complexity 18 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/cli/src/diagram/build-graph.ts:25
execute has cyclomatic complexity 15 and cognitive complexity 26; 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/engine/src/executors/command-lifecycle-executor.ts:71
save has cyclomatic complexity 15 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/adapters/drizzle/src/persistence.ts:270
_handleMessage has cyclomatic complexity 14 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts:539
_connectWithRetry has cyclomatic complexity 13 and cognitive complexity 26; 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/adapters/rabbitmq/src/rabbitmq-event-bus.ts:225
_handleMessage has cyclomatic complexity 13 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. — packages/adapters/nats/src/nats-event-bus.ts:228
analyzeSagaCommands has cyclomatic complexity 12 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/cli/src/diagram/static-analyze.ts:24
_consumeSubscription has cyclomatic complexity 11 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/adapters/nats/src/nats-event-bus.ts:414
collectNameLiterals has cyclomatic complexity 11 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/cli/src/diagram/static-analyze.ts:188
dispatch has cyclomatic complexity 11 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/engine/src/implementations/ee-event-bus.ts:98

What to do

Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.

Do you agree with this assessment?

R3 · Large Files8.7 / 10Strong✓ Tool-verified

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

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

packages/engine/src/domain.ts has 1741 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/engine/src/domain.ts:1
packages/adapters/kafka/src/kafka-event-bus.ts has 810 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/adapters/kafka/src/kafka-event-bus.ts:1
packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts has 717 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/adapters/rabbitmq/src/rabbitmq-event-bus.ts:1
packages/testing-integration/src/contracts/persistence-contract.ts has 536 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/testing-integration/src/contracts/persistence-contract.ts:1
packages/adapters/drizzle/src/persistence.ts has 477 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/adapters/drizzle/src/persistence.ts:1
packages/adapters/nats/src/nats-event-bus.ts has 449 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/adapters/nats/src/nats-event-bus.ts:1
packages/adapters/typeorm/src/persistence.ts has 423 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/adapters/typeorm/src/persistence.ts:1

What to do

Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.

Do you agree with this assessment?

R4 · Test Coverage9.8 / 10Exemplary✓ Tool-verified

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

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

No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×3) — REDACTED:1, scripts/check-spec-docs-links.mjs:1, scripts/copy-license.mjs:1

What to do

Add tests that import the unreached modules (directly or through their public entry).

Do you agree with this assessment?

R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED 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: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

R8 · Dependency Hygiene2.5 / 10Weak✓ 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.

Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×2) — packages/adapters/nats/src/__tests__/integration/nats.reconnect.integration.test.ts:2, packages/adapters/rabbitmq/src/__tests__/integration/rabbitmq.reconnect.integration.test.ts:2
Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED. — packages/eslint-config/library.js:5
Declared in packages/adapters/typeorm/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Declared in packages/eslint-config/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Declared in packages/integrations/nestjs/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

What to do

Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.

Do you agree with this assessment?

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.

Do you agree with this assessment?

S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. Markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. 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.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

`https://cloud.umami.is/script.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. — docs/src/app/layout.tsx:81

What to do

Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

X23 · Unguarded diagnostic materialisation6.1 / 10Adequate✓ Tool-verified

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.

`debug` at line 353 is called with an argument built by `enrichedEvents.map((e) => e.name)` (line 356), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/engine/src/executors/command-lifecycle-executor.ts:353

What to do

Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is JavaScript's evaluation order, not a guess — then put the construction behind the level check the logger offers (`if (logger.isLevelEnabled('debug'))` for pino and winston, `isDebugEnabled()` for log4js, the repository's own debug flag where it has one), or hand the logger the object and a format string (`logger.debug({ payload }, 'raw request')`) so the serialising happens only when the line is written. Moving the call is not the fix: it is the join/projection/stringify in the argument that is paid, wherever the call sits.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

X3 · Exception handling5.1 / 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. (×17) — packages/adapters/drizzle/src/unit-of-work.ts:137, packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts:508, packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts:517, …
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts:296

What to do

Swallowed exception (empty catch)

Do you agree with this assessment?

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.

Do you agree with this assessment?

X5 · Nullable reference types1.8 / 10Critical✓ 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.

1/35 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~4.7 `!` null assertions per 1k TypeScript source lines — 123 assertion(s) across the 26106 source line(s) of the 227 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/adapters/typeorm/src/entities.ts (52), packages/engine/src/domain.ts (10), packages/adapters/kafka/src/kafka-event-bus.ts (8). 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 `?`).

Do you agree with this assessment?

WCAG coverage — what static analysis assessed

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

Dimension	WCAG 2.2 A/AA criteria	Coverage
AC1 · Text alternatives	1.1.1, 1.2.2, 1.2.5	Partial signal
AC2 · Forms & labels	1.3.1, 3.3.2, 4.1.2	Partial signal
AC3 · Page structure	1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2	Partial signal
AC5 · ARIA correctness	4.1.2	Partial signal
AC6 · Visual & motion safety	1.4.3, 2.4.7	Partial — literal CSS only
AC7 · A11y enforcement	enforcement — no page criterion	Enforcement posture (process)

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

Reference — by lens

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

Lens	Score	Rating	Impact
Code Health	61%	Adequate — gated by X5	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	87%	Strong	Strongest area.
Maturity	49%	Weak — gated by M4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	43%	Weak — gated by R8, P3, P8	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	73%	Adequate — gated by D30	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling	79%	Strong	Solid.
Accessibility	71%	Strong	Solid.
Performance	85%	Strong	Solid.

Unscored — 3 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 — 7 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
X10 Duplicated predicate — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.

Not evidenced — 1 control(s) we could not find positive evidence for

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

P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control

Not included — 51 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.

AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX1 Captive dependencies — Not applicable: NestJS makes a provider that injects a request-scoped one request-scoped itself (scope bubbles up the injection chain), and gives every consumer its own transient instance by contract.
AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX4 Dependency direction — not applicable to a transaction-script/CRUD architecture (the inward-dependency rule is for layered/clean styles)
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) — rabbitmq Pulling postgres Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden rabbitmq Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: postgres Pulling rabbitmq Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden rabbitmq Error Get "https://registry-1.docker.io/v2/": Forbidden 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.
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — none of 1 ADRs are conformance-checkable — unverifiable.
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.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) — 8 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
DM1 Aggregate boundaries — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM10 One transaction, one aggregate — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM2 Strongly-typed ids — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM4 Rich vs anemic model — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM5 Encapsulated state — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
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 JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
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 REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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 — 81 finding(s)

D30 · Dependency Vulnerabilities · High CVE · ×39

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.

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
+ 7 more in this group — see findings.md.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED

D30 · Dependency Vulnerabilities · Critical CVE · ×2

REDACTED
REDACTED

R8 · Dependency Hygiene · Unlisted import 'testcontainers' · ×2

Unlisted import 'testcontainers' packages/adapters/nats/src/__tests__/integration/nats.reconnect.integration.test.ts:2 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'testcontainers' packages/adapters/rabbitmq/src/__tests__/integration/rabbitmq.reconnect.integration.test.ts:2 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.

D10 · Test Quality · No assertions (empty test) · ×1

No assertions (empty test): should dispatch standalone commands at runtime packages/engine/src/__tests__/engine/typed-dispatch.test.ts:192 — Test method has an empty body — it asserts nothing and exercises no code.

D30 · Dependency Vulnerabilities · Critical vulnerability · ×1

REDACTED

DM6 · Domain ↔ infrastructure boundary · Domain depends on infrastructure · ×1

Domain depends on infrastructure: run-type-perf packages/core/scripts/run-type-perf.ts:13 — `packages/core/scripts/run-type-perf.ts` (domain layer) depends on `node:fs` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it.

Serious — 330 finding(s)

D17 · Explicit Debt · TodoComment · ×41

TodoComment packages/cli/src/templates/add/event-handler.ts:17 — // TODO: once event types are wired in the projection def, replace with: — 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/cli/src/templates/domain/projection-view-reducers.ts:13 — // TODO: once event types are wired in the projection def, replace with: — 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/cli/src/templates/add/event-handler.ts:29 — // TODO: update view fields from event payload — 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/cli/src/templates/add/command.ts:19 — // TODO: add command payload fields — 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/cli/src/templates/domain/aggregate-commands.ts:13 — // TODO: add command payload fields — 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/cli/src/templates/add/command.ts:34 — // TODO: map command payload to event payload — 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/cli/src/templates/add/command.ts:48 — // TODO: evolve state from event payload — 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/cli/src/templates/domain/aggregate-evolvers.ts:18 — // TODO: evolve state from event payload — 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/cli/src/templates/aggregate/aggregate.ts:16 — // TODO: add more events — 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/cli/src/templates/domain/aggregate.ts:28 — // TODO: add more events — 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/cli/src/templates/aggregate/aggregate.ts:21 — // TODO: add more commands — 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/cli/src/templates/domain/aggregate.ts:33 — // TODO: add more commands — 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/cli/src/templates/aggregate/aggregate.ts:30 — // TODO: replace with domain-specific infrastructure type — 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/cli/src/templates/domain/saga-transition-handlers.ts:13 — // TODO: once the real event type is wired in the saga def, replace with: — 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/cli/src/templates/domain/saga-transition-handlers.ts:27 — // TODO: extract relevant data from the event — 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/cli/src/templates/domain/saga-transition-handlers.ts:29 — // TODO: dispatch commands to other aggregates — 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/cli/src/templates/domain/saga-state.ts:8 — // TODO: add saga state fields for tracking workflow progress — 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/cli/src/templates/domain/projection.ts:17 — // TODO: import event types and on-entries once wired — 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/cli/src/templates/domain/projection.ts:22 — // TODO: replace with event union type — 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/cli/src/templates/domain/projection.ts:31 — // TODO: uncomment and adjust when event types are wired — 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/cli/src/templates/domain/projection-view-reducers.ts:24 — // TODO: populate view fields from event — 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/cli/src/templates/domain/projection-queries.ts:11 — // TODO: define read model fields — 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/cli/src/templates/domain/event-model.ts:14 — // TODO: add event payload fields — 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/cli/src/templates/domain/domain-wiring.ts:34 — // TODO: add domain-wide dependencies (clock, logger, external services) — 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/cli/src/templates/domain/domain-wiring.ts:57 — // TODO: provide infrastructure implementations — 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.
+ 16 more in this group — see findings.md.

D8 · Code Coverage · Low coverage · ×28

Low coverage: packages/adapters/drizzle/src/advisory-locker.ts packages/adapters/drizzle/src/advisory-locker.ts:1 — 0.0% line coverage (0/43).
Low coverage: packages/adapters/drizzle/src/builder.ts packages/adapters/drizzle/src/builder.ts:1 — 0.0% line coverage (0/24).
Low coverage: packages/adapters/drizzle/src/dedicated-state-persistence.ts packages/adapters/drizzle/src/dedicated-state-persistence.ts:1 — 0.0% line coverage (0/31).
Low coverage: packages/adapters/drizzle/src/drizzle-adapter.ts packages/adapters/drizzle/src/drizzle-adapter.ts:1 — 0.0% line coverage (0/31).
Low coverage: packages/adapters/drizzle/src/event-idempotency.ts packages/adapters/drizzle/src/event-idempotency.ts:1 — 0.0% line coverage (0/25).
Low coverage: packages/adapters/drizzle/src/event-reader.ts packages/adapters/drizzle/src/event-reader.ts:1 — 7.1% line coverage (1/14).
Low coverage: packages/adapters/drizzle/src/index.ts packages/adapters/drizzle/src/index.ts:1 — 0.0% line coverage (0/2).
Low coverage: packages/adapters/drizzle/src/json-state-mapper.ts packages/adapters/drizzle/src/json-state-mapper.ts:1 — 0.0% line coverage (0/20).
Low coverage: packages/adapters/drizzle/src/persistence.ts packages/adapters/drizzle/src/persistence.ts:1 — 9.8% line coverage (12/123).
Low coverage: packages/adapters/drizzle/src/unit-of-work.ts packages/adapters/drizzle/src/unit-of-work.ts:1 — 43.1% line coverage (25/58).
Low coverage: packages/adapters/drizzle/src/mysql/advisory-locker.ts packages/adapters/drizzle/src/mysql/advisory-locker.ts:1 — 0.0% line coverage (0/38).
Low coverage: packages/adapters/drizzle/src/pg/advisory-locker.ts packages/adapters/drizzle/src/pg/advisory-locker.ts:1 — 0.0% line coverage (0/47).
Low coverage: packages/adapters/typeorm/src/builder.ts packages/adapters/typeorm/src/builder.ts:1 — 0.0% line coverage (0/16).
Low coverage: packages/adapters/typeorm/src/dedicated-state-persistence.ts packages/adapters/typeorm/src/dedicated-state-persistence.ts:1 — 0.0% line coverage (0/29).
Low coverage: packages/adapters/typeorm/src/entities.ts packages/adapters/typeorm/src/entities.ts:1 — 47.6% line coverage (40/84).
Low coverage: packages/adapters/typeorm/src/event-idempotency.ts packages/adapters/typeorm/src/event-idempotency.ts:1 — 12.5% line coverage (4/32).
Low coverage: packages/adapters/typeorm/src/event-reader.ts packages/adapters/typeorm/src/event-reader.ts:1 — 9.5% line coverage (2/21).
Low coverage: packages/adapters/typeorm/src/index.ts packages/adapters/typeorm/src/index.ts:1 — 0.0% line coverage (0/2).
Low coverage: packages/adapters/typeorm/src/json-state-mapper.ts packages/adapters/typeorm/src/json-state-mapper.ts:1 — 10.0% line coverage (1/10).
Low coverage: packages/adapters/typeorm/src/persistence.ts packages/adapters/typeorm/src/persistence.ts:1 — 0.8% line coverage (1/119).
Low coverage: packages/adapters/typeorm/src/typeorm-adapter.ts packages/adapters/typeorm/src/typeorm-adapter.ts:1 — 6.7% line coverage (1/15).
Low coverage: packages/adapters/typeorm/src/unit-of-work.ts packages/adapters/typeorm/src/unit-of-work.ts:1 — 0.0% line coverage (0/30).
Low coverage: packages/adapters/typeorm/src/mysql/advisory-locker.ts packages/adapters/typeorm/src/mysql/advisory-locker.ts:1 — 10.3% line coverage (3/29).
Low coverage: packages/adapters/typeorm/src/pg/advisory-locker.ts packages/adapters/typeorm/src/pg/advisory-locker.ts:1 — 8.3% line coverage (3/36).
Low coverage: packages/core/src/persistence/concurrency-error.ts packages/core/src/persistence/concurrency-error.ts:1 — 14.3% line coverage (1/7).
+ 3 more in this group — see findings.md.

D23 · Boundary Type-Coupling · Cross-context type ID (core → engine) · ×25

Cross-context type ID (core → engine) packages/engine/src/concurrency-strategy.ts:30 — ID (context core) is exposed in engine's public surface via ConcurrencyStrategy.execute — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/concurrency-strategy.ts:44 — ID (context core) is exposed in engine's public surface via ConcurrencyStrategy.acquireForUow — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/concurrency-strategy.ts:73 — ID (context core) is exposed in engine's public surface via OptimisticConcurrencyStrategy.execute — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/concurrency-strategy.ts:116 — ID (context core) is exposed in engine's public surface via PessimisticConcurrencyStrategy.execute — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/concurrency-strategy.ts:146 — ID (context core) is exposed in engine's public surface via PessimisticConcurrencyStrategy.acquireForUow — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/concurrency-strategy.ts:182 — ID (context core) is exposed in engine's public surface via PerAggregateConcurrencyStrategy.execute — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/concurrency-strategy.ts:196 — ID (context core) is exposed in engine's public surface via PerAggregateConcurrencyStrategy.acquireForUow — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-aggregate-persistence.ts:38 — ID (context core) is exposed in engine's public surface via InMemoryEventSourcedAggregatePersistence.load — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-aggregate-persistence.ts:62 — ID (context core) is exposed in engine's public surface via InMemoryEventSourcedAggregatePersistence.loadAfterVersion — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-aggregate-persistence.ts:72 — ID (context core) is exposed in engine's public surface via InMemoryEventSourcedAggregatePersistence.save — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-aggregate-persistence.ts:160 — ID (context core) is exposed in engine's public surface via InMemoryStateStoredAggregatePersistence.load — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-aggregate-persistence.ts:180 — ID (context core) is exposed in engine's public surface via InMemoryStateStoredAggregatePersistence.save — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-saga-persistence.ts:29 — ID (context core) is exposed in engine's public surface via InMemorySagaPersistence.load — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-saga-persistence.ts:47 — ID (context core) is exposed in engine's public surface via InMemorySagaPersistence.save — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/executors/metadata-enricher.ts:37 — ID (context core) is exposed in engine's public surface via MetadataEnricher.enrich — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/domain.ts:87 — ID (context core) is exposed in engine's public surface via MetadataContext.userId — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-aggregate-locker.ts:42 — ID (context core) is exposed in engine's public surface via InMemoryAggregateLocker.acquire — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-aggregate-locker.ts:87 — ID (context core) is exposed in engine's public surface via InMemoryAggregateLocker.release — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-idempotency-store.ts:38 — ID (context core) is exposed in engine's public surface via InMemoryIdempotencyStore.exists — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-idempotency-store.ts:83 — ID (context core) is exposed in engine's public surface via InMemoryIdempotencyStore.remove — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-snapshot-store.ts:25 — ID (context core) is exposed in engine's public surface via InMemorySnapshotStore.load — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-snapshot-store.ts:41 — ID (context core) is exposed in engine's public surface via InMemorySnapshotStore.save — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-view-store.ts:27 — ID (context core) is exposed in engine's public surface via InMemoryViewStore.save — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-view-store.ts:38 — ID (context core) is exposed in engine's public surface via InMemoryViewStore.load — couples the contexts.
Cross-context type ID (core → engine) packages/engine/src/implementations/in-memory-view-store.ts:49 — ID (context core) is exposed in engine's public surface via InMemoryViewStore.delete — couples the contexts.

D30 · Dependency Vulnerabilities · Medium CVE · ×24

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D10 · Test Quality · No assertions · ×19

No assertions: typed-column mapper: TS rejects mappers with mismatched row keys packages/adapters/drizzle/src/__tests__/builder.test.ts:459 — 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.
No assertions: should use .catch() on consumer loop to prevent unhandled promise rejections packages/adapters/nats/src/__tests__/nats-event-bus.test.ts:437 — 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.
No assertions: stream is created if it doesn't already exist packages/adapters/nats/src/__tests__/integration/nats.integration.test.ts:84 — 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.
No assertions: typed-column mapper: TS rejects configs missing the mapper packages/adapters/prisma/src/__tests__/builder.test.ts:329 — 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.
No assertions: typed-column mapper: TS rejects configs missing the mapper packages/adapters/typeorm/src/__tests__/builder.test.ts:315 — 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.
No assertions: should accept commands from registered aggregates packages/engine/src/__tests__/engine/typed-dispatch.test.ts:130 — 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.
No assertions: should return targetAggregateId for aggregate commands packages/engine/src/__tests__/engine/typed-dispatch.test.ts:173 — 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.
No assertions: should accept queries from registered projections packages/engine/src/__tests__/engine/typed-dispatch.test.ts:221 — 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.
No assertions: should accept queries from registered projections with typed results packages/engine/src/__tests__/engine/typed-dispatch.test.ts:242 — 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.
No assertions: should extract command union from multi-aggregate map packages/engine/src/__tests__/engine/typed-dispatch.test.ts:290 — 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.
No assertions: should extract query union from multi-projection map packages/engine/src/__tests__/engine/typed-dispatch.test.ts:311 — 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.
No assertions: acquire and release on a single key works without blocking packages/engine/src/__tests__/engine/implementations/in-memory-aggregate-locker.test.ts:6 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: release is idempotent (double release does not throw) packages/engine/src/__tests__/engine/implementations/in-memory-aggregate-locker.test.ts:55 — 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.
No assertions: different keys do not interfere packages/engine/src/__tests__/engine/implementations/in-memory-aggregate-locker.test.ts:65 — 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.
No assertions: InferDomain accumulates aggregate commands into the dispatch union packages/engine/src/__tests__/stress/wire-domain-at-scale.test.ts:123 — 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.
No assertions: InferDomain accumulates projection queries into the query union packages/engine/src/__tests__/stress/wire-domain-at-scale.test.ts:135 — 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.
No assertions: InferDomain intersects infrastructure from aggregates, projections, and sagas packages/engine/src/__tests__/stress/wire-domain-at-scale.test.ts:144 — 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.
No assertions: dispatchCommand on the inferred Domain narrows by name (compile-time) packages/engine/src/__tests__/stress/wire-domain-at-scale.test.ts:148 — 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.
No assertions: dispatchCommand rejects names that aren't in the union (compile-time) packages/engine/src/__tests__/stress/wire-domain-at-scale.test.ts:154 — 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.

X3 · Exception handling · Swallowed exception (empty catch) · ×18

Swallowed exception (empty catch) packages/adapters/drizzle/src/unit-of-work.ts:137 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts:296 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts:508 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts:517 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/adapters/typeorm/src/mssql/advisory-locker.ts:66 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/cli/src/utils/discovery.ts:46 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/cli/src/utils/discovery.ts:83 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/cli/src/utils/cli-version.ts:27 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/engine/src/domain.ts:1307 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/engine/src/domain.ts:1374 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/engine/src/domain.ts:1401 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/engine/src/domain.ts:1636 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/engine/src/executors/saga-executor.ts:168 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/engine/src/executors/saga-executor.ts:201 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/engine/src/executors/command-lifecycle-executor.ts:144 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/engine/src/executors/command-lifecycle-executor.ts:161 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/engine/src/executors/command-lifecycle-executor.ts:174 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/engine/src/executors/command-lifecycle-executor.ts:215 — 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.

D12 · Dependency Hygiene · Deprecated · ×15

Deprecated: eslint packages/adapters/drizzle/REDACTED:97 — eslint 8.56.0, declared in packages/adapters/drizzle/REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/adapters/kafka/REDACTED:66 — eslint 8.56.0, declared in packages/adapters/kafka/REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/adapters/nats/REDACTED:66 — eslint 8.56.0, declared in packages/adapters/nats/REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: nats packages/adapters/nats/REDACTED:67 — nats 2.29.3, declared in packages/adapters/nats/REDACTED, is marked deprecated by its publisher: "Package moved. Use @nats-io/transport-node from https://github.com/nats-io/nats.js". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/adapters/prisma/REDACTED:70 — eslint 8.56.0, declared in packages/adapters/prisma/REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/adapters/rabbitmq/REDACTED:69 — eslint 8.56.0, declared in packages/adapters/rabbitmq/REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/adapters/typeorm/REDACTED:67 — eslint 8.56.0, declared in packages/adapters/typeorm/REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/cli/REDACTED:68 — eslint 8.56.0, declared in packages/cli/REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/core/REDACTED:60 — eslint 8.56.0, declared in packages/core/REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @opentelemetry/sdk-trace-base packages/engine/REDACTED:71 — @opentelemetry/sdk-trace-base 2.6.1, declared in packages/engine/REDACTED, is marked deprecated by its publisher: "Use @opentelemetry/sdk-trace package". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @opentelemetry/sdk-trace-node packages/engine/REDACTED:72 — @opentelemetry/sdk-trace-node 2.6.1, declared in packages/engine/REDACTED, is marked deprecated by its publisher: "Use @opentelemetry/sdk-trace package". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/engine/REDACTED:73 — eslint 8.56.0, declared in packages/engine/REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/integrations/nestjs/REDACTED:69 — eslint 8.56.0, declared in packages/integrations/nestjs/REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/testing-integration/REDACTED:38 — eslint 8.56.0, declared in packages/testing-integration/REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/testing/REDACTED:60 — eslint 8.56.0, declared in packages/testing/REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.

D15 · Churn × Complexity Hotspots · Repeated repair · ×10

Repeated repair: packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts:539 — packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts changed 5 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is RabbitMqEventBus._handleMessage at line 539), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(engine): repair OTelInstrumentation import broken by rename”; “fix(messaging): multi-instance delivery, poison-message handling, default-config safety (#134, #135)”; “fix(rabbitmq): tighten exchangeType detection and stop leaking connections”; “fix(rabbitmq): scope exchangeType mismatch detection to assertExchange”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-01..2026-08-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-01 16:00:59 +02:00' --until='2026-08-30 16:00:59 +02:00' --full-history --no-merges -- packages/adapters/rabbitmq/src/rabbitmq-event-bus.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.
Repeated repair: packages/testing-integration/src/contracts/persistence-contract.ts packages/testing-integration/src/contracts/persistence-contract.ts:87 — packages/testing-integration/src/contracts/persistence-contract.ts changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is persistence-contract.definePersistenceContract at line 87), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(testing-integration): normalize -0 in JSON payload roundtrip property test”; “fix(adapters): fix CI failures from phase 1 GA fixes”; “fix(ci): raise prisma hookTimeout and normalize -0 in fast-check payloads”; “fix(adapters): harden SQL adapter concurrency, schemas, and capability gaps”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-01..2026-08-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-01 16:00:59 +02:00' --until='2026-08-30 16:00:59 +02:00' --full-history --no-merges -- packages/testing-integration/src/contracts/persistence-contract.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.
Repeated repair: packages/adapters/typeorm/src/persistence.ts packages/adapters/typeorm/src/persistence.ts:263 — packages/adapters/typeorm/src/persistence.ts changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is TypeORMSagaPersistence.save at line 263), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: conform Prisma/TypeORM SagaPersistence to the contract, fix shared saga test harness”; “fix(adapters): harden SQL adapter concurrency, schemas, and capability gaps”; “fix(ci): make the test/lint dashboard actually mean something (#140)”; “fix(adapters): resolve robustness bugs #102 #103 #112 #115”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-01..2026-08-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-01 16:00:59 +02:00' --until='2026-08-30 16:00:59 +02:00' --full-history --no-merges -- packages/adapters/typeorm/src/persistence.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.
Repeated repair: packages/adapters/prisma/src/mysql/advisory-locker.ts packages/adapters/prisma/src/mysql/advisory-locker.ts:48 — packages/adapters/prisma/src/mysql/advisory-locker.ts changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is MySQLLocker.acquireDb at line 48), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(adapters): fix CI failures from phase 1 GA fixes”; “fix(ci): make the test/lint dashboard actually mean something (#140)”; “fix(prisma): address second round of PR review feedback”; “fix(adapters): resolve robustness bugs #102 #103 #112 #115”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-01..2026-08-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-01 16:00:59 +02:00' --until='2026-08-30 16:00:59 +02:00' --full-history --no-merges -- packages/adapters/prisma/src/mysql/advisory-locker.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.
Repeated repair: packages/adapters/prisma/src/pg/advisory-locker.ts packages/adapters/prisma/src/pg/advisory-locker.ts:48 — packages/adapters/prisma/src/pg/advisory-locker.ts changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is PostgresLocker.acquireDb at line 48), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(adapters): fix CI failures from phase 1 GA fixes”; “fix(ci): make the test/lint dashboard actually mean something (#140)”; “fix(prisma): address second round of PR review feedback”; “fix(adapters): resolve robustness bugs #102 #103 #112 #115”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-01..2026-08-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-01 16:00:59 +02:00' --until='2026-08-30 16:00:59 +02:00' --full-history --no-merges -- packages/adapters/prisma/src/pg/advisory-locker.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.
Repeated repair: packages/adapters/prisma/src/persistence.ts packages/adapters/prisma/src/persistence.ts:35 — packages/adapters/prisma/src/persistence.ts changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is PrismaEventSourcedAggregatePersistence.save at line 35), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: conform Prisma/TypeORM SagaPersistence to the contract, fix shared saga test harness”; “fix(adapters): harden SQL adapter concurrency, schemas, and capability gaps”; “fix(ci): make the test/lint dashboard actually mean something (#140)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-01..2026-08-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-01 16:00:59 +02:00' --until='2026-08-30 16:00:59 +02:00' --full-history --no-merges -- packages/adapters/prisma/src/persistence.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.
Repeated repair: packages/adapters/drizzle/src/persistence.ts packages/adapters/drizzle/src/persistence.ts:270 — packages/adapters/drizzle/src/persistence.ts changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is DrizzleSagaPersistence.save at line 270), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: conform DrizzleSagaPersistence to the SagaPersistence contract”; “fix(adapters): harden SQL adapter concurrency, schemas, and capability gaps”; “fix(ci): make the test/lint dashboard actually mean something (#140)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-01..2026-08-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-01 16:00:59 +02:00' --until='2026-08-30 16:00:59 +02:00' --full-history --no-merges -- packages/adapters/drizzle/src/persistence.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.
Repeated repair: packages/adapters/drizzle/src/unit-of-work.ts packages/adapters/drizzle/src/unit-of-work.ts:122 — packages/adapters/drizzle/src/unit-of-work.ts changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is DrizzleUnitOfWork.commitWithSqlStatements at line 122), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(adapters): fix CI failures from phase 1 GA fixes”; “fix(adapters): harden SQL adapter concurrency, schemas, and capability gaps”; “fix(ci): make the test/lint dashboard actually mean something (#140)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-01..2026-08-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-01 16:00:59 +02:00' --until='2026-08-30 16:00:59 +02:00' --full-history --no-merges -- packages/adapters/drizzle/src/unit-of-work.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.
Repeated repair: packages/adapters/prisma/src/event-idempotency.ts packages/adapters/prisma/src/event-idempotency.ts:60 — packages/adapters/prisma/src/event-idempotency.ts changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is PrismaEventIdempotencyStore.markProcessed at line 60), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(adapters): harden SQL adapter concurrency, schemas, and capability gaps”; “fix(ci): make the test/lint dashboard actually mean something (#140)”; “fix: address Copilot's three follow-up review findings”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-01..2026-08-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-01 16:00:59 +02:00' --until='2026-08-30 16:00:59 +02:00' --full-history --no-merges -- packages/adapters/prisma/src/event-idempotency.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.
Repeated repair: packages/adapters/prisma/src/advisory-locker.ts packages/adapters/prisma/src/advisory-locker.ts:132 — packages/adapters/prisma/src/advisory-locker.ts changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is PrismaAdvisoryLocker.constructor at line 132), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ci): make the test/lint dashboard actually mean something (#140)”; “fix(prisma): address second round of PR review feedback”; “fix(adapters): resolve robustness bugs #102 #103 #112 #115”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-01..2026-08-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-01 16:00:59 +02:00' --until='2026-08-30 16:00:59 +02:00' --full-history --no-merges -- packages/adapters/prisma/src/advisory-locker.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.

D10 · Test Quality · Fixed-sleep synchronisation · ×6

Fixed-sleep synchronisation: recovers and delivers after a full broker outage mid-consume packages/adapters/nats/src/__tests__/integration/nats.reconnect.integration.test.ts:52 — This test starts work it did not wait for (`bus`, still running when the sleep starts) and then orders itself against it with `sleep(1500)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: recovers from a connection reset injected mid-flow packages/adapters/nats/src/__tests__/integration/nats.reconnect.integration.test.ts:89 — This test starts work it did not wait for (`bus`, still running when the sleep starts) and then orders itself against it with `sleep(500)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: recovers and delivers after a full broker outage mid-consume packages/adapters/rabbitmq/src/__tests__/integration/rabbitmq.reconnect.integration.test.ts:57 — This test starts work it did not wait for (`bus`, still running when the sleep starts) and then orders itself against it with `sleep(1500)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: recovers from a connection reset injected mid-flow packages/adapters/rabbitmq/src/__tests__/integration/rabbitmq.reconnect.integration.test.ts:95 — This test starts work it did not wait for (`bus`, still running when the sleep starts) and then orders itself against it with `sleep(500)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: survives an outage while a handler is still in flight, without a silent ack-loss or a wedged consumer packages/adapters/rabbitmq/src/__tests__/integration/rabbitmq.reconnect.integration.test.ts:129 — This test starts work it did not wait for (`bus`, still running when the sleep starts) and then orders itself against it with `sleep(1500)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: second acquire on same key blocks until first release packages/engine/src/__tests__/engine/implementations/in-memory-aggregate-locker.test.ts:17 — This test starts work it did not wait for (`secondAcquire`, still running when the sleep starts) and then orders itself against it with `new Promise((r) => setTimeout(r, 10))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.

P12 · CI test-gate honesty · Runner config excludes tests no gate runs · ×6

Runner config excludes tests no gate runs packages/adapters/drizzle/vitest.config.mts:12 — `src/__tests__/**/*.integration.test.ts` removes 5 test(s) in 3 file(s) (e.g. `packages/adapters/drizzle/src/__tests__/integration/sqlite.integration.test.ts`, `packages/adapters/drizzle/src/__tests__/integration/postgres.integration.test.ts`) from what vitest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.
Runner config excludes tests no gate runs packages/adapters/kafka/vitest.config.mts:14 — `src/__tests__/**/*.integration.test.ts` removes 6 test(s) in 1 file(s) (e.g. `packages/adapters/kafka/src/__tests__/integration/kafka.integration.test.ts`) from what vitest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.
Runner config excludes tests no gate runs packages/adapters/nats/vitest.config.mts:14 — `src/__tests__/**/*.integration.test.ts` removes 8 test(s) in 2 file(s) (e.g. `packages/adapters/nats/src/__tests__/integration/nats.reconnect.integration.test.ts`, `packages/adapters/nats/src/__tests__/integration/nats.integration.test.ts`) from what vitest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.
Runner config excludes tests no gate runs packages/adapters/prisma/vitest.config.mts:12 — `src/__tests__/**/*.integration.test.ts` removes 3 test(s) in 3 file(s) (e.g. `packages/adapters/prisma/src/__tests__/integration/sqlite.integration.test.ts`, `packages/adapters/prisma/src/__tests__/integration/postgres.integration.test.ts`) from what vitest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.
Runner config excludes tests no gate runs packages/adapters/rabbitmq/vitest.config.mts:14 — `src/__tests__/**/*.integration.test.ts` removes 9 test(s) in 2 file(s) (e.g. `packages/adapters/rabbitmq/src/__tests__/integration/rabbitmq.reconnect.integration.test.ts`, `packages/adapters/rabbitmq/src/__tests__/integration/rabbitmq.integration.test.ts`) from what vitest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.
Runner config excludes tests no gate runs packages/adapters/typeorm/vitest.config.mts:12 — `src/__tests__/**/*.integration.test.ts` removes 4 test(s) in 4 file(s) (e.g. `packages/adapters/typeorm/src/__tests__/integration/sqlite.integration.test.ts`, `packages/adapters/typeorm/src/__tests__/integration/postgres.integration.test.ts`) from what vitest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.

D23 · Boundary Type-Coupling · Cross-context type PersistenceConfiguration (core → engine) · ×5

Cross-context type PersistenceConfiguration (core → engine) packages/engine/src/aggregate-persistence-resolver.ts:19 — PersistenceConfiguration (context core) is exposed in engine's public surface via AggregatePersistenceResolver.resolve — couples the contexts.
Cross-context type PersistenceConfiguration (core → engine) packages/engine/src/aggregate-persistence-resolver.ts:32 — PersistenceConfiguration (context core) is exposed in engine's public surface via GlobalAggregatePersistenceResolver.constructor — couples the contexts.
Cross-context type PersistenceConfiguration (core → engine) packages/engine/src/aggregate-persistence-resolver.ts:34 — PersistenceConfiguration (context core) is exposed in engine's public surface via GlobalAggregatePersistenceResolver.resolve — couples the contexts.
Cross-context type PersistenceConfiguration (core → engine) packages/engine/src/aggregate-persistence-resolver.ts:49 — PersistenceConfiguration (context core) is exposed in engine's public surface via PerAggregatePersistenceResolver.constructor — couples the contexts.
Cross-context type PersistenceConfiguration (core → engine) packages/engine/src/aggregate-persistence-resolver.ts:51 — PersistenceConfiguration (context core) is exposed in engine's public surface via PerAggregatePersistenceResolver.resolve — couples the contexts.

D3 · God Classes · FunctionTooLong · ×5

FunctionTooLong: persistence-contract.definePersistenceContract packages/testing-integration/src/contracts/persistence-contract.ts:87 — FunctionTooLong — definePersistenceContract runs 309 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 209 over it, 3.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: event-bus-contract.defineEventBusContract packages/testing-integration/src/contracts/event-bus-contract.ts:47 — FunctionTooLong — defineEventBusContract runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: unit-of-work-contract.defineUnitOfWorkContract packages/testing-integration/src/contracts/unit-of-work-contract.ts:26 — FunctionTooLong — defineUnitOfWorkContract runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: outbox-contract.defineOutboxContract packages/testing-integration/src/contracts/outbox-contract.ts:22 — FunctionTooLong — defineOutboxContract runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: entities.buildEntities packages/adapters/typeorm/src/entities.ts:201 — FunctionTooLong — buildEntities runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

R10 · Code Duplication · Duplicated block (24 lines × 2 locations) · ×4

Duplicated block (24 lines × 2 locations) packages/adapters/drizzle/src/persistence.ts:167 — packages/adapters/drizzle/src/persistence.ts:167 · packages/adapters/drizzle/src/persistence.ts:262 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (24 lines × 2 locations) packages/adapters/prisma/src/index.ts:47 — packages/adapters/prisma/src/index.ts:47 · packages/adapters/typeorm/src/index.ts:50 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (24 lines × 2 locations) packages/adapters/prisma/src/keyed-mutex.ts:12 — packages/adapters/prisma/src/keyed-mutex.ts:12 · packages/adapters/typeorm/src/keyed-mutex.ts:11 — 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.
Duplicated block (24 lines × 2 locations) packages/cli/src/generators/aggregate.ts:47 — packages/cli/src/generators/aggregate.ts:47 · packages/cli/src/generators/projection.ts:50 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

D15 · Churn × Complexity Hotspots · Hotspot · ×3

Hotspot: packages/engine/src/domain.ts packages/engine/src/domain.ts:443 — packages/engine/src/domain.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 113 in Domain.init at line 443. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-01..2026-08-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-01 16:00:59 +02:00' --until='2026-08-30 16:00:59 +02:00' --full-history --no-merges -- packages/engine/src/domain.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/adapters/kafka/src/kafka-event-bus.ts packages/adapters/kafka/src/kafka-event-bus.ts:683 — packages/adapters/kafka/src/kafka-event-bus.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in KafkaEventBus._handleMessage at line 683. 9 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-01..2026-08-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-01 16:00:59 +02:00' --until='2026-08-30 16:00:59 +02:00' --full-history --no-merges -- packages/adapters/kafka/src/kafka-event-bus.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/engine/src/executors/saga-executor.ts packages/engine/src/executors/saga-executor.ts:55 — packages/engine/src/executors/saga-executor.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in SagaExecutor.execute at line 55. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-01..2026-08-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-01 16:00:59 +02:00' --until='2026-08-30 16:00:59 +02:00' --full-history --no-merges -- packages/engine/src/executors/saga-executor.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.

D23 · Boundary Type-Coupling · Cross-context type ID (core → testing) · ×3

Cross-context type ID (core → testing) packages/testing/src/metadata-helpers.ts:98 — ID (context core) is exposed in testing's public surface via TestMetadataFactoryOptions.userId — couples the contexts.
Cross-context type ID (core → testing) packages/testing/src/metadata-helpers.ts:104 — ID (context core) is exposed in testing's public surface via TestMetadataContext.aggregateId — couples the contexts.
Cross-context type ID (core → testing) packages/testing/src/metadata-helpers.ts:108 — ID (context core) is exposed in testing's public surface via TestMetadataContext.userId — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type ID (core → sample-hotel-booking) · ×3

Cross-context type ID (core → sample-hotel-booking) samples/sample-hotel-booking/src/infrastructure/persistence/drizzle-view-store.ts:44 — ID (context core) is exposed in sample-hotel-booking's public surface via DrizzleViewStore.save — couples the contexts.
Cross-context type ID (core → sample-hotel-booking) samples/sample-hotel-booking/src/infrastructure/persistence/drizzle-view-store.ts:76 — ID (context core) is exposed in sample-hotel-booking's public surface via DrizzleViewStore.load — couples the contexts.
Cross-context type ID (core → sample-hotel-booking) samples/sample-hotel-booking/src/infrastructure/persistence/drizzle-view-store.ts:99 — ID (context core) is exposed in sample-hotel-booking's public surface via DrizzleViewStore.delete — couples the contexts.

D3 · God Classes · MethodTooLong · ×3

MethodTooLong: Domain.init packages/engine/src/domain.ts:443 — MethodTooLong — init runs 462 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 362 over it, 4.62× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SagaExecutor.execute packages/engine/src/executors/saga-executor.ts:55 — MethodTooLong — execute runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CommandLifecycleExecutor.executeLifecycle packages/engine/src/executors/command-lifecycle-executor.ts:229 — MethodTooLong — executeLifecycle runs 137 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

R10 · Code Duplication · Duplicated block (19 lines × 2 locations) · ×3

Duplicated block (19 lines × 2 locations) packages/adapters/drizzle/src/dedicated-state-persistence.ts:85 — packages/adapters/drizzle/src/dedicated-state-persistence.ts:85 · packages/adapters/drizzle/src/persistence.ts:214 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (19 lines × 2 locations) packages/cli/src/generators/domain.ts:171 — packages/cli/src/generators/domain.ts:171 · packages/cli/src/generators/saga.ts:28 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (19 lines × 2 locations) packages/core/src/ddd/domain-definition.ts:17 — packages/core/src/ddd/domain-definition.ts:17 · packages/engine/src/domain.ts:135 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.

R10 · Code Duplication · Duplicated block (17 lines × 2 locations) · ×3

Duplicated block (17 lines × 2 locations) packages/adapters/prisma/src/dedicated-state-persistence.ts:81 — packages/adapters/prisma/src/dedicated-state-persistence.ts:81 · packages/adapters/prisma/src/persistence.ts:166 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (17 lines × 2 locations) packages/cli/src/generators/add-command.ts:45 — packages/cli/src/generators/add-command.ts:45 · packages/cli/src/generators/add-query.ts:34 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (17 lines × 2 locations) packages/testing-integration/src/contracts/persistence-contract.ts:149 — packages/testing-integration/src/contracts/persistence-contract.ts:149 · packages/testing-integration/src/contracts/persistence-contract.ts:168 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R4 · Test Coverage · No test reaches this file · ×3

No test reaches this file REDACTED: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 scripts/check-spec-docs-links.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file scripts/copy-license.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

P8 · Schema migrations · Schema created by TypeORM synchronize · ×2

Schema created by TypeORM synchronize: true (no migration path) samples/sample-flash-sale/src/main-pessimistic.ts:71 — TypeORM synchronize: true builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt TypeORM migrations (`typeorm migration:generate` + `migrationsRun`), so every schema change is a versioned file applied the same way in every environment.
Schema created by TypeORM synchronize: true (no migration path) samples/sample-flash-sale/src/main-optimistic.ts:72 — TypeORM synchronize: true builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt TypeORM migrations (`typeorm migration:generate` + `migrationsRun`), so every schema change is a versioned file applied the same way in every environment.

R10 · Code Duplication · Duplicated block (22 lines × 2 locations) · ×2

Duplicated block (22 lines × 2 locations) packages/adapters/typeorm/src/entities.ts:237 — packages/adapters/typeorm/src/entities.ts:237 · packages/adapters/typeorm/src/entities.ts:270 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (22 lines × 2 locations) packages/cli/src/utils/discovery.ts:22 — packages/cli/src/utils/discovery.ts:22 · packages/cli/src/utils/discovery.ts:59 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block (21 lines × 2 locations) · ×2

Duplicated block (21 lines × 2 locations) packages/adapters/prisma/src/advisory-locker.ts:181 — packages/adapters/prisma/src/advisory-locker.ts:181 · packages/adapters/typeorm/src/advisory-locker.ts:92 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (21 lines × 2 locations) packages/testing-integration/src/contracts/unit-of-work-contract.ts:140 — packages/testing-integration/src/contracts/unit-of-work-contract.ts:140 · packages/testing-integration/src/contracts/unit-of-work-contract.ts:187 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block (18 lines × 2 locations) · ×2

Duplicated block (18 lines × 2 locations) packages/adapters/prisma/src/dedicated-state-persistence.ts:54 — packages/adapters/prisma/src/dedicated-state-persistence.ts:54 · packages/adapters/prisma/src/persistence.ts:57 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (18 lines × 2 locations) packages/adapters/typeorm/src/dedicated-state-persistence.ts:79 — packages/adapters/typeorm/src/dedicated-state-persistence.ts:79 · packages/adapters/typeorm/src/persistence.ts:218 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

AC3 · Page structure · Page without a main landmark · ×1

Page without a main landmark docs/src/app/layout.tsx:59 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.

AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1

Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 17 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

D1 · Cyclomatic Complexity · Domain.init (cyclomatic 113) · ×1

Domain.init (cyclomatic 113) packages/engine/src/domain.ts:443 — Domain.init has cyclomatic complexity 113 (threshold 15). Of this number, 92 points are the body's own statements and 21 belong to 9 function items inside it that branch. 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. This file is where this pass's cyclomatic complexity CONCENTRATES: packages/engine/src/domain.ts holds 2 of the 8 methods over the threshold — including the worst — and 101 of the 130 points over it (78%), 9.2× the next-largest file (packages/engine/src/executors/command-lifecycle-executor.ts at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D1 · Cyclomatic Complexity · SagaExecutor.execute (cyclomatic 23) · ×1

SagaExecutor.execute (cyclomatic 23) packages/engine/src/executors/saga-executor.ts:55 — SagaExecutor.execute has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 5 of the 23 points are its own statements and the rest belongs to 9 function items inside it that branch (runSagaLifecycle::runInSpan, runSagaLifecycle::runInSpan::publish, runSagaLifecycle::runInSpan::runHooksOnce, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · CommandLifecycleExecutor.executeLifecycle (cyclomatic 22) · ×1

CommandLifecycleExecutor.executeLifecycle (cyclomatic 22) packages/engine/src/executors/command-lifecycle-executor.ts:229 — CommandLifecycleExecutor.executeLifecycle has cyclomatic complexity 22 (threshold 15). Of this number, 20 points are the body's own statements and 2 belong to 2 function literals inside it that branch. 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 · projection-rebuild.rebuildProjectionImpl (cyclomatic 20) · ×1

projection-rebuild.rebuildProjectionImpl (cyclomatic 20) packages/engine/src/projection-rebuild.ts:179 — projection-rebuild.rebuildProjectionImpl 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 · KafkaEventBus._handleMessage (cyclomatic 19) · ×1

KafkaEventBus._handleMessage (cyclomatic 19) packages/adapters/kafka/src/kafka-event-bus.ts:683 — KafkaEventBus._handleMessage has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · CommandLifecycleExecutor.execute (cyclomatic 19) · ×1

CommandLifecycleExecutor.execute (cyclomatic 19) packages/engine/src/executors/command-lifecycle-executor.ts:71 — CommandLifecycleExecutor.execute has cyclomatic complexity 19 (threshold 15). Of this number, 15 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.

D1 · Cyclomatic Complexity · Domain.rebuildProjection (cyclomatic 18) · ×1

Domain.rebuildProjection (cyclomatic 18) packages/engine/src/domain.ts:1594 — Domain.rebuildProjection has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: packages/engine/src/domain.ts holds 2 of the 8 methods over the threshold — including the worst — and 101 of the 130 points over it (78%), 9.2× the next-largest file (packages/engine/src/executors/command-lifecycle-executor.ts at 11). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D1 · Cyclomatic Complexity · build-graph.buildDomainGraph (cyclomatic 16) · ×1

build-graph.buildDomainGraph (cyclomatic 16) packages/cli/src/diagram/build-graph.ts:25 — build-graph.buildDomainGraph has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D2 · Cognitive Complexity · Domain.init (cognitive 228) · ×1

Domain.init (cognitive 228) packages/engine/src/domain.ts:443 — Domain.init has cognitive complexity 228 (threshold 15). Drivers by points: if/else 82 (155 pts), loops 25 (51 pts), ternaries 6 (12 pts), boolean chains 10 (nesting depth added 105). Of this number, 179 points are the body's own statements and 49 belong to 9 function items inside it that branch. 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. This file is where this pass's cognitive complexity CONCENTRATES: packages/engine/src/domain.ts holds 3 of the 16 methods over the threshold — including the worst — and 223 of the 337 points over it (66%), 6.4× the next-largest file (packages/engine/src/executors/command-lifecycle-executor.ts at 35). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · CommandLifecycleExecutor.execute (cognitive 36) · ×1

CommandLifecycleExecutor.execute (cognitive 36) packages/engine/src/executors/command-lifecycle-executor.ts:71 — CommandLifecycleExecutor.execute has cognitive complexity 36 (threshold 15). Drivers by points: error handling 5 (14 pts), if/else 9 (14 pts), boolean chains 4, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 16). Of this number, 26 points are the body's own statements and 10 belong to 2 function literals inside it that branch. 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 · SagaExecutor.execute (cognitive 34) · ×1

SagaExecutor.execute (cognitive 34) packages/engine/src/executors/saga-executor.ts:55 — SagaExecutor.execute has cognitive complexity 34 (threshold 15). Drivers by points: if/else 14 (16 pts), error handling 5 (8 pts), ternaries 5 (7 pts), loops 2, boolean chains 1 (nesting depth added 7). Most of this is not in the body itself: 8 of the 34 points are its own statements and the rest belongs to 9 function items inside it that branch (runSagaLifecycle::runInSpan, runSagaLifecycle::runInSpan::publish, runSagaLifecycle::runInSpan::runHooksOnce, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · CommandLifecycleExecutor.executeLifecycle (cognitive 29) · ×1

CommandLifecycleExecutor.executeLifecycle (cognitive 29) packages/engine/src/executors/command-lifecycle-executor.ts:229 — CommandLifecycleExecutor.executeLifecycle has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (19 pts), ternaries 4 (7 pts), boolean chains 2, loops 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 · projection-rebuild.rebuildProjectionImpl (cognitive 29) · ×1

projection-rebuild.rebuildProjectionImpl (cognitive 29) packages/engine/src/projection-rebuild.ts:179 — projection-rebuild.rebuildProjectionImpl has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 3 (6 pts), loops 3 (5 pts), boolean chains 3, error handling 1 (nesting depth added 10). 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 · KafkaEventBus._handleMessage (cognitive 25) · ×1

KafkaEventBus._handleMessage (cognitive 25) packages/adapters/kafka/src/kafka-event-bus.ts:683 — KafkaEventBus._handleMessage has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 3 (7 pts), boolean chains 5, error handling 2, loops 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 · RabbitMqEventBus._connectWithRetry (cognitive 23) · ×1

RabbitMqEventBus._connectWithRetry (cognitive 23) packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts:225 — RabbitMqEventBus._connectWithRetry has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (16 pts), error handling 2 (4 pts), loops 2 (3 pts) (nesting depth added 13). Of this number, 19 points are the body's own statements and 4 belong to 2 function literals inside it that branch. 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 · Domain.rebuildProjection (cognitive 23) · ×1

Domain.rebuildProjection (cognitive 23) packages/engine/src/domain.ts:1594 — Domain.rebuildProjection has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 3, error handling 1 (3 pts), loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition. This file is where this pass's cognitive complexity CONCENTRATES: packages/engine/src/domain.ts holds 3 of the 16 methods over the threshold — including the worst — and 223 of the 337 points over it (66%), 6.4× the next-largest file (packages/engine/src/executors/command-lifecycle-executor.ts at 35). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · NatsEventBus._consumeSubscription (cognitive 21) · ×1

NatsEventBus._consumeSubscription (cognitive 21) packages/adapters/nats/src/nats-event-bus.ts:414 — NatsEventBus._consumeSubscription has cognitive complexity 21 (threshold 15). Drivers by points: error handling 6 (16 pts), if/else 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 12). 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 · build-graph.buildDomainGraph (cognitive 21) · ×1

build-graph.buildDomainGraph (cognitive 21) packages/cli/src/diagram/build-graph.ts:25 — build-graph.buildDomainGraph has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 3 (5 pts), boolean chains 4 (nesting depth added 5). 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 · introspect.introspectDomain (cognitive 20) · ×1

introspect.introspectDomain (cognitive 20) packages/cli/src/diagram/introspect.ts:23 — introspect.introspectDomain has cognitive complexity 20 (threshold 15). Drivers by points: loops 8 (13 pts), if/else 4 (7 pts) (nesting depth added 8). Of this number, 19 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · static-analyze.collectNameLiterals (cognitive 20) · ×1

static-analyze.collectNameLiterals (cognitive 20) packages/cli/src/diagram/static-analyze.ts:188 — static-analyze.collectNameLiterals has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 2 (4 pts), ternaries 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · RabbitMqEventBus._handleMessage (cognitive 18) · ×1

RabbitMqEventBus._handleMessage (cognitive 18) packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts:539 — RabbitMqEventBus._handleMessage has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (6 pts), ternaries 2 (6 pts), boolean chains 4, error handling 1, loops 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 · NatsEventBus._handleMessage (cognitive 17) · ×1

NatsEventBus._handleMessage (cognitive 17) packages/adapters/nats/src/nats-event-bus.ts:228 — NatsEventBus._handleMessage has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (6 pts), ternaries 2 (6 pts), boolean chains 4, loops 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 · domain.resolveAggregatePersistence (cognitive 17) · ×1

domain.resolveAggregatePersistence (cognitive 17) packages/engine/src/domain.ts:184 — domain.resolveAggregatePersistence has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (17 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. This file is where this pass's cognitive complexity CONCENTRATES: packages/engine/src/domain.ts holds 3 of the 16 methods over the threshold — including the worst — and 223 of the 337 points over it (66%), 6.4× the next-largest file (packages/engine/src/executors/command-lifecycle-executor.ts at 35). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · static-analyze.analyzeSagaCommands (cognitive 16) · ×1

static-analyze.analyzeSagaCommands (cognitive 16) packages/cli/src/diagram/static-analyze.ts:24 — static-analyze.analyzeSagaCommands has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), loops 4 (7 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D22 · Internal API Consistency · Duplicate intent with different naming and parameter types. Both interfaces check for the existence of a processed key/command. One uses 'hasProcessed' with a string key, the other uses 'exists' with an ID type. · ×1

Duplicate intent with different naming and parameter types. Both interfaces check for the existence of a processed key/command. One uses 'hasProcessed' with a string key, the other uses 'exists' with an ID type. — Unify to a single interface (e.g., IdempotencyStore) with consistent method names like 'exists' or 'hasProcessed' and a unified key type (ID or string). (signatures: EventIdempotencyStore.hasProcessed(key: string): Promise<boolean> | IdempotencyStore.exists(commandId: ID): Promise<boolean>)

D22 · Internal API Consistency · Duplicate intent with different signatures. Both mark an item as processed. One takes a simple key string, the other takes a full record object. · ×1

Duplicate intent with different signatures. Both mark an item as processed. One takes a simple key string, the other takes a full record object. — Unify to a single interface. If the record contains more data, use 'save' or 'markProcessed' with the record. If only the key matters, use 'markProcessed' with the key. (signatures: EventIdempotencyStore.markProcessed(key: string): Promise<void> | IdempotencyStore.save(record: IdempotencyRecord): Promise<void>)

D22 · Internal API Consistency · Duplicate intent. Both interfaces define the same method for cleaning up expired entries. · ×1

Duplicate intent. Both interfaces define the same method for cleaning up expired entries. — Unify into a single IdempotencyStore interface. (signatures: EventIdempotencyStore.removeExpired(ttlMs: number): Promise<void> | IdempotencyStore.removeExpired(ttlMs: number): Promise<void>)

D23 · Boundary Type-Coupling · Cross-context type LogLevel (core → engine) · ×1

Cross-context type LogLevel (core → engine) packages/engine/src/logger.ts:97 — LogLevel (context core) is exposed in engine's public surface via NodddeLogger.constructor — couples the contexts.

D3 · God Classes · FileTooLong · ×1

FileTooLong: src/domain.ts packages/engine/src/domain.ts — FileTooLong — 1027 significant lines (blank, comment-only and punctuation-only lines excluded), about 71% of them inside a single declaration: Domain (380-1689). The bar is 500 significant lines; this is 527 over it, 2.05× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.

D3 · God Classes · ClassTooLong · ×1

ClassTooLong: Domain packages/engine/src/domain.ts:380 — ClassTooLong — 730 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 330 over it, 1.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D35 · Change Coupling · Change coupling · ×1

Change coupling: command-lifecycle-executor.ts ↔ saga-executor.ts packages/engine/src/executors/command-lifecycle-executor.ts:1 — `packages/engine/src/executors/command-lifecycle-executor.ts` and `packages/engine/src/executors/saga-executor.ts` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `fc9acb31` fix(engine): repair OTelInstrumentation import broken by rename; `9fc88a78` feat(engine): add noddde.uow.commit span for UoW commit latency; `3dac7e8f` feat(engine): add framework logging with configurable levels — run `git show` on any of them.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing REDACTED · ×1

REDACTED

D5 · Coupling · Off the main sequence · ×1

Off the main sequence: @noddde/engine — @noddde/engine: abstractness 0.07, instability 0.14, distance 0.79 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.

M1 · Documentation (README) · README may be stale · ×1

README may be stale — 189 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.

P12 · CI test-gate honesty · Coverage collected but not gated · ×1

Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.

PF3 · Async & latency hygiene · Sync-over-async blocking · ×1

Sync-over-async blocking packages/cli/src/commands/diagram.ts:81 — `fs.writeFileSync` in `callback to action` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.

R10 · Code Duplication · Duplication concentrated across 6 sibling directories (38 clone groups) · ×1

Duplication concentrated across 6 sibling directories (38 clone groups) packages/adapters/prisma/src/persistence.ts:47 — 38 duplicated blocks under packages/adapters/ have copies in at least two of the sibling directories drizzle, kafka, nats, prisma, rabbitmq, typeorm — 26 of them are reported below, and 12 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 38 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 38 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 38 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 · Duplication concentrated across 6 sibling directories (7 clone groups) · ×1

Duplication concentrated across 6 sibling directories (7 clone groups) packages/core/src/ddd/domain-definition.ts:17 — 7 duplicated blocks under packages/ have copies in at least two of the sibling directories adapters, cli, core, engine, integrations, testing — 4 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 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 · Duplication concentrated across 3 sibling directories (5 clone groups) · ×1

Duplication concentrated across 3 sibling directories (5 clone groups) packages/adapters/drizzle/src/pg/schema.ts:29 — 5 of the duplicated blocks reported below have copies in at least two of the sibling directories mysql, pg, sqlite under packages/adapters/drizzle/src/. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplicated block with local edits (231 matched lines × 2 locations) · ×1

Duplicated block with local edits (231 matched lines × 2 locations) packages/adapters/prisma/src/persistence.ts:47 — packages/adapters/prisma/src/persistence.ts:47 · packages/adapters/typeorm/src/persistence.ts:90 — the two spans are one implementation copied and then locally edited — 1313 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (90 matched lines × 2 locations) · ×1

Duplicated block with local edits (90 matched lines × 2 locations) packages/cli/src/generators/domain.ts:60 — packages/cli/src/generators/domain.ts:60 · packages/cli/src/generators/project.ts:65 — the two spans are one implementation copied and then locally edited — 416 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (86 matched lines × 2 locations) · ×1

Duplicated block with local edits (86 matched lines × 2 locations) packages/adapters/prisma/src/builder.ts:59 — packages/adapters/prisma/src/builder.ts:59 · packages/adapters/typeorm/src/builder.ts:59 — the two spans are one implementation copied and then locally edited — 436 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (68 matched lines × 2 locations) · ×1

Duplicated block with local edits (68 matched lines × 2 locations) packages/adapters/prisma/src/mysql/advisory-locker.ts:20 — packages/adapters/prisma/src/mysql/advisory-locker.ts:20 · packages/adapters/prisma/src/pg/advisory-locker.ts:20 — the two spans are one implementation copied and then locally edited — 371 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block (60 lines × 2 locations) · ×1

Duplicated block (60 lines × 2 locations) packages/adapters/prisma/src/unit-of-work.ts:14 — packages/adapters/prisma/src/unit-of-work.ts:14 · packages/adapters/typeorm/src/unit-of-work.ts:15 — 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 · Duplicated block (55 lines × 2 locations) · ×1

Duplicated block (55 lines × 2 locations) packages/adapters/drizzle/src/pg/schema.ts:29 — packages/adapters/drizzle/src/pg/schema.ts:29 · packages/adapters/drizzle/src/sqlite/schema.ts:24 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.

R10 · Code Duplication · Duplicated block with local edits (55 matched lines × 2 locations) · ×1

Duplicated block with local edits (55 matched lines × 2 locations) packages/adapters/typeorm/src/mysql/advisory-locker.ts:16 — packages/adapters/typeorm/src/mysql/advisory-locker.ts:16 · packages/adapters/typeorm/src/pg/advisory-locker.ts:16 — the two spans are one implementation copied and then locally edited — 294 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block (48 lines × 2 locations) · ×1

Duplicated block (48 lines × 2 locations) packages/adapters/drizzle/src/mysql/advisory-locker.ts:17 — packages/adapters/drizzle/src/mysql/advisory-locker.ts:17 · packages/adapters/drizzle/src/pg/advisory-locker.ts:19 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block with local edits (45 matched lines × 2 locations) · ×1

Duplicated block with local edits (45 matched lines × 2 locations) packages/testing-integration/src/contracts/saga-contract.ts:5 — packages/testing-integration/src/contracts/saga-contract.ts:5 · packages/testing-integration/src/contracts/snapshot-contract.ts:4 — the two spans are one implementation copied and then locally edited — 286 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block (42 lines × 2 locations) · ×1

Duplicated block (42 lines × 2 locations) packages/integrations/nestjs/src/noddde.module.ts:180 — packages/integrations/nestjs/src/noddde.module.ts:180 · packages/integrations/nestjs/src/noddde.module.ts:240 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block (39 lines × 2 locations) · ×1

Duplicated block (39 lines × 2 locations) packages/adapters/kafka/src/kafka-event-bus.ts:716 — packages/adapters/kafka/src/kafka-event-bus.ts:716 · packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts:554 — 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 · Duplicated block (34 lines × 2 locations) · ×1

Duplicated block (34 lines × 2 locations) packages/testing-integration/src/containers/mysql.ts:8 — packages/testing-integration/src/containers/mysql.ts:8 · packages/testing-integration/src/containers/postgres.ts:7 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.

R10 · Code Duplication · Duplicated block (33 lines × 2 locations) · ×1

Duplicated block (33 lines × 2 locations) packages/cli/src/utils/discovery.ts:96 — packages/cli/src/utils/discovery.ts:96 · packages/cli/src/utils/discovery.ts:135 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

R10 · Code Duplication · Duplicated block (31 lines × 2 locations) · ×1

Duplicated block (31 lines × 2 locations) packages/adapters/prisma/src/persistence.ts:123 — packages/adapters/prisma/src/persistence.ts:123 · packages/adapters/prisma/src/persistence.ts:201 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block (27 lines × 2 locations) · ×1

Duplicated block (27 lines × 2 locations) packages/adapters/drizzle/src/builder.ts:243 — packages/adapters/drizzle/src/builder.ts:243 · packages/adapters/typeorm/src/builder.ts:191 — 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 · Duplicated block with local edits (27 matched lines × 2 locations) · ×1

Duplicated block with local edits (27 matched lines × 2 locations) packages/cli/src/generators/add-command.ts:67 — packages/cli/src/generators/add-command.ts:67 · packages/cli/src/generators/add-query.ts:52 — the two spans are one implementation copied and then locally edited — 198 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block (23 lines × 2 locations) · ×1

Duplicated block (23 lines × 2 locations) packages/adapters/prisma/src/persistence.ts:175 — packages/adapters/prisma/src/persistence.ts:175 · packages/adapters/prisma/src/persistence.ts:239 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block (22 lines × 3 locations) · ×1

Duplicated block (22 lines × 3 locations) packages/adapters/drizzle/src/mysql/schema.ts:69 — packages/adapters/drizzle/src/mysql/schema.ts:69 · packages/adapters/drizzle/src/pg/schema.ts:70 · packages/adapters/drizzle/src/sqlite/schema.ts:62 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.

R10 · Code Duplication · Duplicated block with local edits (19 matched lines × 2 locations) · ×1

Duplicated block with local edits (19 matched lines × 2 locations) packages/adapters/nats/src/nats-event-bus.ts:244 — packages/adapters/nats/src/nats-event-bus.ts:244 · packages/engine/src/implementations/ee-event-bus.ts:109 — the two spans are one implementation copied and then locally edited — 137 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block (19 lines × 3 locations) · ×1

Duplicated block (19 lines × 3 locations) packages/cli/src/generators/add-query.ts:48 — packages/cli/src/generators/add-query.ts:48 · packages/cli/src/generators/aggregate.ts:51 · packages/cli/src/generators/projection.ts:54 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block (16 lines × 3 locations) · ×1

Duplicated block (16 lines × 3 locations) packages/adapters/drizzle/src/advisory-locker.ts:129 — packages/adapters/drizzle/src/advisory-locker.ts:129 · packages/adapters/prisma/src/advisory-locker.ts:182 · packages/adapters/typeorm/src/advisory-locker.ts:93 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R2 · Cyclomatic Complexity · Complex function init (cyclomatic 94, cognitive 183) · ×1

Complex function init (cyclomatic 94, cognitive 183) packages/engine/src/domain.ts:443 — init has cyclomatic complexity 94 and cognitive complexity 183; 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 executeLifecycle (cyclomatic 23, cognitive 32) · ×1

Complex function executeLifecycle (cyclomatic 23, cognitive 32) packages/engine/src/executors/command-lifecycle-executor.ts:229 — executeLifecycle has cyclomatic complexity 23 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function _handleMessage (cyclomatic 23, cognitive 31) · ×1

Complex function _handleMessage (cyclomatic 23, cognitive 31) packages/adapters/kafka/src/kafka-event-bus.ts:683 — _handleMessage has cyclomatic complexity 23 and cognitive complexity 31; 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 rebuildProjectionImpl (cyclomatic 22, cognitive 31) · ×1

Complex function rebuildProjectionImpl (cyclomatic 22, cognitive 31) packages/engine/src/projection-rebuild.ts:179 — rebuildProjectionImpl has cyclomatic complexity 22 and cognitive complexity 31; 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 introspectDomain (cyclomatic 21, cognitive 28) · ×1

Complex function introspectDomain (cyclomatic 21, cognitive 28) packages/cli/src/diagram/introspect.ts:23 — introspectDomain has cyclomatic complexity 21 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function rebuildProjection (cyclomatic 19, cognitive 24) · ×1

Complex function rebuildProjection (cyclomatic 19, cognitive 24) packages/engine/src/domain.ts:1594 — rebuildProjection has cyclomatic complexity 19 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 buildDomainGraph (cyclomatic 18, cognitive 23) · ×1

Complex function buildDomainGraph (cyclomatic 18, cognitive 23) packages/cli/src/diagram/build-graph.ts:25 — buildDomainGraph has cyclomatic complexity 18 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function execute (cyclomatic 15, cognitive 26) · ×1

Complex function execute (cyclomatic 15, cognitive 26) packages/engine/src/executors/command-lifecycle-executor.ts:71 — execute has cyclomatic complexity 15 and cognitive complexity 26; 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 save (cyclomatic 15, cognitive 13) · ×1

Complex function save (cyclomatic 15, cognitive 13) packages/adapters/drizzle/src/persistence.ts:270 — save has cyclomatic complexity 15 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function _handleMessage (cyclomatic 14, cognitive 19) · ×1

Complex function _handleMessage (cyclomatic 14, cognitive 19) packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts:539 — _handleMessage has cyclomatic complexity 14 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function _connectWithRetry (cyclomatic 13, cognitive 26) · ×1

Complex function _connectWithRetry (cyclomatic 13, cognitive 26) packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts:225 — _connectWithRetry has cyclomatic complexity 13 and cognitive complexity 26; 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 _handleMessage (cyclomatic 13, cognitive 18) · ×1

Complex function _handleMessage (cyclomatic 13, cognitive 18) packages/adapters/nats/src/nats-event-bus.ts:228 — _handleMessage has cyclomatic complexity 13 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 analyzeSagaCommands (cyclomatic 12, cognitive 17) · ×1

Complex function analyzeSagaCommands (cyclomatic 12, cognitive 17) packages/cli/src/diagram/static-analyze.ts:24 — analyzeSagaCommands has cyclomatic complexity 12 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 _consumeSubscription (cyclomatic 11, cognitive 22) · ×1

Complex function _consumeSubscription (cyclomatic 11, cognitive 22) packages/adapters/nats/src/nats-event-bus.ts:414 — _consumeSubscription has cyclomatic complexity 11 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function collectNameLiterals (cyclomatic 11, cognitive 21) · ×1

Complex function collectNameLiterals (cyclomatic 11, cognitive 21) packages/cli/src/diagram/static-analyze.ts:188 — collectNameLiterals has cyclomatic complexity 11 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 dispatch (cyclomatic 11, cognitive 14) · ×1

Complex function dispatch (cyclomatic 11, cognitive 14) packages/engine/src/implementations/ee-event-bus.ts:98 — dispatch has cyclomatic complexity 11 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R3 · Large Files · packages/engine/src/domain.ts · ×1

packages/engine/src/domain.ts: 1741 lines of code packages/engine/src/domain.ts:1 — packages/engine/src/domain.ts has 1741 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/adapters/kafka/src/kafka-event-bus.ts · ×1

packages/adapters/kafka/src/kafka-event-bus.ts: 810 lines of code packages/adapters/kafka/src/kafka-event-bus.ts:1 — packages/adapters/kafka/src/kafka-event-bus.ts has 810 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/adapters/rabbitmq/src/rabbitmq-event-bus.ts · ×1

packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts: 717 lines of code packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts:1 — packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts has 717 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/testing-integration/src/contracts/persistence-contract.ts · ×1

packages/testing-integration/src/contracts/persistence-contract.ts: 536 lines of code packages/testing-integration/src/contracts/persistence-contract.ts:1 — packages/testing-integration/src/contracts/persistence-contract.ts has 536 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/adapters/drizzle/src/persistence.ts · ×1

packages/adapters/drizzle/src/persistence.ts: 477 lines of code packages/adapters/drizzle/src/persistence.ts:1 — packages/adapters/drizzle/src/persistence.ts has 477 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/adapters/nats/src/nats-event-bus.ts · ×1

packages/adapters/nats/src/nats-event-bus.ts: 449 lines of code packages/adapters/nats/src/nats-event-bus.ts:1 — packages/adapters/nats/src/nats-event-bus.ts has 449 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/adapters/typeorm/src/persistence.ts · ×1

packages/adapters/typeorm/src/persistence.ts: 423 lines of code packages/adapters/typeorm/src/persistence.ts:1 — packages/adapters/typeorm/src/persistence.ts has 423 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R8 · Dependency Hygiene · Unlisted import 'eslint' · ×1

Unlisted import 'eslint' packages/eslint-config/library.js:5 — Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.

R8 · Dependency Hygiene · Unused dependency 'mssql' · ×1

Unused dependency 'mssql' — Declared in packages/adapters/typeorm/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

R8 · Dependency Hygiene · Unused dependency '@vercel/style-guide' · ×1

Unused dependency '@vercel/style-guide' — Declared in packages/eslint-config/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

R8 · Dependency Hygiene · Unused dependency '@nestjs/platform-express' · ×1

Unused dependency '@nestjs/platform-express' — Declared in packages/integrations/nestjs/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

S1 · Web-Security Posture · Third-party script without Subresource Integrity · ×1

Third-party script without Subresource Integrity docs/src/app/layout.tsx:81 — `https://cloud.umami.is/script.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository.

Minor — 347 finding(s)

D10 · Test Quality · No direct assertions · ×248

No direct assertions: should accept string packages/core/src/__tests__/id.test.ts:5 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should accept number packages/core/src/__tests__/id.test.ts:9 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should accept bigint packages/core/src/__tests__/id.test.ts:13 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should not accept boolean packages/core/src/__tests__/id.test.ts:19 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should not accept symbol packages/core/src/__tests__/id.test.ts:23 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should not accept object packages/core/src/__tests__/id.test.ts:27 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should accept branded string packages/core/src/__tests__/id.test.ts:36 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should accept branded number packages/core/src/__tests__/id.test.ts:40 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should accept a basic query object packages/core/src/__tests__/cqrs/query.test.ts:7 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should accept query with payload packages/core/src/__tests__/cqrs/query.test.ts:12 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should extract the result type from Query packages/core/src/__tests__/cqrs/query.test.ts:23 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should work with complex result types packages/core/src/__tests__/cqrs/query.test.ts:28 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should return any for Query<any> packages/core/src/__tests__/cqrs/query.test.ts:38 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should produce members with payload when specified packages/core/src/__tests__/cqrs/query.test.ts:55 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should produce members without explicit payload when omitted packages/core/src/__tests__/cqrs/query.test.ts:61 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should allow QueryResult to extract the result type packages/core/src/__tests__/cqrs/query.test.ts:66 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should allow QueryResult on the no-payload member packages/core/src/__tests__/cqrs/query.test.ts:71 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should not have an explicit payload property in the intersected type packages/core/src/__tests__/cqrs/query.test.ts:83 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should produce never packages/core/src/__tests__/cqrs/query.test.ts:93 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should receive query payload as first parameter packages/core/src/__tests__/cqrs/query-handler.test.ts:27 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should receive infrastructure as second parameter packages/core/src/__tests__/cqrs/query-handler.test.ts:31 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should return the query result type or a promise of it packages/core/src/__tests__/cqrs/query-handler.test.ts:35 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should not have commandBus in infrastructure packages/core/src/__tests__/cqrs/query-handler.test.ts:63 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should return typed result for a specific query packages/core/src/__tests__/cqrs/query-bus.test.ts:22 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should return array type for list queries packages/core/src/__tests__/cqrs/query-bus.test.ts:29 — No conventional assertion call was detected, and 248 of 351 tests in `packages/core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
+ 223 more in this group — see findings.md.

M4 · Documentation accuracy · README/code drift · ×40

README/code drift specs/README.md:199 — specs/README.md names `packages/docs/content/docs/`, but no file or folder `packages/docs/content/docs` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/index.mdx:14 — docs/content/docs/index.mdx links to `/docs/getting-started/why-noddde`, but `docs/getting-started/why-noddde` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/index.mdx:15 — docs/content/docs/index.mdx links to `/docs/getting-started/quick-start`, but `docs/getting-started/quick-start` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/index.mdx:16 — docs/content/docs/index.mdx links to `/docs/core-concepts/messages-and-types`, but `docs/core-concepts/messages-and-types` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/index.mdx:24 — docs/content/docs/index.mdx links to `/docs/modeling/defining-aggregates`, but `docs/modeling/defining-aggregates` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/index.mdx:25 — docs/content/docs/index.mdx links to `/docs/running/domain-configuration`, but `docs/running/domain-configuration` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/index.mdx:26 — docs/content/docs/index.mdx links to `/docs/running/persistence-adapters`, but `docs/running/persistence-adapters` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/index.mdx:27 — docs/content/docs/index.mdx links to `/docs/design-decisions/why-decider`, but `docs/design-decisions/why-decider` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/cqrs-and-event-sourcing.mdx:32 — docs/content/docs/core-concepts/cqrs-and-event-sourcing.mdx links to `/docs/process-managers/sagas`, but `docs/process-managers/sagas` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/cqrs-and-event-sourcing.mdx:62 — docs/content/docs/core-concepts/cqrs-and-event-sourcing.mdx links to `/docs/modeling/defining-aggregates`, but `docs/modeling/defining-aggregates` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/cqrs-and-event-sourcing.mdx:90 — docs/content/docs/core-concepts/cqrs-and-event-sourcing.mdx links to `/docs/read-model/projections`, but `docs/read-model/projections` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/cqrs-and-event-sourcing.mdx:334 — docs/content/docs/core-concepts/cqrs-and-event-sourcing.mdx links to `/docs/running/domain-configuration`, but `docs/running/domain-configuration` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/decider-pattern.mdx:335 — docs/content/docs/core-concepts/decider-pattern.mdx links to `/docs/modeling/defining-aggregates`, but `docs/modeling/defining-aggregates` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/decider-pattern.mdx:336 — docs/content/docs/core-concepts/decider-pattern.mdx links to `/docs/design-decisions/why-decider`, but `docs/design-decisions/why-decider` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/decider-pattern.mdx:337 — docs/content/docs/core-concepts/decider-pattern.mdx links to `/docs/running/infrastructure`, but `docs/running/infrastructure` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/messages-and-types.mdx:42 — docs/content/docs/core-concepts/messages-and-types.mdx links to `/docs/running/idempotent-commands`, but `docs/running/idempotent-commands` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/messages-and-types.mdx:625 — docs/content/docs/core-concepts/messages-and-types.mdx links to `/docs/getting-started/quick-start`, but `docs/getting-started/quick-start` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/messages-and-types.mdx:626 — docs/content/docs/core-concepts/messages-and-types.mdx links to `/docs/modeling/defining-aggregates`, but `docs/modeling/defining-aggregates` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/messages-and-types.mdx:627 — docs/content/docs/core-concepts/messages-and-types.mdx links to `/docs/core-concepts/decider-pattern`, but `docs/core-concepts/decider-pattern` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/messages-and-types.mdx:628 — docs/content/docs/core-concepts/messages-and-types.mdx links to `/docs/design-decisions/why-aggregate-types`, but `docs/design-decisions/why-aggregate-types` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/core-concepts/messages-and-types.mdx:629 — docs/content/docs/core-concepts/messages-and-types.mdx links to `/docs/design-decisions/why-define-commands-events`, but `docs/design-decisions/why-define-commands-events` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/design-decisions/why-decider.mdx:12 — docs/content/docs/design-decisions/why-decider.mdx links to `/docs/core-concepts/decider-pattern#decider-vs-oop-aggregates`, but `docs/core-concepts/decider-pattern` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/design-decisions/why-injectable-infrastructure.mdx:106 — docs/content/docs/design-decisions/why-injectable-infrastructure.mdx links to `/docs/running/infrastructure`, but `docs/running/infrastructure` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/design-decisions/why-sagas-return-commands.mdx:64 — docs/content/docs/design-decisions/why-sagas-return-commands.mdx links to `/docs/process-managers/sagas#atomicity`, but `docs/process-managers/sagas` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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/content/docs/design-decisions/why-two-persistence-strategies.mdx:74 — docs/content/docs/design-decisions/why-two-persistence-strategies.mdx links to `/docs/running/persistence#decision-matrix`, but `docs/running/persistence` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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.
+ 15 more in this group — see findings.md.

D10 · Test Quality · Mock-dominated test · ×28

Mock-dominated test: should explicitly commit offsets after handling packages/adapters/kafka/src/__tests__/kafka-event-bus.test.ts:451 — This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should use provided logger for warn logging with structured data packages/adapters/kafka/src/__tests__/kafka-event-bus.test.ts:697 — This test sets up 6 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should publish event to subject derived from event name packages/adapters/nats/src/__tests__/nats-event-bus.test.ts:6 — This test sets up 5 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should set maxDeliver on consumer options when resilience.maxRetries is configured packages/adapters/nats/src/__tests__/nats-event-bus.test.ts:213 — This test sets up 10 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should term a poison message (malformed JSON) and continue packages/adapters/nats/src/__tests__/nats-event-bus.test.ts:254 — This test sets up 4 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should ack message when all handlers succeed packages/adapters/nats/src/__tests__/nats-event-bus.test.ts:314 — This test sets up 4 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should use consumerGroup as prefix in durable consumer name packages/adapters/nats/src/__tests__/nats-event-bus.test.ts:477 — This test sets up 9 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should use provided logger for error and warn logging with structured data packages/adapters/nats/src/__tests__/nats-event-bus.test.ts:596 — This test sets up 9 test doubles (for example `vi.fn`) against 3 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should call msg.nak() when any handler fails (existing redelivery behavior is preserved) packages/adapters/nats/src/__tests__/nats-event-bus.test.ts:713 — This test sets up 4 test doubles (for example `vi.fn`) against 3 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should set deliverGroup to the durable name so replicas compete for messages packages/adapters/nats/src/__tests__/nats-event-bus.test.ts:749 — This test sets up 9 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should not resubscribe when a second handler is registered for an already-subscribed event packages/adapters/nats/src/__tests__/nats-event-bus.test.ts:784 — This test sets up 10 test doubles (for example `vi.fn`) against 3 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should publish to the DLQ subject and term when delivery count reaches maxRetries packages/adapters/nats/src/__tests__/nats-event-bus.test.ts:869 — This test sets up 4 test doubles (for example `vi.fn`) against 3 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: dedicated persistence participates in UoW transaction via shared txStore packages/adapters/prisma/src/__tests__/prisma.test.ts:707 — This test sets up 8 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: warns via the provided logger about session affinity packages/adapters/prisma/src/__tests__/advisory-locker.test.ts:81 — This test sets up 5 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should publish event to exchange with event name as routing key packages/adapters/rabbitmq/src/__tests__/rabbitmq-event-bus.test.ts:12 — This test sets up 11 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should call channel.prefetch with configured prefetchCount packages/adapters/rabbitmq/src/__tests__/rabbitmq-event-bus.test.ts:146 — This test sets up 8 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should use createConfirmChannel instead of createChannel packages/adapters/rabbitmq/src/__tests__/rabbitmq-event-bus.test.ts:447 — This test sets up 9 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should call waitForConfirms after publish in dispatch packages/adapters/rabbitmq/src/__tests__/rabbitmq-event-bus.test.ts:477 — This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should register error and close handlers on connection after connect packages/adapters/rabbitmq/src/__tests__/rabbitmq-event-bus.test.ts:521 — This test sets up 8 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should track delivery count in memory and discard after maxRetries packages/adapters/rabbitmq/src/__tests__/rabbitmq-event-bus.test.ts:594 — This test sets up 12 test doubles (for example `vi.fn`) against 3 real object(s) of its own, and its only verification is 8 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should ack poison messages in _setupConsumer consumer packages/adapters/rabbitmq/src/__tests__/rabbitmq-event-bus.test.ts:781 — This test sets up 10 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should call channel.nack(msg, false, true) when any handler fails (existing redelivery behavior is preserved) packages/adapters/rabbitmq/src/__tests__/rabbitmq-event-bus.test.ts:1148 — This test sets up 9 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should not discard 10 distinct same-type messages with no messageId packages/adapters/rabbitmq/src/__tests__/rabbitmq-event-bus.test.ts:1379 — This test sets up 10 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should dead-letter a message redelivered past maxRetries packages/adapters/rabbitmq/src/__tests__/rabbitmq-event-bus.test.ts:1421 — This test sets up 9 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should log an error via the framework logger when _setupConsumer fails packages/adapters/rabbitmq/src/__tests__/rabbitmq-event-bus.test.ts:1480 — This test sets up 7 test doubles (for example `vi.fn`) against 3 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
+ 3 more in this group — see findings.md.

D12 · Dependency Hygiene · Deprecated · ×10

Deprecated: @humanwhocodes/config-array REDACTED:1111 — @humanwhocodes/config-array 0.11.14 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/config-array instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/object-schema REDACTED:1125 — @humanwhocodes/object-schema 2.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/object-schema instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @ungap/structured-clone REDACTED:3329 — @ungap/structured-clone 1.3.0 is resolved in REDACTED and is marked deprecated by its publisher: "Potential CWE-502 - Update to 1.3.1 or higher". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @ungap/structured-clone REDACTED:3334 — @ungap/structured-clone 1.2.0 is resolved in REDACTED and is marked deprecated by its publisher: "Potential CWE-502 - Update to 1.3.1 or higher". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:6440 — 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: glob REDACTED:6452 — glob 7.2.3 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: inflight REDACTED:6842 — inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". 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:9322 — 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.
Deprecated: rimraf REDACTED:9922 — rimraf 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: uuid REDACTED:11384 — uuid 10.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.

X10 · Duplicated predicate · Duplicated predicate · ×5

Duplicated predicate packages/adapters/drizzle/src/errors.ts:18 — `err.code === "ER_DUP_ENTRY" || err.errno === 1062` appears character-identically in 2 files — packages/adapters/drizzle/src/errors.ts, packages/adapters/typeorm/src/errors.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/adapters/prisma/src/dedicated-state-persistence.ts:58 — `error instanceof Error && "code" in error && (error as any).code === "P2002"` appears character-identically in 3 files — packages/adapters/prisma/src/dedicated-state-persistence.ts, packages/adapters/prisma/src/event-idempotency.ts, packages/adapters/prisma/src/persistence.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/adapters/kafka/src/kafka-event-bus.ts:732 — `handler.name && handler.name !== "handler" && handler.name !== ""` appears character-identically in 4 files — packages/adapters/kafka/src/kafka-event-bus.ts, packages/adapters/nats/src/nats-event-bus.ts, packages/adapters/rabbitmq/src/rabbitmq-event-bus.ts, packages/engine/src/implementations/ee-event-bus.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/engine/src/executors/command-lifecycle-executor.ts:171 — `this.onEventsDispatched && events.length > 0` appears character-identically in 2 files — packages/engine/src/executors/command-lifecycle-executor.ts, packages/engine/src/executors/saga-executor.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/adapters/drizzle/src/errors.ts:22 — `typeof err.code === "string" && err.code.startsWith("SQLITE_CONSTRAINT")` appears character-identically in 2 files — packages/adapters/drizzle/src/errors.ts, packages/adapters/typeorm/src/errors.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.

D30 · Dependency Vulnerabilities · Low CVE · ×4

REDACTED
REDACTED
REDACTED
REDACTED

X7 · Silent fallback defaults · Silent fallback default in catch · ×3

Silent fallback default in catch packages/cli/src/utils/discovery.ts:30 — `discoverAggregates` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/cli/src/utils/discovery.ts:67 — `discoverProjections` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/testing-integration/src/contracts/event-bus-contract.ts:91 — `dispatchAndWait` (in `defineEventBusContract`) swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.

D30 · Dependency Vulnerabilities · Low vulnerability · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

M2 · Architecture documentation · ADRs not easily discoverable · ×1

ADRs not easily discoverable — 1 ADR-shaped document(s) detected by content — `specs/api-freeze.spec.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.

P2 · Observability · Logging is not universal · ×1

Logging is not universal — Only 5/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `docs`, `packages/cli`.

P3 · Security & performance tooling · No SAST · ×1

No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 16396 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

X23 · Unguarded diagnostic materialisation · Diagnostic log message is built whether or not it is wanted · ×1

Diagnostic log message is built whether or not it is wanted packages/engine/src/executors/command-lifecycle-executor.ts:353 — `debug` at line 353 is called with an argument built by `enrichedEvents.map((e) => e.name)` (line 356), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.

X5 · Nullable reference types · Strict null checking is not enabled everywhere the repository type-checks · ×1

Strict null checking is not enabled everywhere the repository type-checks — 1/35 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.

X5 · Nullable reference types · Null assertions (`!`) reduce the strict null checking score · ×1

Null assertions (`!`) reduce the strict null checking score — ~4.7 `!` null assertions per 1k TypeScript source lines — 123 assertion(s) across the 26106 source line(s) of the 227 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/adapters/typeorm/src/entities.ts (52), packages/engine/src/domain.ts (10), packages/adapters/kafka/src/kafka-event-bus.ts (8). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

Minor — 22 finding(s)

D12 · Dependency Hygiene · Outdated (npm) · ×22

Outdated (npm): @inquirer/prompts — @inquirer/prompts is pinned at 7.10.1; registry.npmjs.org publishes 8.7.4 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): @prisma/client — @prisma/client is pinned at 6.19.2; registry.npmjs.org publishes 7.10.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): @testcontainers/postgresql — @testcontainers/postgresql is pinned at 10.28.0; registry.npmjs.org publishes 12.2.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): amqplib — amqplib is pinned at 0.10.9; registry.npmjs.org publishes 2.2.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): commander — commander is pinned at 13.1.0; registry.npmjs.org publishes 15.0.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): drizzle-orm — drizzle-orm is pinned at 0.30.10; registry.npmjs.org publishes 0.45.4 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): fastify — fastify is pinned at 5.8.4; registry.npmjs.org publishes 5.12.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.
Outdated (npm): fastify-plugin — fastify-plugin is pinned at 5.1.0; registry.npmjs.org publishes 6.0.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): fumadocs-core — fumadocs-core is pinned at 16.6.17; registry.npmjs.org publishes 16.17.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.
Outdated (npm): fumadocs-mdx — fumadocs-mdx is pinned at 14.2.10; registry.npmjs.org publishes 15.4.9 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): fumadocs-typescript — fumadocs-typescript is pinned at 5.1.5; registry.npmjs.org publishes 5.5.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): fumadocs-ui — fumadocs-ui is pinned at 16.6.17; registry.npmjs.org publishes 16.17.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.
Outdated (npm): mermaid — mermaid is pinned at 11.13.0; registry.npmjs.org publishes 12.2.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.1.6; 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): pg — pg is pinned at 8.20.0; registry.npmjs.org publishes 8.23.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 — 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): testcontainers — testcontainers is pinned at 10.28.0; registry.npmjs.org publishes 12.2.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): tsx — tsx is pinned at 4.21.0; registry.npmjs.org publishes 4.23.15 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): type-fest — type-fest is pinned at 4.35.0; registry.npmjs.org publishes 5.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): typeorm — typeorm is pinned at 0.3.28; registry.npmjs.org publishes 1.1.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): typescript — typescript is pinned at 5.3.3; registry.npmjs.org publishes 7.0.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.

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.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d1aea663d5bd4d80aa9c4bd172bf4287/history.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d1aea663d5bd4d80aa9c4bd172bf4287/tree.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	37	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	71	artifacts/raw/trivy-fs.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	0	artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 8 file(s) — `packages/adapters/drizzle/src/builder.ts`, `packages/adapters/nats/src/nats-event-bus.ts`, `packages/adapters/prisma/src/builder.ts`, `packages/adapters/typeorm/src/builder.ts`, `packages/core/src/cqrs/query/query.ts`, … (+3 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—
D43 · Malicious Dependencies	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	artifacts/raw/trivy-fs.json

Run 01a163e4-8b17-71a1-9aaf-8963447a8c3b · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture — module dependency graph

Architecture: which parts of the code depend on which

At a glance — Code Health · 61% · Adequate · gated by X5 ·

At a glance — Architecture · 87% · Strong ·

At a glance — Maturity · 49% · Weak · gated by M4 ·

At a glance — Readiness · 43% · Weak · gated by R8, P3, P8 ·

At a glance — Security · 73% · Adequate · gated by D30 ·

At a glance — Domain Modelling · 79% · Strong ·

At a glance — Accessibility · 71% · Strong ·

At a glance — Performance · 85% · Strong ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

WCAG coverage — what static analysis assessed

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts