node-ts/bus

Executive summary

node-ts/bus scores 53 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.

The weakest lens counts most in the score, and here that is Maturity, which scores 44 and is rated Weak. Its Documentation accuracy dimension scores 0 out of 10, and until that reaches 4, Maturity can't be rated higher than Adequate. The first actions are to resolve the 1 No ADRs found finding(s) in ADR Quality and to reconcile the README with reality: CONTRIBUTING.md runs `pnpm changeset`, but no package.json declares a `changeset` script; .changeset/README.md runs `pnpm changeset`, but no package.json declares a `changeset` script; docs/persistence.md links to `/guide/outbox`, but `guide/outbox` does not exist; docs/getting-started/handling-messages.md links to `/api/bus-core/interfaces/HandlerContext`, but `api/bus-core/interfaces/HandlerContext` does not exist; docs/getting-started/handling-messages.md links to `/guide/workflows/request-reply`, but `guide/workflows/request-reply` does not exist, and if Maturity rose to 70, the score would rise from 53 to about 60.

32 findings are critical: 19 in Static Analysis (SAST), 11 in Dependency Vulnerabilities, one in Circular Imports and one in Data Compliance (PII/GDPR).

Watchdog couldn't measure 7 dimensions in this code, among them Navigability, Data Protection and Audit Trail, so they are left out of the score. The product code is 51,602 lines, which would take an estimated 0.5 person-years, around €66,000, to rebuild.

Code Health 77 Strong Architecture 60 Adequate, capped by Import Boundaries Maturity 44 Weak, capped by Architecture documentation and Documentation accuracy Production Readiness 55 Adequate, capped by Dependency Hygiene and Security & performance tooling Security and Compliance 63 Adequate, capped by Static Analysis (SAST), Dependency Vulnerabilities and Supply-chain Provenance & Signing 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.

Maturity 44 · counts for 46%Production Readiness 55 · counts for 25%Architecture 60 · counts for 14%Security and Compliance 63 · counts for 8%Code Health 77 · counts for 4%Performance 85 · counts for 2%

If Maturity rose from 44 to 70, the lowest score rated Strong, the score would rise from 53 to about 60.

Code composition: what the lines of code are

Product code 76%Tests 24%

New since the last survey: 98 findings

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

Cyclomatic Complexity · is-same-message-types.readMessageTypes::toValue (cyclomatic 17) packages/bus-cli/src/generate-message-types/is-same-message-types.ts
Cognitive Complexity · is-same-message-types.readMessageTypes::toValue (cognitive 22) packages/bus-cli/src/generate-message-types/is-same-message-types.ts
God Classes · ClassTooLong: RedisTransport packages/bus-redis/src/redis-transport.ts
God Classes · FileTooLong: src/redis-transport.ts packages/bus-redis/src/redis-transport.ts
God Classes · TooManyMethods: RedisTransport packages/bus-redis/src/redis-transport.ts
God Classes · FileTooLong: src/redis-transport.integration.ts packages/bus-redis/src/redis-transport.integration.ts
Code Coverage · Low coverage: packages/bus-core/src/workflow/configure-class-workflow.ts packages/bus-core/src/workflow/configure-class-workflow.ts
Code Coverage · Low coverage: packages/bus-redis/src/index.ts packages/bus-redis/src/index.ts
Code Coverage · Low coverage: packages/bus-redis/src/redis-scripts.ts packages/bus-redis/src/redis-scripts.ts
Dependency Hygiene · Deprecated: @opentelemetry/sdk-trace-base packages/bus-opentelemetry/package.json
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/handler/handler.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/handler/handler-registry.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/handler/default-handler-registry.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/handler/handler-for.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/handler/handler-for.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/error/workflow-already-handles-message.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/error/workflow-already-handles-message.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/error/workflow-already-started-by-message.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/error/workflow-already-started-by-message.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/error/workflow-does-not-handle-message.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/error/workflow-does-not-handle-message.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/function-workflow-definition.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/define-workflow.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/define-workflow.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/define-workflow.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/define-workflow.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/define-workflow.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/workflow.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/workflow.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/service-bus/bus-configuration.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/service-bus/bus-configuration.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/testing/recorded-messages.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/testing/recorded-messages.ts
Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/testing/recorded-messages.ts
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
IaC & Container Security · REDACTED
IaC & Container Security · REDACTED
Code Duplication · Duplication concentrated across 10 sibling directories (44 clone groups) packages/bus-mongodb/src/mongodb-persistence.ts
Code Duplication · Duplicated block with local edits (107 matched lines × 2 locations) packages/bus-postgres/src/postgres-transport.ts
Code Duplication · Duplicated block (19 lines × 2 locations) packages/bus-postgres/src/postgres-transport.integration.ts
Large Files · packages/bus-core/src/service-bus/bus-instance.ts: 2537 lines of code packages/bus-core/src/service-bus/bus-instance.ts
Large Files · packages/bus-sqs/src/sqs-transport.ts: 1496 lines of code packages/bus-sqs/src/sqs-transport.ts
Large Files · packages/bus-rabbitmq/src/rabbitmq-transport.ts: 1359 lines of code packages/bus-rabbitmq/src/rabbitmq-transport.ts
Large Files · packages/bus-redis/src/redis-transport.ts: 1336 lines of code packages/bus-redis/src/redis-transport.ts
Large Files · packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts: 1136 lines of code packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts
Large Files · packages/bus-postgres/src/postgres-persistence.ts: 1059 lines of code packages/bus-postgres/src/postgres-persistence.ts
Large Files · packages/bus-cli/src/generate-message-types/message-type-reader.ts: 1023 lines of code packages/bus-cli/src/generate-message-types/message-type-reader.ts
Large Files · packages/bus-postgres/src/postgres-transport.ts: 962 lines of code packages/bus-postgres/src/postgres-transport.ts
Large Files · packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts: 946 lines of code packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts
Large Files · packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts: 929 lines of code packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts
Large Files · packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts: 881 lines of code packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts
Large Files · packages/bus-mongodb/src/mongodb-persistence.ts: 880 lines of code packages/bus-mongodb/src/mongodb-persistence.ts
Large Files · packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts: 828 lines of code packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts
Large Files · packages/bus-redis/src/redis-transport.integration.ts: 826 lines of code packages/bus-redis/src/redis-transport.integration.ts
Large Files · packages/bus-postgres/src/postgres-persistence.integration.ts: 806 lines of code packages/bus-postgres/src/postgres-persistence.integration.ts
Large Files · packages/bus-postgres/src/postgres-transport.integration.ts: 796 lines of code packages/bus-postgres/src/postgres-transport.integration.ts
Large Files · packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts: 718 lines of code packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts
Large Files · packages/bus-core/src/workflow/registry/workflow-registry.ts: 714 lines of code packages/bus-core/src/workflow/registry/workflow-registry.ts
Large Files · packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts: 704 lines of code packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts
Large Files · packages/bus-nestjs/src/bus-module.integration.ts: 699 lines of code packages/bus-nestjs/src/bus-module.integration.ts
Large Files · packages/bus-mongodb/src/mongodb-persistence.integration.ts: 648 lines of code packages/bus-mongodb/src/mongodb-persistence.integration.ts
Large Files · packages/bus-core/src/outgoing-message/outgoing-message-dispatcher.ts: 635 lines of code packages/bus-core/src/outgoing-message/outgoing-message-dispatcher.ts
Large Files · packages/bus-core/src/service-bus/bus-configuration.ts: 625 lines of code packages/bus-core/src/service-bus/bus-configuration.ts
Large Files · packages/bus-core/src/service-bus/bus-instance-reply.integration.ts: 622 lines of code packages/bus-core/src/service-bus/bus-instance-reply.integration.ts
Large Files · packages/bus-core/src/workflow/persistence/in-memory-persistence.ts: 566 lines of code packages/bus-core/src/workflow/persistence/in-memory-persistence.ts
Large Files · packages/bus-test/src/scheduled-message-round-trip-tests.ts: 552 lines of code packages/bus-test/src/scheduled-message-round-trip-tests.ts
Large Files · packages/bus-core/src/service-bus/bus-instance.integration.ts: 550 lines of code packages/bus-core/src/service-bus/bus-instance.integration.ts
Large Files · packages/bus-cli/src/generate-message-types/run-generate-message-types.integration.ts: 530 lines of code packages/bus-cli/src/generate-message-types/run-generate-message-types.integration.ts
Large Files · packages/bus-core/src/testing/test-workflow.ts: 522 lines of code packages/bus-core/src/testing/test-workflow.ts
Large Files · packages/bus-test/src/transport-tests.ts: 518 lines of code packages/bus-test/src/transport-tests.ts
Large Files · packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts: 503 lines of code packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts
Large Files · packages/bus-sqs/src/sqs-transport.integration.ts: 503 lines of code packages/bus-sqs/src/sqs-transport.integration.ts
Large Files · packages/bus-core/src/service-bus/bus-instance-recoverability.integration.ts: 478 lines of code packages/bus-core/src/service-bus/bus-instance-recoverability.integration.ts
Large Files · packages/bus-test/src/inbox-tests.ts: 472 lines of code packages/bus-test/src/inbox-tests.ts
Large Files · packages/bus-core/src/workflow/workflow.integration.ts: 425 lines of code packages/bus-core/src/workflow/workflow.integration.ts
Large Files · packages/bus-opentelemetry/src/open-telemetry.ts: 412 lines of code packages/bus-opentelemetry/src/open-telemetry.ts
Dependency Hygiene · Unused dependency 'tslib'
Dependency Hygiene · Unused dependency '@node-ts/code-standards'
Dependency Hygiene · Unused dependency 'tslib'
Web-Security Posture · Weak hash algorithm packages/bus-redis/src/redis-scripts.ts
Exception handling · Swallowed exception (empty catch) packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts
Incompleteness & stubs · Fake-async — async method never awaits docs/snippets/mongodb-outbox-testing.ts
Incompleteness & stubs · Hollow method — returns a constant without doing the work docs/snippets/nestjs-testing.ts
Incompleteness & stubs · Empty method body — does nothing with its inputs docs/snippets/nestjs.ts
Incompleteness & stubs · Empty method body — does nothing with its inputs docs/snippets/nestjs.ts
Incompleteness & stubs · Empty method body — does nothing with its inputs docs/snippets/services/index.ts
Incompleteness & stubs · Empty method body — does nothing with its inputs docs/snippets/services/index.ts
Incompleteness & stubs · Empty method body — does nothing with its inputs docs/snippets/services/index.ts
Incompleteness & stubs · Empty method body — does nothing with its inputs docs/snippets/services/index.ts
Incompleteness & stubs · Empty method body — does nothing with its inputs docs/snippets/services/index.ts
Incompleteness & stubs · Hollow method — returns a constant without doing the work docs/snippets/services/index.ts
Incompleteness & stubs · Fake-async — async method never awaits packages/bus-core/src/workflow/registry/workflow-registry.ts
Async & latency hygiene · Sync-over-async blocking packages/bus-test/src/inbox-tests.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: 118 findings

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

Cyclomatic Complexity · is-same-message-types.readMessageTypes (cyclomatic 32) packages/bus-cli/src/generate-message-types/is-same-message-types.ts
God Classes · ClassTooLong: WorkflowRegistry packages/bus-core/src/workflow/registry/workflow-registry.ts
Test Quality · No assertions: should construct workflow instances packages/bus-core/src/workflow/registry/workflow-registry.spec.ts
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Code Duplication · Duplication concentrated across 9 sibling directories (38 clone groups) packages/bus-mongodb/src/mongodb-persistence.ts
Code Duplication · Duplicated block with local edits (24 matched lines × 2 locations) packages/bus-core/src/workflow/workflow-concurrency.integration.ts
Code Duplication · Duplicated block (22 lines × 2 locations) packages/bus-postgres/src/postgres-transport.integration.ts
Code Duplication · Duplicated block (15 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts
Code Duplication · Duplicated block (15 lines × 3 locations) packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts
Code Duplication · Duplicated block (15 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts
Code Duplication · Duplicated block (15 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts
Code Duplication · Duplicated block (15 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-receiver.integration.ts
Code Duplication · Duplicated block (15 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts
Code Duplication · Duplicated block (15 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts
Code Duplication · Duplicated block (15 lines × 2 locations) packages/bus-mongodb/src/mongo-session.ts
Code Duplication · Duplicated block (15 lines × 2 locations) packages/bus-postgres/src/postgres-persistence.integration.ts
Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) packages/bus-core/src/message-handling-context/message-handling-context.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-reply.integration.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/bus-postgres/src/postgres-persistence.integration.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts
Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) packages/bus-sqs-lambda/src/bus-sqs-lambda-receiver.integration.ts
Code Duplication · Duplicated block (13 lines × 3 locations) packages/bus-core/src/handler/handler-for.integration.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts
Code Duplication · Duplicated block (13 lines × 4 locations) packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/bus-core/src/workflow/workflow-timeout.integration.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/bus-postgres/src/postgres-transport.integration.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts
Code Duplication · Duplicated block (12 lines × 6 locations) packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts
Code Duplication · Duplicated block (12 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts
Code Duplication · Duplicated block (12 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts
Code Duplication · Duplicated block (12 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts
Code Duplication · Duplicated block (12 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts
Code Duplication · Duplicated block (12 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts
Code Duplication · Duplicated block (12 lines × 3 locations) packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts
Code Duplication · Duplicated block (12 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts
Code Duplication · Duplicated block (12 lines × 8 locations) packages/bus-core/src/service-bus/bus-instance-recoverability.integration.ts
Code Duplication · Duplicated block (12 lines × 5 locations) packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts
Code Duplication · Duplicated block (12 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts
Code Duplication · Duplicated block (12 lines × 2 locations) packages/bus-mongodb/src/mongodb-persistence.integration.ts
Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) packages/bus-core/src/handler/handler-for.integration.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-receiver.integration.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-recoverability.integration.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-reply.integration.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts
Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) packages/bus-core/src/service-bus/bus-instance.ts
Code Duplication · Duplicated block (11 lines × 3 locations) packages/bus-core/src/workflow/define-workflow.integration.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/bus-nestjs/src/bus-module.integration.ts
Code Duplication · Duplicated block (11 lines × 3 locations) packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts
Code Duplication · Duplicated block (11 lines × 4 locations) packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/bus-rabbitmq/src/rabbitmq-transport.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/bus-cli/src/generate-message-types/run-generate-message-types.integration.ts
Code Duplication · Duplicated block (10 lines × 3 locations) packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts
Code Duplication · Duplicated block (10 lines × 3 locations) packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts
Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-message-types.integration.ts
Code Duplication · Duplicated block (10 lines × 6 locations) packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts
Code Duplication · Duplicated block (10 lines × 3 locations) packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-provisioning.integration.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/bus-core/src/workflow/workflow-timeout.integration.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/bus-postgres/src/postgres-persistence.integration.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/bus-postgres/src/postgres-persistence.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts
Code Duplication · Duplicated block (9 lines × 3 locations) packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts
Code Duplication · Duplicated block (9 lines × 3 locations) packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-reply.integration.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/bus-mongodb/src/mongodb-persistence.integration.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/bus-postgres/src/postgres-persistence.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/bus-postgres/src/postgres-persistence.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts
Code Duplication · Duplicated block with local edits (8 matched lines × 2 locations) packages/bus-cli/src/generate-message-types/message-type-reader.ts
Code Duplication · Duplicated block (8 lines × 3 locations) packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts
Code Duplication · Duplicated block (8 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts
Code Duplication · Duplicated block (8 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts
Code Duplication · Duplicated block (8 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts
Code Duplication · Duplicated block (8 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts
Code Duplication · Duplicated block (8 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts
Code Duplication · Duplicated block (8 lines × 2 locations) packages/bus-core/src/workflow/define-workflow.integration.ts
Code Duplication · Duplicated block (8 lines × 3 locations) packages/bus-postgres/src/postgres-persistence.integration.ts
Code Duplication · Duplicated block (8 lines × 2 locations) packages/bus-postgres/src/postgres-persistence.integration.ts
Code Duplication · Duplicated block (7 lines × 2 locations) packages/bus-cli/src/generate-message-types/message-types-writer.ts
Code Duplication · Duplicated block (7 lines × 2 locations) packages/bus-sqs/src/sqs-transport.integration.ts
Code Duplication · Duplicated block with local edits (6 matched lines × 2 locations) packages/bus-core/src/logger/debug-logger.ts
Code Duplication · Duplicated block (5 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts

Rebuild cost: about €66,000 · Estimate

Cost to rebuild	€22,000 to €110,000, for 364 to 1,156 hours of work, about 0.5 person-years for one engineer
Difficulty of the problem	Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor	×0.7 at a score of 53. 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: 51,602 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 1 No ADRs found finding(s) in ADR Quality.

Raises the score by about 8 points · Low effort · ADR Quality

Reconcile the README with reality: CONTRIBUTING.md runs `pnpm changeset`, but no package.json declares a `changeset` script; .changeset/README.md runs `pnpm changeset`, but no package.json declares a `changeset` script; docs/persistence.md links to `/guide/outbox`, but `guide/outbox` does not exist; docs/getting-started/handling-messages.md links to `/api/bus-core/interfaces/HandlerContext`, but `api/bus-core/interfaces/HandlerContext` does not exist; docs/getting-started/handling-messages.md links to `/guide/workflows/request-reply`, but `guide/workflows/request-reply` does not exist.

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

Record your significant design decisions.

Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.

Raises the score by about 7 points · Medium effort · Architecture documentation

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk

This code would cost about €66,000 to build again, about 0.5 person-years of work. Its weakest lens is Maturity, at 44 (Weak). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.

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

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

If you do one thing first · First action

Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 8 points for low effort, because it clears the 1 ADR Quality 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.

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

The table shows the 40 modules with the most connections; 393 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.bus-cli.test.supported.src.base	2 packages.bus-core.src.logger.logger	3 packages.bus-core.src.provisioning.provisioning-plan	4 packages.bus-core.src.recoverability.message-failure	5 packages.bus-core.src.transport.transport-send-options	6 packages.bus-core.src.workflow.persistence.persistence-transaction	7 packages.bus-core.src.workflow.workflow-state	8 packages.bus-messages.src.message-attributes	9 packages.bus-messages.src.message-declaration	10 packages.bus-messages.src.message-types	11 packages.bus-core.src.handler.handler-context	12 packages.bus-core.src.transport.transport-message	13 packages.bus-core.src.workflow.workflow	14 packages.bus-messages.src.command	17 packages.bus-core.src.handler.handler	19 packages.bus-core.src.handler.handler-registry	20 packages.bus-core.src.serialization.message-serializer	21 packages.bus-core.src.util.core-dependencies	22 packages.bus-core.src.transport.transport	23 packages.bus-core.src.workflow.persistence.persistence	25 packages.bus-core.src.transport.in-memory-queue	26 packages.bus-core.src.workflow.persistence.in-memory-persistence	27 packages.bus-core.src.workflow.registry.workflow-registry	34 packages.bus-core.src.service-bus.bus-instance	35 packages.bus-core.src.test.recording-in-memory-queue	38 packages.bus-core.src.workflow.test.test-workflow
1 packages.bus-cli.test.supported.src.base
2 packages.bus-core.src.logger.logger
3 packages.bus-core.src.provisioning.provisioning-plan
4 packages.bus-core.src.recoverability.message-failure
5 packages.bus-core.src.transport.transport-send-options
6 packages.bus-core.src.workflow.persistence.persistence-transaction
7 packages.bus-core.src.workflow.workflow-state
8 packages.bus-messages.src.message-attributes
9 packages.bus-messages.src.message-declaration
10 packages.bus-messages.src.message-types
11 packages.bus-core.src.handler.handler-context								1
12 packages.bus-core.src.transport.transport-message	1							1
13 packages.bus-core.src.workflow.workflow							1		1
14 packages.bus-messages.src.command	1
15 packages.bus-messages.src.event	1
16 docs.snippets.workflows.completing													2
17 packages.bus-core.src.handler.handler									1		1
18 packages.bus-core.src.testing	2						1	1	1		1		1
19 packages.bus-core.src.handler.handler-registry	1								2						2
20 packages.bus-core.src.serialization.message-serializer										1						1
21 packages.bus-core.src.util.core-dependencies										1						1	1
22 packages.bus-core.src.transport.transport	1		1	1	1			1				1				2		1
23 packages.bus-core.src.workflow.persistence.persistence			1			1	1	1										1
24 docs.snippets.transports.my-transport	1	1	1	1	1			1				1						1	3
25 packages.bus-core.src.transport.in-memory-queue	2	1		1	1			1				1						1	2
26 packages.bus-core.src.workflow.persistence.in-memory-persistence		1				1	2	1										1		2
27 packages.bus-core.src.workflow.registry.workflow-registry	3	1					3	2	2		1	1	1			1		1		1
28 packages.bus-mongodb.src.mongodb-persistence		1	1			1		1										1		3
29 packages.bus-postgres.src.postgres-persistence		1	1			1		1										1		3
30 packages.bus-postgres.src.postgres-transport	1	1	1	1	1			1				1						1	3
31 packages.bus-rabbitmq.src.rabbitmq-transport	1	1	1	1	1			1				1						1	4
32 packages.bus-redis.src.redis-transport	1	1	1	1	1			1				1						1	3
33 packages.bus-sqs.src.sqs-transport	1	1	2	1	1			1				1						1	3
34 packages.bus-core.src.service-bus.bus-instance	1	1	1			1		1			1	1			1	1		1	1	1			1
35 packages.bus-core.src.test.recording-in-memory-queue	1			1	1			1				1									2
36 packages.bus-core.src.service-bus	1	1						1	1						2				1		2	1		5	1
37 packages.bus-core.src.service-bus.bus-configuration															1	1			1	1				1
38 packages.bus-core.src.workflow.test.test-workflow													2											1
39 packages.bus-core.src.service-bus.bus-instance-outboxing_integration	1						5					1	4	2								2				1
40 packages.bus-core.src.workflow.workflow-concurrency_integration							1	1					2		1									2		1

Uses a module listed above itPart of a loopThe module itself

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

The Good

D1 · TypeScript Cyclomatic Complexity 9.0 D2 · TypeScript Cognitive Complexity 8.0 D3 · TypeScript God Classes 8.1 D17 · TypeScript Explicit Debt 10.0 GD1 · Repo Unfinished & placeholder code 10.0 R1 · React / TS Type Safety 10.0 R10 · React / TS Code Duplication 8.6 R2 · React / TS Cyclomatic Complexity 9.9 R7 · React / TS Dead Code 9.9 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 7.2 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 X3 · Repo Exception handling 7.9 X30 · Repo Support guard that admits what it rejects 10.0 X4 · Repo Structured logging 10.0 X5 · Repo Nullable reference types 8.6

The Bad

IC1 · Repo Incompleteness & stubs 6.8 R3 · React / TS Large Files 6.2

At a glance — Architecture · 60% · Adequate · gated by R11 ·

The Good

D5 · TypeScript Coupling 9.4 D6 · TypeScript Cohesion (LCOM4) 10.0 D22 · TypeScript Internal API Consistency 8.0 D23 · TypeScript Boundary Type-Coupling 9.1 D26 · TypeScript Project Cohesion 8.5 D35 · TypeScript Change Coupling 10.0 AX10 · Repo Code composition 9.7 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX6 · Repo Interface segregation 10.0

The Bad

R9 · React / TS Circular Imports 6.3

The Ugly

R11 · React / TS Import Boundaries 0.0

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

The Good

D15 · TypeScript Churn × Complexity Hotspots 10.0 D19 · TypeScript Documentation Quality 9.4 D21 · TypeScript Naming Consistency 10.0 D34 · TypeScript Knowledge Freshness 10.0 M1 · Repo Documentation (README) 8.0 M3 · Repo Folder & project structure 10.0

The Ugly

D20 · TypeScript ADR Quality 0.0 M2 · Repo Architecture documentation 2.0 M4 · Repo Documentation accuracy 0.0

At a glance — Readiness · 55% · Adequate · gated by R8, P3 ·

The Good

D8 · TypeScript Code Coverage 8.2 D9 · TypeScript Test Distribution 10.0 D10 · TypeScript Test Quality 9.9 D11 · TypeScript Test Reliability 10.0 D12 · TypeScript Dependency Hygiene 9.2 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.7 P4 · Repo Deployment & Rollback 8.0 P6 · Repo Release Hygiene 10.0 R4 · React / TS Test Coverage 9.9 R6 · React / TS Tooling 10.0

The Ugly

P3 · Repo Security & performance tooling 3.0 R8 · React / TS Dependency Hygiene 0.0

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

The Good

D28 · TypeScript Secrets (history) 10.0 D31 · TypeScript IaC & Container Security 9.4 D32 · TypeScript Data Compliance (PII/GDPR) 7.1 D37 · TypeScript Vulnerability-disclosure Policy 10.0 D43 · TypeScript Malicious Dependencies 10.0 D44 · TypeScript Platform End-of-Life 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0

The Bad

S1 · Repo Web-Security Posture 6.0

The Ugly

D29 · TypeScript Static Analysis (SAST) 1.2 D30 · TypeScript Dependency Vulnerabilities 1.7 D36 · TypeScript Supply-chain Provenance & Signing 0.0 X17 · Repo Uncapped recursion over a caller-supplied document 3.5

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	21	High / Critical
A05:2025 — Injection	19	High / Critical
A02:2025 — Security Misconfiguration	6	Medium
A01:2025 — Broken Access Control	1	High / Critical

Roadmap

First, resolve the missing architectural decision records and ensure documentation accurately reflects the current codebase by fixing broken links and reconciling instructions with reality. Next, clean up the dependency list by removing unused packages and explicitly declaring imports to maintain hygiene. Finally, address import boundary violations by reorganizing shared test helpers to prevent production code from depending on them.

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

Do this	Helps	Effort	Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality.	+8.0 pts	Low	ADR Quality
Reconcile the README with reality: CONTRIBUTING.md runs `pnpm changeset`, but no package.json declares a `changeset` script; .changeset/README.md runs `pnpm changeset`, but no package.json declares a `changeset` script; docs/persistence.md links to `/guide/outbox`, but `guide/outbox` does not exist; docs/getting-started/handling-messages.md links to `/api/bus-core/interfaces/HandlerContext`, but `api/bus-core/interfaces/HandlerContext` does not exist; docs/getting-started/handling-messages.md links to `/guide/workflows/request-reply`, but `guide/workflows/request-reply` does not exist.	+7.3 pts	Medium	Documentation accuracy
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.	+6.8 pts	Medium	Architecture documentation
Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (5).	+1.3 pts	Low	Dependency Hygiene
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.	+2.5 pts	Medium	Dependency Hygiene
Fix the listed violations: move the shared test helper into a source directory production code may depend on (56 rows).	+1.9 pts	Medium	Import Boundaries
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.	+1.9 pts	Medium	Security & performance tooling
Resolve the 1 Documentation finding(s) in Documentation Quality — start with index.md.	+0.9 pts	Low	Documentation Quality

File quality

Per-file score 0–10 — a quality signature. Of 127 files carrying findings, judged against the Production bar: 1% slop · 23% mixed · 76% near-clean.

File	Score	Band	Worst signal
REDACTED	0.0	Slop	Dependency Vulnerabilities: Critical CVE: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.6	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.1	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.9	Mixed	IaC & Container Security: Medium IaC: REDACTED
packages/bus-cli/src/generate-message-types/is-same-message-types.ts	5.9	Mixed	Cyclomatic Complexity: is-same-message-types.readMessageTypes::toValue (cyclomatic 17)
packages/bus-core/src/outgoing-message/outgoing-message-dispatcher.ts	7.0	Mixed	Cognitive Complexity: OutgoingMessageDispatcher.probe (cognitive 16)
packages/bus-cli/src/generate-message-types/message-type-reader.ts	7.0	Mixed	Cyclomatic Complexity: MessageTypeReader.describeObjectType (cyclomatic 19)
packages/bus-core/src/workflow/define-workflow.ts	7.1	Mixed	Boundary Type-Coupling: Cross-context type MessageDeclaration (bus-messages → bus-core)
packages/bus-core/src/service-bus/bus-instance.ts	7.2	Mixed	Cognitive Complexity: BusInstance.sendCommittedMessages (cognitive 20)
packages/bus-rabbitmq/src/rabbitmq-transport.ts	7.2	Mixed	Cognitive Complexity: RabbitMqTransport.publishMessage (cognitive 19)
REDACTED	7.2	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	7.2	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	7.2	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	7.2	Mixed	Data Compliance (PII/GDPR): High: REDACTED
packages/bus-sqs/src/sqs-transport.ts	7.4	Mixed	God Classes: FileTooLong: src/sqs-transport.ts
packages/bus-redis/src/redis-transport.ts	7.4	Mixed	God Classes: ClassTooLong: RedisTransport
packages/bus-postgres/src/postgres-transport.ts	7.4	Mixed	God Classes: ClassTooLong: PostgresTransport
packages/bus-core/src/service-bus/bus.spec.ts	7.4	Mixed	Test Quality: No assertions: should accept a concurrency of 1
packages/bus-core/src/testing/recorded-messages.ts	7.4	Mixed	Boundary Type-Coupling: Cross-context type MessageDeclaration (bus-messages → bus-core)

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

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

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

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

Could not be resolved — 8

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. 74 of 79 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 — 79 dimensions across the health lenses

D1D2D3D5D6D8D9D10D11D12D13D14D15D17D19D20D21D22D23D26D28D29D30D31D32D34D35D36D37D43D44AX10AX3AX4AX6GD1IC1M1M2M3M4P1P10P2P3P4P6PF3R1R10R11R2R3R4R6R7R8R9S1X1X12X13X14X15X16X17X18X19X21X22X23X24X25X28X29X3X30X4X5

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, 424 of 446 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 01a16474-59db-7e98-82e0-d0677c2e43e8.

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 (12 contributor(s) across 398 commit(s) sampled, automation and bot accounts excluded). One of them holds 92% of the history; the other 11 hold 0.7% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
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) — 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. `docs/scripts/sync-readmes.mjs`, `packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts`, `packages/bus-core/src/workflow/workflow.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — mongo Pulling rabbitmq Pulling postgres Pulling redis Pulling localstack Pulling valkey Pulling localstack Error Get "https://registry-1.docker.io/v2/": Forbidden mongo Error context canceled postgres Error context canceled redis Error context canceled rabbitmq Error context canceled valkey Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: mongo Pulling valkey Pulling postgres Pulling localstack Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden valkey Error Get "https://registry-1.docker.io/v2/": Forbidden mongo Error context canceled localstack Error context canceled rabbitmq Error context canceled redis Error context canceled 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.
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'mongodb' is imported (docs/snippets/mongodb-outbox.ts:3), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'mongodb' is imported (docs/snippets/mongodb-outbox.ts:3), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'mongodb' is imported (docs/snippets/mongodb-outbox.ts:3), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'mongodb' is imported (docs/snippets/mongodb-outbox.ts:3), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
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. 83 further occurrence(s) are not listed individually; the score already reflects all 123.
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. 98 further occurrence(s) are not listed individually; the score already reflects all 138.
R11 Import Boundaries — 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. 16 further occurrence(s) are not listed individually; the score already reflects all 56.
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.

Repo exclusion declarations: 2 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

Limitations & what we did not check

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

Per-dimension blind spots

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

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside 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.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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, D21, D22, D26, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity9.0 / 10Stronggated by 6 serious findings✓ Tool-verified

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

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

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

6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was message-type-reviver.reviveValue at 24.

message-type-reviver.reviveValue (cyclomatic 24)packages/bus-core/src/serialization/message-type-reviver.ts:77

sync-readmes.syncReadme (cyclomatic 19)docs/scripts/sync-readmes.mjs:245

MessageTypeReader.describeObjectType (cyclomatic 19)packages/bus-cli/src/generate-message-types/message-type-reader.ts:891

generate-message-types.generateMessageTypes (cyclomatic 19)packages/bus-cli/src/generate-message-types/generate-message-types.ts:102

is-same-message-types.readMessageTypes::toValue (cyclomatic 17)packages/bus-cli/src/generate-message-types/is-same-message-types.ts:56

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

What to do

Bring the 6 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with message-type-reviver.reviveValue (cyclomatic 24), sync-readmes.syncReadme (cyclomatic 19), MessageTypeReader.describeObjectType (cyclomatic 19). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cyclomatic Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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 Complexity8.0 / 10Strong✓ Tool-verified

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

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

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

13 method(s) exceeded the cognitive complexity threshold of 15; the worst was sync-readmes.syncReadme at 36.

sync-readmes.syncReadme (cognitive 36)docs/scripts/sync-readmes.mjs:245

message-type-reviver.reviveValue (cognitive 31)packages/bus-core/src/serialization/message-type-reviver.ts:77

is-same-message-types.readMessageTypes (cognitive 24)packages/bus-cli/src/generate-message-types/is-same-message-types.ts:12

is-same-message-types.readMessageTypes::toValue (cognitive 22)packages/bus-cli/src/generate-message-types/is-same-message-types.ts:56

MessageTypeReader.describeObjectType (cognitive 21)packages/bus-cli/src/generate-message-types/message-type-reader.ts:891

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

What to do

Bring the 13 bodies over 15 down to 15 or less in Cognitive Complexity — start with sync-readmes.syncReadme (cognitive 36), message-type-reviver.reviveValue (cognitive 31), is-same-message-types.readMessageTypes (cognitive 24). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 13 together lifts Cognitive Complexity from 8.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D3 · God Classes8.1 / 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.1 / 10 · rule-coverage 100% · ceiling Prevented

34 god class(es) detected.

FileTooLong: service-bus/bus-instance.ts · ×19packages/bus-core/src/service-bus/bus-instance.ts

ClassTooLong: BusInstance · ×8packages/bus-core/src/service-bus/bus-instance.ts:415

TooManyMethods: BusInstance · ×6packages/bus-core/src/service-bus/bus-instance.ts:415

FunctionTooLong: open-telemetry.openTelemetrypackages/bus-opentelemetry/src/open-telemetry.ts:208

What to do

Resolve the 19 FileTooLong finding(s) in God Classes — start with bus-instance.ts, sqs-transport.ts, rabbitmq-transport.integration.ts. — One of this dimension's main actionable groups (19 warning-level).
Resolve the 8 ClassTooLong finding(s) in God Classes — start with bus-instance.ts, rabbitmq-transport.ts, sqs-transport.ts. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 6 TooManyMethods finding(s) in God Classes — start with bus-instance.ts, rabbitmq-transport.ts, redis-transport.ts. — One of this dimension's main actionable groups (6 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: @node-ts/bus-core

What to do

Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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 39 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

Do you agree with this assessment?

D8 · Code Coverage8.2 / 10Strong✓ 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 8.2 / 10 · rule-coverage 100% · ceiling Verified

Line coverage 45.1% — 75 file(s) below 50%. Measured from the JavaScript/TypeScript suite (jest via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root).

Low coverage: jest.config.ts · ×75jest.config.ts:1

What to do

Resolve the 75 Low coverage finding(s) in Code Coverage — start with index.ts (33), jest.config.ts, cli.ts. — One of this dimension's main actionable groups (75 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

767 test methods: 767 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 767 `it`/`test` case(s) across 59 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.9 / 10Stronggated by 5 serious findings✓ Tool-verified

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

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

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

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

No assertions: should initialize without errors · ×5packages/bus-core/src/container/container-adapter.spec.ts:333

What to do

Resolve the 5 No assertions finding(s) in Test Quality — start with bus.spec.ts (3), container-adapter.spec.ts, sleep.spec.ts. — One of this dimension's main actionable groups (5 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 (jest via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root (204 tests)): measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

Do you agree with this assessment?

D12 · Dependency Hygiene9.2 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

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

Deprecated: @opentelemetry/sdk-trace-basepackages/bus-opentelemetry/package.json:63

Deprecated: circular-json · ×5REDACTED:2950

Outdated (npm): serialize-errorpackages/bus-core/package.json:45

Outdated (npm): @aws-sdk/client-sns · ×4

What to do

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

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 13 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 13 production dependency(ies) this repository's committed lockfile resolves, across 13 product package.json 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 Hotspots10.0 / 10Exemplary✓ Tool-verified

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

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

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

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 docs/ directory provide a clear overview of the bus project (what it does, its main components, Node.js version requirement), installation/build commands, usage examples, and links to the published documentation site. The packages/bus-*/README.md documents each adapter package independently but is focused on that tier rather than the repository's root; all are internal-focused for their directories. The documentation is comprehensive and well-structured for a message-driven service bus project. The READMEs of each package directory (bus-rabbitmq, bus-sqs-lambda, etc.) describe what the directory provides with installation, usage examples, and configuration, while the root docs/home.md gives an overview, features, and links to persistence, transports, and handling-messages guides. A single architecture/transport reference document is also present in docs/transports.md. The project's documentation is clear and complete for its readers — the READMEs cover shutdown, delayed delivery, dependency injection, loggers, and long-running processes with concrete code examples, while architecture/Docs markdown files provide comprehensive design coverage. The overview is present in each document (the first paragraph of every guide), and all visible sections are named in the outline; there are no missing-overview or unstructured issues.

Documentation: no project overviewdocs/index.md

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

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 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs found

What to do

Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.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 ConsistencyStrong◐ Sampled · advisory

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

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

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

2 API inconsistencies across a 400-member sample of 247 exposed types.

Duplicate Logger Interface: `DebugLogger` exposes the exact same method signatures as the `Logger` interface. This creates redundancy where consumers must choose between a generic interface and a specific implementation that looks identical, potentially causing confusion about which to depend on.

Inconsistent Provision Options Naming: `Transport` uses `TransportProvisionOptions` while `Persistence` uses `PersistenceProvisionOptions`. While the types are distinct, the naming convention is inconsistent with the initialization options (`TransportInitializationOptions` vs `PersistenceInitializationOptions`) and lacks a shared base interface or unified naming pattern for 'ProvisionOptions' across the transport/persistence abstraction.

What to do

Resolve the 1 Duplicate Logger Interface finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Inconsistent Provision Options Naming 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-Coupling9.1 / 10Stronggated by 24 serious findings✓ Tool-verified

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

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

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

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

24 domain type(s) cross context boundaries across 13 contexts.

Cross-context type MessageDeclaration (bus-messages → bus-core) · ×24packages/bus-core/src/handler/handler.ts:30

What to do

Resolve the 24 Cross-context type MessageDeclaration (bus-messages → bus-core) finding(s) in Boundary Type-Coupling — start with define-workflow.ts (5), recorded-messages.ts (3), handler-for.ts (2). — One of this dimension's main actionable groups (24 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 Cohesion8.5 / 10Strong✓ 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 8.5 / 10 · rule-coverage 100% · ceiling Documented

1 of 13 build units (npm) flagged as possibly oversized/incoherent.

Split packages/bus-core

What to do

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

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

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)1.2 / 10Critical✓ Tool-verified

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

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

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

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

19 finding(s): 0 critical, 19 high, 0 medium, 0 low. 7 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `docs/scripts/sync-readmes.mjs` (line 126), `packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts` (line 89, line 90), `packages/bus-core/src/workflow/workflow.ts` (line 188, line 189) — 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.

REDACTED

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

What to do

Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 7 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 (7 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 Vulnerabilities1.7 / 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 1.7 / 10 · rule-coverage 100% · ceiling Documented

17 finding(s): 1 critical, 10 high, 4 medium, 2 low.

REDACTED

What to do

Resolve the 10 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10). — One of this dimension's main actionable groups (10 issue-level).
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-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 Security9.4 / 10Stronggated by 6 serious findings✓ Tool-verified

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 9.4 / 10 · rule-coverage 100% · ceiling Documented

6 finding(s): 0 critical, 0 high, 6 medium, 0 low.

REDACTED

What to do

Resolve the 6 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).

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

Do you agree with this assessment?

D32 · Data Compliance (PII/GDPR)7.1 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.

Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using Watchdog's own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.

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

1 finding(s): 0 critical, 1 high, 0 medium, 0 low. semgrep could not parse 3 file(s) — `docs/scripts/sync-readmes.mjs`, `packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts`, `packages/bus-core/src/workflow/workflow.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.

REDACTED

What to do

Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d32_recommendation.md · top locations in Appendix A, every location in findings.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 121 of the 393 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 Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

REDACTED

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. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

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?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AX10 · Code composition9.7 / 10Exemplary✓ Tool-verified

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

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

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

What to do

The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.

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?

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

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

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

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?

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 & stubs6.8 / 10Adequate✓ Tool-verified

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.

`insertOne` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — docs/snippets/mongodb-outbox-testing.ts:14
`charge` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — docs/snippets/nestjs-testing.ts:28
`charge` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×2) — docs/snippets/nestjs.ts:38, docs/snippets/services/index.ts:9
`record` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×2) — docs/snippets/nestjs.ts:43, docs/snippets/services/index.ts:20
`reserveRoom` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — docs/snippets/services/index.ts:5
`ship` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — docs/snippets/services/index.ts:24
`write` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — docs/snippets/services/index.ts:35
`read` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — docs/snippets/services/index.ts:39
`initialize` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/bus-core/src/workflow/registry/workflow-registry.ts:203

What to do

Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.

Do you agree with this assessment?

M1 · Documentation (README)8.0 / 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.

What to do

Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.

Do you agree with this assessment?

M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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

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

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

What to do

Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.

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.

CONTRIBUTING.md runs `pnpm changeset`, but no package.json declares a `changeset` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:70
.changeset/README.md runs `pnpm changeset`, but no package.json declares a `changeset` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — .changeset/README.md:3
docs/persistence.md links to `/guide/outbox`, but `guide/outbox` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/persistence.md:20
docs/getting-started/handling-messages.md links to `/api/bus-core/interfaces/HandlerContext`, but `api/bus-core/interfaces/HandlerContext` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/getting-started/handling-messages.md:20
docs/getting-started/handling-messages.md links to `/guide/workflows/request-reply`, but `guide/workflows/request-reply` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/getting-started/handling-messages.md:20
docs/getting-started/installation.md links to `/transports`, but `transports` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/getting-started/installation.md:63
docs/guide/delayed-delivery.md links to `/persistence`, but `persistence` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/delayed-delivery.md:32
docs/guide/delayed-delivery.md links to `/guide/middleware#outgoing-middleware`, but `guide/middleware` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/delayed-delivery.md:36
docs/guide/delayed-delivery.md links to `/persistence/postgres`, but `persistence/postgres` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/delayed-delivery.md:61
docs/guide/delayed-delivery.md links to `/persistence/mongodb`, but `persistence/mongodb` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/delayed-delivery.md:62
docs/guide/dependency-injection.md links to `/guide/nestjs`, but `guide/nestjs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/dependency-injection.md:30
docs/guide/loggers.md links to `/guide/loggers/custom-loggers`, but `guide/loggers/custom-loggers` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/loggers.md:18
docs/guide/middleware.md links to `/transports/sqs-lambda`, but `transports/sqs-lambda` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/middleware.md:30
docs/guide/middleware.md links to `/getting-started/handling-messages`, but `getting-started/handling-messages` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/middleware.md:30
docs/guide/middleware.md links to `/guide/opentelemetry`, but `guide/opentelemetry` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/middleware.md:40
docs/guide/middleware.md links to `/guide/recoverability`, but `guide/recoverability` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/middleware.md:52
docs/guide/middleware.md links to `/guide/workflows/request-reply`, but `guide/workflows/request-reply` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/middleware.md:80
docs/guide/middleware.md links to `/transports/rabbitmq`, but `transports/rabbitmq` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/middleware.md:102
docs/guide/middleware.md links to `/transports/amazon-sqs`, but `transports/amazon-sqs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/middleware.md:103
docs/guide/middleware.md links to `/upgrading/v2`, but `upgrading/v2` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/middleware.md:132
docs/guide/multiple-buses.md links to `/api/bus-core/interfaces/HandlerContext`, but `api/bus-core/interfaces/HandlerContext` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/multiple-buses.md:19
docs/guide/nestjs.md links to `/getting-started/handling-messages`, but `getting-started/handling-messages` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/nestjs.md:34
docs/guide/nestjs.md links to `/guide/serializers/message-types`, but `guide/serializers/message-types` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/nestjs.md:34
docs/guide/nestjs.md links to `/guide/multiple-buses`, but `guide/multiple-buses` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/nestjs.md:72
docs/guide/opentelemetry.md links to `/guide/middleware`, but `guide/middleware` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/opentelemetry.md:8
docs/guide/opentelemetry.md links to `/guide/message-attributes/message-id`, but `guide/message-attributes/message-id` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/opentelemetry.md:77
docs/guide/opentelemetry.md links to `/guide/message-attributes/correlation-id`, but `guide/message-attributes/correlation-id` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/opentelemetry.md:78
docs/guide/opentelemetry.md links to `/guide/message-attributes/attributes`, but `guide/message-attributes/attributes` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/opentelemetry.md:88
docs/guide/opentelemetry.md links to `/guide/recoverability`, but `guide/recoverability` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/opentelemetry.md:104
docs/guide/outbox.md links to `/persistence/postgres`, but `persistence/postgres` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/outbox.md:25
docs/guide/outbox.md links to `/persistence/mongodb`, but `persistence/mongodb` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/outbox.md:27
docs/guide/outbox.md links to `/persistence/custom`, but `persistence/custom` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/outbox.md:28
docs/guide/outbox.md links to `/guide/delayed-delivery`, but `guide/delayed-delivery` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/outbox.md:28
docs/guide/outbox.md links to `/guide/workflows/request-reply`, but `guide/workflows/request-reply` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/outbox.md:35
docs/guide/outbox.md links to `/guide/recoverability`, but `guide/recoverability` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/outbox.md:38
docs/guide/outbox.md links to `/guide/middleware#outgoing-middleware`, but `guide/middleware` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/outbox.md:40
docs/guide/outbox.md links to `/guide/testing#testing-a-handler`, but `guide/testing` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/outbox.md:90
docs/guide/provisioning.md links to `/transports/amazon-sqs#provisioning`, but `transports/amazon-sqs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/provisioning.md:16
docs/guide/provisioning.md links to `/transports/rabbitmq#provisioning`, but `transports/rabbitmq` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/provisioning.md:17
docs/guide/provisioning.md links to `/transports/postgres#provisioning`, but `transports/postgres` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/provisioning.md:18

What to do

Reconcile the README with reality: CONTRIBUTING.md runs `pnpm changeset`, but no package.json declares a `changeset` script; .changeset/README.md runs `pnpm changeset`, but no package.json declares a `changeset` script; docs/persistence.md links to `/guide/outbox`, but `guide/outbox` does not exist; docs/getting-started/handling-messages.md links to `/api/bus-core/interfaces/HandlerContext`, but `api/bus-core/interfaces/HandlerContext` does not exist; docs/getting-started/handling-messages.md links to `/guide/workflows/request-reply`, but `guide/workflows/request-reply` 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.7 / 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 8/9 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/bus-cli`.
`packages/bus-core/src/middleware/middleware.ts` reports through `console.*` at line 24 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/bus-core/src/middleware/middleware.ts:24
`packages/bus-core/src/middleware/handler-invocation-context.ts` reports through `console.*` at line 9 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/bus-core/src/middleware/handler-invocation-context.ts:9
`packages/bus-core/src/middleware/bus-middleware.ts` reports through `console.*` at line 16 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/bus-core/src/middleware/bus-middleware.ts:16
`packages/bus-core/src/recoverability/failure-header.ts` reports through `console.*` at line 24 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/bus-core/src/recoverability/failure-header.ts:24
`packages/bus-core/src/service-bus/bus-configuration.ts` reports through `console.*` at line 574 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/bus-core/src/service-bus/bus-configuration.ts:574

What to do

Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.

Do you agree with this assessment?

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

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

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

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

What to do

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

Do you agree with this assessment?

P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

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

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

What to do

The pipeline declares a deployment environment, but whether required reviewers / protection rules are attached to it lives in repository settings we cannot read — confirm the gate is enforced before production promotion.

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?

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.

a busy-wait on the clock in `callback to beforeAll` 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/bus-test/src/inbox-tests.ts:504

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

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

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

Do you agree with this assessment?

R10 · Code Duplication8.6 / 10Strong✓ Tool-verified

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

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

44 duplicated blocks under packages/ have copies in at least two of the sibling directories bus-cli, bus-core, bus-messages, bus-mongodb, bus-nestjs, bus-opentelemetry (+4 more sibling(s) not listed) — 23 of them are reported below, and 21 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 44 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 44 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 44 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/bus-mongodb/src/mongodb-persistence.ts:124
22 duplicated blocks under packages/bus-core/src/ have copies in at least two of the sibling directories handler, message-handling-context, message-lifecycle-context, service-bus, transport, workflow — 5 of them are reported below, and 17 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 22 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 22 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 22 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/bus-core/src/service-bus/bus-instance-reply.integration.ts:128
packages/bus-mongodb/src/mongodb-persistence.ts:124 · packages/bus-postgres/src/postgres-persistence.ts:277 — the two spans are one implementation copied and then locally edited — 754 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/bus-mongodb/src/mongodb-persistence.ts:124
packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts:458 · packages/bus-opentelemetry/src/open-telemetry.integration.ts:63 — the two spans are one implementation copied and then locally edited — 606 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/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts:458
packages/bus-postgres/src/postgres-transport.ts:344 · packages/bus-redis/src/redis-transport.ts:517 — the two spans are one implementation copied and then locally edited — 500 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/bus-postgres/src/postgres-transport.ts:344
packages/bus-mongodb/src/mongo-session.integration.ts:48 · packages/bus-postgres/src/postgres-transaction.integration.ts:40 — the two spans are one implementation copied and then locally edited — 474 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/bus-mongodb/src/mongo-session.integration.ts:48
packages/bus-mongodb/src/mongo-session.integration.ts:212 · packages/bus-postgres/src/postgres-transaction.integration.ts:145 — the two spans are one implementation copied and then locally edited — 406 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/bus-mongodb/src/mongo-session.integration.ts:212
packages/bus-mongodb/src/mongodb-persistence.integration.ts:455 · packages/bus-postgres/src/postgres-persistence.integration.ts:157 — the two spans are one implementation copied and then locally edited — 298 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/bus-mongodb/src/mongodb-persistence.integration.ts:455
packages/bus-core/src/service-bus/bus-instance-recoverability.integration.ts:200 · packages/bus-core/src/service-bus/bus-instance-recoverability.integration.ts:378 — the two spans are one implementation copied and then locally edited — 278 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/bus-core/src/service-bus/bus-instance-recoverability.integration.ts:200
packages/bus-mongodb/src/mongodb-persistence.integration.ts:557 · packages/bus-postgres/src/postgres-persistence.integration.ts:230 — 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/bus-mongodb/src/mongodb-persistence.integration.ts:557
packages/bus-core/src/service-bus/bus-instance-reply.integration.ts:128 · packages/bus-core/src/workflow/define-workflow.integration.ts:214 — the two spans are one implementation copied and then locally edited — 242 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/bus-core/src/service-bus/bus-instance-reply.integration.ts:128
packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts:212 · packages/bus-sqs/src/sqs-transport.integration.ts:306 — 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/bus-rabbitmq/src/rabbitmq-transport.integration.ts:212
packages/bus-mongodb/src/mongodb-persistence-transaction.ts:130 · packages/bus-postgres/src/postgres-persistence-transaction.ts:70 — the two spans are one implementation copied and then locally edited — 169 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/bus-mongodb/src/mongodb-persistence-transaction.ts:130
packages/bus-core/src/service-bus/bus-instance-message-types.integration.ts:102 · packages/bus-core/src/service-bus/bus-instance-message-types.integration.ts:146 — the two spans are one implementation copied and then locally edited — 178 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/bus-core/src/service-bus/bus-instance-message-types.integration.ts:102
packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:755 · packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:860 — 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/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:755
packages/bus-core/src/workflow/workflow.integration.ts:143 · packages/bus-core/src/workflow/workflow.integration.ts:174 — 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/bus-core/src/workflow/workflow.integration.ts:143
packages/bus-core/src/workflow/define-workflow-concurrency.integration.ts:77 · packages/bus-core/src/workflow/workflow-concurrency.integration.ts:83 — the two spans are one implementation copied and then locally edited — 108 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/bus-core/src/workflow/define-workflow-concurrency.integration.ts:77
packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts:362 · packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts:431 — 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/bus-core/src/service-bus/bus-instance-inbox.integration.ts:362
packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts:217 · packages/bus-opentelemetry/src/transport-propagation.integration.ts:118 — the two spans are one implementation copied and then locally edited — 101 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/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts:217
packages/bus-postgres/src/postgres-transport.ts:348 · packages/bus-redis/src/redis-transport.ts:522 · packages/bus-sqs/src/sqs-transport.ts:285 — 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/bus-postgres/src/postgres-transport.ts:348
packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts:596 · packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts:723 — 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/bus-core/src/service-bus/bus-instance-middleware.integration.ts:596
packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts:414 · packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts:441 — 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/bus-rabbitmq/src/rabbitmq-transport.integration.ts:414
packages/bus-core/src/service-bus/bus-instance-handler-context.integration.ts:197 · packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:233 — 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/bus-core/src/service-bus/bus-instance-handler-context.integration.ts:197
packages/bus-core/src/service-bus/bus-instance-isolation.integration.ts:23 · packages/bus-core/src/service-bus/bus-instance-isolation.integration.ts:46 — all 2 copies are in the same file, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited. — packages/bus-core/src/service-bus/bus-instance-isolation.integration.ts:23
packages/bus-core/src/service-bus/bus-instance.integration.ts:363 · packages/bus-core/src/service-bus/bus-instance.integration.ts:400 — 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/bus-core/src/service-bus/bus-instance.integration.ts:363
packages/bus-postgres/src/postgres-transport.integration.ts:208 · packages/bus-postgres/src/postgres-transport.integration.ts:252 — 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/bus-postgres/src/postgres-transport.integration.ts:208
packages/bus-core/src/service-bus/bus-instance-recoverability.integration.ts:282 · packages/bus-core/src/service-bus/bus-instance-recoverability.integration.ts:469 — 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/bus-core/src/service-bus/bus-instance-recoverability.integration.ts:282
packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts:276 · packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts:340 — 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/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts:276
packages/bus-core/src/workflow/workflow-startedby.integration.ts:36 · packages/bus-core/src/workflow/workflow-startedby.integration.ts:56 — 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/bus-core/src/workflow/workflow-startedby.integration.ts:36
packages/bus-cli/src/generate-message-types/run-generate-message-types.integration.ts:107 · packages/bus-core/src/handler/handler-for.integration.ts:24 — 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/bus-cli/src/generate-message-types/run-generate-message-types.integration.ts:107
packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:251 · packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:306 — 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/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:251
packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:518 · packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:578 — 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/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:518
packages/bus-core/src/service-bus/bus-instance.integration.ts:211 · packages/bus-core/src/workflow/workflow-startedby.integration.ts:83 — the two spans are one implementation copied and then locally edited — 77 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/bus-core/src/service-bus/bus-instance.integration.ts:211
packages/bus-cli/src/provision/run-provision.integration.ts:66 · packages/bus-cli/src/provision/run-provision.integration.ts:86 · packages/bus-cli/src/provision/run-provision.integration.ts:105 — all 3 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/bus-cli/src/provision/run-provision.integration.ts:66
packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:622 · packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:693 — 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/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:622
packages/bus-mongodb/src/mongodb-persistence.integration.ts:298 · packages/bus-mongodb/src/mongodb-persistence.integration.ts:340 — 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/bus-mongodb/src/mongodb-persistence.integration.ts:298
packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts:139 · packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts:297 — 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/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts:139
packages/bus-cli/src/generate-message-types/run-generate-message-types.integration.ts:281 · packages/bus-core/src/handler/handler-for.integration.ts:208 — 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/bus-cli/src/generate-message-types/run-generate-message-types.integration.ts:281
packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts:547 · packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts:701 — 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/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts:547
packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts:126 · packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts:675 — 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/bus-core/src/service-bus/bus-instance-dispatched.integration.ts:126

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?

R11 · Import Boundaries0.0 / 10Critical✓ Tool-verified

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

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

packages/bus-core/src/handler/handler-for.integration.ts:7 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/handler/handler-for.integration.ts:7
packages/bus-core/src/handler/handler.integration.ts:6 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/handler/handler.integration.ts:6
packages/bus-core/src/handler/handler.integration.ts:13 imports packages/bus-core/src/test/test-command.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/handler/handler.integration.ts:13
packages/bus-core/src/handler/handler.integration.ts:14 imports packages/bus-core/src/test/test-command-3.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/handler/handler.integration.ts:14
packages/bus-core/src/handler/handler.integration.ts:15 imports packages/bus-core/src/test/test-command-getter-class-handler.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/handler/handler.integration.ts:15
packages/bus-core/src/handler/handler.integration.ts:16 imports packages/bus-core/src/test/test-event.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/handler/handler.integration.ts:16
packages/bus-core/src/handler/handler.integration.ts:17 imports packages/bus-core/src/test/test-event-class-handler.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/handler/handler.integration.ts:17
packages/bus-core/src/service-bus/bus-instance-concurrency.integration.ts:4 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-concurrency.integration.ts:4
packages/bus-core/src/service-bus/bus-instance-concurrency.integration.ts:5 imports packages/bus-core/src/test/test-command.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-concurrency.integration.ts:5
packages/bus-core/src/service-bus/bus-instance-concurrency.integration.ts:6 imports packages/bus-core/src/test/test-event.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-concurrency.integration.ts:6
packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts:15 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts:15
packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts:16 imports packages/bus-core/src/test/test-command.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts:16
packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts:17 imports packages/bus-core/src/test/test-event.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts:17
packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts:14 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts:14
packages/bus-core/src/service-bus/bus-instance-handler-context.integration.ts:7 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-handler-context.integration.ts:7
packages/bus-core/src/service-bus/bus-instance-handler-context.integration.ts:19 imports packages/bus-core/src/workflow/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-handler-context.integration.ts:19
packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts:9 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts:9
packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts:10 imports packages/bus-core/src/test/test-command.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts:10
packages/bus-core/src/service-bus/bus-instance-isolation.integration.ts:11 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-isolation.integration.ts:11
packages/bus-core/src/service-bus/bus-instance-message-types.integration.ts:6 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-message-types.integration.ts:6
packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts:14 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts:14
packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:8 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:8
packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:13 imports packages/bus-core/src/test/test-command.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:13
packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:14 imports packages/bus-core/src/test/test-command-2.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:14
packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:15 imports packages/bus-core/src/test/test-event.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:15
packages/bus-core/src/service-bus/bus-instance-provisioning.integration.ts:6 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-provisioning.integration.ts:6
packages/bus-core/src/service-bus/bus-instance-provisioning.integration.ts:7 imports packages/bus-core/src/test/test-event.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-provisioning.integration.ts:7
packages/bus-core/src/service-bus/bus-instance-provisioning.integration.ts:22 imports packages/bus-core/src/workflow/test/test-function-workflow.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-provisioning.integration.ts:22
packages/bus-core/src/service-bus/bus-instance-provisioning.integration.ts:26 imports packages/bus-core/src/workflow/test/test-workflow-state.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-provisioning.integration.ts:26
packages/bus-core/src/service-bus/bus-instance-receiver.integration.ts:17 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-receiver.integration.ts:17
packages/bus-core/src/service-bus/bus-instance-receiver.integration.ts:24 imports packages/bus-core/src/test/test-command-3.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-receiver.integration.ts:24
packages/bus-core/src/service-bus/bus-instance-recoverability.integration.ts:15 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-recoverability.integration.ts:15
packages/bus-core/src/service-bus/bus-instance-reply.integration.ts:13 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-reply.integration.ts:13
packages/bus-core/src/service-bus/bus-instance-reply.integration.ts:35 imports packages/bus-core/src/workflow/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-reply.integration.ts:35
packages/bus-core/src/service-bus/bus-instance-requested-settlement.integration.ts:7 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-requested-settlement.integration.ts:7
packages/bus-core/src/service-bus/bus-instance-return-message.integration.ts:4 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-return-message.integration.ts:4
packages/bus-core/src/service-bus/bus-instance-return-message.integration.ts:5 imports packages/bus-core/src/test/test-command.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-return-message.integration.ts:5
packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts:14 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts:14
packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts:19 imports packages/bus-core/src/test/test-command.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts:19
packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts:20 imports packages/bus-core/src/test/test-event.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts:20

What to do

Fix the listed violations: move the shared test helper into a source directory production code may depend on (56 rows).

Do you agree with this assessment?

R2 · Cyclomatic Complexity9.9 / 10Exemplary✓ Tool-verified

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

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

(anonymous) has cyclomatic complexity 23 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/bus-core/src/serialization/message-type-reviver.ts:82
describeObjectType has cyclomatic complexity 19 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/bus-cli/src/generate-message-types/message-type-reader.ts:891
(anonymous) 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/bus-cli/src/generate-message-types/is-same-message-types.ts:56
describeObject has cyclomatic complexity 16 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/bus-cli/src/generate-message-types/message-type-reader.ts:785
(anonymous) has cyclomatic complexity 15 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/bus-cli/src/generate-message-types/is-same-message-types.ts:12
(anonymous) has cyclomatic complexity 15 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/bus-cli/src/generate-message-types/generate-message-types.ts:104
evaluateString has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/bus-cli/src/generate-message-types/message-type-reader.ts:605
findRegistrations has cyclomatic complexity 13 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/bus-nestjs/src/bus-lifecycle-host.ts:240
resolveDueAt has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/bus-core/src/service-bus/bus-instance.ts:1829
(anonymous) has cyclomatic complexity 12 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/bus-cli/src/provision/run-provision.ts:89
settleMessage has cyclomatic complexity 12 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/bus-core/src/service-bus/bus-instance.ts:1289
messageNameOf has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/bus-cli/src/generate-message-types/message-type-reader.ts:493
describe has cyclomatic complexity 12 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/bus-cli/src/generate-message-types/message-type-reader.ts:724
(anonymous) has cyclomatic complexity 12 and cognitive complexity 10; 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/bus-core/src/outgoing-message/assert-delivery-options.ts:17
readSourceFile has cyclomatic complexity 11 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/bus-cli/src/generate-message-types/message-type-reader.ts:179
readObjectTypeMessage 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/bus-cli/src/generate-message-types/message-type-reader.ts:336
(anonymous) has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/bus-cli/src/generate-message-types/run-generate-message-types.ts:69
provision has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/bus-core/src/service-bus/bus-instance.ts:658
initialize has cyclomatic complexity 11 and cognitive complexity 10; 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/bus-core/src/service-bus/bus-instance.ts:585

What to do

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

Do you agree with this assessment?

R3 · Large Files6.2 / 10Adequate✓ Tool-verified

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

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

packages/bus-core/src/service-bus/bus-instance.ts has 2537 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/bus-core/src/service-bus/bus-instance.ts:1
packages/bus-sqs/src/sqs-transport.ts has 1496 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/bus-sqs/src/sqs-transport.ts:1
packages/bus-rabbitmq/src/rabbitmq-transport.ts has 1359 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/bus-rabbitmq/src/rabbitmq-transport.ts:1
packages/bus-redis/src/redis-transport.ts has 1336 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/bus-redis/src/redis-transport.ts:1
packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts has 1136 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/bus-rabbitmq/src/rabbitmq-transport.integration.ts:1
packages/bus-postgres/src/postgres-persistence.ts has 1059 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/bus-postgres/src/postgres-persistence.ts:1
packages/bus-cli/src/generate-message-types/message-type-reader.ts has 1023 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/bus-cli/src/generate-message-types/message-type-reader.ts:1
packages/bus-postgres/src/postgres-transport.ts has 962 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/bus-postgres/src/postgres-transport.ts:1
packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts has 946 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/bus-core/src/service-bus/bus-instance-middleware.integration.ts:1
packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts has 929 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/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts:1
packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts has 881 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/bus-core/src/service-bus/bus-instance-dispatched.integration.ts:1
packages/bus-mongodb/src/mongodb-persistence.ts has 880 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/bus-mongodb/src/mongodb-persistence.ts:1
packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts has 828 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/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:1
packages/bus-redis/src/redis-transport.integration.ts has 826 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/bus-redis/src/redis-transport.integration.ts:1
packages/bus-postgres/src/postgres-persistence.integration.ts has 806 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/bus-postgres/src/postgres-persistence.integration.ts:1
packages/bus-postgres/src/postgres-transport.integration.ts has 796 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/bus-postgres/src/postgres-transport.integration.ts:1
packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts has 718 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/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts:1
packages/bus-core/src/workflow/registry/workflow-registry.ts has 714 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/bus-core/src/workflow/registry/workflow-registry.ts:1
packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts has 704 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/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts:1
packages/bus-nestjs/src/bus-module.integration.ts has 699 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/bus-nestjs/src/bus-module.integration.ts:1
packages/bus-mongodb/src/mongodb-persistence.integration.ts has 648 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/bus-mongodb/src/mongodb-persistence.integration.ts:1
packages/bus-core/src/outgoing-message/outgoing-message-dispatcher.ts has 635 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/bus-core/src/outgoing-message/outgoing-message-dispatcher.ts:1
packages/bus-core/src/service-bus/bus-configuration.ts has 625 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/bus-core/src/service-bus/bus-configuration.ts:1
packages/bus-core/src/service-bus/bus-instance-reply.integration.ts has 622 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/bus-core/src/service-bus/bus-instance-reply.integration.ts:1
packages/bus-core/src/workflow/persistence/in-memory-persistence.ts has 566 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/bus-core/src/workflow/persistence/in-memory-persistence.ts:1
packages/bus-test/src/scheduled-message-round-trip-tests.ts has 552 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/bus-test/src/scheduled-message-round-trip-tests.ts:1
packages/bus-core/src/service-bus/bus-instance.integration.ts has 550 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/bus-core/src/service-bus/bus-instance.integration.ts:1
packages/bus-cli/src/generate-message-types/run-generate-message-types.integration.ts has 530 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/bus-cli/src/generate-message-types/run-generate-message-types.integration.ts:1
packages/bus-core/src/testing/test-workflow.ts has 522 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/bus-core/src/testing/test-workflow.ts:1
packages/bus-test/src/transport-tests.ts has 518 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/bus-test/src/transport-tests.ts:1
packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts has 503 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/bus-core/src/service-bus/bus-instance-inbox.integration.ts:1
packages/bus-sqs/src/sqs-transport.integration.ts has 503 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/bus-sqs/src/sqs-transport.integration.ts:1
packages/bus-core/src/service-bus/bus-instance-recoverability.integration.ts has 478 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/bus-core/src/service-bus/bus-instance-recoverability.integration.ts:1
packages/bus-test/src/inbox-tests.ts has 472 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/bus-test/src/inbox-tests.ts:1
packages/bus-core/src/workflow/workflow.integration.ts has 425 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/bus-core/src/workflow/workflow.integration.ts:1
packages/bus-opentelemetry/src/open-telemetry.ts has 412 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/bus-opentelemetry/src/open-telemetry.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.9 / 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. (×2) — tools/check-packages.mjs:1, packages/bus-cli/bus.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 package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

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

Do you agree with this assessment?

R7 · Dead Code9.9 / 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.

2 file(s) (~10 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: packages/bus-cli/test/imports-generated/src/index.ts imports './message-types.generated.js', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — packages/bus-cli/test/imports-generated
1 file(s) (~16 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/bus-cli/test/non-strict
1 file(s) (~46 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/bus-cli/test/provision
Nothing imports this binding — it is safe to review for removal. — packages/bus-core/src/serialization/message-type-reviver.ts:13
This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments. — packages/bus-core/src/workflow/persistence/in-memory-persistence.ts:99

What to do

Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.

Do you agree with this assessment?

R8 · Dependency Hygiene0.0 / 10Critical✓ 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.

Declared in packages/bus-cli/package.json 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/bus-core/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)

What to do

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

Do you agree with this assessment?

R9 · Circular Imports6.3 / 10Adequate✓ 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.

packages/bus-core/src/container/container-adapter.ts → packages/bus-core/src/util/index.ts → packages/bus-core/src/util/core-dependencies.ts → packages/bus-core/src/container/index.ts → packages/bus-core/src/container/container-adapter.ts (one verified cycle inside a mutually-dependent group of 22 files) — packages/bus-core/src/container/container-adapter.ts:2

What to do

Break each cycle by extracting the shared piece into a module both sides can import.

Do you agree with this assessment?

S1 · Web-Security Posture6.0 / 10Adequate✓ 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. 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. Its Node HTTP listeners were read for HTTPS enforcement alone — TLS served, a redirect to https:// or HSTS, or a TLS-terminating proxy configuration committed beside the server — each judged per server package.

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.

MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×2) — packages/bus-postgres/src/postgres-transport.ts:97, packages/bus-redis/src/redis-scripts.ts:24
`app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — docs/snippets/nestjs.ts:135

What to do

Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 2 sites, not one: `packages/bus-postgres/src/postgres-transport.ts:97` (createHash("md5")), `packages/bus-redis/src/redis-scripts.ts:24` (createHash("sha1")). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.

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 document3.5 / 10Weak✓ Tool-verified

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

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

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

What to do

Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.

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 materialisation7.2 / 10Strong✓ 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 1926 is called with an argument built by `toStore.map(({ id, kind, dueAt }) => ({ id, kind, dueAt }))` (line 1927), 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/bus-core/src/service-bus/bus-instance.ts:1926
`debug` at line 727 is called with an argument built by `indexes.map(({ name }) => name)` (line 729), 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/bus-mongodb/src/mongodb-persistence.ts:727
`debug` at line 915 is called with an argument built by `entries.map(({ id }) => id)` (line 917), 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/bus-redis/src/redis-transport.ts:915

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 handling7.9 / 10Strong✓ 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. — packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts:159

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?

X4 · Structured logging10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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 `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

Do you agree with this assessment?

X5 · Nullable reference types8.6 / 10Strong✓ Tool-verified

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

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

21/22 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.
~2.7 `!` null assertions per 1k TypeScript source lines — 139 assertion(s) across the 52231 source line(s) of the 425 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/bus-rabbitmq/src/rabbitmq-transport.integration.ts (32), packages/bus-sqs/src/sqs-transport.ts (28), packages/bus-core/src/service-bus/bus-instance-reply.integration.ts (7). 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?

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	77%	Strong	Solid.
Architecture	60%	Adequate — gated by R11	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity	44%	Weak — gated by M2, M4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	55%	Adequate — gated by R8, P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	63%	Adequate — gated by D29, D30, D36	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance	85%	Strong	Strongest area.

Unscored — 2 check(s) recorded observations but carry no score

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

P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — 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 — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score.

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

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

C3 Audit Trail — Not assessed: this repository stores data through 'mongodb' (docs/snippets/mongodb-outbox.ts:3) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
C4 Data Retention — Not assessed: this repository stores data through 'mongodb' (docs/snippets/mongodb-outbox.ts:3) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
C5 Data-Subject Rights — Not assessed: this repository stores data through 'mongodb' (docs/snippets/mongodb-outbox.ts:3) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control

Not included — 47 check(s) not relevant to this codebase

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

AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: 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).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
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) — mongo Pulling rabbitmq Pulling postgres Pulling redis Pulling localstack Pulling valkey Pulling localstack Error Get "https://registry-1.docker.io/v2/": Forbidden mongo Error context canceled postgres Error context canceled redis Error context canceled rabbitmq Error context canceled valkey Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: mongo Pulling valkey Pulling postgres Pulling localstack Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden valkey Error Get "https://registry-1.docker.io/v2/": Forbidden mongo Error context canceled localstack Error context canceled rabbitmq Error context canceled redis Error context canceled 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 — Not assessed: this repository stores data through 'mongodb' (docs/snippets/mongodb-outbox.ts:3) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.mjs,.ts), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D4 Code Duplication — This repository's production source (.mts, .ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 domain event(s); its domain events are published by services or handlers — no domain entity raises one)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: docs/snippets/nestjs.ts:132 (NestFactory.create))
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage data present for 145 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: 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.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 32 finding(s)

D30 · Dependency Vulnerabilities · High CVE · ×10

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D30 · Dependency Vulnerabilities · Critical CVE · ×1

REDACTED

D32 · Data Compliance (PII/GDPR) · REDACTED · ×1

REDACTED

R9 · Circular Imports · Import cycle (4 files) · ×1

Import cycle (4 files) packages/bus-core/src/container/container-adapter.ts:2 — packages/bus-core/src/container/container-adapter.ts → packages/bus-core/src/util/index.ts → packages/bus-core/src/util/core-dependencies.ts → packages/bus-core/src/container/index.ts → packages/bus-core/src/container/container-adapter.ts (one verified cycle inside a mutually-dependent group of 22 files)

Serious — 329 finding(s)

D8 · Code Coverage · Low coverage · ×75

Low coverage: jest.config.ts jest.config.ts:1 — 0.0% line coverage (0/2).
Low coverage: packages/bus-cli/src/cli.ts packages/bus-cli/src/cli.ts:1 — 0.0% line coverage (0/14).
Low coverage: packages/bus-cli/src/index.ts packages/bus-cli/src/index.ts:1 — 0.0% line coverage (0/2).
Low coverage: packages/bus-cli/src/generate-message-types/index.ts packages/bus-cli/src/generate-message-types/index.ts:1 — 0.0% line coverage (0/3).
Low coverage: packages/bus-cli/src/generate-message-types/is-same-message-types.ts packages/bus-cli/src/generate-message-types/is-same-message-types.ts:1 — 0.0% line coverage (0/52).
Low coverage: packages/bus-cli/src/generate-message-types/run-generate-message-types.ts packages/bus-cli/src/generate-message-types/run-generate-message-types.ts:1 — 0.0% line coverage (0/65).
Low coverage: packages/bus-cli/src/provision/format-provision-report.ts packages/bus-cli/src/provision/format-provision-report.ts:1 — 0.0% line coverage (0/16).
Low coverage: packages/bus-cli/src/provision/index.ts packages/bus-cli/src/provision/index.ts:1 — 0.0% line coverage (0/2).
Low coverage: packages/bus-core/src/index.ts packages/bus-core/src/index.ts:1 — 0.0% line coverage (0/16).
Low coverage: packages/bus-core/src/container/index.ts packages/bus-core/src/container/index.ts:1 — 0.0% line coverage (0/1).
Low coverage: packages/bus-core/src/handler/index.ts packages/bus-core/src/handler/index.ts:1 — 0.0% line coverage (0/8).
Low coverage: packages/bus-core/src/logger/index.ts packages/bus-core/src/logger/index.ts:1 — 0.0% line coverage (0/3).
Low coverage: packages/bus-core/src/message-handling-context/index.ts packages/bus-core/src/message-handling-context/index.ts:1 — 0.0% line coverage (0/1).
Low coverage: packages/bus-core/src/message-lifecycle-context/index.ts packages/bus-core/src/message-lifecycle-context/index.ts:1 — 0.0% line coverage (0/1).
Low coverage: packages/bus-core/src/message-lifecycle-context/message-lifecycle-context.ts packages/bus-core/src/message-lifecycle-context/message-lifecycle-context.ts:1 — 0.0% line coverage (0/12).
Low coverage: packages/bus-core/src/middleware/index.ts packages/bus-core/src/middleware/index.ts:1 — 0.0% line coverage (0/7).
Low coverage: packages/bus-core/src/middleware/middleware-pipeline.ts packages/bus-core/src/middleware/middleware-pipeline.ts:1 — 0.0% line coverage (0/19).
Low coverage: packages/bus-core/src/middleware/requested-settlement.ts packages/bus-core/src/middleware/requested-settlement.ts:1 — 0.0% line coverage (0/3).
Low coverage: packages/bus-core/src/outbox/buffered-workflow-state-store.ts packages/bus-core/src/outbox/buffered-workflow-state-store.ts:1 — 0.0% line coverage (0/18).
Low coverage: packages/bus-core/src/outbox/inbox-cleanup.ts packages/bus-core/src/outbox/inbox-cleanup.ts:1 — 0.0% line coverage (0/3).
Low coverage: packages/bus-core/src/outbox/inbox-retention.ts packages/bus-core/src/outbox/inbox-retention.ts:1 — 0.0% line coverage (0/1).
Low coverage: packages/bus-core/src/outbox/index.ts packages/bus-core/src/outbox/index.ts:1 — 0.0% line coverage (0/3).
Low coverage: packages/bus-core/src/outbox/outbox-persistence.ts packages/bus-core/src/outbox/outbox-persistence.ts:1 — 0.0% line coverage (0/3).
Low coverage: packages/bus-core/src/outbox/unit-of-work-context.ts packages/bus-core/src/outbox/unit-of-work-context.ts:1 — 0.0% line coverage (0/8).
Low coverage: packages/bus-core/src/outgoing-message/index.ts packages/bus-core/src/outgoing-message/index.ts:1 — 0.0% line coverage (0/5).
+ 50 more in this group — see findings.md.

R11 · Import Boundaries · Boundary violation [package · ×40

Boundary violation [package:test-suite-dependency] packages/bus-core/src/handler/handler-for.integration.ts:7 — packages/bus-core/src/handler/handler-for.integration.ts:7 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/handler/handler.integration.ts:6 — packages/bus-core/src/handler/handler.integration.ts:6 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/handler/handler.integration.ts:13 — packages/bus-core/src/handler/handler.integration.ts:13 imports packages/bus-core/src/test/test-command.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/handler/handler.integration.ts:14 — packages/bus-core/src/handler/handler.integration.ts:14 imports packages/bus-core/src/test/test-command-3.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/handler/handler.integration.ts:15 — packages/bus-core/src/handler/handler.integration.ts:15 imports packages/bus-core/src/test/test-command-getter-class-handler.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/handler/handler.integration.ts:16 — packages/bus-core/src/handler/handler.integration.ts:16 imports packages/bus-core/src/test/test-event.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/handler/handler.integration.ts:17 — packages/bus-core/src/handler/handler.integration.ts:17 imports packages/bus-core/src/test/test-event-class-handler.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/service-bus/bus-instance-concurrency.integration.ts:4 — packages/bus-core/src/service-bus/bus-instance-concurrency.integration.ts:4 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/service-bus/bus-instance-concurrency.integration.ts:5 — packages/bus-core/src/service-bus/bus-instance-concurrency.integration.ts:5 imports packages/bus-core/src/test/test-command.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/service-bus/bus-instance-concurrency.integration.ts:6 — packages/bus-core/src/service-bus/bus-instance-concurrency.integration.ts:6 imports packages/bus-core/src/test/test-event.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts:15 — packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts:15 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts:16 — packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts:16 imports packages/bus-core/src/test/test-command.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts:17 — packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts:17 imports packages/bus-core/src/test/test-event.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts:14 — packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts:14 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/service-bus/bus-instance-handler-context.integration.ts:7 — packages/bus-core/src/service-bus/bus-instance-handler-context.integration.ts:7 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/service-bus/bus-instance-handler-context.integration.ts:19 — packages/bus-core/src/service-bus/bus-instance-handler-context.integration.ts:19 imports packages/bus-core/src/workflow/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts:9 — packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts:9 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts:10 — packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts:10 imports packages/bus-core/src/test/test-command.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/service-bus/bus-instance-isolation.integration.ts:11 — packages/bus-core/src/service-bus/bus-instance-isolation.integration.ts:11 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/service-bus/bus-instance-message-types.integration.ts:6 — packages/bus-core/src/service-bus/bus-instance-message-types.integration.ts:6 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts:14 — packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts:14 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:8 — packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:8 imports packages/bus-core/src/test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:13 — packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:13 imports packages/bus-core/src/test/test-command.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:14 — packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:14 imports packages/bus-core/src/test/test-command-2.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:15 — packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:15 imports packages/bus-core/src/test/test-event.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
+ 15 more in this group — see findings.md.

D23 · Boundary Type-Coupling · Cross-context type MessageDeclaration (bus-messages → bus-core) · ×24

Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/handler/handler.ts:30 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via Handler.messageType — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/handler/handler-registry.ts:54 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via HandlerRegistry.register — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/handler/default-handler-registry.ts:40 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via DefaultHandlerRegistry.register — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/handler/handler-for.ts:71 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via HandlerFor.messageType — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/handler/handler-for.ts:54 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via handler-for.handlerFor — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/error/workflow-already-handles-message.ts:4 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via WorkflowAlreadyHandlesMessage.constructor — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/error/workflow-already-handles-message.ts:6 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via WorkflowAlreadyHandlesMessage.messageType — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/error/workflow-already-started-by-message.ts:4 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via WorkflowAlreadyStartedByMessage.constructor — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/error/workflow-already-started-by-message.ts:6 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via WorkflowAlreadyStartedByMessage.messageType — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/error/workflow-does-not-handle-message.ts:15 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via WorkflowDoesNotHandleMessage.constructor — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/error/workflow-does-not-handle-message.ts:17 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via WorkflowDoesNotHandleMessage.messageType — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/function-workflow-definition.ts:16 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via FunctionWorkflowHandler.messageType — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/define-workflow.ts:105 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via FunctionWorkflow.startedBy — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/define-workflow.ts:125 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via FunctionWorkflow.when — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/define-workflow.ts:148 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via FunctionWorkflow.when — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/define-workflow.ts:165 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via FunctionWorkflow.startedByHandler — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/define-workflow.ts:177 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via FunctionWorkflow.whenHandler — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/workflow.ts:230 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via WorkflowMapper.startedBy — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/workflow/workflow.ts:266 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via WorkflowMapper.when — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/service-bus/bus-configuration.ts:349 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via BusConfiguration.withHandler — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/service-bus/bus-configuration.ts:358 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via BusConfiguration.withHandler — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/testing/recorded-messages.ts:37 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via RecordedMessages.sentOf — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/testing/recorded-messages.ts:48 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via RecordedMessages.publishedOf — couples the contexts.
Cross-context type MessageDeclaration (bus-messages → bus-core) packages/bus-core/src/testing/recorded-messages.ts:59 — MessageDeclaration (context bus-messages) is exposed in bus-core's public surface via RecordedMessages.repliedOf — couples the contexts.

D3 · God Classes · FileTooLong · ×19

FileTooLong: service-bus/bus-instance.ts packages/bus-core/src/service-bus/bus-instance.ts — FileTooLong — 1502 significant lines (blank, comment-only and punctuation-only lines excluded), about 83% of them inside a single declaration: BusInstance (415-2671). The bar is 500 significant lines; this is 1002 over it, 3.00× 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.
FileTooLong: src/sqs-transport.ts packages/bus-sqs/src/sqs-transport.ts — FileTooLong — 934 significant lines (blank, comment-only and punctuation-only lines excluded), about 71% of them inside a single declaration: SqsTransport (197-1324). The bar is 500 significant lines; this is 434 over it, 1.87× 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.
FileTooLong: src/rabbitmq-transport.integration.ts packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts — FileTooLong — 853 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 353 over it, 1.71× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/rabbitmq-transport.ts packages/bus-rabbitmq/src/rabbitmq-transport.ts — FileTooLong — 843 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: RabbitMqTransport (217-1458). The bar is 500 significant lines; this is 343 over it, 1.69× 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.
FileTooLong: src/redis-transport.ts packages/bus-redis/src/redis-transport.ts — FileTooLong — 792 significant lines (blank, comment-only and punctuation-only lines excluded), about 82% of them inside a single declaration: RedisTransport (298-1403). The bar is 500 significant lines; this is 292 over it, 1.58× 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.
FileTooLong: service-bus/bus-instance-middleware.integration.ts packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts — FileTooLong — 736 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 236 over it, 1.47× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/postgres-persistence.ts packages/bus-postgres/src/postgres-persistence.ts — FileTooLong — 723 significant lines (blank, comment-only and punctuation-only lines excluded), about 66% of them inside a single declaration: PostgresPersistence (268-963). The bar is 500 significant lines; this is 223 over it, 1.45× 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.
FileTooLong: service-bus/bus-instance-transactional-outbox.integration.ts packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts — FileTooLong — 720 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 220 over it, 1.44× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: generate-message-types/message-type-reader.ts packages/bus-cli/src/generate-message-types/message-type-reader.ts — FileTooLong — 691 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: MessageTypeReader (96-1073). The bar is 500 significant lines; this is 191 over it, 1.38× 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.
FileTooLong: service-bus/bus-instance-dispatched.integration.ts packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts — FileTooLong — 647 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: settlementOf (76-971). The bar is 500 significant lines; this is 147 over it, 1.29× 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.
FileTooLong: src/redis-transport.integration.ts packages/bus-redis/src/redis-transport.integration.ts — FileTooLong — 631 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 131 over it, 1.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/postgres-persistence.integration.ts packages/bus-postgres/src/postgres-persistence.integration.ts — FileTooLong — 621 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 121 over it, 1.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: service-bus/bus-instance-outboxing.integration.ts packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts — FileTooLong — 620 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 120 over it, 1.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/postgres-transport.integration.ts packages/bus-postgres/src/postgres-transport.integration.ts — FileTooLong — 592 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: redriveSql (116-884). The bar is 500 significant lines; this is 92 over it, 1.18× 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.
FileTooLong: src/postgres-transport.ts packages/bus-postgres/src/postgres-transport.ts — FileTooLong — 587 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: PostgresTransport (149-1017). The bar is 500 significant lines; this is 87 over it, 1.17× 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.
FileTooLong: service-bus/bus-instance-delayed-delivery.integration.ts packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts — FileTooLong — 558 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 58 over it, 1.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/open-telemetry-scenarios.integration.ts packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts — FileTooLong — 553 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 53 over it, 1.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/mongodb-persistence.ts packages/bus-mongodb/src/mongodb-persistence.ts — FileTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded), about 76% of them inside a single declaration: MongodbPersistence (115-791). The bar is 500 significant lines; this is 45 over it, 1.09× 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.
FileTooLong: src/bus-module.integration.ts packages/bus-nestjs/src/bus-module.integration.ts — FileTooLong — 524 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 24 over it, 1.05× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.

D3 · God Classes · ClassTooLong · ×8

ClassTooLong: BusInstance packages/bus-core/src/service-bus/bus-instance.ts:415 — ClassTooLong — 1250 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods. The bar is 400 significant lines; this is 850 over it, 3.13× 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.
ClassTooLong: RabbitMqTransport packages/bus-rabbitmq/src/rabbitmq-transport.ts:217 — ClassTooLong — 736 significant lines (blank, comment-only and punctuation-only lines excluded), 48 methods. The bar is 400 significant lines; this is 336 over it, 1.84× 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.
ClassTooLong: SqsTransport packages/bus-sqs/src/sqs-transport.ts:197 — ClassTooLong — 665 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 400 significant lines; this is 265 over it, 1.66× 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.
ClassTooLong: RedisTransport packages/bus-redis/src/redis-transport.ts:298 — ClassTooLong — 648 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 400 significant lines; this is 248 over it, 1.62× 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.
ClassTooLong: MessageTypeReader packages/bus-cli/src/generate-message-types/message-type-reader.ts:96 — ClassTooLong — 648 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 400 significant lines; this is 248 over it, 1.62× 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.
ClassTooLong: PostgresTransport packages/bus-postgres/src/postgres-transport.ts:149 — ClassTooLong — 519 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 400 significant lines; this is 119 over it, 1.30× 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.
ClassTooLong: PostgresPersistence packages/bus-postgres/src/postgres-persistence.ts:268 — ClassTooLong — 477 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 77 over it, 1.19× 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.
ClassTooLong: MongodbPersistence packages/bus-mongodb/src/mongodb-persistence.ts:115 — ClassTooLong — 415 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 15 over it, 1.04× 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.

IC1 · Incompleteness & stubs · Empty method body · ×7

Empty method body — does nothing with its inputs docs/snippets/nestjs.ts:38 — `charge` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs docs/snippets/nestjs.ts:43 — `record` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs docs/snippets/services/index.ts:5 — `reserveRoom` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs docs/snippets/services/index.ts:9 — `charge` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs docs/snippets/services/index.ts:20 — `record` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs docs/snippets/services/index.ts:24 — `ship` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs docs/snippets/services/index.ts:35 — `write` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.

D3 · God Classes · TooManyMethods · ×6

TooManyMethods: BusInstance packages/bus-core/src/service-bus/bus-instance.ts:415 — TooManyMethods — 59 methods. The bar is 30 methods; this is 29 over it, 1.97× 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.
TooManyMethods: RabbitMqTransport packages/bus-rabbitmq/src/rabbitmq-transport.ts:217 — TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× 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.
TooManyMethods: RedisTransport packages/bus-redis/src/redis-transport.ts:298 — TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× 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.
TooManyMethods: MessageTypeReader packages/bus-cli/src/generate-message-types/message-type-reader.ts:96 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× 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.
TooManyMethods: PostgresTransport packages/bus-postgres/src/postgres-transport.ts:149 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× 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.
TooManyMethods: SqsTransport packages/bus-sqs/src/sqs-transport.ts:197 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× 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.

D31 · IaC & Container Security · Medium IaC · ×6

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D10 · Test Quality · No assertions · ×5

No assertions: should initialize without errors packages/bus-core/src/container/container-adapter.spec.ts:333 — 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 a concurrency of 1 packages/bus-core/src/service-bus/bus.spec.ts:85 — 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 a concurrency > 1 packages/bus-core/src/service-bus/bus.spec.ts:89 — 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 dispose packages/bus-core/src/service-bus/bus.spec.ts:297 — 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 sleep the duration of timeoutMs packages/bus-core/src/util/sleep.spec.ts:13 — 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.

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

Duplicated block (19 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-handler-context.integration.ts:197 — packages/bus-core/src/service-bus/bus-instance-handler-context.integration.ts:197 · packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:233 — 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/bus-core/src/service-bus/bus-instance-isolation.integration.ts:23 — packages/bus-core/src/service-bus/bus-instance-isolation.integration.ts:23 · packages/bus-core/src/service-bus/bus-instance-isolation.integration.ts:46 — all 2 copies are in the same file, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited.
Duplicated block (19 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance.integration.ts:363 — packages/bus-core/src/service-bus/bus-instance.integration.ts:363 · packages/bus-core/src/service-bus/bus-instance.integration.ts:400 — 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 (19 lines × 2 locations) packages/bus-postgres/src/postgres-transport.integration.ts:208 — packages/bus-postgres/src/postgres-transport.integration.ts:208 · packages/bus-postgres/src/postgres-transport.integration.ts:252 — 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.

D30 · Dependency Vulnerabilities · Medium CVE · ×3

REDACTED
REDACTED
REDACTED

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

Duplicated block (18 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-recoverability.integration.ts:282 — packages/bus-core/src/service-bus/bus-instance-recoverability.integration.ts:282 · packages/bus-core/src/service-bus/bus-instance-recoverability.integration.ts:469 — 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 (18 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts:276 — packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts:276 · packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts:340 — 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 (18 lines × 2 locations) packages/bus-core/src/workflow/workflow-startedby.integration.ts:36 — packages/bus-core/src/workflow/workflow-startedby.integration.ts:36 · packages/bus-core/src/workflow/workflow-startedby.integration.ts:56 — 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 (17 lines × 2 locations) · ×3

Duplicated block (17 lines × 2 locations) packages/bus-cli/src/generate-message-types/run-generate-message-types.integration.ts:107 — packages/bus-cli/src/generate-message-types/run-generate-message-types.integration.ts:107 · packages/bus-core/src/handler/handler-for.integration.ts:24 — 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/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:251 — packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:251 · packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:306 — 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 (17 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:518 — packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:518 · packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:578 — 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 (16 lines × 2 locations) · ×3

Duplicated block (16 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:622 — packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:622 · packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:693 — 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 (16 lines × 2 locations) packages/bus-mongodb/src/mongodb-persistence.integration.ts:298 — packages/bus-mongodb/src/mongodb-persistence.integration.ts:298 · packages/bus-mongodb/src/mongodb-persistence.integration.ts:340 — 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 (16 lines × 2 locations) packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts:139 — packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts:139 · packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts:297 — 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 (15 lines × 2 locations) · ×3

Duplicated block (15 lines × 2 locations) packages/bus-cli/src/generate-message-types/run-generate-message-types.integration.ts:281 — packages/bus-cli/src/generate-message-types/run-generate-message-types.integration.ts:281 · packages/bus-core/src/handler/handler-for.integration.ts:208 — 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 (15 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts:547 — packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts:547 · packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts:701 — 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 (15 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts:126 — packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts:126 · packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts:675 — 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.

IC1 · Incompleteness & stubs · Fake-async · ×2

Fake-async — async method never awaits docs/snippets/mongodb-outbox-testing.ts:14 — `insertOne` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/bus-core/src/workflow/registry/workflow-registry.ts:203 — `initialize` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.

IC1 · Incompleteness & stubs · Hollow method · ×2

Hollow method — returns a constant without doing the work docs/snippets/nestjs-testing.ts:28 — `charge` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work docs/snippets/services/index.ts:39 — `read` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.

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

Duplicated block (21 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts:596 — packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts:596 · packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts:723 — 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/bus-rabbitmq/src/rabbitmq-transport.integration.ts:414 — packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts:414 · packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts:441 — 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 · ×2

No test reaches this file tools/check-packages.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 packages/bus-cli/bus.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.

R8 · Dependency Hygiene · Unused dependency 'tslib' · ×2

Unused dependency 'tslib' — Declared in packages/bus-cli/package.json 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.
Unused dependency 'tslib' — Declared in packages/bus-core/package.json 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 · Weak hash algorithm · ×2

Weak hash algorithm packages/bus-postgres/src/postgres-transport.ts:97 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/bus-redis/src/redis-scripts.ts:24 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.

D1 · Cyclomatic Complexity · message-type-reviver.reviveValue (cyclomatic 24) · ×1

message-type-reviver.reviveValue (cyclomatic 24) packages/bus-core/src/serialization/message-type-reviver.ts:77 — message-type-reviver.reviveValue has cyclomatic complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to one function literal inside it that branches. 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 · sync-readmes.syncReadme (cyclomatic 19) · ×1

sync-readmes.syncReadme (cyclomatic 19) docs/scripts/sync-readmes.mjs:245 — sync-readmes.syncReadme has cyclomatic complexity 19 (threshold 15). Of this number, 16 points are the body's own statements and 3 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 · MessageTypeReader.describeObjectType (cyclomatic 19) · ×1

MessageTypeReader.describeObjectType (cyclomatic 19) packages/bus-cli/src/generate-message-types/message-type-reader.ts:891 — MessageTypeReader.describeObjectType 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 · generate-message-types.generateMessageTypes (cyclomatic 19) · ×1

generate-message-types.generateMessageTypes (cyclomatic 19) packages/bus-cli/src/generate-message-types/generate-message-types.ts:102 — generate-message-types.generateMessageTypes has cyclomatic complexity 19 (threshold 15). Of this number, 11 points are the body's own statements and 8 belong to 6 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · is-same-message-types.readMessageTypes · ×1

is-same-message-types.readMessageTypes::toValue (cyclomatic 17) packages/bus-cli/src/generate-message-types/is-same-message-types.ts:56 — is-same-message-types.readMessageTypes::toValue has cyclomatic complexity 17 (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 · MessageTypeReader.describeObject (cyclomatic 16) · ×1

MessageTypeReader.describeObject (cyclomatic 16) packages/bus-cli/src/generate-message-types/message-type-reader.ts:785 — MessageTypeReader.describeObject 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.

D12 · Dependency Hygiene · Deprecated · ×1

Deprecated: @opentelemetry/sdk-trace-base packages/bus-opentelemetry/package.json:63 — @opentelemetry/sdk-trace-base 2.11.0, declared in packages/bus-opentelemetry/package.json, 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.

D2 · Cognitive Complexity · sync-readmes.syncReadme (cognitive 36) · ×1

sync-readmes.syncReadme (cognitive 36) docs/scripts/sync-readmes.mjs:245 — sync-readmes.syncReadme has cognitive complexity 36 (threshold 15). Drivers by points: if/else 10 (21 pts), ternaries 2 (7 pts), boolean chains 3, error handling 1 (3 pts), loops 2 (nesting depth added 18). Of this number, 32 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 · message-type-reviver.reviveValue (cognitive 31) · ×1

message-type-reviver.reviveValue (cognitive 31) packages/bus-core/src/serialization/message-type-reviver.ts:77 — message-type-reviver.reviveValue has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 8 (15 pts), if/else 9 (11 pts), boolean chains 5 (nesting depth added 9). Of this number, 27 points are the body's own statements and 4 belong to one function literal inside it that branches. 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 · is-same-message-types.readMessageTypes (cognitive 24) · ×1

is-same-message-types.readMessageTypes (cognitive 24) packages/bus-cli/src/generate-message-types/is-same-message-types.ts:12 — is-same-message-types.readMessageTypes has cognitive complexity 24 (threshold 15). Drivers by points: if/else 17 (25 pts), loops 4 (10 pts), ternaries 3 (9 pts), boolean chains 7 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (is-same-message-types.readMessageTypes::toValue) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.

D2 · Cognitive Complexity · is-same-message-types.readMessageTypes · ×1

is-same-message-types.readMessageTypes::toValue (cognitive 22) packages/bus-cli/src/generate-message-types/is-same-message-types.ts:56 — is-same-message-types.readMessageTypes::toValue has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (14 pts), ternaries 1 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 6). 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 shape REPEATS in the file: one other method here (is-same-message-types.readMessageTypes) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.

D2 · Cognitive Complexity · MessageTypeReader.describeObjectType (cognitive 21) · ×1

MessageTypeReader.describeObjectType (cognitive 21) packages/bus-cli/src/generate-message-types/message-type-reader.ts:891 — MessageTypeReader.describeObjectType has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 4 (6 pts), boolean chains 5 (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 · BusInstance.sendCommittedMessages (cognitive 20) · ×1

BusInstance.sendCommittedMessages (cognitive 20) packages/bus-core/src/service-bus/bus-instance.ts:2389 — BusInstance.sendCommittedMessages has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (11 pts), error handling 3 (5 pts), boolean chains 3, loops 1 (nesting depth added 5). Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 2405). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · MessageTypeReader.describeObject (cognitive 19) · ×1

MessageTypeReader.describeObject (cognitive 19) packages/bus-cli/src/generate-message-types/message-type-reader.ts:785 — MessageTypeReader.describeObject has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 3 (6 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 · RabbitMqTransport.publishMessage (cognitive 19) · ×1

RabbitMqTransport.publishMessage (cognitive 19) packages/bus-rabbitmq/src/rabbitmq-transport.ts:1399 — RabbitMqTransport.publishMessage has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (12 pts), ternaries 2 (4 pts), error handling 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MessageTypeReader.readSourceFile (cognitive 18) · ×1

MessageTypeReader.readSourceFile (cognitive 18) packages/bus-cli/src/generate-message-types/message-type-reader.ts:179 — MessageTypeReader.readSourceFile has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 2, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · BusLifecycleHost.findRegistrations (cognitive 18) · ×1

BusLifecycleHost.findRegistrations (cognitive 18) packages/bus-nestjs/src/bus-lifecycle-host.ts:240 — BusLifecycleHost.findRegistrations has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 4 (nesting depth added 6). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · generate-message-types.generateMessageTypes (cognitive 16) · ×1

generate-message-types.generateMessageTypes (cognitive 16) packages/bus-cli/src/generate-message-types/generate-message-types.ts:102 — generate-message-types.generateMessageTypes has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 5, ternaries 3 (4 pts) (nesting depth added 1). Of this number, 11 points are the body's own statements and 5 belong to 6 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · run-provision.runProvision (cognitive 16) · ×1

run-provision.runProvision (cognitive 16) packages/bus-cli/src/provision/run-provision.ts:84 — run-provision.runProvision has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (7 pts), if/else 4 (5 pts), boolean chains 2, error handling 2 (nesting depth added 3). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. 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 · OutgoingMessageDispatcher.probe (cognitive 16) · ×1

OutgoingMessageDispatcher.probe (cognitive 16) packages/bus-core/src/outgoing-message/outgoing-message-dispatcher.ts:296 — OutgoingMessageDispatcher.probe has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 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.

D22 · Internal API Consistency · Duplicate Logger Interface · ×1

Duplicate Logger Interface: `DebugLogger` exposes the exact same method signatures as the `Logger` interface. This creates redundancy where consumers must choose between a generic interface and a specific implementation that looks identical, potentially causing confusion about which to depend on. — Ensure `DebugLogger` implements `Logger` explicitly in the type definitions, or remove `DebugLogger` from the public API surface if it is an internal implementation detail, forcing users to depend on the `Logger` interface. (signatures: Logger.debug(message: string, meta?: object): void | DebugLogger.debug(message: string, meta?: object): void | Logger.trace(message: string, meta?: object): void | DebugLogger.trace(message: string, meta?: object): void | Logger.info(message: string, meta?: object): void | DebugLogger.info(message: string, meta?: object): void | Logger.warn(message: string, meta?: object): void | DebugLogger.warn(message: string, meta?: object): void | Logger.error(message: string, meta?: object): void | DebugLogger.error(message: string, meta?: object): void | Logger.fatal(message: string, meta?: object): void | DebugLogger.fatal(message: string, meta?: object): void)

D22 · Internal API Consistency · Inconsistent Provision Options Naming · ×1

Inconsistent Provision Options Naming: `Transport` uses `TransportProvisionOptions` while `Persistence` uses `PersistenceProvisionOptions`. While the types are distinct, the naming convention is inconsistent with the initialization options (`TransportInitializationOptions` vs `PersistenceInitializationOptions`) and lacks a shared base interface or unified naming pattern for 'ProvisionOptions' across the transport/persistence abstraction. — Introduce a shared `ProvisionOptions` interface or base class that both `TransportProvisionOptions` and `PersistenceProvisionOptions` extend, or standardize the naming to `ProvisionOptions` with a discriminator if they share common fields like `dryRun`. (signatures: Transport.provision(options: TransportProvisionOptions): Promise<ProvisioningPlan> | Persistence.provision(options: PersistenceProvisionOptions): Promise<ProvisioningPlan>)

D3 · God Classes · FunctionTooLong · ×1

FunctionTooLong: open-telemetry.openTelemetry packages/bus-opentelemetry/src/open-telemetry.ts:208 — FunctionTooLong — openTelemetry runs 155 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 55 over it, 1.55× 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.

D30 · Dependency Vulnerabilities · Medium vulnerability · ×1

REDACTED

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

REDACTED

D5 · Coupling · Off the main sequence · ×1

Off the main sequence: @node-ts/bus-core — @node-ts/bus-core: abstractness 0.13, instability 0.10, distance 0.77 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.

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/bus-test/src/inbox-tests.ts:504 — a busy-wait on the clock in `callback to beforeAll` 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 10 sibling directories (44 clone groups) · ×1

Duplication concentrated across 10 sibling directories (44 clone groups) packages/bus-mongodb/src/mongodb-persistence.ts:124 — 44 duplicated blocks under packages/ have copies in at least two of the sibling directories bus-cli, bus-core, bus-messages, bus-mongodb, bus-nestjs, bus-opentelemetry (+4 more sibling(s) not listed) — 23 of them are reported below, and 21 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 44 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 44 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 44 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 (22 clone groups) · ×1

Duplication concentrated across 6 sibling directories (22 clone groups) packages/bus-core/src/service-bus/bus-instance-reply.integration.ts:128 — 22 duplicated blocks under packages/bus-core/src/ have copies in at least two of the sibling directories handler, message-handling-context, message-lifecycle-context, service-bus, transport, workflow — 5 of them are reported below, and 17 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 22 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 22 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 22 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 (169 matched lines × 2 locations) · ×1

Duplicated block with local edits (169 matched lines × 2 locations) packages/bus-mongodb/src/mongodb-persistence.ts:124 — packages/bus-mongodb/src/mongodb-persistence.ts:124 · packages/bus-postgres/src/postgres-persistence.ts:277 — the two spans are one implementation copied and then locally edited — 754 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 (114 matched lines × 2 locations) · ×1

Duplicated block with local edits (114 matched lines × 2 locations) packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts:458 — packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts:458 · packages/bus-opentelemetry/src/open-telemetry.integration.ts:63 — the two spans are one implementation copied and then locally edited — 606 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 (107 matched lines × 2 locations) · ×1

Duplicated block with local edits (107 matched lines × 2 locations) packages/bus-postgres/src/postgres-transport.ts:344 — packages/bus-postgres/src/postgres-transport.ts:344 · packages/bus-redis/src/redis-transport.ts:517 — the two spans are one implementation copied and then locally edited — 500 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 (81 matched lines × 2 locations) · ×1

Duplicated block with local edits (81 matched lines × 2 locations) packages/bus-mongodb/src/mongo-session.integration.ts:48 — packages/bus-mongodb/src/mongo-session.integration.ts:48 · packages/bus-postgres/src/postgres-transaction.integration.ts:40 — the two spans are one implementation copied and then locally edited — 474 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 (72 matched lines × 2 locations) · ×1

Duplicated block with local edits (72 matched lines × 2 locations) packages/bus-mongodb/src/mongo-session.integration.ts:212 — packages/bus-mongodb/src/mongo-session.integration.ts:212 · packages/bus-postgres/src/postgres-transaction.integration.ts:145 — the two spans are one implementation copied and then locally edited — 406 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 (64 matched lines × 2 locations) · ×1

Duplicated block with local edits (64 matched lines × 2 locations) packages/bus-mongodb/src/mongodb-persistence.integration.ts:455 — packages/bus-mongodb/src/mongodb-persistence.integration.ts:455 · packages/bus-postgres/src/postgres-persistence.integration.ts:157 — the two spans are one implementation copied and then locally edited — 298 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 (54 matched lines × 2 locations) · ×1

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

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

Duplicated block (53 lines × 2 locations) packages/bus-mongodb/src/mongodb-persistence.integration.ts:557 — packages/bus-mongodb/src/mongodb-persistence.integration.ts:557 · packages/bus-postgres/src/postgres-persistence.integration.ts:230 — 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 (47 matched lines × 2 locations) · ×1

Duplicated block with local edits (47 matched lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-reply.integration.ts:128 — packages/bus-core/src/service-bus/bus-instance-reply.integration.ts:128 · packages/bus-core/src/workflow/define-workflow.integration.ts:214 — the two spans are one implementation copied and then locally edited — 242 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 (37 lines × 2 locations) · ×1

Duplicated block (37 lines × 2 locations) packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts:212 — packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts:212 · packages/bus-sqs/src/sqs-transport.integration.ts:306 — 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 (34 matched lines × 2 locations) · ×1

Duplicated block with local edits (34 matched lines × 2 locations) packages/bus-mongodb/src/mongodb-persistence-transaction.ts:130 — packages/bus-mongodb/src/mongodb-persistence-transaction.ts:130 · packages/bus-postgres/src/postgres-persistence-transaction.ts:70 — the two spans are one implementation copied and then locally edited — 169 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 (28 matched lines × 2 locations) · ×1

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

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

Duplicated block (28 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:755 — packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:755 · packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:860 — 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/bus-core/src/workflow/workflow.integration.ts:143 — packages/bus-core/src/workflow/workflow.integration.ts:143 · packages/bus-core/src/workflow/workflow.integration.ts:174 — 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 with local edits (26 matched lines × 2 locations) · ×1

Duplicated block with local edits (26 matched lines × 2 locations) packages/bus-core/src/workflow/define-workflow-concurrency.integration.ts:77 — packages/bus-core/src/workflow/define-workflow-concurrency.integration.ts:77 · packages/bus-core/src/workflow/workflow-concurrency.integration.ts:83 — the two spans are one implementation copied and then locally edited — 108 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 (22 lines × 2 locations) · ×1

Duplicated block (22 lines × 2 locations) packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts:362 — packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts:362 · packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts:431 — 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 with local edits (22 matched lines × 2 locations) · ×1

Duplicated block with local edits (22 matched lines × 2 locations) packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts:217 — packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts:217 · packages/bus-opentelemetry/src/transport-propagation.integration.ts:118 — the two spans are one implementation copied and then locally edited — 101 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 (22 lines × 3 locations) · ×1

Duplicated block (22 lines × 3 locations) packages/bus-postgres/src/postgres-transport.ts:348 — packages/bus-postgres/src/postgres-transport.ts:348 · packages/bus-redis/src/redis-transport.ts:522 · packages/bus-sqs/src/sqs-transport.ts:285 — 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 with local edits (17 matched lines × 2 locations) · ×1

Duplicated block with local edits (17 matched lines × 2 locations) packages/bus-core/src/service-bus/bus-instance.integration.ts:211 — packages/bus-core/src/service-bus/bus-instance.integration.ts:211 · packages/bus-core/src/workflow/workflow-startedby.integration.ts:83 — the two spans are one implementation copied and then locally edited — 77 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 (16 lines × 3 locations) · ×1

Duplicated block (16 lines × 3 locations) packages/bus-cli/src/provision/run-provision.integration.ts:66 — packages/bus-cli/src/provision/run-provision.integration.ts:66 · packages/bus-cli/src/provision/run-provision.integration.ts:86 · packages/bus-cli/src/provision/run-provision.integration.ts:105 — all 3 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.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 23, cognitive 28) · ×1

Complex function (anonymous) (cyclomatic 23, cognitive 28) packages/bus-core/src/serialization/message-type-reviver.ts:82 — (anonymous) has cyclomatic complexity 23 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 describeObjectType (cyclomatic 19, cognitive 21) · ×1

Complex function describeObjectType (cyclomatic 19, cognitive 21) packages/bus-cli/src/generate-message-types/message-type-reader.ts:891 — describeObjectType has cyclomatic complexity 19 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 (anonymous) (cyclomatic 18, cognitive 23) · ×1

Complex function (anonymous) (cyclomatic 18, cognitive 23) packages/bus-cli/src/generate-message-types/is-same-message-types.ts:56 — (anonymous) 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 describeObject (cyclomatic 16, cognitive 19) · ×1

Complex function describeObject (cyclomatic 16, cognitive 19) packages/bus-cli/src/generate-message-types/message-type-reader.ts:785 — describeObject has cyclomatic complexity 16 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 (anonymous) (cyclomatic 15, cognitive 25) · ×1

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

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

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

R2 · Cyclomatic Complexity · Complex function evaluateString (cyclomatic 14, cognitive 13) · ×1

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

R2 · Cyclomatic Complexity · Complex function findRegistrations (cyclomatic 13, cognitive 19) · ×1

Complex function findRegistrations (cyclomatic 13, cognitive 19) packages/bus-nestjs/src/bus-lifecycle-host.ts:240 — findRegistrations has cyclomatic complexity 13 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 resolveDueAt (cyclomatic 13, cognitive 12) · ×1

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

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 12, cognitive 14) · ×1

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

R2 · Cyclomatic Complexity · Complex function settleMessage (cyclomatic 12, cognitive 14) · ×1

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

R2 · Cyclomatic Complexity · Complex function messageNameOf (cyclomatic 12, cognitive 13) · ×1

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

R2 · Cyclomatic Complexity · Complex function describe (cyclomatic 12, cognitive 12) · ×1

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

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 12, cognitive 10) · ×1

Complex function (anonymous) (cyclomatic 12, cognitive 10) packages/bus-core/src/outgoing-message/assert-delivery-options.ts:17 — (anonymous) has cyclomatic complexity 12 and cognitive complexity 10; 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 readSourceFile (cyclomatic 11, cognitive 18) · ×1

Complex function readSourceFile (cyclomatic 11, cognitive 18) packages/bus-cli/src/generate-message-types/message-type-reader.ts:179 — readSourceFile has cyclomatic complexity 11 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 readObjectTypeMessage (cyclomatic 11, cognitive 14) · ×1

Complex function readObjectTypeMessage (cyclomatic 11, cognitive 14) packages/bus-cli/src/generate-message-types/message-type-reader.ts:336 — readObjectTypeMessage 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.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 11, cognitive 13) · ×1

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

R2 · Cyclomatic Complexity · Complex function provision (cyclomatic 11, cognitive 12) · ×1

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

R2 · Cyclomatic Complexity · Complex function initialize (cyclomatic 11, cognitive 10) · ×1

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

R3 · Large Files · packages/bus-core/src/service-bus/bus-instance.ts · ×1

packages/bus-core/src/service-bus/bus-instance.ts: 2537 lines of code packages/bus-core/src/service-bus/bus-instance.ts:1 — packages/bus-core/src/service-bus/bus-instance.ts has 2537 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/bus-sqs/src/sqs-transport.ts · ×1

packages/bus-sqs/src/sqs-transport.ts: 1496 lines of code packages/bus-sqs/src/sqs-transport.ts:1 — packages/bus-sqs/src/sqs-transport.ts has 1496 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/bus-rabbitmq/src/rabbitmq-transport.ts · ×1

packages/bus-rabbitmq/src/rabbitmq-transport.ts: 1359 lines of code packages/bus-rabbitmq/src/rabbitmq-transport.ts:1 — packages/bus-rabbitmq/src/rabbitmq-transport.ts has 1359 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/bus-redis/src/redis-transport.ts · ×1

packages/bus-redis/src/redis-transport.ts: 1336 lines of code packages/bus-redis/src/redis-transport.ts:1 — packages/bus-redis/src/redis-transport.ts has 1336 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/bus-rabbitmq/src/rabbitmq-transport.integration.ts · ×1

packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts: 1136 lines of code packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts:1 — packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts has 1136 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/bus-postgres/src/postgres-persistence.ts · ×1

packages/bus-postgres/src/postgres-persistence.ts: 1059 lines of code packages/bus-postgres/src/postgres-persistence.ts:1 — packages/bus-postgres/src/postgres-persistence.ts has 1059 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/bus-cli/src/generate-message-types/message-type-reader.ts · ×1

packages/bus-cli/src/generate-message-types/message-type-reader.ts: 1023 lines of code packages/bus-cli/src/generate-message-types/message-type-reader.ts:1 — packages/bus-cli/src/generate-message-types/message-type-reader.ts has 1023 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/bus-postgres/src/postgres-transport.ts · ×1

packages/bus-postgres/src/postgres-transport.ts: 962 lines of code packages/bus-postgres/src/postgres-transport.ts:1 — packages/bus-postgres/src/postgres-transport.ts has 962 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/bus-core/src/service-bus/bus-instance-middleware.integration.ts · ×1

packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts: 946 lines of code packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts:1 — packages/bus-core/src/service-bus/bus-instance-middleware.integration.ts has 946 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/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts · ×1

packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts: 929 lines of code packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts:1 — packages/bus-core/src/service-bus/bus-instance-transactional-outbox.integration.ts has 929 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/bus-core/src/service-bus/bus-instance-dispatched.integration.ts · ×1

packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts: 881 lines of code packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts:1 — packages/bus-core/src/service-bus/bus-instance-dispatched.integration.ts has 881 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/bus-mongodb/src/mongodb-persistence.ts · ×1

packages/bus-mongodb/src/mongodb-persistence.ts: 880 lines of code packages/bus-mongodb/src/mongodb-persistence.ts:1 — packages/bus-mongodb/src/mongodb-persistence.ts has 880 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/bus-core/src/service-bus/bus-instance-outboxing.integration.ts · ×1

packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts: 828 lines of code packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts:1 — packages/bus-core/src/service-bus/bus-instance-outboxing.integration.ts has 828 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/bus-redis/src/redis-transport.integration.ts · ×1

packages/bus-redis/src/redis-transport.integration.ts: 826 lines of code packages/bus-redis/src/redis-transport.integration.ts:1 — packages/bus-redis/src/redis-transport.integration.ts has 826 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/bus-postgres/src/postgres-persistence.integration.ts · ×1

packages/bus-postgres/src/postgres-persistence.integration.ts: 806 lines of code packages/bus-postgres/src/postgres-persistence.integration.ts:1 — packages/bus-postgres/src/postgres-persistence.integration.ts has 806 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/bus-postgres/src/postgres-transport.integration.ts · ×1

packages/bus-postgres/src/postgres-transport.integration.ts: 796 lines of code packages/bus-postgres/src/postgres-transport.integration.ts:1 — packages/bus-postgres/src/postgres-transport.integration.ts has 796 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/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts · ×1

packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts: 718 lines of code packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts:1 — packages/bus-core/src/service-bus/bus-instance-delayed-delivery.integration.ts has 718 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/bus-core/src/workflow/registry/workflow-registry.ts · ×1

packages/bus-core/src/workflow/registry/workflow-registry.ts: 714 lines of code packages/bus-core/src/workflow/registry/workflow-registry.ts:1 — packages/bus-core/src/workflow/registry/workflow-registry.ts has 714 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/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts · ×1

packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts: 704 lines of code packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts:1 — packages/bus-opentelemetry/src/open-telemetry-scenarios.integration.ts has 704 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/bus-nestjs/src/bus-module.integration.ts · ×1

packages/bus-nestjs/src/bus-module.integration.ts: 699 lines of code packages/bus-nestjs/src/bus-module.integration.ts:1 — packages/bus-nestjs/src/bus-module.integration.ts has 699 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/bus-mongodb/src/mongodb-persistence.integration.ts · ×1

packages/bus-mongodb/src/mongodb-persistence.integration.ts: 648 lines of code packages/bus-mongodb/src/mongodb-persistence.integration.ts:1 — packages/bus-mongodb/src/mongodb-persistence.integration.ts has 648 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/bus-core/src/outgoing-message/outgoing-message-dispatcher.ts · ×1

packages/bus-core/src/outgoing-message/outgoing-message-dispatcher.ts: 635 lines of code packages/bus-core/src/outgoing-message/outgoing-message-dispatcher.ts:1 — packages/bus-core/src/outgoing-message/outgoing-message-dispatcher.ts has 635 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/bus-core/src/service-bus/bus-configuration.ts · ×1

packages/bus-core/src/service-bus/bus-configuration.ts: 625 lines of code packages/bus-core/src/service-bus/bus-configuration.ts:1 — packages/bus-core/src/service-bus/bus-configuration.ts has 625 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/bus-core/src/service-bus/bus-instance-reply.integration.ts · ×1

packages/bus-core/src/service-bus/bus-instance-reply.integration.ts: 622 lines of code packages/bus-core/src/service-bus/bus-instance-reply.integration.ts:1 — packages/bus-core/src/service-bus/bus-instance-reply.integration.ts has 622 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/bus-core/src/workflow/persistence/in-memory-persistence.ts · ×1

packages/bus-core/src/workflow/persistence/in-memory-persistence.ts: 566 lines of code packages/bus-core/src/workflow/persistence/in-memory-persistence.ts:1 — packages/bus-core/src/workflow/persistence/in-memory-persistence.ts has 566 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/bus-test/src/scheduled-message-round-trip-tests.ts · ×1

packages/bus-test/src/scheduled-message-round-trip-tests.ts: 552 lines of code packages/bus-test/src/scheduled-message-round-trip-tests.ts:1 — packages/bus-test/src/scheduled-message-round-trip-tests.ts has 552 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/bus-core/src/service-bus/bus-instance.integration.ts · ×1

packages/bus-core/src/service-bus/bus-instance.integration.ts: 550 lines of code packages/bus-core/src/service-bus/bus-instance.integration.ts:1 — packages/bus-core/src/service-bus/bus-instance.integration.ts has 550 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/bus-cli/src/generate-message-types/run-generate-message-types.integration.ts · ×1

packages/bus-cli/src/generate-message-types/run-generate-message-types.integration.ts: 530 lines of code packages/bus-cli/src/generate-message-types/run-generate-message-types.integration.ts:1 — packages/bus-cli/src/generate-message-types/run-generate-message-types.integration.ts has 530 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/bus-core/src/testing/test-workflow.ts · ×1

packages/bus-core/src/testing/test-workflow.ts: 522 lines of code packages/bus-core/src/testing/test-workflow.ts:1 — packages/bus-core/src/testing/test-workflow.ts has 522 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/bus-test/src/transport-tests.ts · ×1

packages/bus-test/src/transport-tests.ts: 518 lines of code packages/bus-test/src/transport-tests.ts:1 — packages/bus-test/src/transport-tests.ts has 518 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/bus-core/src/service-bus/bus-instance-inbox.integration.ts · ×1

packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts: 503 lines of code packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts:1 — packages/bus-core/src/service-bus/bus-instance-inbox.integration.ts has 503 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/bus-sqs/src/sqs-transport.integration.ts · ×1

packages/bus-sqs/src/sqs-transport.integration.ts: 503 lines of code packages/bus-sqs/src/sqs-transport.integration.ts:1 — packages/bus-sqs/src/sqs-transport.integration.ts has 503 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/bus-core/src/service-bus/bus-instance-recoverability.integration.ts · ×1

packages/bus-core/src/service-bus/bus-instance-recoverability.integration.ts: 478 lines of code packages/bus-core/src/service-bus/bus-instance-recoverability.integration.ts:1 — packages/bus-core/src/service-bus/bus-instance-recoverability.integration.ts has 478 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/bus-test/src/inbox-tests.ts · ×1

packages/bus-test/src/inbox-tests.ts: 472 lines of code packages/bus-test/src/inbox-tests.ts:1 — packages/bus-test/src/inbox-tests.ts has 472 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/bus-core/src/workflow/workflow.integration.ts · ×1

packages/bus-core/src/workflow/workflow.integration.ts: 425 lines of code packages/bus-core/src/workflow/workflow.integration.ts:1 — packages/bus-core/src/workflow/workflow.integration.ts has 425 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/bus-opentelemetry/src/open-telemetry.ts · ×1

packages/bus-opentelemetry/src/open-telemetry.ts: 412 lines of code packages/bus-opentelemetry/src/open-telemetry.ts:1 — packages/bus-opentelemetry/src/open-telemetry.ts has 412 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 · Unused dependency '@node-ts/code-standards' · ×1

Unused dependency '@node-ts/code-standards' — Declared in packages/bus-core/package.json 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.

X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×1

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

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

Swallowed exception (empty catch) packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts:159 — 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.

Minor — 81 finding(s)

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

README/code drift CONTRIBUTING.md:70 — CONTRIBUTING.md runs `pnpm changeset`, but no package.json declares a `changeset` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift .changeset/README.md:3 — .changeset/README.md runs `pnpm changeset`, but no package.json declares a `changeset` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/persistence.md:20 — docs/persistence.md links to `/guide/outbox`, but `guide/outbox` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/getting-started/handling-messages.md:20 — docs/getting-started/handling-messages.md links to `/api/bus-core/interfaces/HandlerContext`, but `api/bus-core/interfaces/HandlerContext` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/getting-started/handling-messages.md:20 — docs/getting-started/handling-messages.md links to `/guide/workflows/request-reply`, but `guide/workflows/request-reply` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/getting-started/installation.md:63 — docs/getting-started/installation.md links to `/transports`, but `transports` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guide/delayed-delivery.md:32 — docs/guide/delayed-delivery.md links to `/persistence`, but `persistence` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guide/delayed-delivery.md:36 — docs/guide/delayed-delivery.md links to `/guide/middleware#outgoing-middleware`, but `guide/middleware` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guide/delayed-delivery.md:61 — docs/guide/delayed-delivery.md links to `/persistence/postgres`, but `persistence/postgres` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guide/delayed-delivery.md:62 — docs/guide/delayed-delivery.md links to `/persistence/mongodb`, but `persistence/mongodb` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guide/dependency-injection.md:30 — docs/guide/dependency-injection.md links to `/guide/nestjs`, but `guide/nestjs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guide/loggers.md:18 — docs/guide/loggers.md links to `/guide/loggers/custom-loggers`, but `guide/loggers/custom-loggers` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guide/middleware.md:30 — docs/guide/middleware.md links to `/transports/sqs-lambda`, but `transports/sqs-lambda` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guide/middleware.md:30 — docs/guide/middleware.md links to `/getting-started/handling-messages`, but `getting-started/handling-messages` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guide/middleware.md:40 — docs/guide/middleware.md links to `/guide/opentelemetry`, but `guide/opentelemetry` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guide/middleware.md:52 — docs/guide/middleware.md links to `/guide/recoverability`, but `guide/recoverability` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guide/middleware.md:80 — docs/guide/middleware.md links to `/guide/workflows/request-reply`, but `guide/workflows/request-reply` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guide/middleware.md:102 — docs/guide/middleware.md links to `/transports/rabbitmq`, but `transports/rabbitmq` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guide/middleware.md:103 — docs/guide/middleware.md links to `/transports/amazon-sqs`, but `transports/amazon-sqs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guide/middleware.md:132 — docs/guide/middleware.md links to `/upgrading/v2`, but `upgrading/v2` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guide/multiple-buses.md:19 — docs/guide/multiple-buses.md links to `/api/bus-core/interfaces/HandlerContext`, but `api/bus-core/interfaces/HandlerContext` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guide/nestjs.md:34 — docs/guide/nestjs.md links to `/getting-started/handling-messages`, but `getting-started/handling-messages` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guide/nestjs.md:34 — docs/guide/nestjs.md links to `/guide/serializers/message-types`, but `guide/serializers/message-types` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guide/nestjs.md:72 — docs/guide/nestjs.md links to `/guide/multiple-buses`, but `guide/multiple-buses` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guide/opentelemetry.md:8 — docs/guide/opentelemetry.md links to `/guide/middleware`, but `guide/middleware` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
+ 15 more in this group — see findings.md.

X10 · Duplicated predicate · Duplicated predicate · ×11

Duplicated predicate packages/bus-core/src/service-bus/bus-instance.ts:1640 — `'deliverAfter' in messageAttributes || 'deliverAt' in messageAttributes` appears character-identically in 2 files — packages/bus-core/src/service-bus/bus-instance.ts, packages/bus-core/src/testing/create-recording-handler-context.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/bus-core/src/recoverability/create-message-failure.ts:16 — `error instanceof HandlerDispatchRejected && error.rejections.length === 1` appears character-identically in 2 files — packages/bus-core/src/recoverability/create-message-failure.ts, packages/bus-opentelemetry/src/open-telemetry.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/bus-opentelemetry/src/transport-propagation.integration.ts:24 — `process.env.LOCALSTACK_ENDPOINT || 'http://localhost:4566'` appears character-identically in 3 files — packages/bus-opentelemetry/src/transport-propagation.integration.ts, packages/bus-sqs-lambda/src/bus-sqs-lambda-receiver.integration.ts, packages/bus-sqs/src/sqs-transport.integration.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/bus-mongodb/src/mongo-session.integration.ts:32 — `process.env.MONGODB_URL || 'mongodb://localhost:27017/workflows?directConnection=true'` appears character-identically in 2 files — packages/bus-mongodb/src/mongo-session.integration.ts, packages/bus-mongodb/src/mongodb-persistence.integration.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/bus-postgres/src/postgres-persistence.integration.ts:33 — `process.env.POSTGRES_URL || 'postgres://postgres:password@localhost:6432/postgres'` appears character-identically in 3 files — packages/bus-postgres/src/postgres-persistence.integration.ts, packages/bus-postgres/src/postgres-transaction.integration.ts, packages/bus-postgres/src/postgres-transport.integration.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/bus-opentelemetry/src/transport-propagation.integration.ts:25 — `process.env.RABBITMQ_URL || 'amqp://guest:guest@0.0.0.0'` appears character-identically in 2 files — packages/bus-opentelemetry/src/transport-propagation.integration.ts, packages/bus-rabbitmq/src/rabbitmq-transport.integration.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/bus-rabbitmq/src/rabbitmq-transport.integration.ts:120 — `rabbitMessage.properties.headers && rabbitMessage.properties.headers.attributes` appears character-identically in 2 files — packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts, packages/bus-rabbitmq/src/rabbitmq-transport.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/bus-rabbitmq/src/rabbitmq-transport.integration.ts:127 — `rabbitMessage.properties.headers && rabbitMessage.properties.headers.stickyAttributes` appears character-identically in 2 files — packages/bus-rabbitmq/src/rabbitmq-transport.integration.ts, packages/bus-rabbitmq/src/rabbitmq-transport.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/bus-cli/src/generate-message-types/is-same-message-types.ts:58 — `ts.isParenthesizedExpression(expression) || ts.isAsExpression(expression) || ts.isSatisfiesExpression(expression)` appears character-identically in 2 files — packages/bus-cli/src/generate-message-types/is-same-message-types.ts, packages/bus-cli/src/generate-message-types/message-type-reader.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/bus-core/src/workflow/has-lookup-value.ts:15 — `value !== undefined && value !== null && value !== ''` appears character-identically in 2 files — packages/bus-core/src/workflow/has-lookup-value.ts, packages/bus-sqs/src/sqs-transport.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/bus-mongodb/src/key-encoding.ts:57 — `value === null || typeof value !== 'object'` appears character-identically in 2 files — packages/bus-mongodb/src/key-encoding.ts, packages/bus-mongodb/src/mongodb-persistence.integration.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.

D12 · Dependency Hygiene · Deprecated · ×5

Deprecated: circular-json REDACTED:2950 — circular-json 0.3.3 is resolved in REDACTED and is marked deprecated by its publisher: "CircularJSON is in maintenance only, flatted is its successor.". 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:3374 — 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:3383 — 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:3475 — 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: postinstall-build REDACTED:4225 — postinstall-build 5.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "postinstall-build's behavior is now built into npm! You should migrate off of postinstall-build and use the new `prepare` lifecycle script with npm 5.0.0 or greater.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.

P2 · Observability · Console output used as the logging channel · ×5

Console output used as the logging channel packages/bus-core/src/middleware/middleware.ts:24 — `packages/bus-core/src/middleware/middleware.ts` reports through `console.*` at line 24 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/bus-core/src/middleware/handler-invocation-context.ts:9 — `packages/bus-core/src/middleware/handler-invocation-context.ts` reports through `console.*` at line 9 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/bus-core/src/middleware/bus-middleware.ts:16 — `packages/bus-core/src/middleware/bus-middleware.ts` reports through `console.*` at line 16 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/bus-core/src/recoverability/failure-header.ts:24 — `packages/bus-core/src/recoverability/failure-header.ts` reports through `console.*` at line 24 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/bus-core/src/service-bus/bus-configuration.ts:574 — `packages/bus-core/src/service-bus/bus-configuration.ts` reports through `console.*` at line 574 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.

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

Diagnostic log message is built whether or not it is wanted packages/bus-core/src/service-bus/bus-instance.ts:1926 — `debug` at line 1926 is called with an argument built by `toStore.map(({ id, kind, dueAt }) => ({ id, kind, dueAt }))` (line 1927), 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.
Diagnostic log message is built whether or not it is wanted packages/bus-mongodb/src/mongodb-persistence.ts:727 — `debug` at line 727 is called with an argument built by `indexes.map(({ name }) => name)` (line 729), 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.
Diagnostic log message is built whether or not it is wanted packages/bus-redis/src/redis-transport.ts:915 — `debug` at line 915 is called with an argument built by `entries.map(({ id }) => id)` (line 917), 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.

D30 · Dependency Vulnerabilities · Low CVE · ×2

REDACTED
REDACTED

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

Outdated (npm): serialize-error packages/bus-core/package.json:45 — serialize-error is pinned at 8.1.0; registry.npmjs.org publishes 13.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.

D19 · Documentation Quality · Documentation · ×1

Documentation: no project overview docs/index.md — The home page has a hero banner and a brief description but no paragraph stating what the project does or what it is for, unlike the rabbitmq/bus-sqs READMEs that open with an overview. Add one sentence explaining the bus's purpose (message-driven applications in TypeScript) so readers can skip past the banner.

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.

D26 · Project Cohesion · Split packages/bus-core · ×1

Split packages/bus-core — A huge bus-core project whose namespaces are all transport/workflow/error/handler/serialization plus recoverability and an outgoing-message outbox, each a distinct concern. Suggested: split into domain buses, workflow engines, error handlers, serialization libraries

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

REDACTED

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

REDACTED

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

REDACTED

M2 · Architecture documentation · No ADRs · ×1

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

P2 · Observability · Logging is not universal · ×1

Logging is not universal — Only 8/9 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/bus-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 12876 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.

R7 · Dead Code · Unused export 'MAX_REVIVE_DEPTH' · ×1

Unused export 'MAX_REVIVE_DEPTH' packages/bus-core/src/serialization/message-type-reviver.ts:13 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Write-only private field 'logger' · ×1

Write-only private field 'logger' packages/bus-core/src/workflow/persistence/in-memory-persistence.ts:99 — This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments.

S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×1

No app-layer HTTPS enforcement detected docs/snippets/nestjs.ts:135 — `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)

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 — 21/22 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 — ~2.7 `!` null assertions per 1k TypeScript source lines — 139 assertion(s) across the 52231 source line(s) of the 425 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/bus-rabbitmq/src/rabbitmq-transport.integration.ts (32), packages/bus-sqs/src/sqs-transport.ts (28), packages/bus-core/src/service-bus/bus-instance-reply.integration.ts (7). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

Minor — 4 finding(s)

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

Outdated (npm): @aws-sdk/client-sns — @aws-sdk/client-sns is pinned at 3.1142.0; registry.npmjs.org publishes 3.1155.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @aws-sdk/client-sqs — @aws-sdk/client-sqs is pinned at 3.1142.0; registry.npmjs.org publishes 3.1155.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @aws-sdk/util-arn-parser — @aws-sdk/util-arn-parser is pinned at 3.972.41; registry.npmjs.org publishes 3.972.45 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.23.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.

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-87a7df36847b4ef48f00b4f0412d253e/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-87a7df36847b4ef48f00b4f0412d253e/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 .	19	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	17	artifacts/raw/trivy-fs.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	6	artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep --config /opt/semgrep-rules/gdpr.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	1	artifacts/raw/semgrep-gdpr.json
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 01a16474-59db-7e98-82e0-d0677c2e43e8 · 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 · 77% · Strong ·

At a glance — Architecture · 60% · Adequate · gated by R11 ·

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

At a glance — Readiness · 55% · Adequate · gated by R8, P3 ·

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

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

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts