nestjs/nest

Executive summary

nestjs/nest is rated At risk because critical security findings are open. Its score is held back in part because it has uses of packages that aren't listed. It scores 48 out of 100, which the At risk rating leaves unchanged.

Production Readiness, at 40, is the weakest lens and counts most in the score. The best first step is fixing the password or key in the code, worth about 6 points. Tidying the declared packages would lift Production Readiness itself, worth about 4 points. Raising Production Readiness to 70 would lift the score to about 54.

Sixteen known security holes in the packages the code depends on can be used by attackers. Nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and four settings leave the servers or containers unsafe. Updating the vulnerable packages, pinning each tool to an exact version and correcting the unsafe settings would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once. The 16 loops of files that import each other need breaking.

The product code is 69,723 lines, about €160,000 to rebuild.

Code Health 65 Adequate Architecture 55 Adequate, capped by Coupling and Circular Imports Maturity 43 Weak, capped by Architecture documentation and Documentation accuracy Production Readiness 40 Weak, capped by Dependency Hygiene and Schema migrations Security and Compliance 70 Adequate, capped by Static Analysis (SAST) and Dependency Vulnerabilities Domain Modelling 100 ★ Exemplary Performance 85 Strong

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

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.

Production Readiness 40 · counts for 46%Maturity 43 · counts for 25%Architecture 55 · counts for 14%Code Health 65 · counts for 8%Security and Compliance 70 · counts for 4%Performance 85 · counts for 2%Domain Modelling 100 · counts for 1%

If Production Readiness rose from 40 to 70, the lowest score rated Strong, the score would rise from 48 to about 54.

Code composition: what the lines of code are

Product code 41%Tests 59%

New since the last survey: 144 findings

These 144 critical or serious findings weren't in the previous survey, on 12 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

Cyclomatic Complexity · ValidationPipe.transform (cyclomatic 20) packages/common/pipes/validation.pipe.ts
Cyclomatic Complexity · FastifyAdapter.constructor (cyclomatic 19) REDACTED
Cyclomatic Complexity · FastifyAdapter.reply (cyclomatic 19) REDACTED
Cyclomatic Complexity · ExpressAdapter.reply (cyclomatic 17) packages/platform-express/adapters/express-adapter.ts
Cyclomatic Complexity · RouterExplorer.applyHostFilter (cyclomatic 16) packages/core/router/router-explorer.ts
Cognitive Complexity · FastifyAdapter.constructor (cognitive 24) REDACTED
Cognitive Complexity · FastifyAdapter.reply (cognitive 22) REDACTED
Cognitive Complexity · ExpressAdapter.reply (cognitive 20) packages/platform-express/adapters/express-adapter.ts
Cognitive Complexity · ValidationPipe.transform (cognitive 19) packages/common/pipes/validation.pipe.ts
Cognitive Complexity · FastifyAdapter.createMiddlewareFactory (cognitive 19) REDACTED
Cognitive Complexity · ServerGrpc.writeObservableToGrpc (cognitive 17) packages/microservices/server/server-grpc.ts
God Classes · ClassTooLong: RouterExecutionContext packages/core/router/router-execution-context.ts
God Classes · MethodTooLong: RouterExecutionContext.create packages/core/router/router-execution-context.ts
God Classes · FileTooLong: router/router-execution-context.ts packages/core/router/router-execution-context.ts
God Classes · ClassTooLong: ExpressAdapter packages/platform-express/adapters/express-adapter.ts
God Classes · ClassTooLong: InstanceWrapper packages/core/injector/instance-wrapper.ts
Coupling · Circular dependency packages/core/package.json
Cohesion (LCOM4) · Low cohesion: Server (LCOM4 4) packages/microservices/server/server.ts
Test Quality · Skipped test: should allow for the client to end the response and be able to make another integration/send-files/e2e/express.spec.ts
Test Quality · Skipped test: should not stream a non-file integration/send-files/e2e/fastify.spec.ts
Dependency Hygiene · Deprecated: nats package.json
Churn × Complexity Hotspots · Hotspot: REDACTED REDACTED
Churn × Complexity Hotspots · Hotspot: packages/platform-express/adapters/express-adapter.ts packages/platform-express/adapters/express-adapter.ts
Churn × Complexity Hotspots · Hotspot: packages/common/pipes/validation.pipe.ts packages/common/pipes/validation.pipe.ts
Churn × Complexity Hotspots · Hotspot: packages/core/router/route-params-factory.ts packages/core/router/route-params-factory.ts
Churn × Complexity Hotspots · Repeated repair: packages/core/middleware/utils.ts packages/core/middleware/utils.ts
Churn × Complexity Hotspots · Repeated repair: packages/core/middleware/route-info-path-extractor.ts packages/core/middleware/route-info-path-extractor.ts
Churn × Complexity Hotspots · Repeated repair: packages/microservices/helpers/json-socket.ts packages/microservices/helpers/json-socket.ts
Churn × Complexity Hotspots · Repeated repair: packages/common/services/console-logger.service.ts packages/common/services/console-logger.service.ts
Churn × Complexity Hotspots · Repeated repair: packages/core/router/router-execution-context.ts packages/core/router/router-execution-context.ts
Churn × Complexity Hotspots · Repeated repair: packages/common/interfaces/http/http-server.interface.ts packages/common/interfaces/http/http-server.interface.ts
Churn × Complexity Hotspots · Repeated repair: packages/microservices/interfaces/microservice-configuration.interface.ts packages/microservices/interfaces/microservice-configuration.interface.ts
Churn × Complexity Hotspots · Repeated repair: packages/platform-socket.io/adapters/io-adapter.ts packages/platform-socket.io/adapters/io-adapter.ts
Churn × Complexity Hotspots · Repeated repair: packages/common/file-stream/streamable-file.ts packages/common/file-stream/streamable-file.ts
Churn × Complexity Hotspots · Repeated repair: packages/core/middleware/builder.ts packages/core/middleware/builder.ts
Churn × Complexity Hotspots · Repeated repair: packages/testing/testing-injector.ts packages/testing/testing-injector.ts
Churn × Complexity Hotspots · Repeated repair: packages/core/middleware/middleware-module.ts packages/core/middleware/middleware-module.ts
Churn × Complexity Hotspots · Repeated repair: packages/core/interceptors/interceptors-consumer.ts packages/core/interceptors/interceptors-consumer.ts
Churn × Complexity Hotspots · Repeated repair: packages/core/injector/module-ref.ts packages/core/injector/module-ref.ts
Churn × Complexity Hotspots · Repeated repair: packages/microservices/constants.ts packages/microservices/constants.ts
Churn × Complexity Hotspots · Repeated repair: packages/microservices/exceptions/base-rpc-exception-filter.ts packages/microservices/exceptions/base-rpc-exception-filter.ts
Churn × Complexity Hotspots · Repeated repair: packages/websockets/exceptions/base-ws-exception-filter.ts packages/websockets/exceptions/base-ws-exception-filter.ts
Churn × Complexity Hotspots · Repeated repair: packages/core/discovery/discoverable-meta-host-collection.ts packages/core/discovery/discoverable-meta-host-collection.ts
Churn × Complexity Hotspots · Repeated repair: packages/core/security/cross-origin-protection.ts packages/core/security/cross-origin-protection.ts
Churn × Complexity Hotspots · Repeated repair: packages/microservices/serializers/kafka-request.serializer.ts packages/microservices/serializers/kafka-request.serializer.ts
Churn × Complexity Hotspots · Repeated repair: packages/core/helpers/external-context-creator.ts packages/core/helpers/external-context-creator.ts
Churn × Complexity Hotspots · Repeated repair: packages/core/middleware/routes-mapper.ts packages/core/middleware/routes-mapper.ts
Churn × Complexity Hotspots · Repeated repair: packages/platform-express/multer/interceptors/any-files.interceptor.ts packages/platform-express/multer/interceptors/any-files.interceptor.ts
Churn × Complexity Hotspots · Repeated repair: packages/platform-express/multer/interceptors/file-fields.interceptor.ts packages/platform-express/multer/interceptors/file-fields.interceptor.ts
Churn × Complexity Hotspots · Repeated repair: packages/platform-express/multer/interceptors/file.interceptor.ts packages/platform-express/multer/interceptors/file.interceptor.ts
Churn × Complexity Hotspots · Repeated repair: packages/platform-express/multer/interceptors/files.interceptor.ts packages/platform-express/multer/interceptors/files.interceptor.ts
Churn × Complexity Hotspots · Repeated repair: packages/core/helpers/handler-metadata-storage.ts packages/core/helpers/handler-metadata-storage.ts
Churn × Complexity Hotspots · Repeated repair: packages/microservices/context/rpc-proxy.ts packages/microservices/context/rpc-proxy.ts
Boundary Type-Coupling · Cross-context type ModuleDefinition (core → testing) packages/testing/interfaces/override-module.interface.ts
Boundary Type-Coupling · Cross-context type ModuleDefinition (core → testing) packages/testing/testing-module.builder.ts
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Code Duplication · Duplication concentrated across 9 sibling directories (44 clone groups) packages/microservices/context/rpc-context-creator.ts
Code Duplication · Duplicated block with local edits (215 matched lines × 2 locations) packages/microservices/context/rpc-context-creator.ts
Code Duplication · Duplicated block with local edits (97 matched lines × 2 locations) packages/core/interceptors/interceptors-context-creator.ts
Code Duplication · Duplicated block with local edits (88 matched lines × 2 locations) packages/microservices/server/server-nats.ts
Code Duplication · Wholesale file copy (55 identical lines × 2 files) packages/microservices/utils/param.utils.ts
Code Duplication · Wholesale file copy (52 identical lines × 3 files) packages/platform-socket.io/utils/merge-map-bounded.util.ts
Code Duplication · Duplicated block (46 lines × 2 locations) packages/platform-express/multer/interceptors/file-fields.interceptor.ts
Code Duplication · Duplicated block (46 lines × 2 locations) packages/platform-express/multer/interceptors/file.interceptor.ts
Code Duplication · Duplicated block (41 lines × 2 locations) packages/platform-express/adapters/utils/get-media-type-version.util.ts
Code Duplication · Duplicated block with local edits (40 matched lines × 2 locations) packages/microservices/client/client-nats.ts
Code Duplication · Duplicated block (29 lines × 2 locations) packages/microservices/client/client-kafka.ts
Code Duplication · Duplicated block (28 lines × 2 locations) packages/platform-express/multer/interceptors/any-files.interceptor.ts
Code Duplication · Duplicated block (27 lines × 2 locations) packages/microservices/client/client-mqtt.ts
Cyclomatic Complexity · Complex function (top-level) (cyclomatic 29, cognitive 29) packages/core/exceptions/base-exception-filter.ts
Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 25, cognitive 28) REDACTED
Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 23, cognitive 22) packages/platform-express/adapters/express-adapter.ts
Cyclomatic Complexity · Complex function transform (cyclomatic 20, cognitive 58) packages/common/pipes/parse-array.pipe.ts
Cyclomatic Complexity · Complex function transform (cyclomatic 20, cognitive 20) packages/common/pipes/validation.pipe.ts
Cyclomatic Complexity · Complex function (top-level) (cyclomatic 18, cognitive 16) packages/microservices/serializers/kafka-request.serializer.ts
Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 17, cognitive 16) packages/common/decorators/http/create-route-param-metadata.decorator.ts
Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 14, cognitive 18) packages/microservices/client/client-nats.ts
Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 14, cognitive 15) packages/microservices/client/client-mqtt.ts
Cyclomatic Complexity · Complex function processBuffer (cyclomatic 13, cognitive 29) packages/microservices/helpers/json-socket.ts
Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 13, cognitive 14) REDACTED
Large Files · REDACTED: 1683 lines of code REDACTED
Large Files · packages/core/injector/injector.ts: 1632 lines of code packages/core/injector/injector.ts
Large Files · packages/common/decorators/http/route-params.decorator.ts: 1101 lines of code packages/common/decorators/http/route-params.decorator.ts
Large Files · packages/microservices/server/server-grpc.ts: 910 lines of code packages/microservices/server/server-grpc.ts
Large Files · packages/common/services/console-logger.service.ts: 896 lines of code packages/common/services/console-logger.service.ts
Large Files · packages/core/scanner.ts: 772 lines of code packages/core/scanner.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: 203 findings

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

God Classes · MethodTooLong: RouterResponseController.sse packages/core/router/router-response-controller.ts
Coupling · Circular dependency
Churn × Complexity Hotspots · Hotspot: packages/common/pipes/file/file-type.validator.ts packages/common/pipes/file/file-type.validator.ts
Churn × Complexity Hotspots · Repeated repair: packages/common/pipes/parse-date.pipe.ts packages/common/pipes/parse-date.pipe.ts
Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
Knowledge Freshness · Orphaned knowledge packages/microservices/external/kafka.interface.ts
Change Coupling · Change coupling: app.controller.ts ↔ router-response-controller.ts integration/nest-application/sse/src/app.controller.ts
Change Coupling · Change coupling: client-rmq.ts ↔ server-rmq.ts packages/microservices/client/client-rmq.ts
Code Duplication · Duplication concentrated across 7 sibling directories (38 clone groups) packages/microservices/context/rpc-context-creator.ts
Code Duplication · Duplicated block with local edits (217 matched lines × 2 locations) packages/microservices/context/rpc-context-creator.ts
Code Duplication · Duplicated block with local edits (104 matched lines × 2 locations) packages/microservices/client/client-redis.ts
Code Duplication · Duplicated block with local edits (95 matched lines × 2 locations) packages/core/interceptors/interceptors-context-creator.ts
Code Duplication · Duplicated block with local edits (78 matched lines × 2 locations) packages/microservices/server/server-nats.ts
Code Duplication · Wholesale file copy (57 identical lines × 2 files) packages/microservices/utils/param.utils.ts
Code Duplication · Duplicated block (45 lines × 2 locations) packages/microservices/client/client-mqtt.ts
Code Duplication · Duplicated block (37 lines × 2 locations) packages/microservices/client/client-kafka.ts
Code Duplication · Duplicated block (37 lines × 2 locations) packages/microservices/client/client-mqtt.ts
Code Duplication · Duplicated block (36 lines × 3 locations) packages/platform-express/multer/interceptors/file-fields.interceptor.ts
Code Duplication · Duplicated block with local edits (35 matched lines × 2 locations) packages/microservices/client/client-nats.ts
Code Duplication · Duplicated block (35 lines × 2 locations) packages/platform-express/multer/interceptors/any-files.interceptor.ts
Code Duplication · Duplicated block with local edits (31 matched lines × 2 locations) packages/platform-fastify/multipart/multipart/multipart.parser.ts
Code Duplication · Duplicated block (24 lines × 2 locations) packages/common/pipes/parse-bool.pipe.ts
Code Duplication · Duplicated block (24 lines × 2 locations) packages/microservices/decorators/message-pattern.decorator.ts
Code Duplication · Duplicated block (23 lines × 3 locations) packages/core/helpers/external-context-creator.ts
Code Duplication · Duplicated block (23 lines × 2 locations) packages/core/router/router-exception-filters.ts
Code Duplication · Duplicated block (23 lines × 2 locations) REDACTED
Code Duplication · Duplicated block (22 lines × 2 locations) packages/core/hooks/on-app-bootstrap.hook.ts
Code Duplication · Duplicated block (22 lines × 3 locations) packages/core/router/router-execution-context.ts
Code Duplication · Duplicated block (22 lines × 2 locations) packages/platform-express/adapters/express-adapter.ts
Code Duplication · Duplicated block (21 lines × 2 locations) packages/core/exceptions/external-exceptions-handler.ts
Code Duplication · Duplicated block (21 lines × 2 locations) packages/core/guards/guards-context-creator.ts
Code Duplication · Duplicated block (21 lines × 2 locations) REDACTED
Code Duplication · Duplicated block (21 lines × 2 locations) packages/microservices/server/server-mqtt.ts
Code Duplication · Duplicated block (20 lines × 2 locations) integration/microservices/src/nats/nats.controller.ts
Code Duplication · Duplicated block (20 lines × 2 locations) integration/scopes/src/hello/hello.module.ts
Code Duplication · Duplicated block (20 lines × 3 locations) packages/common/pipes/parse-enum.pipe.ts
Code Duplication · Duplicated block (20 lines × 2 locations) packages/core/router/router-explorer.ts
Code Duplication · Duplicated block (20 lines × 3 locations) packages/microservices/server/server-mqtt.ts
Code Duplication · Duplicated block with local edits (20 matched lines × 2 locations) packages/platform-fastify/multipart/multipart/multipart-interceptor.factory.ts
Code Duplication · Duplicated block (19 lines × 2 locations) packages/core/middleware/routes-mapper.ts
Code Duplication · Duplicated block (18 lines × 2 locations) integration/graphql-schema-first/src/cats/cats-request-scoped.service.ts
Code Duplication · Duplicated block (18 lines × 2 locations) integration/typeorm/src/async-class-options.module.ts
Code Duplication · Duplicated block with local edits (18 matched lines × 2 locations) packages/core/router/route-conflict-detector.ts
Code Duplication · Duplicated block (18 lines × 2 locations) packages/platform-express/adapters/utils/get-media-type-version.util.ts
Code Duplication · Duplicated block with local edits (17 matched lines × 2 locations) integration/graphql-code-first/src/common/scalars/date.scalar.ts
Code Duplication · Duplicated block (17 lines × 4 locations) integration/inspector/src/database/database.controller.ts
Code Duplication · Duplicated block (17 lines × 2 locations) integration/microservices/src/grpc/grpc.controller.ts
Code Duplication · Duplicated block (17 lines × 2 locations) packages/microservices/client/client-mqtt.ts
Code Duplication · Duplicated block (16 lines × 5 locations) integration/inspector/src/circular-hello/hello.controller.ts
Code Duplication · Duplicated block with local edits (16 matched lines × 2 locations) integration/inspector/src/durable/durable-context-id.strategy.ts
Code Duplication · Duplicated block (16 lines × 2 locations) integration/inspector/src/users/users.service.ts
Code Duplication · Duplicated block (16 lines × 2 locations) integration/microservices/src/mqtt/mqtt-broadcast.controller.ts
Code Duplication · Duplicated block (16 lines × 21 locations) packages/common/exceptions/bad-gateway.exception.ts
Code Duplication · Duplicated block (16 lines × 2 locations) packages/common/interfaces/nest-application-context.interface.ts
Code Duplication · Duplicated block (16 lines × 2 locations) packages/core/exceptions/exceptions-handler.ts
Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) integration/scopes/src/inject-inquirer/hello-request/request-logger.service.ts
Code Duplication · Duplicated block (15 lines × 2 locations) packages/common/services/console-logger.service.ts
Code Duplication · Duplicated block (15 lines × 2 locations) packages/core/injector/injector.ts
Code Duplication · Duplicated block (15 lines × 2 locations) packages/core/injector/module.ts
Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) packages/core/router/route-path-factory.ts
Code Duplication · Duplicated block (15 lines × 3 locations) packages/core/router/router-exception-filters.ts
Code Duplication · Duplicated block (15 lines × 2 locations) packages/microservices/client/client-mqtt.ts
Code Duplication · Duplicated block (15 lines × 2 locations) packages/microservices/client/client-redis.ts
Code Duplication · Duplicated block (15 lines × 2 locations) packages/microservices/client/client-rmq.ts
Code Duplication · Duplicated block (15 lines × 2 locations) packages/websockets/web-sockets-controller.ts
Code Duplication · Duplicated block (14 lines × 2 locations) integration/microservices/src/kafka/kafka.controller.ts
Code Duplication · Duplicated block (14 lines × 2 locations) integration/scopes/src/hello/guards/request-scoped.guard.ts
Code Duplication · Duplicated block (14 lines × 2 locations) integration/websockets/src/app.gateway.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/core/discovery/discovery-service.ts
Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) packages/core/errors/exceptions-zone.ts
Code Duplication · Duplicated block (14 lines × 3 locations) packages/core/router/router-explorer.ts
Code Duplication · Duplicated block (14 lines × 2 locations) REDACTED
Code Duplication · Duplicated block (14 lines × 2 locations) packages/microservices/client/client-kafka.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/microservices/exceptions/rpc-exception.ts
Code Duplication · Duplicated block (14 lines × 3 locations) packages/microservices/module/clients.module.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/microservices/server/server-kafka.ts
Code Duplication · Duplicated block (13 lines × 2 locations) integration/inspector/src/circular-hello/hello.module.ts
Code Duplication · Duplicated block (13 lines × 2 locations) integration/scopes/src/circular-transient/hello.module.ts
Code Duplication · Duplicated block (13 lines × 3 locations) packages/common/decorators/core/use-guards.decorator.ts
Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) packages/common/pipes/file/file-type.validator.ts
Code Duplication · Duplicated block (13 lines × 5 locations) packages/common/pipes/parse-bool.pipe.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/core/middleware/middleware-module.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/core/nest-application.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/microservices/client/client-tcp.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/microservices/client/client-tcp.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/microservices/listeners-controller.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/microservices/server/server-grpc.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/microservices/server/server-mqtt.ts
Code Duplication · Duplicated block (12 lines × 4 locations) integration/inspector/src/circular-hello/guards/request-scoped.guard.ts
Code Duplication · Duplicated block (12 lines × 2 locations) integration/microservices/src/kafka-concurrent/kafka-concurrent.controller.ts

Rebuild cost: about €160,000 · Estimate

Cost to rebuild	€52,000 to €260,000, for 863 to 2,739 hours of work, about 1.1 person-years for 1 to 3 engineers
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 48. 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: 69,723 lines of product code
What it is not	Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.

Raises the score by about 6 points · Low effort · REDACTED Scanning

Resolve the 3 No assertions (empty test) finding(s) in Test Quality — start with router-response-controller.spec.ts (2), fastify-multiple.spec.ts.

Raises the score by about 3 points · Low effort · Test Quality

Improve Test Distribution — currently 6.5/10.

Raises the score by about 5 points · Medium effort · Test Distribution

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 €160,000 to build again, about 1.1 person-years of work. Its weakest lens is Production Readiness, at 40 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.

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

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

If you do one thing first · First action

Resolve the 1 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for low effort, because it clears the 1 REDACTED Scanning 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, which only happens where the projects form a dependency cycle. A graph without cycles 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.

500 modules, with 855 dependencies between them. 4 loops run through 13 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 460 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 common.enums.request-method_enum	4 common.interfaces.features.pipe-transform_interface	5 common.interfaces.modules.injection-token_interface	6 common.interfaces.nest-application-options_interface	7 common.interfaces.type_interface	8 common.interfaces.version-options_interface	9 common.services.logger_service	12 microservices.interfaces.packet_interface	13 common.interfaces.features.execution-context_interface	14 common.interfaces.http.http-server_interface	15 common.interfaces.modules.dynamic-module_interface	16 common.interfaces.modules.provider_interface	17 core.injector.injector	19 microservices.server.server	20 websockets.context.ws-context-creator	21 common.interfaces.features.nest-interceptor_interface	22 core.adapters.http-adapter	23 core.injector.container	24 core.router.router-execution-context	25 core.injector.module-ref	26 core.injector.module	27 core.injector.instance-wrapper	28 core.application-config	30 core.inspector.graph-inspector	31 core.nest-application-context	32 core.middleware.middleware-module	33 core.router.router-explorer	35 microservices.context.rpc-context-creator	37 core.nest-application
1 common.enums.request-method_enum
2 common.exceptions.http_exception
3 common.interfaces.features.arguments-host_interface
4 common.interfaces.features.pipe-transform_interface
5 common.interfaces.modules.injection-token_interface
6 common.interfaces.nest-application-options_interface
7 common.interfaces.type_interface
8 common.interfaces.version-options_interface
9 common.services.logger_service
10 core.errors.exceptions.runtime_exception
11 microservices.interfaces.microservice-configuration_interface
12 microservices.interfaces.packet_interface
13 common.interfaces.features.execution-context_interface					1
14 common.interfaces.http.http-server_interface	1			1		1
15 common.interfaces.modules.dynamic-module_interface					1
16 common.interfaces.modules.provider_interface			4		1
17 core.injector.injector			1		1		1														1	6
18 microservices.client.client-proxy								1
19 microservices.server.server							1	1
20 websockets.context.ws-context-creator		1
21 common.interfaces.features.nest-interceptor_interface									1
22 core.adapters.http-adapter	1			1		1				1
23 core.injector.container			1		1						1	1									1	1
24 core.router.router-execution-context	1	1								1
25 core.injector.module-ref					1								1					1			1	1
26 core.injector.module			1		1							5						1		1		1
27 core.injector.instance-wrapper			2				1					1									1
28 core.application-config		1														1						1
29 core.helpers.external-context-creator		1																1				1
30 core.inspector.graph-inspector																		1			1	1
31 core.nest-application-context													1					1			1	1
32 core.middleware.middleware-module			1							1			1					1			1	2	1	1
33 core.router.router-explorer	2				1	1							1					1	1		1	2	1	1
34 core.scanner			2		1							1						1			1	1		1
35 microservices.context.rpc-context-creator		1																					1
36 websockets.web-sockets-controller													1		1			1			1	2	1	1
37 core.nest-application				1						1							1	1					1	1	1	1
38 core.router.routes-resolver					1					1			1					1				1	1	1			1
39 microservices.listeners-controller													1	1				1			1	2		1				1
40 testing.testing-module				1						1							1	1			1		1	1	1				1

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 65% · Adequate ·

The Good

D1 · TypeScript Cyclomatic Complexity 7.5 D3 · TypeScript God Classes 8.8 D17 · TypeScript Explicit Debt 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 7.5 R1 · React / TS Type Safety 8.5 R10 · React / TS Code Duplication 8.7 R2 · React / TS Cyclomatic Complexity 9.3 R3 · React / TS Large Files 8.9 R7 · React / TS Dead Code 7.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 10.0 X25 · Repo Inert configuration knob 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0

The Bad

D2 · TypeScript Cognitive Complexity 6.5 X3 · Repo Exception handling 6.4 X4 · Repo Structured logging 5.1

The Ugly

X5 · Repo Nullable reference types 4.9

At a glance — Architecture · 55% · Adequate · gated by D5, R9 ·

The Good

D6 · TypeScript Cohesion (LCOM4) 9.6 D23 · TypeScript Boundary Type-Coupling 9.9 D35 · TypeScript Change Coupling 10.0 AX10 · Repo Code composition 8.9 AX3 · Repo Project dependency cycles 7.1 AX4 · Repo Dependency direction 7.1 AX6 · Repo Interface segregation 9.9 R11 · React / TS Import Boundaries 9.8

The Ugly

D5 · TypeScript Coupling 0.0 D26 · TypeScript Project Cohesion 4.0 R9 · React / TS Circular Imports 0.0

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

The Good

D15 · TypeScript Churn × Complexity Hotspots 9.9 D16 · TypeScript Bus Factor 8.9 D19 · TypeScript Documentation Quality 10.0 D34 · TypeScript Knowledge Freshness 9.4 M1 · Repo Documentation (README) 7.9 M3 · Repo Folder & project structure 10.0

The Ugly

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

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

The Good

D10 · TypeScript Test Quality 10.0 D12 · TypeScript Dependency Hygiene 9.4 D14 · TypeScript License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P2 · Repo Observability 7.0 P3 · Repo Security & performance tooling 7.0 P4 · Repo Deployment & Rollback 7.0 R4 · React / TS Test Coverage 9.5 R5 · React / TS Dependency Freshness 8.1 R6 · React / TS Tooling 10.0

The Bad

D9 · TypeScript Test Distribution 6.5 D13 · TypeScript REDACTED Scanning 5.0 P6 · Repo Release Hygiene 5.0

The Ugly

P5 · Repo DR & Backup 4.0 P8 · Repo Schema migrations 3.0 R8 · React / TS Dependency Hygiene 0.0

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

The Good

D28 · TypeScript Secrets (history) 9.0 D31 · TypeScript IaC & Container Security 8.3 D37 · TypeScript Vulnerability-disclosure Policy 10.0 D43 · TypeScript Malicious Dependencies 10.0 C2 · Repo Access Controls 7.0 S1 · Repo Web-Security Posture 8.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0

The Bad

D44 · TypeScript Platform End-of-Life 6.0

The Ugly

D29 · TypeScript Static Analysis (SAST) 2.3 D30 · TypeScript Dependency Vulnerabilities 0.0 X17 · Repo Uncapped recursion over a caller-supplied document 2.2

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

The Good

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

At a glance — 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	27	High / Critical
A05:2025 — Injection	18	High / Critical
A02:2025 — Security Misconfiguration	8	High / Critical
A07:2025 — Authentication Failures	3	High / Critical

Roadmap

Immediately resolve the leaked private key to secure the codebase, then streamline test execution by improving distribution across the extensive JavaScript and TypeScript suites. Concurrently, correct documentation inaccuracies by removing broken links and reconciling README files with the actual repository structure. Finally, clean up dependencies by removing unused packages and explicitly declaring imports, while establishing a dedicated folder to record significant architectural decisions for future reference.

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

Do this	Helps	Effort	Dimension
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.	+5.7 pts	Low	REDACTED Scanning
Resolve the 3 No assertions (empty test) finding(s) in Test Quality — start with router-response-controller.spec.ts (2), fastify-multiple.spec.ts.	+3.1 pts	Low	Test Quality
Improve Test Distribution — currently 6.5/10.	+4.7 pts	Medium	Test Distribution
Reconcile the README with reality: packages/common/Readme.md links to `readme_zh.md`, but `packages/common/readme_zh.md` does not exist; packages/common/Readme.md links to `readme_kr.md`, but `packages/common/readme_kr.md` does not exist; packages/common/Readme.md links to `readme_jp.md`, but `packages/common/readme_jp.md` does not exist; packages/core/Readme.md links to `readme_zh.md`, but `packages/core/readme_zh.md` does not exist; packages/core/Readme.md links to `readme_kr.md`, but `packages/core/readme_kr.md` does not exist.	+4.7 pts	Medium	Documentation accuracy
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.	+4.0 pts	Medium	Dependency Hygiene
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.	+3.9 pts	Medium	Architecture documentation
Resolve the 1 Circular dependency finding(s) in Coupling — start with package.json.	+1.9 pts	Low	Coupling
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion.	+1.5 pts	Low	Project Cohesion

File quality

Per-file score 0–10 — a quality signature. Of 99 files carrying findings, judged against the Production bar: 4% slop · 37% mixed · 59% near-clean.

File	Score	Band	Worst signal
REDACTED	0.0	Slop	Dependency Vulnerabilities: Critical CVE: REDACTED
REDACTED	0.8	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	2.5	Slop	Static Analysis (SAST): High: REDACTED
packages/core/test/router/router-response-controller.spec.ts	3.9	Slop	Test Quality: No assertions (empty test): should close on socket close
REDACTED	4.0	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	4.4	Mixed	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	4.8	Mixed	Static Analysis (SAST): High: REDACTED
packages/platform-express/adapters/express-adapter.ts	5.5	Mixed	Cyclomatic Complexity: ExpressAdapter.applyVersionFilter (cyclomatic 33)
tools/gulp/tasks/samples.ts	6.0	Mixed	Explicit Debt: TodoComment
REDACTED	6.4	Mixed	Static Analysis (SAST): Medium: REDACTED
package.json	6.4	Mixed	Platform End-of-Life: End-of-life runtime: Node.js 20
integration/send-files/e2e/express.spec.ts	6.7	Mixed	Explicit Debt: TodoComment
packages/microservices/test/client/client-grpc.spec.ts	6.8	Mixed	Test Quality: No assertions: should create grpcService
REDACTED	6.9	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	7.2	Mixed	Static Analysis (SAST): High: REDACTED
packages/common/services/utils/redact.util.ts	7.4	Mixed	Cyclomatic Complexity: redact.util.createRedactor (cyclomatic 46)
packages/core/security/security-headers.ts	7.4	Mixed	Cyclomatic Complexity: security-headers.resolveSecurityHeaders (cyclomatic 22)
packages/core/injector/injector.ts	7.4	Mixed	God Classes: ClassTooLong: Injector
packages/common/services/console-logger.service.ts	7.4	Mixed	God Classes: TooManyMethods: ConsoleLogger
packages/core/scanner.ts	7.4	Mixed	God Classes: ClassTooLong: DependenciesScanner

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

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

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

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

Could not be resolved — 6

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 79 of 79 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — 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

D1D2D3D5D6D9D10D12D13D14D15D16D17D19D23D26D28D29D30D31D34D35D37D43D44AX10AX3AX4AX6C2DM6DM9GD1IC1M1M2M3M4P1P10P2P3P4P5P6P8PF3R1R10R11R2R3R4R5R6R7R8R9S1X1X12X13X14X15X16X17X18X19X21X22X23X24X25X28X29X3X30X4X5

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, 876 of 907 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	—	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a177f4-cfd6-7bc7-9213-25c4212e68fc.

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.

D19 Documentation Quality — 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — 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. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/common/services/log-levels.constant.ts`, `packages/core/helpers/router-method-factory.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 (sample/37-outbox/docker-compose.yml). compose up failed (exit 18 — an image could not be pulled) — postgres Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: postgres Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
R10 Code Duplication — measured, with a gap in what it reached — 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. 148 further occurrence(s) are not listed individually; the score already reflects all 188.
R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 4 further occurrence(s) are not listed individually; the score already reflects all 44.
R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 45 further occurrence(s) are not listed individually; the score already reflects all 85.
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: 5 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.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a 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.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity7.5 / 10Strong✓ Tool-verified

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

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

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

16 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was redact.util.createRedactor at 46. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being multer.utils.transformException at 21 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/platform-express/multer/multer/multer.utils.ts (multer.utils.transformException at 21), packages/core/exceptions/base-exception-filter.ts (BaseExceptionFilter.isHttpError at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

redact.util.createRedactor (cyclomatic 46)packages/common/services/utils/redact.util.ts:33

ExpressAdapter.applyVersionFilter (cyclomatic 33)packages/platform-express/adapters/express-adapter.ts:543

RouterResponseController.sse (cyclomatic 27)packages/core/router/router-response-controller.ts:124

RouteParamsFactory.exchangeKeyForValue (cyclomatic 26)packages/core/router/route-params-factory.ts:29

serialize-cookie.serializeCookie (cyclomatic 25)packages/core/helpers/cookies/serialize-cookie.ts:40

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

What to do

Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with redact.util.createRedactor (cyclomatic 46), ExpressAdapter.applyVersionFilter (cyclomatic 33). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 7.5 to about 8.0/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
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 Complexity6.5 / 10Adequate✓ Tool-verified

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

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

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

24 method(s) exceeded the cognitive complexity threshold of 15; the worst was ParseArrayPipe.transform at 66.

ExpressAdapter.applyVersionFilter::handlerForMediaTypeVersioning (cognitive 17) · ×2packages/platform-express/adapters/express-adapter.ts:612

ParseArrayPipe.transform (cognitive 66)packages/common/pipes/parse-array.pipe.ts:84

redact.util.createRedactor (cognitive 58)packages/common/services/utils/redact.util.ts:33

serialize-cookie.serializeCookie (cognitive 31)packages/core/helpers/cookies/serialize-cookie.ts:40

JsonSocket.processBuffer (cognitive 29)packages/microservices/helpers/json-socket.ts:114

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

What to do

Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with ParseArrayPipe.transform (cognitive 66), redact.util.createRedactor (cognitive 58), serialize-cookie.serializeCookie (cognitive 31). — 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 3 together lifts Cognitive Complexity from 6.5 to about 7.4/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
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.8 / 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.8 / 10 · rule-coverage 100% · ceiling Prevented

32 god class(es) detected.

TooManyMethods: AbstractHttpAdapter · ×12packages/core/adapters/http-adapter.ts:60

ClassTooLong: Injector · ×10packages/core/injector/injector.ts:111

FileTooLong: injector/injector.ts · ×8packages/core/injector/injector.ts

FunctionTooLong: redact.util.createRedactorpackages/common/services/utils/redact.util.ts:33

MethodTooLong: RouterExecutionContext.createpackages/core/router/router-execution-context.ts:106

What to do

Resolve the 12 TooManyMethods finding(s) in God Classes — start with http-adapter.ts, REDACTED, injector.ts. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 10 ClassTooLong finding(s) in God Classes — start with injector.ts, REDACTED, scanner.ts. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 8 FileTooLong finding(s) in God Classes — start with injector.ts, REDACTED, kafka.interface.ts. — One of this dimension's main actionable groups (8 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 · Coupling0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Prevented

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

Circular dependencypackages/core/package.json:44

What to do

Resolve the 1 Circular dependency finding(s) in Coupling — start with package.json. — One of this dimension's main actionable groups (1 issue-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)9.6 / 10Stronggated by 4 serious findings✓ Tool-verified

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

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

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

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

4 of 134 classes have LCOM4 above 3.

Low cohesion: ExpressAdapter (LCOM4 12) · ×4packages/platform-express/adapters/express-adapter.ts:68

What to do

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

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

Do you agree with this assessment?

D9 · Test Distribution6.5 / 10Adequate✓ Tool-verified

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

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

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

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

What to do

Improve Test Distribution — currently 6.5/10. — 6496 test methods: 4751 unit, 7 integration, 0 BDD, 1738 e2e. The JavaScript/TypeScript suite contributes 6496 `it`/`test` case(s) across 602 test file(s) declaring at least one; its tier split is read from package names and paths only.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality10.0 / 10Adequategated by 3 critical 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

117 skipped (115 with a documented reason), 14 zero-assertion, 5 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 6496 tests.

No assertions (empty test): should close on socket close · ×3packages/core/test/router/router-response-controller.spec.ts:632

No assertions: should initialize and close without error · ×11packages/testing/test/testing-module.spec.ts:185

Fixed-sleep synchronisation: should not subscribe async SSE producer Observable when client disconnects mid-await (interceptor case, issue #17352) · ×5packages/core/test/router/router-response-controller.spec.ts:778

Skipped test: should allow for the client to end the response and be able to make another · ×2integration/send-files/e2e/express.spec.ts:99

Mock-dominated test: should call "decorateWithNamespace" and not call "createSocketServer" · ×137packages/websockets/test/socket-server-provider.spec.ts:61

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

What to do

Resolve the 3 No assertions (empty test) finding(s) in Test Quality — start with router-response-controller.spec.ts (2), fastify-multiple.spec.ts. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 11 No assertions finding(s) in Test Quality — start with client-grpc.spec.ts (2), concurrent-kafka.spec.ts (2), capturing-logger.spec.ts (2). — One of this dimension's main actionable groups (11 warning-level).
Resolve the 5 Fixed-sleep synchronisation finding(s) in Test Quality — start with router-response-controller.spec.ts (3), express.spec.ts, fastify.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?

D12 · Dependency Hygiene9.4 / 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.4 / 10 · rule-coverage 100% · ceiling Verified

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

Deprecated: natspackage.json:145

Deprecated: @npmcli/move-file · ×22REDACTED:3509

Outdated (npm): fast-json-stringify · ×2

What to do

Resolve the 22 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (22). — One of this dimension's main actionable groups (22 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).
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 · REDACTED Scanning5.0 / 10Adequate✓ Tool-verified

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

1 secret(s) detected.

REDACTED

What to do

Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

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

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

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

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

Top hotspots: REDACTED (39×20=780); packages/core/router/router-response-controller.ts (16×27=432); packages/platform-express/adapters/express-adapter.ts (22×17=374) Repeated repair below the complexity floor: packages/core/injector/injector.ts (23 of 24 changes were fixes); packages/microservices/server/server-grpc.ts (16 of 17 changes were fixes); packages/microservices/server/server-tcp.ts (15 of 17 changes were fixes)

Repeated repair: packages/core/injector/injector.ts · ×58packages/core/injector/injector.ts:400

Hotspot: REDACTED · ×10REDACTED:1243

What to do

Resolve the 58 Repeated repair finding(s) in Churn × Complexity Hotspots — start with injector.ts, server-grpc.ts, server-tcp.ts. — One of this dimension's main actionable groups (58 warning-level).
Resolve the 10 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED, router-response-controller.ts, express-adapter.ts. — One of this dimension's main actionable groups (10 warning-level).

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

Do you agree with this assessment?

D16 · Bus Factor8.9 / 10Strong✓ Tool-verified

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

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

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

21 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/core/helpers/external-context-creator.ts. Counted over 186 of the 1103 production source files in this repository: 916 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.

Off-boarding risk: anonymized user #1

Further sole-owners (lower concentration)

What to do

Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

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

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

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

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

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

TodoComment · ×4tools/gulp/tasks/samples.ts:26

What to do

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

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

Do you agree with this assessment?

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

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

1 of 1 documentation facets pass in full. 14 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

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

Cross-context type ModuleDefinition (core → testing) · ×2packages/testing/interfaces/override-module.interface.ts:8

What to do

Resolve the 2 Cross-context type ModuleDefinition (core → testing) finding(s) in Boundary Type-Coupling — start with override-module.interface.ts, testing-module.builder.ts. — One of this dimension's main actionable groups (2 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 Cohesion4.0 / 10Weak✓ 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 4.0 / 10 · rule-coverage 100% · ceiling Documented

3 of 10 build units (npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D28 · Secrets (history)9.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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

Method: REDACTED 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 9.0 / 10 · rule-coverage 100% · ceiling Documented

1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED

What to do

Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

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

18 finding(s): 0 critical, 10 high, 8 medium, 0 low. 4 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 2 file(s) — `packages/common/services/log-levels.constant.ts` (line 8), `packages/core/helpers/router-method-factory.ts` (line 22) — 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

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

What to do

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

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

Do you agree with this assessment?

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

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

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

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

27 finding(s): 2 critical, 14 high, 10 medium, 1 low.

REDACTED

What to do

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

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

Do you agree with this assessment?

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

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

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

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

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

REDACTED

What to do

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

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

Do you agree with this assessment?

D34 · Knowledge Freshness9.4 / 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 9.4 / 10 · rule-coverage 100% · ceiling Documented

10 of 187 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is tools/benchmarks/src/main.ts. Counted over 187 of the 1103 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×10tools/benchmarks/src/main.ts:1

Orphaned files with no living knowledge

✓ On the Gold path — maintain.

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

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-Life6.0 / 10Adequate✓ 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 6.0 / 10 · rule-coverage 100% · ceiling Documented

1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 19 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.

End-of-life runtime: Node.js 20package.json:164

What to do

Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AX10 · Code composition8.9 / 10Strong✓ Tool-verified

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

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

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

What to do

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

Do you agree with this assessment?

AX3 · Project dependency cycles7.1 / 10Strong✓ 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.

The projects @nestjs/core → @nestjs/microservices → @nestjs/core (one cycle inside a mutually-dependent group of 5 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference. — packages/core/package.json:44

What to do

Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.

Do you agree with this assessment?

AX4 · Dependency direction7.1 / 10Strong✓ 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.

`@nestjs/core` is a Domain project but references `@nestjs/websockets`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — packages/core/package.json:46

What to do

Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).

Do you agree with this assessment?

AX6 · Interface segregation9.9 / 10Exemplary✓ Tool-verified

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

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

`HttpServer` declares 36 required operations: `use`, `use`, `get`, `get`, `post`, `post`, `head`, `head`, `delete`, `delete`, `put`, `put`, `patch`, `patch`, `all`, `all`, `options`, `options`, `listen`, `listen`, `reply`, `status`, `end`, `render`, `redirect`, `isHeadersSent`, `setHeader`, `createMiddlewareFactory`, `getInstance`, `registerParserMiddleware`, `enableCors`, `getHttpServer`, `initHttpServer`, `close`, `getType`, `applyVersionFilter`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. Those 36 declarations carry 26 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 26 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/common/interfaces/http/http-server.interface.ts:190
`INestApplicationContext` declares 16 required operations under just 9 distinct name(s): `select`, `get`, `get`, `get`, `get`, `resolve`, `resolve`, `resolve`, `resolve`, `resolve`, `registerRequestByContextId`, `close`, `useLogger`, `flushLogs`, `enableShutdownHooks`, `init`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 16 separate responsibilities: a caller binds to 9 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 16 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — packages/common/interfaces/nest-application-context.interface.ts:29
`INestApplication` declares 20 required operations: `use`, `enableCors`, `enableCsrfProtection`, `useSecurityHeaders`, `enableVersioning`, `listen`, `listen`, `getUrl`, `setGlobalPrefix`, `useWebSocketAdapter`, `connectMicroservice`, `getMicroservices`, `getHttpServer`, `getHttpAdapter`, `startAllMicroservices`, `useGlobalFilters`, `useGlobalPipes`, `useGlobalInterceptors`, `useGlobalGuards`, `close`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. Those 20 declarations carry 19 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 19 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/common/interfaces/nest-application.interface.ts:22

What to do

Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.

Do you agree with this assessment?

C2 · Access Controls7.0 / 10Strong✓ Tool-verified

Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.

Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.

Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.

What to do

Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.

Do you agree with this assessment?

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

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

IC1 · Incompleteness & stubs7.5 / 10Strong✓ 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.

`remove` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — integration/graphql-code-first/src/recipes/recipes.service.ts:28
`asynchronous` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — integration/hello-world/src/errors/errors.controller.ts:11
`create` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — integration/inspector/src/cats/cats.controller.ts:14
`syncCall` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — integration/microservices/src/grpc-advanced/advanced.grpc.controller.ts:119
`streamReqCall` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — integration/microservices/src/grpc-advanced/advanced.grpc.controller.ts:155
`sumStreamPass` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — integration/microservices/src/grpc/grpc.controller.ts:92
`go` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — integration/microservices/src/kafka-concurrent/kafka-concurrent.messages.controller.ts:12
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×6) — integration/cors/e2e/fastify.spec.ts:10, integration/hello-world/e2e/fastify-multiple.spec.ts:2, integration/microservices/e2e/concurrent-kafka.spec.ts:10, …

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

Do you agree with this assessment?

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

Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 20 of 53 project(s) that lack one — worth up to 0.8 pts.

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✓ Tool-verified

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.

packages/common/Readme.md links to `readme_zh.md`, but `packages/common/readme_zh.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/common/Readme.md:38
packages/common/Readme.md links to `readme_kr.md`, but `packages/common/readme_kr.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/common/Readme.md:39
packages/common/Readme.md links to `readme_jp.md`, but `packages/common/readme_jp.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/common/Readme.md:40
packages/core/Readme.md links to `readme_zh.md`, but `packages/core/readme_zh.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/core/Readme.md:38
packages/core/Readme.md links to `readme_kr.md`, but `packages/core/readme_kr.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/core/Readme.md:39
packages/core/Readme.md links to `readme_jp.md`, but `packages/core/readme_jp.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/core/Readme.md:40
packages/microservices/Readme.md links to `readme_zh.md`, but `packages/microservices/readme_zh.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/microservices/Readme.md:38
packages/microservices/Readme.md links to `readme_kr.md`, but `packages/microservices/readme_kr.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/microservices/Readme.md:39
packages/microservices/Readme.md links to `readme_jp.md`, but `packages/microservices/readme_jp.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/microservices/Readme.md:40
packages/platform-express/Readme.md links to `readme_zh.md`, but `packages/platform-express/readme_zh.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/platform-express/Readme.md:38
packages/platform-express/Readme.md links to `readme_kr.md`, but `packages/platform-express/readme_kr.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/platform-express/Readme.md:39
packages/platform-express/Readme.md links to `readme_jp.md`, but `packages/platform-express/readme_jp.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/platform-express/Readme.md:40
packages/platform-fastify/Readme.md links to `readme_zh.md`, but `packages/platform-fastify/readme_zh.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/platform-fastify/Readme.md:38
packages/platform-fastify/Readme.md links to `readme_kr.md`, but `packages/platform-fastify/readme_kr.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/platform-fastify/Readme.md:39
packages/platform-fastify/Readme.md links to `readme_jp.md`, but `packages/platform-fastify/readme_jp.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/platform-fastify/Readme.md:40
packages/platform-socket.io/Readme.md links to `readme_zh.md`, but `packages/platform-socket.io/readme_zh.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/platform-socket.io/Readme.md:38
packages/platform-socket.io/Readme.md links to `readme_kr.md`, but `packages/platform-socket.io/readme_kr.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/platform-socket.io/Readme.md:39
packages/platform-socket.io/Readme.md links to `readme_jp.md`, but `packages/platform-socket.io/readme_jp.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/platform-socket.io/Readme.md:40
packages/platform-ws/Readme.md links to `readme_zh.md`, but `packages/platform-ws/readme_zh.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/platform-ws/Readme.md:38
packages/platform-ws/Readme.md links to `readme_kr.md`, but `packages/platform-ws/readme_kr.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/platform-ws/Readme.md:39
packages/platform-ws/Readme.md links to `readme_jp.md`, but `packages/platform-ws/readme_jp.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/platform-ws/Readme.md:40
packages/testing/Readme.md links to `readme_zh.md`, but `packages/testing/readme_zh.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/testing/Readme.md:38
packages/testing/Readme.md links to `readme_kr.md`, but `packages/testing/readme_kr.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/testing/Readme.md:39
packages/testing/Readme.md links to `readme_jp.md`, but `packages/testing/readme_jp.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/testing/Readme.md:40
packages/websockets/Readme.md links to `readme_zh.md`, but `packages/websockets/readme_zh.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/websockets/Readme.md:38
packages/websockets/Readme.md links to `readme_kr.md`, but `packages/websockets/readme_kr.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/websockets/Readme.md:39
packages/websockets/Readme.md links to `readme_jp.md`, but `packages/websockets/readme_jp.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/websockets/Readme.md:40

What to do

Reconcile the README with reality: packages/common/Readme.md links to `readme_zh.md`, but `packages/common/readme_zh.md` does not exist; packages/common/Readme.md links to `readme_kr.md`, but `packages/common/readme_kr.md` does not exist; packages/common/Readme.md links to `readme_jp.md`, but `packages/common/readme_jp.md` does not exist; packages/core/Readme.md links to `readme_zh.md`, but `packages/core/readme_zh.md` does not exist; packages/core/Readme.md links to `readme_kr.md`, but `packages/core/readme_kr.md` 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 · Observability7.0 / 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.

`integration/repl/src/repl.ts` reports through `console.*` at line 8 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — integration/repl/src/repl.ts:8
`integration/nest-application/listen/src/fastify-fd-main.js` reports through `console.*` at line 28 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — integration/nest-application/listen/src/fastify-fd-main.js:28
`integration/inspector/src/core/interceptors/logging.interceptor.ts` reports through `console.*` at line 13 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — integration/inspector/src/core/interceptors/logging.interceptor.ts:13
`integration/inspector/src/core/interceptors/logging.interceptor.ts` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — integration/inspector/src/core/interceptors/logging.interceptor.ts:18
`integration/inspector/src/common/middleware/logger.middleware.ts` reports through `console.*` at line 6 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — integration/inspector/src/common/middleware/logger.middleware.ts:6
`integration/discovery/src/my-webhook/cleanup.webhook.ts` reports through `console.*` at line 7 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — integration/discovery/src/my-webhook/cleanup.webhook.ts:7
`integration/discovery/src/my-webhook/flush.webhook.ts` reports through `console.*` at line 7 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — integration/discovery/src/my-webhook/flush.webhook.ts:7
`integration/auto-mock/src/foo.service.ts` reports through `console.*` at line 6 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — integration/auto-mock/src/foo.service.ts:6
`packages/common/services/console-logger.service.ts` reports through `console.*` at line 462 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/common/services/console-logger.service.ts:462
`packages/common/services/console-logger.service.ts` reports through `console.*` at line 464 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/common/services/console-logger.service.ts:464
`packages/common/services/console-logger.service.ts` reports through `console.*` at line 490 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/common/services/console-logger.service.ts:490
`packages/common/services/console-logger.service.ts` reports through `console.*` at line 492 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/common/services/console-logger.service.ts:492
`packages/common/services/console-logger.service.ts` reports through `console.*` at line 728 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/common/services/console-logger.service.ts:728
`packages/common/decorators/http/route-params.decorator.ts` reports through `console.*` at line 224 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/common/decorators/http/route-params.decorator.ts:224
`packages/common/decorators/http/route-params.decorator.ts` reports through `console.*` at line 241 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/common/decorators/http/route-params.decorator.ts:241
`packages/common/decorators/http/route-params.decorator.ts` reports through `console.*` at line 261 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/common/decorators/http/route-params.decorator.ts:261
`packages/common/decorators/http/route-params.decorator.ts` reports through `console.*` at line 281 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/common/decorators/http/route-params.decorator.ts:281
`packages/common/decorators/http/route-params.decorator.ts` reports through `console.*` at line 307 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/common/decorators/http/route-params.decorator.ts:307
`packages/common/decorators/http/route-params.decorator.ts` reports through `console.*` at line 324 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/common/decorators/http/route-params.decorator.ts:324
`packages/common/decorators/http/route-params.decorator.ts` reports through `console.*` at line 343 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/common/decorators/http/route-params.decorator.ts:343

What to do

Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.

Do you agree with this assessment?

P3 · Security & performance tooling7.0 / 10Strong✓ Tool-verified

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

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

What to do

Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

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

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

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

Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.

What to do

Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.

Do you agree with this assessment?

P5 · DR & Backup4.0 / 10Weak✓ Tool-verified

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

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

What to do

Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
No persistence guard on critical data stores — use Docker named volumes (or your orchestrator's persistent-volume equivalent) so the data store can't be wiped by a container recreate (or, in cloud, set purge-protection / soft-delete / prevent_destroy).

Do you agree with this assessment?

P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.

Do you agree with this assessment?

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

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

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

TypeORM synchronize: true builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt TypeORM migrations (`typeorm migration:generate` + `migrationsRun`), so every schema change is a versioned file applied the same way in every environment. (×9) — sample/13-mongo-typeorm/src/app.module.ts:13, sample/07-sequelize/src/app.module.ts:15, sample/05-sql-typeorm/src/app.module.ts:15, …

What to do

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

Do you agree with this assessment?

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.

`readFileSync` in `index` 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. — sample/28-sse/src/app.controller.ts:17

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 Safety8.5 / 10Strong✓ Tool-verified

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

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

What to do

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

Do you agree with this assessment?

R10 · Code Duplication8.7 / 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 common, core, microservices, platform-express, platform-fastify, platform-socket.io (+3 more sibling(s) not listed) — 34 of them are reported below, and 10 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/microservices/context/rpc-context-creator.ts:60
32 duplicated blocks under integration/ have copies in at least two of the sibling directories graphql-code-first, graphql-schema-first, injector, inspector, mongoose, repl (+4 more sibling(s) not listed) — 16 of them are reported below, and 16 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 32 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 32 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 32 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. — integration/inspector/src/dogs/dogs.controller.ts:14
22 duplicated blocks under packages/microservices/ have copies in at least two of the sibling directories client, server — 17 of them are reported below, and 5 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/microservices/client/client-proxy.ts:199
12 duplicated blocks under packages/core/ have copies in at least two of the sibling directories exceptions, guards, helpers, interceptors, middleware, pipes (+1 more sibling(s) not listed) — 10 of them are reported below, and 2 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 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 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 12 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/core/interceptors/interceptors-context-creator.ts:15
11 duplicated blocks under integration/scopes/src/ have copies in at least two of the sibling directories circular-hello, circular-transient, hello, msvc, transient — 4 of them are reported below, and 7 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 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 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 11 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. — integration/scopes/src/hello/hello.module.ts:7
8 of the duplicated blocks reported below have copies in at least two of the sibling directories kafka, kafka-concurrent, mqtt, nats, redis, rmq under integration/microservices/src/. That concentration is one structural fact, not 8 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 8 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. — integration/microservices/src/redis/redis.controller.ts:21
packages/microservices/context/rpc-context-creator.ts:60 · packages/websockets/context/ws-context-creator.ts:34 — the two spans are one implementation copied and then locally edited — 1117 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/microservices/context/rpc-context-creator.ts:60
packages/core/interceptors/interceptors-context-creator.ts:15 · packages/core/pipes/pipes-context-creator.ts:15 — the two spans are one implementation copied and then locally edited — 517 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/core/interceptors/interceptors-context-creator.ts:15
packages/microservices/server/server-nats.ts:51 · packages/microservices/server/server-redis.ts:41 — 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/microservices/server/server-nats.ts:51
integration/microservices/src/app.controller.ts:8 · integration/microservices/src/tcp-tls/app.controller.ts:8 — these 2 files are line-for-line copies of one another — 75 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — integration/microservices/src/app.controller.ts:8
packages/core/nest-application.ts:552 · packages/microservices/nest-microservice.ts:212 — the two spans are one implementation copied and then locally edited — 326 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/core/nest-application.ts:552
packages/core/helpers/external-context-creator.ts:306 · packages/microservices/context/rpc-context-creator.ts:308 · packages/websockets/context/ws-context-creator.ts:231 — 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/core/helpers/external-context-creator.ts:306
packages/core/helpers/external-context-creator.ts:127 · packages/core/router/router-execution-context.ts:137 — the two spans are one implementation copied and then locally edited — 268 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/core/helpers/external-context-creator.ts:127
packages/platform-express/multer/multer.module.ts:14 · packages/platform-fastify/multipart/multipart.module.ts:21 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/platform-express/multer/multer.module.ts:14
integration/microservices/src/app.module.ts:13 · integration/microservices/src/tcp-tls/app.module.ts:26 — the two spans are one implementation copied and then locally edited — 257 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. — integration/microservices/src/app.module.ts:13
packages/microservices/utils/param.utils.ts:1 · packages/websockets/utils/param.utils.ts:1 — these 2 files are line-for-line copies of one another — 55 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/microservices/utils/param.utils.ts:1
packages/platform-socket.io/utils/merge-map-bounded.util.ts:4 · packages/platform-ws/utils/merge-map-bounded.util.ts:4 · packages/websockets/utils/merge-map-bounded.util.ts:4 — these 3 files are line-for-line copies of one another — 52 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/platform-socket.io/utils/merge-map-bounded.util.ts:4
integration/nest-application/sse/src/app.controller.ts:168 · integration/nest-application/sse/src/app.controller.ts:256 — 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. — integration/nest-application/sse/src/app.controller.ts:168
packages/platform-express/multer/interceptors/file-fields.interceptor.ts:33 · packages/platform-express/multer/interceptors/file.interceptor.ts:31 — 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/platform-express/multer/interceptors/file-fields.interceptor.ts:33
packages/platform-express/multer/interceptors/file.interceptor.ts:31 · packages/platform-express/multer/interceptors/files.interceptor.ts:34 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/platform-express/multer/interceptors/file.interceptor.ts:31
packages/microservices/client/client-proxy.ts:199 · packages/microservices/server/server.ts:384 — the two spans are one implementation copied and then locally edited — 248 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/microservices/client/client-proxy.ts:199
packages/microservices/decorators/event-pattern.decorator.ts:52 · packages/microservices/decorators/message-pattern.decorator.ts:42 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/microservices/decorators/event-pattern.decorator.ts:52
integration/microservices/src/redis/redis.controller.ts:21 · integration/microservices/src/rmq/rmq.controller.ts:42 — the two spans are one implementation copied and then locally edited — 340 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. — integration/microservices/src/redis/redis.controller.ts:21
packages/platform-express/adapters/utils/get-media-type-version.util.ts:5 · packages/platform-fastify/adapters/utils/get-media-type-version.util.ts:5 — 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/platform-express/adapters/utils/get-media-type-version.util.ts:5
packages/microservices/client/client-nats.ts:205 · packages/microservices/server/server-nats.ts:324 — the two spans are one implementation copied and then locally edited — 204 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/microservices/client/client-nats.ts:205
packages/core/guards/guards-context-creator.ts:16 · packages/core/pipes/pipes-context-creator.ts:15 — 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/core/guards/guards-context-creator.ts:16
packages/core/hooks/before-app-shutdown.hook.ts:47 · packages/core/hooks/on-app-shutdown.hook.ts:43 — 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/core/hooks/before-app-shutdown.hook.ts:47
vitest.config.coverage.mts:12 · vitest.config.integration.mts:12 · vitest.config.mts:12 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — vitest.config.coverage.mts:12
packages/common/decorators/http/route-params.decorator.ts:495 · packages/common/decorators/http/route-params.decorator.ts:651 · packages/common/decorators/http/route-params.decorator.ts:936 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — packages/common/decorators/http/route-params.decorator.ts:495
packages/core/metadata-scanner.ts:20 · packages/core/metadata-scanner.ts:78 — the two spans are one implementation copied and then locally edited — 131 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/core/metadata-scanner.ts:20
packages/microservices/decorators/payload.decorator.ts:14 · packages/websockets/decorators/message-body.decorator.ts:14 — the two spans are one implementation copied and then locally edited — 150 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/microservices/decorators/payload.decorator.ts:14
packages/common/pipes/parse-float.pipe.ts:13 · packages/common/pipes/parse-int.pipe.ts:17 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/common/pipes/parse-float.pipe.ts:13
packages/core/injector/module-ref.ts:47 · packages/core/nest-application-context.ts:130 — the two spans are one implementation copied and then locally edited — 219 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/core/injector/module-ref.ts:47
packages/microservices/client/client-kafka.ts:147 · packages/microservices/client/client-rmq.ts:120 — 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/microservices/client/client-kafka.ts:147
packages/core/exceptions/base-exception-filter-context.ts:47 · packages/core/pipes/pipes-context-creator.ts:64 — 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/core/exceptions/base-exception-filter-context.ts:47
packages/platform-express/multer/interceptors/any-files.interceptor.ts:30 · packages/platform-express/multer/interceptors/no-files.interceptor.ts:29 — 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/platform-express/multer/interceptors/any-files.interceptor.ts:30
packages/microservices/client/client-mqtt.ts:288 · packages/microservices/client/client-tcp.ts:124 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/microservices/client/client-mqtt.ts:288
integration/hello-world/src/host-array/host-array.controller.ts:8 · integration/hello-world/src/host/host.controller.ts:8 — 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. — integration/hello-world/src/host-array/host-array.controller.ts:8
packages/core/exceptions/external-exception-filter-context.ts:48 · packages/core/guards/guards-context-creator.ts:102 · packages/core/interceptors/interceptors-context-creator.ts:101 · packages/core/pipes/pipes-context-creator.ts:93 — the 4 copies are spread across 4 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — packages/core/exceptions/external-exception-filter-context.ts:48
integration/inspector/src/dogs/dogs.controller.ts:14 · integration/inspector/src/users/users.controller.ts:14 · integration/repl/src/users/users.controller.ts:14 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — integration/inspector/src/dogs/dogs.controller.ts:14

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 Boundaries9.8 / 10Exemplary✓ 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.

REDACTED:38 imports fastify/lib/reply.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — REDACTED:38
REDACTED:39 imports fastify/lib/symbols.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — REDACTED:39
REDACTED:69 imports find-my-way/lib/url-sanitizer.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — REDACTED:69

What to do

Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.

Do you agree with this assessment?

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

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

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

(top-level) has cyclomatic complexity 29 and cognitive complexity 29; 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/core/exceptions/base-exception-filter.ts:1
serializeCookie has cyclomatic complexity 26 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/helpers/cookies/serialize-cookie.ts:40
exchangeKeyForValue has cyclomatic complexity 26 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/router/route-params-factory.ts:29
(anonymous) has cyclomatic complexity 25 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. — REDACTED:1245
(anonymous) has cyclomatic complexity 23 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/platform-express/adapters/express-adapter.ts:419
resolveSecurityHeaders has cyclomatic complexity 22 and cognitive complexity 27; 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/core/security/security-headers.ts:252
transform has cyclomatic complexity 20 and cognitive complexity 58; 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/common/pipes/parse-array.pipe.ts:84
transform has cyclomatic complexity 20 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/common/pipes/validation.pipe.ts:151
processMultipart has cyclomatic complexity 19 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/platform-fastify/multipart/multipart/multipart.parser.ts:417
(top-level) has cyclomatic complexity 18 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/microservices/serializers/kafka-request.serializer.ts:1
(anonymous) has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/common/decorators/http/create-route-param-metadata.decorator.ts:44
scanForModules has cyclomatic complexity 16 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/scanner.ts:108
capture has cyclomatic complexity 15 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/testing/services/capturing-logger.service.ts:197
redactObject has cyclomatic complexity 14 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/common/services/utils/redact.util.ts:178
(anonymous) has cyclomatic complexity 14 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/microservices/client/client-nats.ts:314
(anonymous) has cyclomatic complexity 14 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/microservices/client/client-mqtt.ts:323
processBuffer has cyclomatic complexity 13 and cognitive complexity 29; 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/microservices/helpers/json-socket.ts:114
(anonymous) has cyclomatic complexity 13 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. — REDACTED:1249
transformException has cyclomatic complexity 13 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/platform-fastify/multipart/multipart/multipart.utils.ts:49

What to do

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

Do you agree with this assessment?

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

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

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

REDACTED has 1683 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages/core/injector/injector.ts has 1632 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/core/injector/injector.ts:1
packages/microservices/external/kafka.interface.ts has 1178 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/microservices/external/kafka.interface.ts:1
packages/common/decorators/http/route-params.decorator.ts has 1101 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/common/decorators/http/route-params.decorator.ts:1
packages/microservices/server/server-grpc.ts has 910 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/microservices/server/server-grpc.ts:1
packages/common/services/console-logger.service.ts has 896 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/common/services/console-logger.service.ts:1
packages/core/scanner.ts has 772 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/core/scanner.ts:1
packages/common/interfaces/http/http-server.interface.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/common/interfaces/http/http-server.interface.ts:1
packages/platform-express/adapters/express-adapter.ts has 706 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/platform-express/adapters/express-adapter.ts:1
packages/core/nest-application.ts has 686 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/core/nest-application.ts:1
packages/core/router/router-execution-context.ts has 667 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/core/router/router-execution-context.ts:1
packages/websockets/web-sockets-controller.ts has 660 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/websockets/web-sockets-controller.ts:1
packages/core/adapters/http-adapter.ts has 650 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/core/adapters/http-adapter.ts:1
packages/core/injector/instance-wrapper.ts has 640 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/core/injector/instance-wrapper.ts:1
packages/core/injector/module.ts has 612 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/core/injector/module.ts:1
packages/microservices/client/client-rmq.ts has 561 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/microservices/client/client-rmq.ts:1
packages/platform-fastify/multipart/multipart/multipart.parser.ts has 549 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/platform-fastify/multipart/multipart/multipart.parser.ts:1
packages/core/router/router-explorer.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/core/router/router-explorer.ts:1
packages/microservices/client/client-kafka.ts has 502 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/microservices/client/client-kafka.ts:1
packages/microservices/server/server-rmq.ts has 499 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/microservices/server/server-rmq.ts:1
packages/core/nest-application-context.ts has 498 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/core/nest-application-context.ts:1
packages/microservices/server/server-kafka.ts has 479 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/microservices/server/server-kafka.ts:1
packages/microservices/server/server.ts has 479 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/microservices/server/server.ts:1
packages/core/security/security-headers.ts has 468 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/core/security/security-headers.ts:1
packages/common/pipes/validation.pipe.ts has 460 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/common/pipes/validation.pipe.ts:1
packages/microservices/client/client-mqtt.ts has 451 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/microservices/client/client-mqtt.ts:1
packages/microservices/client/client-redis.ts has 422 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/microservices/client/client-redis.ts:1
packages/microservices/nest-microservice.ts has 418 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/microservices/nest-microservice.ts:1
REDACTED has 415 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages/core/security/cross-origin-protection.ts has 402 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/security/cross-origin-protection.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.5 / 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. (×40) — tools/gulp/tasks/samples.ts:1, integration/_support/register-local-packages.ts:1, scripts/docker-compose.js:1, …

What to do

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

Do you agree with this assessment?

R5 · Dependency Freshness8.1 / 10Strong✓ Tool-verified

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

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

What to do

Bump outdated dependencies to current versions to limit upgrade debt.

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 Code7.9 / 10Strong✓ Tool-verified

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

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

Unreachable from the 58 application, 5 tooling and 536 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×35) — integration/_support/register-local-packages.ts, integration/microservices/src/rmq/rmq-broadcast.controller.ts, integration/inspector/src/durable/durable-context-id.strategy.ts, …
no import path from any entry point (58 application, 5 tooling, 536 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (integration/inspector/src/defaults/defaults.module.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — integration/inspector/src/defaults/defaults.service.ts
no import path from any entry point (58 application, 5 tooling, 536 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (integration/route-conflict/src/main.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — integration/route-conflict/src/app.module.ts
no import path from any entry point (58 application, 5 tooling, 536 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (integration/scopes/src/main.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — integration/scopes/src/app.module.ts
no import path from any entry point (58 application, 5 tooling, 536 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (integration/inspector/src/defaults/defaults.service.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — integration/inspector/src/defaults/core.service.ts

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.

Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×7) — integration/microservices/src/nats/nats.controller.ts:1, integration/inspector/src/chat/dto/update-chat.dto.ts:1, integration/cookies/e2e/cookies.spec.ts:14, …
Declared in the root 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. (×3)
Every import is type-only — move it to devDependencies. — packages/common/decorators/http/create-route-param-metadata.decorator.ts:1
Only test files import it (first: packages/platform-ws/test/ws-adapter-create.spec.ts:2) — move it to devDependencies. — packages/platform-ws/package.json:30

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 Imports0.0 / 10Critical✓ 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.

integration/injector/src/circular-modules/circular.module.ts → integration/injector/src/circular-modules/input.module.ts → integration/injector/src/circular-modules/circular.module.ts — integration/injector/src/circular-modules/circular.module.ts:3
integration/injector/src/circular-modules/circular.service.ts → integration/injector/src/circular-modules/input.service.ts → integration/injector/src/circular-modules/circular.service.ts — integration/injector/src/circular-modules/circular.service.ts:6
integration/injector/src/circular-properties/circular-properties.module.ts → integration/injector/src/circular-properties/input-properties.module.ts → integration/injector/src/circular-properties/circular-properties.module.ts — integration/injector/src/circular-properties/circular-properties.module.ts:3
integration/injector/src/circular-properties/circular.service.ts → integration/injector/src/circular-properties/input.service.ts → integration/injector/src/circular-properties/circular.service.ts — integration/injector/src/circular-properties/circular.service.ts:6
integration/injector/src/circular/circular.service.ts → integration/injector/src/circular/input.service.ts → integration/injector/src/circular/circular.service.ts — integration/injector/src/circular/circular.service.ts:6
integration/inspector/src/circular-modules/circular.module.ts → integration/inspector/src/circular-modules/input.module.ts → integration/inspector/src/circular-modules/circular.module.ts — integration/inspector/src/circular-modules/circular.module.ts:3
integration/inspector/src/circular-modules/circular.service.ts → integration/inspector/src/circular-modules/input.service.ts → integration/inspector/src/circular-modules/circular.service.ts — integration/inspector/src/circular-modules/circular.service.ts:2
integration/scopes/src/durable/durable-elephants.service.ts → integration/scopes/src/durable/durable-lions.service.ts → integration/scopes/src/durable/durable-elephants.service.ts — integration/scopes/src/durable/durable-elephants.service.ts:2
integration/testing-module-override/circular-dependency/a.module.ts → integration/testing-module-override/circular-dependency/b.module.ts → integration/testing-module-override/circular-dependency/a.module.ts — integration/testing-module-override/circular-dependency/a.module.ts:2
packages/common/decorators/core/exception-filters.decorator.ts → packages/common/index.ts → packages/common/decorators/index.ts → packages/common/decorators/core/index.ts → packages/common/decorators/core/exception-filters.decorator.ts (one verified cycle inside a mutually-dependent group of 30 files) — packages/common/decorators/core/exception-filters.decorator.ts:2
packages/common/interfaces/features/execution-context.interface.ts → packages/common/interfaces/index.ts → packages/common/interfaces/features/execution-context.interface.ts (one verified cycle inside a mutually-dependent group of 3 files) — packages/common/interfaces/features/execution-context.interface.ts:1
packages/core/application-config.ts → packages/core/injector/instance-wrapper.ts → packages/core/injector/module.ts → packages/core/application-config.ts (one verified cycle inside a mutually-dependent group of 48 files) — packages/core/application-config.ts:14
packages/core/index.ts → packages/core/nest-factory.ts → packages/microservices/index.ts → packages/microservices/nest-microservice.ts → packages/core/index.ts (one verified cycle inside a mutually-dependent group of 12 files) — packages/core/index.ts:26
packages/core/repl/native-functions/debug-repl-fn.ts → packages/core/repl/repl-function.ts → packages/core/repl/repl-context.ts → packages/core/repl/native-functions/index.ts → packages/core/repl/native-functions/debug-repl-fn.ts (one verified cycle inside a mutually-dependent group of 9 files) — packages/core/repl/native-functions/debug-repl-fn.ts:3
REDACTED → packages/microservices/client/client-proxy.ts → packages/microservices/deserializers/incoming-response.deserializer.ts → packages/microservices/interfaces/index.ts → packages/microservices/interfaces/client-kafka-proxy.interface.ts → packages/microservices/client/index.ts → REDACTED (one verified cycle inside a mutually-dependent group of 26 files) — REDACTED:10
packages/testing/interfaces/index.ts → packages/testing/interfaces/override-by.interface.ts → packages/testing/testing-module.builder.ts → packages/testing/interfaces/index.ts (one verified cycle inside a mutually-dependent group of 5 files) — packages/testing/interfaces/index.ts:3

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 Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. 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.

`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.) (×11) — integration/graphql-code-first/src/main.ts:8, integration/graphql-schema-first/src/main.ts:6, integration/hooks/src/enable-shutdown-hooks-main.ts:41, …
`httpServer.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.) — REDACTED:172

What to do

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 document2.2 / 10Critical✓ 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.

`getServiceNames` is exported, takes a document from its caller (line 177) and hands it to `collectDeepServices`, which calls itself at line 888 (`this.collectDeepServices`) with a piece of `grpcDefinition` — and nowhere in `collectDeepServices` 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 `collectDeepServices` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/microservices/server/server-grpc.ts:888
`stripProtoKeys` is exported and takes `value: any` from its caller, and it calls itself at line 29 (`stripProtoKeys`) with a piece of `value` (and at line 45) — and nowhere in `stripProtoKeys` 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 `stripProtoKeys` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/common/utils/strip-proto-keys.util.ts:29
`createUploadModule` is exported, takes a document from its caller (line 79) and hands it to `describeFiles`, which calls itself at line 46 (`describeFiles`) with a piece of `files` — and nowhere in `describeFiles` 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 `describeFiles` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — integration/file-upload/src/upload.module.ts:46

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 materialisation10.0 / 10Exemplary○ Nothing flagged

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

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

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 handling6.4 / 10Adequate✓ Tool-verified

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

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

An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×5) — REDACTED:373, packages/platform-express/multer/multer/multer.utils.ts:115, packages/microservices/helpers/kafka-parser.ts:78, …
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×7) — packages/microservices/client/client-mqtt.ts:202, packages/microservices/client/client-nats.ts:118, packages/microservices/client/client-nats.ts:173, …

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 logging5.1 / 10Adequate✓ Tool-verified

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.

`info` at line 100 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — tools/gulp/tasks/samples.ts:100
`info` at line 114 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — tools/gulp/tasks/samples.ts:114
`error` at line 122 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — tools/gulp/tasks/samples.ts:122
`error` at line 546 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/websockets/web-sockets-controller.ts:546
`log` at line 689 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. (×2) — packages/websockets/web-sockets-controller.ts:689, packages/core/injector/instance-wrapper.ts:689
`warn` at line 336 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — REDACTED:336
`error` at line 297 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/microservices/server/server-kafka.ts:297
`error` at line 325 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/microservices/server/server-kafka.ts:325
`error` at line 289 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/microservices/server/server-nats.ts:289
`error` at line 295 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/microservices/server/server-nats.ts:295
`log` at line 317 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/microservices/server/server-nats.ts:317
`log` at line 327 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/microservices/server/server-nats.ts:327
`log` at line 343 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/microservices/server/server-nats.ts:343
`error` at line 312 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/microservices/client/client-kafka.ts:312
`error` at line 294 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/microservices/client/client-mqtt.ts:294
`error` at line 163 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/microservices/client/client-nats.ts:163
`error` at line 175 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/microservices/client/client-nats.ts:175
`log` at line 190 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/microservices/client/client-nats.ts:190
`debug` at line 201 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/microservices/client/client-nats.ts:201
`log` at line 208 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/microservices/client/client-nats.ts:208
`log` at line 224 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/microservices/client/client-nats.ts:224
`error` at line 323 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/microservices/client/client-redis.ts:323
`error` at line 130 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/microservices/client/client-tcp.ts:130
`error` at line 361 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/core/router/router-explorer.ts:361
`warn` at line 405 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/core/router/router-explorer.ts:405
`warn` at line 278 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/core/router/router-response-controller.ts:278
`error` at line 23 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/core/repl/native-functions/debug-repl-fn.ts:23
`log` at line 1710 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/core/injector/injector.ts:1710
`log` at line 1726 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/core/injector/injector.ts:1726
`log` at line 702 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/core/injector/instance-wrapper.ts:702
`warn` at line 63 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/core/injector/opaque-key-factory/deep-hashed-module-opaque-key-factory.ts:63
`warn` at line 21 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/core/helpers/safe-instance-decorator.ts:21

What to do

Interpolated log message defeats structured logging

Do you agree with this assessment?

X5 · Nullable reference types4.9 / 10Weak✓ 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.

41/81 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~4.8 `!` null assertions per 1k TypeScript source lines — 337 assertion(s) across the 69527 source line(s) of the 1084 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/core/injector/injector.ts (18), packages/core/injector/instance-wrapper.ts (15), packages/core/scanner.ts (14). 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	65%	Adequate	Acceptable, with room to improve.
Architecture	55%	Adequate — gated by D5, R9	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity	43%	Weak — gated by M2, M4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	40%	Weak — gated by R8, P8	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	70%	Adequate — gated by D29, D30	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling	100%	Exemplary	Strongest area.
Performance	85%	Strong	Solid.

Unscored — 4 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.

D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
P12 CI test-gate honesty — 3 observation(s) recorded · Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.

Not included — 57 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) — postgres Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: postgres Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D11 Test Reliability — Test reliability NOT MEASURED: the JavaScript/TypeScript suite's dependency install refused the committed lockfile, so no test ever ran and flakiness could not be exercised — the dependency install for the repository root refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. It is excluded from the score rather than counted as a defect; a lockfile in sync with package.json is what lets the suite be re-run.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, TypeScript, html not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .ts, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
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 (.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.
D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D4 Code Duplication — This repository's production source (.ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for the repository root refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
DM1 Aggregate boundaries — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM10 One transaction, one aggregate — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM2 Strongly-typed ids — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM4 Rich vs anemic model — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM5 Encapsulated state — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: REDACTED:396 (http.createServer())
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage --coverage.reporter=lcovonly`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
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.
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.
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 — 73 finding(s)

D30 · Dependency Vulnerabilities · High CVE · ×13

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

D11 · Test Reliability · Test suite cannot be installed from its own lockfile · ×12

Test suite cannot be installed from its own lockfile: the repository root — The vitest suite in the repository root was never exercised because its dependency install refused the committed lockfile — the dependency install for the repository root refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
Test suite cannot be installed from its own lockfile: sample/01-cats-app/ — The vitest suite in sample/01-cats-app/ was never exercised because its dependency install refused the committed lockfile — the dependency install for sample/01-cats-app/ refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
Test suite cannot be installed from its own lockfile: sample/02-gateways/ — The vitest suite in sample/02-gateways/ was never exercised because its dependency install refused the committed lockfile — the dependency install for sample/02-gateways/ refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
Test suite cannot be installed from its own lockfile: sample/03-microservices/ — The vitest suite in sample/03-microservices/ was never exercised because its dependency install refused the committed lockfile — the dependency install for sample/03-microservices/ refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
Test suite cannot be installed from its own lockfile: sample/04-grpc/ — The vitest suite in sample/04-grpc/ was never exercised because its dependency install refused the committed lockfile — the dependency install for sample/04-grpc/ refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
Test suite cannot be installed from its own lockfile: sample/05-sql-typeorm/ — The vitest suite in sample/05-sql-typeorm/ was never exercised because its dependency install refused the committed lockfile — the dependency install for sample/05-sql-typeorm/ refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
Test suite cannot be installed from its own lockfile: sample/06-mongoose/ — The vitest suite in sample/06-mongoose/ was never exercised because its dependency install refused the committed lockfile — the dependency install for sample/06-mongoose/ refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
Test suite cannot be installed from its own lockfile: sample/07-sequelize/ — The vitest suite in sample/07-sequelize/ was never exercised because its dependency install refused the committed lockfile — the dependency install for sample/07-sequelize/ refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
Test suite cannot be installed from its own lockfile: sample/08-webpack/ — The vitest suite in sample/08-webpack/ was never exercised because its dependency install refused the committed lockfile — the dependency install for sample/08-webpack/ refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
Test suite cannot be installed from its own lockfile: sample/09-babel-example/ — The vitest suite in sample/09-babel-example/ was never exercised because its dependency install refused the committed lockfile — the dependency install for sample/09-babel-example/ refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
Test suite cannot be installed from its own lockfile: sample/10-fastify/ — The vitest suite in sample/10-fastify/ was never exercised because its dependency install refused the committed lockfile — the dependency install for sample/10-fastify/ refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
Test suite cannot be installed from its own lockfile: sample/11-swagger/ — The vitest suite in sample/11-swagger/ was never exercised because its dependency install refused the committed lockfile — the dependency install for sample/11-swagger/ refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.

R9 · Circular Imports · Import cycle (2 files) · ×10

Import cycle (2 files) integration/injector/src/circular-modules/circular.module.ts:3 — integration/injector/src/circular-modules/circular.module.ts → integration/injector/src/circular-modules/input.module.ts → integration/injector/src/circular-modules/circular.module.ts
Import cycle (2 files) integration/injector/src/circular-modules/circular.service.ts:6 — integration/injector/src/circular-modules/circular.service.ts → integration/injector/src/circular-modules/input.service.ts → integration/injector/src/circular-modules/circular.service.ts
Import cycle (2 files) integration/injector/src/circular-properties/circular-properties.module.ts:3 — integration/injector/src/circular-properties/circular-properties.module.ts → integration/injector/src/circular-properties/input-properties.module.ts → integration/injector/src/circular-properties/circular-properties.module.ts
Import cycle (2 files) integration/injector/src/circular-properties/circular.service.ts:6 — integration/injector/src/circular-properties/circular.service.ts → integration/injector/src/circular-properties/input.service.ts → integration/injector/src/circular-properties/circular.service.ts
Import cycle (2 files) integration/injector/src/circular/circular.service.ts:6 — integration/injector/src/circular/circular.service.ts → integration/injector/src/circular/input.service.ts → integration/injector/src/circular/circular.service.ts
Import cycle (2 files) integration/inspector/src/circular-modules/circular.module.ts:3 — integration/inspector/src/circular-modules/circular.module.ts → integration/inspector/src/circular-modules/input.module.ts → integration/inspector/src/circular-modules/circular.module.ts
Import cycle (2 files) integration/inspector/src/circular-modules/circular.service.ts:2 — integration/inspector/src/circular-modules/circular.service.ts → integration/inspector/src/circular-modules/input.service.ts → integration/inspector/src/circular-modules/circular.service.ts
Import cycle (2 files) integration/scopes/src/durable/durable-elephants.service.ts:2 — integration/scopes/src/durable/durable-elephants.service.ts → integration/scopes/src/durable/durable-lions.service.ts → integration/scopes/src/durable/durable-elephants.service.ts
Import cycle (2 files) integration/testing-module-override/circular-dependency/a.module.ts:2 — integration/testing-module-override/circular-dependency/a.module.ts → integration/testing-module-override/circular-dependency/b.module.ts → integration/testing-module-override/circular-dependency/a.module.ts
Import cycle (2 files) packages/common/interfaces/features/execution-context.interface.ts:1 — packages/common/interfaces/features/execution-context.interface.ts → packages/common/interfaces/index.ts → packages/common/interfaces/features/execution-context.interface.ts (one verified cycle inside a mutually-dependent group of 3 files)

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED

D31 · IaC & Container Security · High IaC · ×4

REDACTED
REDACTED
REDACTED
REDACTED

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

No assertions (empty test): should close on socket close packages/core/test/router/router-response-controller.spec.ts:632 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): should close the request when observable completes packages/core/test/router/router-response-controller.spec.ts:979 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): placeholder integration/hello-world/e2e/fastify-multiple.spec.ts:3 — Test method has an empty body — it asserts nothing and exercises no code.

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

Import cycle (4 files) packages/common/decorators/core/exception-filters.decorator.ts:2 — packages/common/decorators/core/exception-filters.decorator.ts → packages/common/index.ts → packages/common/decorators/index.ts → packages/common/decorators/core/index.ts → packages/common/decorators/core/exception-filters.decorator.ts (one verified cycle inside a mutually-dependent group of 30 files)
Import cycle (4 files) packages/core/index.ts:26 — packages/core/index.ts → packages/core/nest-factory.ts → packages/microservices/index.ts → packages/microservices/nest-microservice.ts → packages/core/index.ts (one verified cycle inside a mutually-dependent group of 12 files)
Import cycle (4 files) packages/core/repl/native-functions/debug-repl-fn.ts:3 — packages/core/repl/native-functions/debug-repl-fn.ts → packages/core/repl/repl-function.ts → packages/core/repl/repl-context.ts → packages/core/repl/native-functions/index.ts → packages/core/repl/native-functions/debug-repl-fn.ts (one verified cycle inside a mutually-dependent group of 9 files)

D30 · Dependency Vulnerabilities · Critical CVE · ×2

REDACTED
REDACTED

R8 · Dependency Hygiene · Unlisted import '@nats-io/nats-core' · ×2

Unlisted import '@nats-io/nats-core' integration/microservices/src/nats/nats.controller.ts:1 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@nats-io/nats-core' packages/microservices/test/serializers/nats-record.serializer.spec.ts:1 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'cookie-signature' · ×2

Unlisted import 'cookie-signature' integration/cookies/e2e/cookies.spec.ts:14 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'cookie-signature' packages/core/test/helpers/cookies/cookie-signer.spec.ts:8 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import '@fastify/error' · ×2

Unlisted import '@fastify/error' packages/core/test/exceptions/exceptions-handler.spec.ts:10 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@fastify/error' packages/platform-fastify/test/adapters/fastify-adapter.spec.ts:7 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R9 · Circular Imports · Import cycle (3 files) · ×2

Import cycle (3 files) packages/core/application-config.ts:14 — packages/core/application-config.ts → packages/core/injector/instance-wrapper.ts → packages/core/injector/module.ts → packages/core/application-config.ts (one verified cycle inside a mutually-dependent group of 48 files)
Import cycle (3 files) packages/testing/interfaces/index.ts:3 — packages/testing/interfaces/index.ts → packages/testing/interfaces/override-by.interface.ts → packages/testing/testing-module.builder.ts → packages/testing/interfaces/index.ts (one verified cycle inside a mutually-dependent group of 5 files)

AX3 · Project dependency cycles · Project dependency cycle · ×1

Project dependency cycle packages/core/package.json:44 — The projects @nestjs/core → @nestjs/microservices → @nestjs/core (one cycle inside a mutually-dependent group of 5 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference.

AX4 · Dependency direction · Dependency-rule violation · ×1

Dependency-rule violation: @nestjs/core (Domain) → @nestjs/websockets (Web) packages/core/package.json:46 — `@nestjs/core` is a Domain project but references `@nestjs/websockets`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.

D13 · REDACTED Scanning · Leaked secret · ×1

REDACTED

D28 · Secrets (history) · REDACTED · ×1

REDACTED

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

REDACTED

D30 · Dependency Vulnerabilities · High vulnerability · ×1

REDACTED

D5 · Coupling · Circular dependency · ×1

Circular dependency packages/core/package.json:44 — @nestjs/core → @nestjs/microservices → @nestjs/core (one cycle inside a mutually-dependent group of 5 modules)

R8 · Dependency Hygiene · Unlisted import '@nestjs/mapped-types' · ×1

Unlisted import '@nestjs/mapped-types' integration/inspector/src/chat/dto/update-chat.dto.ts:1 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

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

Import cycle (6 files) REDACTED:10 — REDACTED → packages/microservices/client/client-proxy.ts → packages/microservices/deserializers/incoming-response.deserializer.ts → packages/microservices/interfaces/index.ts → packages/microservices/interfaces/client-kafka-proxy.interface.ts → packages/microservices/client/index.ts → REDACTED (one verified cycle inside a mutually-dependent group of 26 files)

Serious — 404 finding(s)

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

Repeated repair: packages/core/injector/injector.ts packages/core/injector/injector.ts:400 — packages/core/injector/injector.ts changed 24 times in last 90 days and 23 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is Injector.resolveConstructorParams at line 400), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): resolve request-scoped forward refs for concurrent requests (#18200)”; “fix(core): detect cycles in request-scoped forward references (#18186)”; “fix(core,websockets): run transient enhancers bound to static gateways”; “fix(core): stop reusing durable instances holding a failed placeholder”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/core/injector/injector.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/microservices/server/server-grpc.ts packages/microservices/server/server-grpc.ts:441 — packages/microservices/server/server-grpc.ts changed 17 times in last 90 days and 16 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is ServerGrpc.writeObservableToGrpc at line 441), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(microservices): preserve request order during deferred replay (#18179)”; “fix(microservices): pause grpc request streams while replies wait”; “fix(microservices): end grpc unary subscriptions with the call”; “fix(microservices): fail grpc calls whose handler promise rejects”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/microservices/server/server-grpc.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/microservices/server/server-tcp.ts packages/microservices/server/server-tcp.ts:200 — packages/microservices/server/server-tcp.ts changed 17 times in last 90 days and 15 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is ServerTCP.handleClose at line 200), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(microservices): bound how long a tcp packet may take to arrive”; “fix(microservices): retry the tcp server again after close and listen (#18238)”; “fix(microservices): clear the tcp retry timer when a new listen starts (#18223)”; “fix(microservices): reset the tcp retry attempts on each listen (#18206)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/microservices/server/server-tcp.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/microservices/client/client-mqtt.ts packages/microservices/client/client-mqtt.ts:320 — packages/microservices/client/client-mqtt.ts changed 15 times in last 90 days and 15 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is ClientMqtt.publish at line 320), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(microservices): reject mqtt topics longer than 65535 bytes”; “fix(microservices): count mqtt requests that wait for the subscription”; “fix(microservices): drop idle reply channels from subscription counts”; “fix(microservices): drop the mqtt client when a reconnect is refused”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/microservices/client/client-mqtt.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: REDACTED REDACTED:193 — REDACTED changed 13 times in last 90 days and 12 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is WsAdapter.bindMessageHandlers at line 193), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core,express,fastify,ws,socket.io): load adapters with an older core (#18251)”; “fix(ws): stop reading from a client that does not read its replies”; “fix(websockets): bound how many messages of a client are handled at once”; “fix(ws): listen on the host of a gateway with its own port and a path”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/microservices/server/server-rmq.ts packages/microservices/server/server-rmq.ts:515 — packages/microservices/server/server-rmq.ts changed 13 times in last 90 days and 12 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is ServerRMQ.matchRmqPattern at line 515), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(microservices): count every failed rmq connection attempt (#18204)”; “fix(microservices): drop rmq replies that amqp cannot address”; “fix(microservices): consume again after the rmq consumer is cancelled”; “fix(microservices): close rmq server connection when channel close fails (#18165)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/microservices/server/server-rmq.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/websockets/web-sockets-controller.ts packages/websockets/web-sockets-controller.ts:449 — packages/websockets/web-sockets-controller.ts changed 12 times in last 90 days and 12 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is WebSocketsController.createRequestScopedEventHandler at line 449), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(websockets): await deferred loads of a gateway's scoped enhancers”; “fix(core,websockets): run transient enhancers bound to static gateways”; “fix(websockets): create the filters of a gateway that failed to resolve”; “fix(websockets): resolve hook error filters in the connection's context”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/websockets/web-sockets-controller.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/microservices/server/server-mqtt.ts packages/microservices/server/server-mqtt.ts:237 — packages/microservices/server/server-mqtt.ts changed 13 times in last 90 days and 11 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is ServerMqtt.matchMqttPattern at line 237), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(microservices): honor mqtt topic filter boundaries (#18221)”; “fix(microservices): route mqtt messages by the topic they arrived on”; “fix(microservices): validate request ids before echoing them”; “fix(microservices): reject mqtt topics longer than 65535 bytes”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/microservices/server/server-mqtt.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/microservices/client/client-redis.ts packages/microservices/client/client-redis.ts:356 — packages/microservices/client/client-redis.ts changed 11 times in last 90 days and 11 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is ClientRedis.publish at line 356), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(microservices): drop idle reply channels from subscription counts”; “fix(microservices): fail redis listen on rejected subscriptions (#18060)”; “fix(microservices): do not crash when the redis connection drops (#18054)”; “fix(microservices): survive custom deserializer errors in clients (#17995)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/microservices/client/client-redis.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/core/nest-application.ts packages/core/nest-application.ts:231 — packages/core/nest-application.ts changed 15 times in last 90 days and 10 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is NestApplication.registerRouter at line 231), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): read the url protocol from the server (#18252)”; “fix(core,microservices): let only the hybrid application bind gateways”; “fix(core,microservices): flush buffered logs when initialization fails (#18111)”; “fix(core): reset the listening state when the application closes (#17951)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/core/nest-application.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/microservices/server/server-redis.ts packages/microservices/server/server-redis.ts:156 — packages/microservices/server/server-redis.ts changed 12 times in last 90 days and 10 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is ServerRedis.handleMessage at line 156), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(microservices): re-arm the redis retries on a new listen (#18250)”; “fix(microservices): let only the exact message handler answer a request (#18229)”; “fix(microservices): validate request ids before echoing them”; “fix(microservices): reply to a request only from its message handler”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/microservices/server/server-redis.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/microservices/client/client-rmq.ts packages/microservices/client/client-rmq.ts:294 — packages/microservices/client/client-rmq.ts changed 10 times in last 90 days and 10 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is ClientRMQ.setupChannel at line 294), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(microservices): only emit rmq replies that a request waits for”; “fix(microservices): use unguessable request ids and nats reply inboxes”; “fix(microservices): close the rmq channel before the connection (#18161)”; “fix(microservices): close the connection when the channel close fails (#18081)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/microservices/client/client-rmq.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/microservices/server/server-nats.ts packages/microservices/server/server-nats.ts:284 — packages/microservices/server/server-nats.ts changed 10 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is ServerNats.handleStatusUpdates at line 284), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(microservices): report a nats connection that gave up reconnecting (#18255)”; “fix(microservices): let only the exact message handler answer a request (#18229)”; “fix(microservices): validate request ids before echoing them”; “fix(microservices): reply to a request only from its message handler”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/microservices/server/server-nats.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/microservices/server/server-kafka.ts packages/microservices/server/server-kafka.ts:285 — packages/microservices/server/server-kafka.ts changed 10 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is ServerKafka.handleMessage at line 285), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(microservices): do not emit a trailing null to kafka requesters (#18249)”; “fix(microservices): decode kafka reply headers as text”; “fix(microservices): limit the size of kafka messages the parser decodes”; “fix(microservices): resolve kafka events whose stream completes empty (#17924)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/microservices/server/server-kafka.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/microservices/client/client-tcp.ts packages/microservices/client/client-tcp.ts:64 — packages/microservices/client/client-tcp.ts changed 9 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is ClientTCP.connect at line 64), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(microservices): bound how long a tcp packet may take to arrive”; “fix(microservices): keep reading tcp replies during client backpressure (#18162)”; “fix(microservices): wait for the TCP TLS handshake (#18002)”; “fix(microservices): survive custom deserializer errors in clients (#17995)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/microservices/client/client-tcp.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/core/router/sse-stream.ts packages/core/router/sse-stream.ts:153 — packages/core/router/sse-stream.ts changed 9 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is SseStream.commitHeaders at line 153), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): tolerate sse request sockets without tuning methods (#18262)”; “fix(core): hand sse header errors to the exception filters”; “fix(core): do not mutate the message when assigning an sse event id (#18086)”; “fix(core): end sse streams whose event data cannot be serialized (#18025)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/core/router/sse-stream.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/core/middleware/utils.ts packages/core/middleware/utils.ts:194 — packages/core/middleware/utils.ts changed 8 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is utils.isMiddlewareRouteExcluded at line 194), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): read a quoted media type version in the middleware exclusions (#18201)”; “fix(core,common): exclude a version only for requests that ask for it”; “fix(core): stop wildcard exclusions from covering their parent route”; “fix(core): mount middleware paths on routes excluded from the prefix”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/core/middleware/utils.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/microservices/nest-microservice.ts packages/microservices/nest-microservice.ts:119 — packages/microservices/nest-microservice.ts changed 8 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is NestMicroservice.registerModules at line 119), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(microservices): leave the init hooks to the hybrid application”; “fix(microservices): call the init hooks once when init() is called”; “fix(core,microservices): let only the hybrid application bind gateways”; “fix(core,microservices): flush buffered logs when initialization fails (#18111)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/microservices/nest-microservice.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/microservices/server/server.ts packages/microservices/server/server.ts:201 — packages/microservices/server/server.ts changed 9 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is Server.send at line 201), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(microservices): fail the request when its last reply cannot be sent (#18211)”; “fix(microservices): validate request ids before echoing them”; “fix(microservices): drain streamed replies in linear time”; “fix(microservices): share the processing hook envelope across transports (#17799)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/microservices/server/server.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/core/scanner.ts packages/core/scanner.ts:108 — packages/core/scanner.ts changed 8 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is DependenciesScanner.scanForModules at line 108), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): name the array and index of undefined module entries (#18254)”; “fix(core): fail at startup when a global enhancer is not instantiated”; “fix(core): apply the enhancers of class providers under any token”; “fix(core): fail at startup for request-scoped class global enhancers (#18104)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/core/scanner.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/core/middleware/route-info-path-extractor.ts packages/core/middleware/route-info-path-extractor.ts:90 — packages/core/middleware/route-info-path-extractor.ts changed 8 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is RouteInfoPathExtractor.extractExcludedRoutesCoveredBy at line 90), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): let exclusions cover routes excluded from the global prefix (#18209)”; “fix(core,common): exclude a version only for requests that ask for it”; “fix(core): run middleware on a controller root excluded by a wildcard”; “fix(core): mount middleware paths on routes excluded from the prefix”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/core/middleware/route-info-path-extractor.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/microservices/client/client-kafka.ts packages/microservices/client/client-kafka.ts:300 — packages/microservices/client/client-kafka.ts changed 8 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is ClientKafka.createResponseCallback at line 300), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(microservices): limit the size of kafka messages the parser decodes”; “fix(microservices): fail pending kafka request on deserializer error (#18043)”; “fix(microservices): close both kafka client connections when one fails (#18027)”; “fix(microservices): keep a newer kafka connection when a stale one fails (#17869)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/microservices/client/client-kafka.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/core/errors/messages.ts packages/core/errors/messages.ts:63 — packages/core/errors/messages.ts changed 7 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is messages.UNKNOWN_DEPENDENCIES_MESSAGE at line 63), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): name the array and index of undefined module entries (#18254)”; “fix(core): fail at startup when a global enhancer is not instantiated”; “fix(core): reject create() when a dependency is request-scoped (#18142)”; “fix(core): fail at startup for request-scoped class global enhancers (#18104)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/core/errors/messages.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/microservices/helpers/json-socket.ts packages/microservices/helpers/json-socket.ts:114 — packages/microservices/helpers/json-socket.ts changed 6 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is JsonSocket.processBuffer at line 114), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(microservices): bound how long a tcp packet may take to arrive”; “fix(microservices): drop tcp peers that stop reading their responses”; “fix(microservices): reject tcp data too long to be a content length”; “fix(microservices): keep reading tcp replies during client backpressure (#18162)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/microservices/helpers/json-socket.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/common/services/console-logger.service.ts packages/common/services/console-logger.service.ts:786 — packages/common/services/console-logger.service.ts changed 6 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is ConsoleLogger.stringifyJsonLogObject at line 786), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(common): cut json log records short past a million characters”; “fix(common): call stringifyReplacer with the logger as this (#18146)”; “fix(common): detect stacks whose error message spans several lines (#18145)”; “fix(common): parse `error()` calls with a lone or an undefined stack (#18144)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/common/services/console-logger.service.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
+ 33 more in this group — see findings.md.

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

No test reaches this file tools/gulp/tasks/samples.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file integration/_support/register-local-packages.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file scripts/docker-compose.js: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 tools/gulp/tasks/move.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file scripts/wait-for-rabbitmq.js: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 integration/microservices/src/rmq/rmq-broadcast.controller.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file tools/gulp/tasks/clean.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file integration/inspector/src/durable/durable-context-id.strategy.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file tools/gulp/util/task-helpers.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file integration/graphql-schema-first/src/common/scalars/date.scalar.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file tools/gulp/tasks/copy-misc.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file integration/versioning/src/main.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file integration/inspector/src/defaults/defaults.service.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file integration/graphql-code-first/src/main.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file integration/hello-world/src/hello/dto/test.dto.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file integration/hello-world/src/host-array/dto/test.dto.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file integration/hello-world/src/host/dto/test.dto.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file integration/inspector/src/circular-hello/dto/test.dto.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file integration/scopes/src/circular-hello/dto/test.dto.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file integration/scopes/src/circular-transient/dto/test.dto.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file integration/scopes/src/hello/dto/test.dto.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file integration/scopes/src/msvc/dto/test.dto.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file integration/scopes/src/transient/dto/test.dto.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file integration/route-conflict/src/main.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file integration/graphql-schema-first/src/main.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
+ 15 more in this group — see findings.md.

D3 · God Classes · TooManyMethods · ×12

TooManyMethods: AbstractHttpAdapter packages/core/adapters/http-adapter.ts:60 — TooManyMethods — 94 methods. The bar is 30 methods; this is 64 over it, 3.13× the bar. Most of these members implement http-server_interface.HttpServer (48 of 59 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: FastifyAdapter REDACTED:203 — TooManyMethods — 85 methods. The bar is 30 methods; this is 55 over it, 2.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Injector packages/core/injector/injector.ts:111 — TooManyMethods — 61 methods. The bar is 30 methods; this is 31 over it, 2.03× 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: NestApplication packages/core/nest-application.ts:55 — TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× 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: ExpressAdapter packages/platform-express/adapters/express-adapter.ts:68 — TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× 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: ConsoleLogger packages/common/services/console-logger.service.ts:177 — TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× 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: InstanceWrapper packages/core/injector/instance-wrapper.ts:81 — TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× 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: Module packages/core/injector/module.ts:44 — TooManyMethods — 39 methods. The bar is 30 methods; this is 9 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.
TooManyMethods: ApplicationConfig packages/core/application-config.ts:17 — 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: DependenciesScanner packages/core/scanner.ts:77 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× 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: NestContainer packages/core/injector/container.ts:32 — 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.
TooManyMethods: NestApplicationContext packages/core/nest-application-context.ts:37 — 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.

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

Swallowed exception (empty catch) REDACTED:373 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/platform-express/multer/multer/multer.utils.ts:115 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/microservices/helpers/kafka-parser.ts:78 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/microservices/client/client-kafka.ts:322 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/microservices/client/client-mqtt.ts:202 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/microservices/client/client-nats.ts:118 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/microservices/client/client-nats.ts:173 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/microservices/client/client-redis.ts:183 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/microservices/client/client-rmq.ts:226 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/microservices/client/client-rmq.ts:227 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/microservices/client/client-rmq.ts:372 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/common/pipes/parse-array.pipe.ts:117 — 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.

D10 · Test Quality · No assertions · ×11

No assertions: should initialize and close without error packages/testing/test/testing-module.spec.ts:185 — 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 not throw if the message is an invalid json packages/microservices/test/server/server-rmq.spec.ts:395 — 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 create grpcService packages/microservices/test/client/client-grpc.spec.ts:64 — 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 create grpcService packages/microservices/test/client/client-grpc.spec.ts:72 — 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 send message packages/microservices/test/client/client-tcp.spec.ts:70 — 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 require transform option when second generic type is provided packages/core/test/services/reflector.service.spec.ts:76 — 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: Create kafka topics/partitions integration/microservices/e2e/concurrent-kafka.spec.ts:62 — 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: Start Kafka apps integration/microservices/e2e/concurrent-kafka.spec.ts:145 — 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 bootstrap when module-local provider instances have non-static dependency trees integration/injector/e2e/injector.spec.ts:24 — 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 capture the framework logs integration/hello-world/e2e/capturing-logger.spec.ts:71 — 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 capture the logs from then on integration/hello-world/e2e/capturing-logger.spec.ts:115 — 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.

D15 · Churn × Complexity Hotspots · Hotspot · ×10

Hotspot: REDACTED REDACTED:1243 — REDACTED changed 39 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in FastifyAdapter.createMiddlewareFactory at line 1243. 37 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/core/router/router-response-controller.ts packages/core/router/router-response-controller.ts:124 — packages/core/router/router-response-controller.ts changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in RouterResponseController.sse at line 124. 14 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/core/router/router-response-controller.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/platform-express/adapters/express-adapter.ts packages/platform-express/adapters/express-adapter.ts:166 — packages/platform-express/adapters/express-adapter.ts changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in ExpressAdapter.reply at line 166. 21 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/platform-express/adapters/express-adapter.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/platform-express/multer/multer/multer.utils.ts packages/platform-express/multer/multer/multer.utils.ts:135 — packages/platform-express/multer/multer/multer.utils.ts changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in multer.utils.transformException at line 135. 9 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/platform-express/multer/multer/multer.utils.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/microservices/client/client-nats.ts packages/microservices/client/client-nats.ts:155 — packages/microservices/client/client-nats.ts changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in ClientNats.handleStatusUpdates at line 155. 12 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/microservices/client/client-nats.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/common/pipes/validation.pipe.ts packages/common/pipes/validation.pipe.ts:151 — packages/common/pipes/validation.pipe.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in ValidationPipe.transform at line 151. 7 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/common/pipes/validation.pipe.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/common/pipes/parse-array.pipe.ts packages/common/pipes/parse-array.pipe.ts:84 — packages/common/pipes/parse-array.pipe.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in ParseArrayPipe.transform at line 84. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/common/pipes/parse-array.pipe.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/core/exceptions/base-exception-filter.ts packages/core/exceptions/base-exception-filter.ts:89 — packages/core/exceptions/base-exception-filter.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in BaseExceptionFilter.isHttpError at line 89. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/core/exceptions/base-exception-filter.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/common/decorators/http/create-route-param-metadata.decorator.ts packages/common/decorators/http/create-route-param-metadata.decorator.ts:23 — packages/common/decorators/http/create-route-param-metadata.decorator.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in create-route-param-metadata.decorator.createParamDecorator at line 23. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/common/decorators/http/create-route-param-metadata.decorator.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/core/router/route-params-factory.ts packages/core/router/route-params-factory.ts:29 — packages/core/router/route-params-factory.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in RouteParamsFactory.exchangeKeyForValue at line 29. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 09:02:24 +01:00' --until='2026-10-26 09:02:24 +01:00' --full-history --no-merges -- packages/core/router/route-params-factory.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.

D3 · God Classes · ClassTooLong · ×10

ClassTooLong: Injector packages/core/injector/injector.ts:111 — ClassTooLong — 1093 significant lines (blank, comment-only and punctuation-only lines excluded), 61 methods. The bar is 400 significant lines; this is 693 over it, 2.73× 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: FastifyAdapter REDACTED:203 — ClassTooLong — 948 significant lines (blank, comment-only and punctuation-only lines excluded), 85 methods. The bar is 400 significant lines; this is 548 over it, 2.37× 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: DependenciesScanner packages/core/scanner.ts:77 — ClassTooLong — 516 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 400 significant lines; this is 116 over it, 1.29× 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: ConsoleLogger packages/common/services/console-logger.service.ts:177 — ClassTooLong — 481 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 400 significant lines; this is 81 over it, 1.20× 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: WebSocketsController packages/websockets/web-sockets-controller.ts:48 — ClassTooLong — 468 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 68 over it, 1.17× 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: RouterExecutionContext packages/core/router/router-execution-context.ts:88 — ClassTooLong — 450 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 50 over it, 1.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: Module packages/core/injector/module.ts:44 — ClassTooLong — 438 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 400 significant lines; this is 38 over it, 1.10× 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: NestApplication packages/core/nest-application.ts:55 — ClassTooLong — 426 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 400 significant lines; this is 26 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.
ClassTooLong: ExpressAdapter packages/platform-express/adapters/express-adapter.ts:68 — ClassTooLong — 405 significant lines (blank, comment-only and punctuation-only lines excluded), 47 methods. The bar is 400 significant lines; this is 5 over it, 1.01× 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: InstanceWrapper packages/core/injector/instance-wrapper.ts:81 — ClassTooLong — 404 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 400 significant lines; this is 4 over it, 1.01× 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.

D30 · Dependency Vulnerabilities · Medium CVE · ×10

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

R7 · Dead Code · Dead file (~10 LoC) · ×10

Dead file (~10 LoC) integration/graphql-code-first/src/main.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~10 LoC) integration/hello-world/src/hello/dto/test.dto.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~10 LoC) integration/hello-world/src/host-array/dto/test.dto.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~10 LoC) integration/hello-world/src/host/dto/test.dto.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~10 LoC) integration/inspector/src/circular-hello/dto/test.dto.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~10 LoC) integration/scopes/src/circular-hello/dto/test.dto.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~10 LoC) integration/scopes/src/circular-transient/dto/test.dto.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~10 LoC) integration/scopes/src/hello/dto/test.dto.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~10 LoC) integration/scopes/src/msvc/dto/test.dto.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~10 LoC) integration/scopes/src/transient/dto/test.dto.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Schema created by TypeORM synchronize: true (no migration path) sample/13-mongo-typeorm/src/app.module.ts:13 — TypeORM synchronize: true builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt TypeORM migrations (`typeorm migration:generate` + `migrationsRun`), so every schema change is a versioned file applied the same way in every environment.
Schema created by TypeORM synchronize: true (no migration path) sample/07-sequelize/src/app.module.ts:15 — TypeORM synchronize: true builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt TypeORM migrations (`typeorm migration:generate` + `migrationsRun`), so every schema change is a versioned file applied the same way in every environment.
Schema created by TypeORM synchronize: true (no migration path) sample/05-sql-typeorm/src/app.module.ts:15 — TypeORM synchronize: true builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt TypeORM migrations (`typeorm migration:generate` + `migrationsRun`), so every schema change is a versioned file applied the same way in every environment.
Schema created by TypeORM synchronize: true (no migration path) integration/typeorm/ormconfig.json:9 — TypeORM synchronize: true builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt TypeORM migrations (`typeorm migration:generate` + `migrationsRun`), so every schema change is a versioned file applied the same way in every environment.
Schema created by TypeORM synchronize: true (no migration path) integration/typeorm/src/app.module.ts:16 — TypeORM synchronize: true builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt TypeORM migrations (`typeorm migration:generate` + `migrationsRun`), so every schema change is a versioned file applied the same way in every environment.
Schema created by TypeORM synchronize: true (no migration path) integration/typeorm/src/async-class-options.module.ts:20 — TypeORM synchronize: true builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt TypeORM migrations (`typeorm migration:generate` + `migrationsRun`), so every schema change is a versioned file applied the same way in every environment.
Schema created by TypeORM synchronize: true (no migration path) integration/typeorm/src/async-existing-options.module.ts:20 — TypeORM synchronize: true builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt TypeORM migrations (`typeorm migration:generate` + `migrationsRun`), so every schema change is a versioned file applied the same way in every environment.
Schema created by TypeORM synchronize: true (no migration path) integration/typeorm/src/async-options.module.ts:17 — TypeORM synchronize: true builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt TypeORM migrations (`typeorm migration:generate` + `migrationsRun`), so every schema change is a versioned file applied the same way in every environment.
Schema created by TypeORM synchronize: true (no migration path) integration/typeorm/src/database.module.ts:20 — TypeORM synchronize: true builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt TypeORM migrations (`typeorm migration:generate` + `migrationsRun`), so every schema change is a versioned file applied the same way in every environment.

D3 · God Classes · FileTooLong · ×8

FileTooLong: injector/injector.ts packages/core/injector/injector.ts — FileTooLong — 1158 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: Injector (111-1748). The bar is 500 significant lines; this is 658 over it, 2.32× 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: REDACTED REDACTED — FileTooLong — 1105 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: FastifyAdapter (203-1810). The bar is 500 significant lines; this is 605 over it, 2.21× 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: external/kafka.interface.ts packages/microservices/external/kafka.interface.ts — FileTooLong — 1015 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 515 over it, 2.03× 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: core/scanner.ts packages/core/scanner.ts — FileTooLong — 587 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: DependenciesScanner (77-841). 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: server/server-grpc.ts packages/microservices/server/server-grpc.ts — FileTooLong — 577 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 77 over it, 1.15× 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: services/console-logger.service.ts packages/common/services/console-logger.service.ts — FileTooLong — 534 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: ConsoleLogger (178-971). The bar is 500 significant lines; this is 34 over it, 1.07× 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: router/router-execution-context.ts packages/core/router/router-execution-context.ts — FileTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded), about 84% of them inside a single declaration: RouterExecutionContext (88-705). The bar is 500 significant lines; this is 33 over it, 1.07× 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: websockets/web-sockets-controller.ts packages/websockets/web-sockets-controller.ts — FileTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: WebSocketsController (48-694). The bar is 500 significant lines; this is 14 over it, 1.03× 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.

R7 · Dead Code · Dead file (~8 LoC) · ×7

Dead file (~8 LoC) integration/graphql-schema-first/src/main.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~8 LoC) integration/lazy-modules/src/main.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~8 LoC) integration/microservices/src/main.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~8 LoC) integration/mongoose/src/main.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~8 LoC) integration/scopes/src/main.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~8 LoC) integration/typeorm/src/main.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~8 LoC) packages/core/errors/exceptions/invalid-middleware-configuration.exception.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Fake-async — async method never awaits integration/hello-world/src/errors/errors.controller.ts:11 — `asynchronous` 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 integration/inspector/src/cats/cats.controller.ts:14 — `create` 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 integration/microservices/src/grpc-advanced/advanced.grpc.controller.ts:119 — `syncCall` 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 integration/microservices/src/grpc-advanced/advanced.grpc.controller.ts:155 — `streamReqCall` 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 integration/microservices/src/grpc/grpc.controller.ts:92 — `sumStreamPass` 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 integration/microservices/src/kafka-concurrent/kafka-concurrent.messages.controller.ts:12 — `go` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.

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

Fixed-sleep synchronisation: should not subscribe async SSE producer Observable when client disconnects mid-await (interceptor case, issue #17352) packages/core/test/router/router-response-controller.spec.ts:778 — This test starts work it did not wait for (`ssePromise`, still running when the sleep starts) and then orders itself against it with `new Promise(resolve => setTimeout(resolve, 10))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: should write an error event and end the stream when a message cannot be serialized packages/core/test/router/router-response-controller.spec.ts:1576 — This test starts work it did not wait for (`promise`, still running when the sleep starts) and then orders itself against it with `new Promise(resolve => setTimeout(resolve, 10))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: should write an error event and end the stream when a message field cannot be serialized packages/core/test/router/router-response-controller.spec.ts:1616 — This test starts work it did not wait for (`promise`, still running when the sleep starts) and then orders itself against it with `new Promise(resolve => setTimeout(resolve, 10))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: should return 503 for NEW queued requests on existing connections during shutdown integration/graceful-shutdown/e2e/express.spec.ts:53 — This test starts work it did not wait for (`closePromise`, still running when the sleep starts) and then orders itself against it with `new Promise(r => setTimeout(r, 0))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: should return 503 for NEW queued requests on existing connections during shutdown integration/graceful-shutdown/e2e/fastify.spec.ts:218 — This test starts work it did not wait for (`inFlight`, still running when the sleep starts) and then orders itself against it with `sleep(100)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

R7 · Dead Code · Dead file (~7 LoC) · ×5

Dead file (~7 LoC) integration/injector/src/app.module.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~7 LoC) integration/inspector/src/defaults/defaults.module.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~7 LoC) integration/route-conflict/src/app.module.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (integration/route-conflict/src/main.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~7 LoC) integration/scopes/src/app.module.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (integration/scopes/src/main.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~7 LoC) integration/websockets/src/app.module.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~1 LoC) · ×5

Dead file (~1 LoC) integration/inspector/src/chat/entities/chat.entity.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~1 LoC) integration/inspector/src/database/entities/database.entity.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~1 LoC) integration/inspector/src/dogs/entities/dog.entity.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~1 LoC) integration/inspector/src/external-svc/entities/external-svc.entity.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~1 LoC) integration/inspector/src/users/entities/user.entity.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

D17 · Explicit Debt · TodoComment · ×4

TodoComment tools/gulp/tasks/samples.ts:26 — // TODO: temporarily ignore Prisma sample as require('.') — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tools/gulp/tasks/samples.ts:35 — // TODO: samples that use third-party compiler plugins (e.g. @nestjs/swagger, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tools/gulp/tasks/samples.ts:140 — // TODO: re-enable test:samples and test:e2e:samples once third-party @nestjs/* — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment integration/send-files/e2e/express.spec.ts:98 — // TODO: temporarily turned off (flaky test) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.

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

REDACTED
REDACTED
REDACTED
REDACTED

D6 · Cohesion (LCOM4) · Low cohesion · ×4

Low cohesion: ExpressAdapter (LCOM4 12) packages/platform-express/adapters/express-adapter.ts:68 — ExpressAdapter's methods fall into 12 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 12 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: FastifyAdapter (LCOM4 8) REDACTED:203 — FastifyAdapter's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: StreamableFile (LCOM4 4) packages/common/file-stream/streamable-file.ts:16 — StreamableFile's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Server (LCOM4 4) packages/microservices/server/server.ts:64 — Server's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.

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

Runner config excludes tests no gate runs vitest.config.integration.mts:55 — `integration/graphql-code-first/**` removes 3 test(s) in 3 file(s) (e.g. `integration/graphql-code-first/e2e/code-first.spec.ts`, `integration/graphql-code-first/e2e/guards-filters.spec.ts`) from what vitest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.
Runner config excludes tests no gate runs vitest.config.integration.mts:57 — `integration/inspector/**` removes 2 test(s) in 1 file(s) (e.g. `integration/inspector/e2e/graph-inspector.spec.ts`) from what vitest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.
Runner config excludes tests no gate runs vitest.config.integration.mts:59 — `integration/repl/e2e/repl.spec.ts` removes 10 test(s) in 1 file(s) (e.g. `integration/repl/e2e/repl.spec.ts`) from what vitest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.

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

Boundary violation [package:third-party-deep-import] REDACTED:38 — REDACTED:38 imports fastify/lib/reply.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] REDACTED:39 — REDACTED:39 imports fastify/lib/symbols.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] REDACTED:69 — REDACTED:69 imports find-my-way/lib/url-sanitizer.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.

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

Recursive walk over a caller-supplied document has no depth cap packages/microservices/server/server-grpc.ts:888 — `getServiceNames` is exported, takes a document from its caller (line 177) and hands it to `collectDeepServices`, which calls itself at line 888 (`this.collectDeepServices`) with a piece of `grpcDefinition` — and nowhere in `collectDeepServices` 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 `collectDeepServices` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/common/utils/strip-proto-keys.util.ts:29 — `stripProtoKeys` is exported and takes `value: any` from its caller, and it calls itself at line 29 (`stripProtoKeys`) with a piece of `value` (and at line 45) — and nowhere in `stripProtoKeys` 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 `stripProtoKeys` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap integration/file-upload/src/upload.module.ts:46 — `createUploadModule` is exported, takes a document from its caller (line 79) and hands it to `describeFiles`, which calls itself at line 46 (`describeFiles`) with a piece of `files` — and nowhere in `describeFiles` 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 `describeFiles` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.

D10 · Test Quality · Skipped test · ×2

Skipped test: should allow for the client to end the response and be able to make another integration/send-files/e2e/express.spec.ts:99 — Skipped — switched off by it.skip
Skipped test: should not stream a non-file integration/send-files/e2e/fastify.spec.ts:52 — Skipped — switched off by it.skip

D2 · Cognitive Complexity · ExpressAdapter.applyVersionFilter · ×2

ExpressAdapter.applyVersionFilter::handlerForMediaTypeVersioning (cognitive 17) packages/platform-express/adapters/express-adapter.ts:612 — ExpressAdapter.applyVersionFilter::handlerForMediaTypeVersioning has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ExpressAdapter.applyVersionFilter::handlerForHeaderVersioning) 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.
ExpressAdapter.applyVersionFilter::handlerForHeaderVersioning (cognitive 17) packages/platform-express/adapters/express-adapter.ts:654 — ExpressAdapter.applyVersionFilter::handlerForHeaderVersioning has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ExpressAdapter.applyVersionFilter::handlerForMediaTypeVersioning) 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.

D23 · Boundary Type-Coupling · Cross-context type ModuleDefinition (core → testing) · ×2

Cross-context type ModuleDefinition (core → testing) packages/testing/interfaces/override-module.interface.ts:8 — ModuleDefinition (context core) is exposed in testing's public surface via OverrideModule.useModule — couples the contexts.
Cross-context type ModuleDefinition (core → testing) packages/testing/testing-module.builder.ts:95 — ModuleDefinition (context core) is exposed in testing's public surface via TestingModuleBuilder.overrideModule — couples the contexts.

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

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

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

Duplicated block with local edits (30 matched lines × 2 locations) packages/core/metadata-scanner.ts:20 — packages/core/metadata-scanner.ts:20 · packages/core/metadata-scanner.ts:78 — the two spans are one implementation copied and then locally edited — 131 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.
Duplicated block with local edits (30 matched lines × 2 locations) packages/microservices/decorators/payload.decorator.ts:14 — packages/microservices/decorators/payload.decorator.ts:14 · packages/websockets/decorators/message-body.decorator.ts:14 — the two spans are one implementation copied and then locally edited — 150 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

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

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

Duplicated block (28 lines × 2 locations) packages/core/exceptions/base-exception-filter-context.ts:47 — packages/core/exceptions/base-exception-filter-context.ts:47 · packages/core/pipes/pipes-context-creator.ts:64 — 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 (28 lines × 2 locations) packages/platform-express/multer/interceptors/any-files.interceptor.ts:30 — packages/platform-express/multer/interceptors/any-files.interceptor.ts:30 · packages/platform-express/multer/interceptors/no-files.interceptor.ts:29 — 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.

R7 · Dead Code · Dead file (~9 LoC) · ×2

Dead file (~9 LoC) integration/route-conflict/src/main.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~9 LoC) packages/microservices/external/nats-codec.interface.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~2 LoC) · ×2

Dead file (~2 LoC) packages/common/interfaces/controllers/index.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~2 LoC) packages/core/interfaces/index.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

D1 · Cyclomatic Complexity · redact.util.createRedactor (cyclomatic 46) · ×1

redact.util.createRedactor (cyclomatic 46) packages/common/services/utils/redact.util.ts:33 — redact.util.createRedactor has cyclomatic complexity 46 (threshold 15). Most of this is not in the body itself: 6 of the 46 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 178, 104, 74, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · ExpressAdapter.applyVersionFilter (cyclomatic 33) · ×1

ExpressAdapter.applyVersionFilter (cyclomatic 33) packages/platform-express/adapters/express-adapter.ts:543 — ExpressAdapter.applyVersionFilter has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 6 of the 33 points are its own statements and the rest belongs to 4 function items inside it that branch (handlerForCustomVersioning, handlerForMediaTypeVersioning, handlerForHeaderVersioning, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · RouterResponseController.sse (cyclomatic 27) · ×1

RouterResponseController.sse (cyclomatic 27) packages/core/router/router-response-controller.ts:124 — RouterResponseController.sse has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 2 of the 27 points are its own statements and the rest belongs to 14 function literals inside it that branch (lines 226, 294, 355, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · RouteParamsFactory.exchangeKeyForValue (cyclomatic 26) · ×1

RouteParamsFactory.exchangeKeyForValue (cyclomatic 26) packages/core/router/route-params-factory.ts:29 — RouteParamsFactory.exchangeKeyForValue has cyclomatic complexity 26 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · serialize-cookie.serializeCookie (cyclomatic 25) · ×1

serialize-cookie.serializeCookie (cyclomatic 25) packages/core/helpers/cookies/serialize-cookie.ts:40 — serialize-cookie.serializeCookie has cyclomatic complexity 25 (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 · ParseArrayPipe.transform (cyclomatic 24) · ×1

ParseArrayPipe.transform (cyclomatic 24) packages/common/pipes/parse-array.pipe.ts:84 — ParseArrayPipe.transform has cyclomatic complexity 24 (threshold 15). Of this number, 20 points are the body's own statements and 4 belong to one function item 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 · create-route-param-metadata.decorator.createParamDecorator (cyclomatic 22) · ×1

create-route-param-metadata.decorator.createParamDecorator (cyclomatic 22) packages/common/decorators/http/create-route-param-metadata.decorator.ts:23 — create-route-param-metadata.decorator.createParamDecorator has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 44, 52). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · security-headers.resolveSecurityHeaders (cyclomatic 22) · ×1

security-headers.resolveSecurityHeaders (cyclomatic 22) packages/core/security/security-headers.ts:252 — security-headers.resolveSecurityHeaders has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · ValidationPipe.transform (cyclomatic 20) · ×1

ValidationPipe.transform (cyclomatic 20) packages/common/pipes/validation.pipe.ts:151 — ValidationPipe.transform has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · FastifyAdapter.createMiddlewareFactory (cyclomatic 20) · ×1

FastifyAdapter.createMiddlewareFactory (cyclomatic 20) REDACTED:1243 — FastifyAdapter.createMiddlewareFactory has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 1249, 1285). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · FastifyAdapter.constructor (cyclomatic 19) · ×1

FastifyAdapter.constructor (cyclomatic 19) REDACTED:348 — FastifyAdapter.constructor has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 428, 480, 492, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · FastifyAdapter.reply (cyclomatic 19) · ×1

FastifyAdapter.reply (cyclomatic 19) REDACTED:739 — FastifyAdapter.reply 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 · FileTypeValidator.isValid (cyclomatic 17) · ×1

FileTypeValidator.isValid (cyclomatic 17) packages/common/pipes/file/file-type.validator.ts:128 — FileTypeValidator.isValid 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 · ExpressAdapter.reply (cyclomatic 17) · ×1

ExpressAdapter.reply (cyclomatic 17) packages/platform-express/adapters/express-adapter.ts:166 — ExpressAdapter.reply has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs 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 · multipart.parser.processMultipart (cyclomatic 17) · ×1

multipart.parser.processMultipart (cyclomatic 17) packages/platform-fastify/multipart/multipart/multipart.parser.ts:417 — multipart.parser.processMultipart 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 · RouterExplorer.applyHostFilter (cyclomatic 16) · ×1

RouterExplorer.applyHostFilter (cyclomatic 16) packages/core/router/router-explorer.ts:345 — RouterExplorer.applyHostFilter has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 378, 355). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D11 · Test Reliability · Test reliability not measured · ×1

Test reliability not measured — JavaScript/TypeScript suite install refused the lockfile — Test reliability NOT MEASURED: the JavaScript/TypeScript suite's dependency install refused the committed lockfile, so no test ever ran and flakiness could not be exercised — the dependency install for the repository root refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. It is excluded from the score rather than counted as a defect; a lockfile in sync with package.json is what lets the suite be re-run.

D12 · Dependency Hygiene · Deprecated · ×1

Deprecated: nats package.json:145 — nats 2.29.3, declared in package.json, is marked deprecated by its publisher: "Package moved. Use @nats-io/transport-node from https://github.com/nats-io/nats.js". Replace it with the package or version that message names, or record why this one must stay.

D2 · Cognitive Complexity · ParseArrayPipe.transform (cognitive 66) · ×1

ParseArrayPipe.transform (cognitive 66) packages/common/pipes/parse-array.pipe.ts:84 — ParseArrayPipe.transform has cognitive complexity 66 (threshold 15). Drivers by points: if/else 17 (36 pts), loops 3 (12 pts), error handling 3 (10 pts), boolean chains 4, ternaries 1 (4 pts) (nesting depth added 38). Of this number, 58 points are the body's own statements and 8 belong to one function item inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · redact.util.createRedactor (cognitive 58) · ×1

redact.util.createRedactor (cognitive 58) packages/common/services/utils/redact.util.ts:33 — redact.util.createRedactor has cognitive complexity 58 (threshold 15). Drivers by points: if/else 27 (35 pts), loops 9 (11 pts), boolean chains 6, ternaries 4 (5 pts), error handling 1 (nesting depth added 11). Most of this is not in the body itself: 6 of the 58 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 178, 104, 74, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · serialize-cookie.serializeCookie (cognitive 31) · ×1

serialize-cookie.serializeCookie (cognitive 31) packages/core/helpers/cookies/serialize-cookie.ts:40 — serialize-cookie.serializeCookie has cognitive complexity 31 (threshold 15). Drivers by points: if/else 18 (25 pts), boolean chains 5, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · JsonSocket.processBuffer (cognitive 29) · ×1

JsonSocket.processBuffer (cognitive 29) packages/microservices/helpers/json-socket.ts:114 — JsonSocket.processBuffer has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (27 pts), boolean chains 1, loops 1 (nesting depth added 15). 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 · RouterExplorer.applyHostFilter (cognitive 25) · ×1

RouterExplorer.applyHostFilter (cognitive 25) packages/core/router/router-explorer.ts:345 — RouterExplorer.applyHostFilter has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2 (5 pts), boolean chains 2, error handling 1 (2 pts), ternaries 2 (nesting depth added 10). Most of this is not in the body itself: 3 of the 25 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 378, 355). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · security-headers.resolveSecurityHeaders (cognitive 24) · ×1

security-headers.resolveSecurityHeaders (cognitive 24) packages/core/security/security-headers.ts:252 — security-headers.resolveSecurityHeaders has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (16 pts), ternaries 4 (7 pts), loops 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · FastifyAdapter.constructor (cognitive 24) · ×1

FastifyAdapter.constructor (cognitive 24) REDACTED:348 — FastifyAdapter.constructor has cognitive complexity 24 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 4, error handling 1 (2 pts), ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 5 of the 24 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 428, 480, 409, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · multipart.parser.processMultipart (cognitive 23) · ×1

multipart.parser.processMultipart (cognitive 23) packages/platform-fastify/multipart/multipart/multipart.parser.ts:417 — multipart.parser.processMultipart has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 3 (5 pts), ternaries 1 (2 pts), error handling 1, match/switch 1 (nesting depth added 9). 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 · FastifyAdapter.reply (cognitive 22) · ×1

FastifyAdapter.reply (cognitive 22) REDACTED:739 — FastifyAdapter.reply has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 7, ternaries 1 (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 · FileTypeValidator.isValid (cognitive 20) · ×1

FileTypeValidator.isValid (cognitive 20) packages/common/pipes/file/file-type.validator.ts:128 — FileTypeValidator.isValid has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3, ternaries 1 (2 pts), error handling 1 (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 · ExpressAdapter.reply (cognitive 20) · ×1

ExpressAdapter.reply (cognitive 20) packages/platform-express/adapters/express-adapter.ts:166 — ExpressAdapter.reply has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 4, ternaries 1 (nesting depth added 5). Of this number, 18 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 · create-route-param-metadata.decorator.createParamDecorator (cognitive 19) · ×1

create-route-param-metadata.decorator.createParamDecorator (cognitive 19) packages/common/decorators/http/create-route-param-metadata.decorator.ts:23 — create-route-param-metadata.decorator.createParamDecorator has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 10, ternaries 4 (5 pts), if/else 2 (3 pts), loops 1 (nesting depth added 2). None of this is in the body itself: all 19 points belong to 2 function literals inside it that branch (lines 44, 52). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · ValidationPipe.transform (cognitive 19) · ×1

ValidationPipe.transform (cognitive 19) packages/common/pipes/validation.pipe.ts:151 — ValidationPipe.transform has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10, boolean chains 6, ternaries 2 (3 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · ClientNats.handleStatusUpdates (cognitive 19) · ×1

ClientNats.handleStatusUpdates (cognitive 19) packages/microservices/client/client-nats.ts:155 — ClientNats.handleStatusUpdates has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 2 (7 pts), if/else 3 (6 pts), error handling 1 (2 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ClientGrpcProxy.createUnaryServiceMethod (cognitive 19) · ×1

ClientGrpcProxy.createUnaryServiceMethod (cognitive 19) REDACTED:225 — ClientGrpcProxy.createUnaryServiceMethod has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 3 (nesting depth added 8). None of this is in the body itself: all 19 points belong to 6 function literals inside it that branch (lines 239, 229, 236, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · FastifyAdapter.createMiddlewareFactory (cognitive 19) · ×1

FastifyAdapter.createMiddlewareFactory (cognitive 19) REDACTED:1243 — FastifyAdapter.createMiddlewareFactory has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 3 (4 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 5). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 1249, 1285). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · samples.executeNpmScriptInSamples (cognitive 18) · ×1

samples.executeNpmScriptInSamples (cognitive 18) tools/gulp/tasks/samples.ts:18 — samples.executeNpmScriptInSamples has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 3 (5 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · RouteParamsFactory.exchangeKeyForValue (cognitive 18) · ×1

RouteParamsFactory.exchangeKeyForValue (cognitive 18) packages/core/router/route-params-factory.ts:29 — RouteParamsFactory.exchangeKeyForValue has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 7 (14 pts), boolean chains 3, match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · ServerGrpc.writeObservableToGrpc (cognitive 17) · ×1

ServerGrpc.writeObservableToGrpc (cognitive 17) packages/microservices/server/server-grpc.ts:441 — ServerGrpc.writeObservableToGrpc has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 2, loops 1 (nesting depth added 1). None of this is in the body itself: all 17 points belong to 3 function literals inside it that branch (lines 447, 476, 512). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · ServerNats.handleStatusUpdates (cognitive 17) · ×1

ServerNats.handleStatusUpdates (cognitive 17) packages/microservices/server/server-nats.ts:284 — ServerNats.handleStatusUpdates has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 2 (7 pts), if/else 2 (4 pts), error handling 1 (2 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 9). 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 · security-headers.serializeContentSecurityPolicy (cognitive 16) · ×1

security-headers.serializeContentSecurityPolicy (cognitive 16) packages/core/security/security-headers.ts:136 — security-headers.serializeContentSecurityPolicy has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (nesting depth added 3). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · CapturingLogger.capture (cognitive 16) · ×1

CapturingLogger.capture (cognitive 16) packages/testing/services/capturing-logger.service.ts:197 — CapturingLogger.capture has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 4 (5 pts), boolean chains 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

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

REDACTED

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

REDACTED

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

REDACTED

D3 · God Classes · FunctionTooLong · ×1

FunctionTooLong: redact.util.createRedactor packages/common/services/utils/redact.util.ts:33 — FunctionTooLong — createRedactor runs 150 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× 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.

D3 · God Classes · MethodTooLong · ×1

MethodTooLong: RouterExecutionContext.create packages/core/router/router-execution-context.ts:106 — MethodTooLong — create runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× 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.

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

REDACTED

D44 · Platform End-of-Life · End-of-life runtime · ×1

End-of-life runtime: Node.js 20 package.json:164 — package.json declares Node.js 20 as this project's engines.node, and Node.js 20, support ended 2026-04-30. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2026-04-30 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.

D8 · Code Coverage · Coverage not measured · ×1

Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for the repository root refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.

IC1 · Incompleteness & stubs · Hollow method · ×1

Hollow method — returns a constant without doing the work integration/graphql-code-first/src/recipes/recipes.service.ts:28 — `remove` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.

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

Sync-over-async blocking sample/28-sse/src/app.controller.ts:17 — `readFileSync` in `index` 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 9 sibling directories (44 clone groups) · ×1

Duplication concentrated across 9 sibling directories (44 clone groups) packages/microservices/context/rpc-context-creator.ts:60 — 44 duplicated blocks under packages/ have copies in at least two of the sibling directories common, core, microservices, platform-express, platform-fastify, platform-socket.io (+3 more sibling(s) not listed) — 34 of them are reported below, and 10 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 10 sibling directories (32 clone groups) · ×1

Duplication concentrated across 10 sibling directories (32 clone groups) integration/inspector/src/dogs/dogs.controller.ts:14 — 32 duplicated blocks under integration/ have copies in at least two of the sibling directories graphql-code-first, graphql-schema-first, injector, inspector, mongoose, repl (+4 more sibling(s) not listed) — 16 of them are reported below, and 16 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 32 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 32 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 32 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 2 sibling directories (22 clone groups) · ×1

Duplication concentrated across 2 sibling directories (22 clone groups) packages/microservices/client/client-proxy.ts:199 — 22 duplicated blocks under packages/microservices/ have copies in at least two of the sibling directories client, server — 17 of them are reported below, and 5 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 · Duplication concentrated across 7 sibling directories (12 clone groups) · ×1

Duplication concentrated across 7 sibling directories (12 clone groups) packages/core/interceptors/interceptors-context-creator.ts:15 — 12 duplicated blocks under packages/core/ have copies in at least two of the sibling directories exceptions, guards, helpers, interceptors, middleware, pipes (+1 more sibling(s) not listed) — 10 of them are reported below, and 2 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 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 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 12 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 5 sibling directories (11 clone groups) · ×1

Duplication concentrated across 5 sibling directories (11 clone groups) integration/scopes/src/hello/hello.module.ts:7 — 11 duplicated blocks under integration/scopes/src/ have copies in at least two of the sibling directories circular-hello, circular-transient, hello, msvc, transient — 4 of them are reported below, and 7 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 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 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 11 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 (8 clone groups) · ×1

Duplication concentrated across 6 sibling directories (8 clone groups) integration/microservices/src/redis/redis.controller.ts:21 — 8 of the duplicated blocks reported below have copies in at least two of the sibling directories kafka, kafka-concurrent, mqtt, nats, redis, rmq under integration/microservices/src/. That concentration is one structural fact, not 8 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 8 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 (215 matched lines × 2 locations) · ×1

Duplicated block with local edits (215 matched lines × 2 locations) packages/microservices/context/rpc-context-creator.ts:60 — packages/microservices/context/rpc-context-creator.ts:60 · packages/websockets/context/ws-context-creator.ts:34 — the two spans are one implementation copied and then locally edited — 1117 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 (97 matched lines × 2 locations) · ×1

Duplicated block with local edits (97 matched lines × 2 locations) packages/core/interceptors/interceptors-context-creator.ts:15 — packages/core/interceptors/interceptors-context-creator.ts:15 · packages/core/pipes/pipes-context-creator.ts:15 — the two spans are one implementation copied and then locally edited — 517 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 (88 matched lines × 2 locations) · ×1

Duplicated block with local edits (88 matched lines × 2 locations) packages/microservices/server/server-nats.ts:51 — packages/microservices/server/server-nats.ts:51 · packages/microservices/server/server-redis.ts:41 — 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 · Wholesale file copy (75 identical lines × 2 files) · ×1

Wholesale file copy (75 identical lines × 2 files) integration/microservices/src/app.controller.ts:8 — integration/microservices/src/app.controller.ts:8 · integration/microservices/src/tcp-tls/app.controller.ts:8 — these 2 files are line-for-line copies of one another — 75 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.

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

Duplicated block with local edits (67 matched lines × 2 locations) packages/core/nest-application.ts:552 — packages/core/nest-application.ts:552 · packages/microservices/nest-microservice.ts:212 — the two spans are one implementation copied and then locally edited — 326 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 (61 lines × 3 locations) · ×1

Duplicated block (61 lines × 3 locations) packages/core/helpers/external-context-creator.ts:306 — packages/core/helpers/external-context-creator.ts:306 · packages/microservices/context/rpc-context-creator.ts:308 · packages/websockets/context/ws-context-creator.ts:231 — 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 (61 matched lines × 2 locations) · ×1

Duplicated block with local edits (61 matched lines × 2 locations) packages/core/helpers/external-context-creator.ts:127 — packages/core/helpers/external-context-creator.ts:127 · packages/core/router/router-execution-context.ts:137 — the two spans are one implementation copied and then locally edited — 268 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 (61 lines × 2 locations) · ×1

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

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

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

R10 · Code Duplication · Wholesale file copy (55 identical lines × 2 files) · ×1

Wholesale file copy (55 identical lines × 2 files) packages/microservices/utils/param.utils.ts:1 — packages/microservices/utils/param.utils.ts:1 · packages/websockets/utils/param.utils.ts:1 — these 2 files are line-for-line copies of one another — 55 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.

R10 · Code Duplication · Wholesale file copy (52 identical lines × 3 files) · ×1

Wholesale file copy (52 identical lines × 3 files) packages/platform-socket.io/utils/merge-map-bounded.util.ts:4 — packages/platform-socket.io/utils/merge-map-bounded.util.ts:4 · packages/platform-ws/utils/merge-map-bounded.util.ts:4 · packages/websockets/utils/merge-map-bounded.util.ts:4 — these 3 files are line-for-line copies of one another — 52 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.

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

Duplicated block (49 lines × 2 locations) integration/nest-application/sse/src/app.controller.ts:168 — integration/nest-application/sse/src/app.controller.ts:168 · integration/nest-application/sse/src/app.controller.ts:256 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

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

Duplicated block with local edits (44 matched lines × 2 locations) packages/microservices/client/client-proxy.ts:199 — packages/microservices/client/client-proxy.ts:199 · packages/microservices/server/server.ts:384 — the two spans are one implementation copied and then locally edited — 248 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 (44 lines × 2 locations) · ×1

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

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

Duplicated block with local edits (41 matched lines × 2 locations) integration/microservices/src/redis/redis.controller.ts:21 — integration/microservices/src/redis/redis.controller.ts:21 · integration/microservices/src/rmq/rmq.controller.ts:42 — the two spans are one implementation copied and then locally edited — 340 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 (41 lines × 2 locations) · ×1

Duplicated block (41 lines × 2 locations) packages/platform-express/adapters/utils/get-media-type-version.util.ts:5 — packages/platform-express/adapters/utils/get-media-type-version.util.ts:5 · packages/platform-fastify/adapters/utils/get-media-type-version.util.ts:5 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.

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

Duplicated block with local edits (40 matched lines × 2 locations) packages/microservices/client/client-nats.ts:205 — packages/microservices/client/client-nats.ts:205 · packages/microservices/server/server-nats.ts:324 — the two spans are one implementation copied and then locally edited — 204 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/core/guards/guards-context-creator.ts:16 — packages/core/guards/guards-context-creator.ts:16 · packages/core/pipes/pipes-context-creator.ts:15 — 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 (36 lines × 2 locations) · ×1

Duplicated block (36 lines × 2 locations) packages/core/hooks/before-app-shutdown.hook.ts:47 — packages/core/hooks/before-app-shutdown.hook.ts:47 · packages/core/hooks/on-app-shutdown.hook.ts:43 — 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 (35 lines × 3 locations) · ×1

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

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

Duplicated block (33 lines × 3 locations) packages/common/decorators/http/route-params.decorator.ts:495 — packages/common/decorators/http/route-params.decorator.ts:495 · packages/common/decorators/http/route-params.decorator.ts:651 · packages/common/decorators/http/route-params.decorator.ts:936 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

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

Duplicated block with local edits (29 matched lines × 2 locations) packages/core/injector/module-ref.ts:47 — packages/core/injector/module-ref.ts:47 · packages/core/nest-application-context.ts:130 — the two spans are one implementation copied and then locally edited — 219 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 (27 lines × 2 locations) · ×1

Duplicated block (27 lines × 2 locations) packages/microservices/client/client-mqtt.ts:288 — packages/microservices/client/client-mqtt.ts:288 · packages/microservices/client/client-tcp.ts:124 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.

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

Duplicated block (26 lines × 2 locations) integration/hello-world/src/host-array/host-array.controller.ts:8 — integration/hello-world/src/host-array/host-array.controller.ts:8 · integration/hello-world/src/host/host.controller.ts:8 — 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 (26 lines × 4 locations) · ×1

Duplicated block (26 lines × 4 locations) packages/core/exceptions/external-exception-filter-context.ts:48 — packages/core/exceptions/external-exception-filter-context.ts:48 · packages/core/guards/guards-context-creator.ts:102 · packages/core/interceptors/interceptors-context-creator.ts:101 · packages/core/pipes/pipes-context-creator.ts:93 — the 4 copies are spread across 4 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.

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

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

R2 · Cyclomatic Complexity · Complex function (top-level) (cyclomatic 29, cognitive 29) · ×1

Complex function (top-level) (cyclomatic 29, cognitive 29) packages/core/exceptions/base-exception-filter.ts:1 — (top-level) has cyclomatic complexity 29 and cognitive complexity 29; 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 serializeCookie (cyclomatic 26, cognitive 32) · ×1

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

R2 · Cyclomatic Complexity · Complex function exchangeKeyForValue (cyclomatic 26, cognitive 18) · ×1

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

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

Complex function (anonymous) (cyclomatic 25, cognitive 28) REDACTED:1245 — (anonymous) has cyclomatic complexity 25 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 (anonymous) (cyclomatic 23, cognitive 22) · ×1

Complex function (anonymous) (cyclomatic 23, cognitive 22) packages/platform-express/adapters/express-adapter.ts:419 — (anonymous) has cyclomatic complexity 23 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 resolveSecurityHeaders (cyclomatic 22, cognitive 27) · ×1

Complex function resolveSecurityHeaders (cyclomatic 22, cognitive 27) packages/core/security/security-headers.ts:252 — resolveSecurityHeaders has cyclomatic complexity 22 and cognitive complexity 27; 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 transform (cyclomatic 20, cognitive 58) · ×1

Complex function transform (cyclomatic 20, cognitive 58) packages/common/pipes/parse-array.pipe.ts:84 — transform has cyclomatic complexity 20 and cognitive complexity 58; 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 transform (cyclomatic 20, cognitive 20) · ×1

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

R2 · Cyclomatic Complexity · Complex function processMultipart (cyclomatic 19, cognitive 25) · ×1

Complex function processMultipart (cyclomatic 19, cognitive 25) packages/platform-fastify/multipart/multipart/multipart.parser.ts:417 — processMultipart has cyclomatic complexity 19 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 (top-level) (cyclomatic 18, cognitive 16) · ×1

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

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

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

R2 · Cyclomatic Complexity · Complex function scanForModules (cyclomatic 16, cognitive 17) · ×1

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

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

Complex function capture (cyclomatic 15, cognitive 16) packages/testing/services/capturing-logger.service.ts:197 — capture has cyclomatic complexity 15 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 redactObject (cyclomatic 14, cognitive 21) · ×1

Complex function redactObject (cyclomatic 14, cognitive 21) packages/common/services/utils/redact.util.ts:178 — redactObject has cyclomatic complexity 14 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 14, cognitive 18) · ×1

Complex function (anonymous) (cyclomatic 14, cognitive 18) packages/microservices/client/client-nats.ts:314 — (anonymous) has cyclomatic complexity 14 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 (anonymous) (cyclomatic 14, cognitive 15) · ×1

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

R2 · Cyclomatic Complexity · Complex function processBuffer (cyclomatic 13, cognitive 29) · ×1

Complex function processBuffer (cyclomatic 13, cognitive 29) packages/microservices/helpers/json-socket.ts:114 — processBuffer has cyclomatic complexity 13 and cognitive complexity 29; 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 13, cognitive 14) · ×1

Complex function (anonymous) (cyclomatic 13, cognitive 14) REDACTED:1249 — (anonymous) has cyclomatic complexity 13 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 transformException (cyclomatic 13, cognitive 14) · ×1

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

R3 · Large Files · REDACTED · ×1

REDACTED: 1683 lines of code REDACTED:1 — REDACTED has 1683 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/core/injector/injector.ts · ×1

packages/core/injector/injector.ts: 1632 lines of code packages/core/injector/injector.ts:1 — packages/core/injector/injector.ts has 1632 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/microservices/external/kafka.interface.ts · ×1

packages/microservices/external/kafka.interface.ts: 1178 lines of code packages/microservices/external/kafka.interface.ts:1 — packages/microservices/external/kafka.interface.ts has 1178 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/common/decorators/http/route-params.decorator.ts · ×1

packages/common/decorators/http/route-params.decorator.ts: 1101 lines of code packages/common/decorators/http/route-params.decorator.ts:1 — packages/common/decorators/http/route-params.decorator.ts has 1101 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/microservices/server/server-grpc.ts · ×1

packages/microservices/server/server-grpc.ts: 910 lines of code packages/microservices/server/server-grpc.ts:1 — packages/microservices/server/server-grpc.ts has 910 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/common/services/console-logger.service.ts · ×1

packages/common/services/console-logger.service.ts: 896 lines of code packages/common/services/console-logger.service.ts:1 — packages/common/services/console-logger.service.ts has 896 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/core/scanner.ts · ×1

packages/core/scanner.ts: 772 lines of code packages/core/scanner.ts:1 — packages/core/scanner.ts has 772 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/common/interfaces/http/http-server.interface.ts · ×1

packages/common/interfaces/http/http-server.interface.ts: 714 lines of code packages/common/interfaces/http/http-server.interface.ts:1 — packages/common/interfaces/http/http-server.interface.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/platform-express/adapters/express-adapter.ts · ×1

packages/platform-express/adapters/express-adapter.ts: 706 lines of code packages/platform-express/adapters/express-adapter.ts:1 — packages/platform-express/adapters/express-adapter.ts has 706 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/core/nest-application.ts · ×1

packages/core/nest-application.ts: 686 lines of code packages/core/nest-application.ts:1 — packages/core/nest-application.ts has 686 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/core/router/router-execution-context.ts · ×1

packages/core/router/router-execution-context.ts: 667 lines of code packages/core/router/router-execution-context.ts:1 — packages/core/router/router-execution-context.ts has 667 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/websockets/web-sockets-controller.ts · ×1

packages/websockets/web-sockets-controller.ts: 660 lines of code packages/websockets/web-sockets-controller.ts:1 — packages/websockets/web-sockets-controller.ts has 660 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/core/adapters/http-adapter.ts · ×1

packages/core/adapters/http-adapter.ts: 650 lines of code packages/core/adapters/http-adapter.ts:1 — packages/core/adapters/http-adapter.ts has 650 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/core/injector/instance-wrapper.ts · ×1

packages/core/injector/instance-wrapper.ts: 640 lines of code packages/core/injector/instance-wrapper.ts:1 — packages/core/injector/instance-wrapper.ts has 640 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/core/injector/module.ts · ×1

packages/core/injector/module.ts: 612 lines of code packages/core/injector/module.ts:1 — packages/core/injector/module.ts has 612 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/microservices/client/client-rmq.ts · ×1

packages/microservices/client/client-rmq.ts: 561 lines of code packages/microservices/client/client-rmq.ts:1 — packages/microservices/client/client-rmq.ts has 561 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/platform-fastify/multipart/multipart/multipart.parser.ts · ×1

packages/platform-fastify/multipart/multipart/multipart.parser.ts: 549 lines of code packages/platform-fastify/multipart/multipart/multipart.parser.ts:1 — packages/platform-fastify/multipart/multipart/multipart.parser.ts has 549 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/core/router/router-explorer.ts · ×1

packages/core/router/router-explorer.ts: 503 lines of code packages/core/router/router-explorer.ts:1 — packages/core/router/router-explorer.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/microservices/client/client-kafka.ts · ×1

packages/microservices/client/client-kafka.ts: 502 lines of code packages/microservices/client/client-kafka.ts:1 — packages/microservices/client/client-kafka.ts has 502 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/microservices/server/server-rmq.ts · ×1

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

R3 · Large Files · packages/core/nest-application-context.ts · ×1

packages/core/nest-application-context.ts: 498 lines of code packages/core/nest-application-context.ts:1 — packages/core/nest-application-context.ts has 498 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/microservices/server/server-kafka.ts · ×1

packages/microservices/server/server-kafka.ts: 479 lines of code packages/microservices/server/server-kafka.ts:1 — packages/microservices/server/server-kafka.ts has 479 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/microservices/server/server.ts · ×1

packages/microservices/server/server.ts: 479 lines of code packages/microservices/server/server.ts:1 — packages/microservices/server/server.ts has 479 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/core/security/security-headers.ts · ×1

packages/core/security/security-headers.ts: 468 lines of code packages/core/security/security-headers.ts:1 — packages/core/security/security-headers.ts has 468 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/common/pipes/validation.pipe.ts · ×1

packages/common/pipes/validation.pipe.ts: 460 lines of code packages/common/pipes/validation.pipe.ts:1 — packages/common/pipes/validation.pipe.ts has 460 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/microservices/client/client-mqtt.ts · ×1

packages/microservices/client/client-mqtt.ts: 451 lines of code packages/microservices/client/client-mqtt.ts:1 — packages/microservices/client/client-mqtt.ts has 451 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/microservices/client/client-redis.ts · ×1

packages/microservices/client/client-redis.ts: 422 lines of code packages/microservices/client/client-redis.ts:1 — packages/microservices/client/client-redis.ts has 422 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/microservices/nest-microservice.ts · ×1

packages/microservices/nest-microservice.ts: 418 lines of code packages/microservices/nest-microservice.ts:1 — packages/microservices/nest-microservice.ts has 418 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 · REDACTED · ×1

REDACTED: 415 lines of code REDACTED:1 — REDACTED has 415 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/core/security/cross-origin-protection.ts · ×1

packages/core/security/cross-origin-protection.ts: 402 lines of code packages/core/security/cross-origin-protection.ts:1 — packages/core/security/cross-origin-protection.ts has 402 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R7 · Dead Code · Dead file (~69 LoC) · ×1

Dead file (~69 LoC) integration/_support/register-local-packages.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~39 LoC) · ×1

Dead file (~39 LoC) integration/microservices/src/rmq/rmq-broadcast.controller.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~23 LoC) · ×1

Dead file (~23 LoC) integration/inspector/src/durable/durable-context-id.strategy.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~22 LoC) · ×1

Dead file (~22 LoC) integration/graphql-schema-first/src/common/scalars/date.scalar.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~15 LoC) · ×1

Dead file (~15 LoC) integration/versioning/src/main.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~11 LoC) · ×1

Dead file (~11 LoC) integration/inspector/src/defaults/defaults.service.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (integration/inspector/src/defaults/defaults.module.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~5 LoC) · ×1

Dead file (~5 LoC) packages/microservices/serializers/index.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~4 LoC) · ×1

Dead file (~4 LoC) integration/inspector/src/defaults/core.service.ts — no import path from any entry point (58 application, 5 tooling, 536 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (integration/inspector/src/defaults/defaults.service.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R8 · Dependency Hygiene · Unused dependency 'body-parser' · ×1

Unused dependency 'body-parser' — Declared in the root 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.

R8 · Dependency Hygiene · Unused dependency 'cache-manager' · ×1

Unused dependency 'cache-manager' — Declared in the root 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.

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

Unused dependency 'coveralls' — Declared in the root 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.

Minor — 313 finding(s)

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

Mock-dominated test: should call "decorateWithNamespace" and not call "createSocketServer" packages/websockets/test/socket-server-provider.spec.ts:61 — This test sets up 3 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should not call the handler when a deferred load of its context fails packages/websockets/test/web-sockets-controller.spec.ts:528 — This test sets up 6 test doubles (for example `vi.fn`) against 3 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should pass async hook errors to the exception filter packages/websockets/test/web-sockets-controller.spec.ts:850 — This test sets up 4 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should resolve the exception filters in the context of each connection packages/websockets/test/web-sockets-controller.spec.ts:1070 — This test sets up 4 test doubles (for example `vi .spyOn`) against 2 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should create its enhancers in the context of the connection before its filters handle the error packages/websockets/test/web-sockets-controller.spec.ts:1139 — This test sets up 3 test doubles (for example `vi .spyOn`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should log each message handler packages/websockets/test/web-sockets-controller.spec.ts:1677 — This test sets up 3 test doubles (for example `vi.spyOn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should close a client once more than "maxSendBufferSize" bytes are queued for it packages/platform-ws/test/ws-adapter.spec.ts:287 — This test sets up 3 test doubles (for example `vi .spyOn`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should not handle the messages of a client with more than "maxSendBufferSize" bytes queued packages/platform-ws/test/ws-adapter.spec.ts:304 — This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should let 128 MB be queued for a client by default packages/platform-ws/test/ws-adapter.spec.ts:319 — This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should register only one disconnect listener regardless of call count packages/platform-socket.io/test/io-adapter.spec.ts:67 — This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should register the exact-match path $path through "$expressMethod" at $registeredPath packages/platform-express/test/adapters/express-adapter.spec.ts:167 — This test sets up 3 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should register the express built-in parsers for json and urlencoded payloads packages/platform-express/test/adapters/express-adapter.spec.ts:219 — This test sets up 3 test doubles (for example `vi .spyOn`) against 1 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should call listen() on server when listen() is called packages/microservices/test/nest-microservice.spec.ts:97 — This test sets up 9 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should call the lifecycle hooks once when init() is called packages/microservices/test/nest-microservice.spec.ts:117 — This test sets up 11 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should assign the clients, register the listeners and call the lifecycle hooks packages/microservices/test/nest-microservice.spec.ts:173 — This test sets up 5 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should leave the clients and the lifecycle hooks to the application it is connected to packages/microservices/test/nest-microservice.spec.ts:191 — This test sets up 5 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should delegate on() to server packages/microservices/test/nest-microservice.spec.ts:230 — This test sets up 9 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should warn when called after initialization packages/microservices/test/nest-microservice.spec.ts:271 — This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should let the rmq server set up a channel packages/microservices/test/server/server-factory.spec.ts:178 — This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should call callback with a thrown error as an argument packages/microservices/test/server/server-grpc.spec.ts:81 — This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should call "addService" packages/microservices/test/server/server-grpc.spec.ts:133 — This test sets up 3 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should call "addService" packages/microservices/test/server/server-grpc.spec.ts:173 — This test sets up 3 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should call native method packages/microservices/test/server/server-grpc.spec.ts:454 — This test sets up 6 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should handle error thrown in handler packages/microservices/test/server/server-grpc.spec.ts:473 — This test sets up 7 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should call native & callback methods packages/microservices/test/server/server-grpc.spec.ts:551 — This test sets up 6 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
+ 112 more in this group — see findings.md.

X4 · Structured logging · Interpolated log message defeats structured logging · ×33

Interpolated log message defeats structured logging tools/gulp/tasks/samples.ts:100 — `info` at line 100 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging tools/gulp/tasks/samples.ts:114 — `info` at line 114 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging tools/gulp/tasks/samples.ts:122 — `error` at line 122 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/websockets/web-sockets-controller.ts:546 — `error` at line 546 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/websockets/web-sockets-controller.ts:689 — `log` at line 689 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging REDACTED:336 — `warn` at line 336 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/microservices/server/server-kafka.ts:297 — `error` at line 297 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/microservices/server/server-kafka.ts:325 — `error` at line 325 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/microservices/server/server-nats.ts:289 — `error` at line 289 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/microservices/server/server-nats.ts:295 — `error` at line 295 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/microservices/server/server-nats.ts:317 — `log` at line 317 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/microservices/server/server-nats.ts:327 — `log` at line 327 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/microservices/server/server-nats.ts:343 — `log` at line 343 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/microservices/client/client-kafka.ts:312 — `error` at line 312 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/microservices/client/client-mqtt.ts:294 — `error` at line 294 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/microservices/client/client-nats.ts:163 — `error` at line 163 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/microservices/client/client-nats.ts:175 — `error` at line 175 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/microservices/client/client-nats.ts:190 — `log` at line 190 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/microservices/client/client-nats.ts:201 — `debug` at line 201 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/microservices/client/client-nats.ts:208 — `log` at line 208 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/microservices/client/client-nats.ts:224 — `log` at line 224 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/microservices/client/client-redis.ts:323 — `error` at line 323 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/microservices/client/client-tcp.ts:130 — `error` at line 130 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/core/router/router-explorer.ts:361 — `error` at line 361 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/core/router/router-explorer.ts:405 — `warn` at line 405 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
+ 8 more in this group — see findings.md.

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

README/code drift packages/common/Readme.md:38 — packages/common/Readme.md links to `readme_zh.md`, but `packages/common/readme_zh.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/common/Readme.md:39 — packages/common/Readme.md links to `readme_kr.md`, but `packages/common/readme_kr.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/common/Readme.md:40 — packages/common/Readme.md links to `readme_jp.md`, but `packages/common/readme_jp.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/core/Readme.md:38 — packages/core/Readme.md links to `readme_zh.md`, but `packages/core/readme_zh.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/core/Readme.md:39 — packages/core/Readme.md links to `readme_kr.md`, but `packages/core/readme_kr.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/core/Readme.md:40 — packages/core/Readme.md links to `readme_jp.md`, but `packages/core/readme_jp.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/microservices/Readme.md:38 — packages/microservices/Readme.md links to `readme_zh.md`, but `packages/microservices/readme_zh.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/microservices/Readme.md:39 — packages/microservices/Readme.md links to `readme_kr.md`, but `packages/microservices/readme_kr.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/microservices/Readme.md:40 — packages/microservices/Readme.md links to `readme_jp.md`, but `packages/microservices/readme_jp.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/platform-express/Readme.md:38 — packages/platform-express/Readme.md links to `readme_zh.md`, but `packages/platform-express/readme_zh.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/platform-express/Readme.md:39 — packages/platform-express/Readme.md links to `readme_kr.md`, but `packages/platform-express/readme_kr.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/platform-express/Readme.md:40 — packages/platform-express/Readme.md links to `readme_jp.md`, but `packages/platform-express/readme_jp.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/platform-fastify/Readme.md:38 — packages/platform-fastify/Readme.md links to `readme_zh.md`, but `packages/platform-fastify/readme_zh.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/platform-fastify/Readme.md:39 — packages/platform-fastify/Readme.md links to `readme_kr.md`, but `packages/platform-fastify/readme_kr.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/platform-fastify/Readme.md:40 — packages/platform-fastify/Readme.md links to `readme_jp.md`, but `packages/platform-fastify/readme_jp.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/platform-socket.io/Readme.md:38 — packages/platform-socket.io/Readme.md links to `readme_zh.md`, but `packages/platform-socket.io/readme_zh.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/platform-socket.io/Readme.md:39 — packages/platform-socket.io/Readme.md links to `readme_kr.md`, but `packages/platform-socket.io/readme_kr.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/platform-socket.io/Readme.md:40 — packages/platform-socket.io/Readme.md links to `readme_jp.md`, but `packages/platform-socket.io/readme_jp.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/platform-ws/Readme.md:38 — packages/platform-ws/Readme.md links to `readme_zh.md`, but `packages/platform-ws/readme_zh.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/platform-ws/Readme.md:39 — packages/platform-ws/Readme.md links to `readme_kr.md`, but `packages/platform-ws/readme_kr.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/platform-ws/Readme.md:40 — packages/platform-ws/Readme.md links to `readme_jp.md`, but `packages/platform-ws/readme_jp.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/testing/Readme.md:38 — packages/testing/Readme.md links to `readme_zh.md`, but `packages/testing/readme_zh.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/testing/Readme.md:39 — packages/testing/Readme.md links to `readme_kr.md`, but `packages/testing/readme_kr.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/testing/Readme.md:40 — packages/testing/Readme.md links to `readme_jp.md`, but `packages/testing/readme_jp.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/websockets/Readme.md:38 — packages/websockets/Readme.md links to `readme_zh.md`, but `packages/websockets/readme_zh.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
+ 2 more in this group — see findings.md.

X10 · Duplicated predicate · Duplicated predicate · ×25

Duplicated predicate packages/platform-express/multer/multer/multer.utils.ts:138 — `!error || error instanceof HttpException` appears character-identically in 2 files — packages/platform-express/multer/multer/multer.utils.ts, packages/platform-fastify/multipart/multipart/multipart.utils.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/microservices/client/client-nats.ts:394 — `!requestHeaders && !this.options?.headers` appears character-identically in 2 files — packages/microservices/client/client-nats.ts, packages/microservices/client/client-rmq.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/platform-fastify/multipart/multipart/multipart.parser.ts:194 — `!stream.readableEnded && !stream.errored` appears character-identically in 2 files — packages/platform-fastify/multipart/multipart/multipart.parser.ts, packages/platform-fastify/multipart/storage/disk.storage.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/microservices/client/client-nats.ts:219 — `'data' in status && isObject(status.data)` appears character-identically in 2 files — packages/microservices/client/client-nats.ts, packages/microservices/server/server-nats.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/microservices/decorators/event-pattern.decorator.ts:60 — `(isNumber(transportOrExtras) || isSymbol(transportOrExtras)) && isNil(maybeExtras)` appears character-identically in 2 files — packages/microservices/decorators/event-pattern.decorator.ts, packages/microservices/decorators/message-pattern.decorator.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/microservices/factories/rpc-params-factory.ts:14 — `(isObject(payload) && !Array.isArray(payload) && !ArrayBuffer.isView(payload)) || (!isNil(payload) && Object.hasOwn(Object(payload), key))` appears character-identically in 2 files — packages/microservices/factories/rpc-params-factory.ts, packages/websockets/factories/ws-params-factory.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/microservices/client/client-kafka.ts:128 — `(options && options.parser) || undefined` appears character-identically in 2 files — packages/microservices/client/client-kafka.ts, packages/microservices/server/server-kafka.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/microservices/client/client-kafka.ts:550 — `(options && options.serializer) || new KafkaRequestSerializer()` appears character-identically in 2 files — packages/microservices/client/client-kafka.ts, packages/microservices/server/server-kafka.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/microservices/client/client-kafka.ts:121 — `clientOptions.brokers || [KAFKA_DEFAULT_BROKER]` appears character-identically in 2 files — packages/microservices/client/client-kafka.ts, packages/microservices/server/server-kafka.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/microservices/client/client-kafka.ts:126 — `clientOptions.clientId || KAFKA_DEFAULT_CLIENT` appears character-identically in 2 files — packages/microservices/client/client-kafka.ts, packages/microservices/server/server-kafka.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/microservices/client/client-kafka.ts:127 — `consumerOptions.groupId || KAFKA_DEFAULT_GROUP` appears character-identically in 2 files — packages/microservices/client/client-kafka.ts, packages/microservices/server/server-kafka.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/core/exceptions/external-exception-filter-context.ts:56 — `contextId === STATIC_CONTEXT && !inquirerId` appears character-identically in 6 files — packages/core/exceptions/external-exception-filter-context.ts, packages/core/guards/guards-context-creator.ts, packages/core/interceptors/interceptors-context-creator.ts, packages/core/pipes/pipes-context-creator.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/core/helpers/external-context-creator.ts:180 — `fnCanActivate && (await fnCanActivate(args))` appears character-identically in 3 files — packages/core/helpers/external-context-creator.ts, packages/microservices/context/rpc-context-creator.ts, packages/websockets/context/ws-context-creator.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/common/decorators/core/use-guards.decorator.ts:37 — `guard && (isFunction(guard) || isFunction(guard.canActivate))` appears character-identically in 2 files — packages/common/decorators/core/use-guards.decorator.ts, packages/core/guards/guards-context-creator.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/platform-socket.io/utils/merge-map-bounded.util.ts:44 — `head && active < concurrent && !subscriber.closed` appears character-identically in 3 files — packages/platform-socket.io/utils/merge-map-bounded.util.ts, packages/platform-ws/utils/merge-map-bounded.util.ts, packages/websockets/utils/merge-map-bounded.util.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/common/decorators/core/use-interceptors.decorator.ts:39 — `interceptor && (isFunction(interceptor) || isFunction(interceptor.intercept))` appears character-identically in 2 files — packages/common/decorators/core/use-interceptors.decorator.ts, packages/core/interceptors/interceptors-context-creator.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/platform-express/adapters/express-adapter.ts:700 — `isHttpError(error) && error.statusCode < 500` appears character-identically in 2 files — packages/platform-express/adapters/express-adapter.ts, REDACTED. 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/core/exceptions/base-exception-filter.ts:82 — `isObject(err) && !!(err as Error).message` appears character-identically in 2 files — packages/core/exceptions/base-exception-filter.ts, packages/websockets/exceptions/base-ws-exception-filter.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/platform-express/adapters/express-adapter.ts:778 — `isObject(err) && err instanceof Error && typeof (err as any).expose === 'boolean' && typeof (err as any).statusCode === 'number' && (err as …` appears character-identically in 2 files — packages/platform-express/adapters/express-adapter.ts, REDACTED. 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/microservices/client/client-mqtt.ts:360 — `isObject(packet?.data) && packet.data instanceof MqttRecord` appears character-identically in 2 files — packages/microservices/client/client-mqtt.ts, packages/microservices/serializers/mqtt-record.serializer.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/microservices/exceptions/rpc-exception.ts:16 — `isObject(this.error) && isString((this.error as Record<string, any>).message)` appears character-identically in 2 files — packages/microservices/exceptions/rpc-exception.ts, packages/websockets/errors/ws-exception.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/microservices/decorators/event-pattern.decorator.ts:64 — `isObject(transportOrExtras) && isNil(maybeExtras)` appears character-identically in 2 files — packages/microservices/decorators/event-pattern.decorator.ts, packages/microservices/decorators/message-pattern.decorator.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/core/router/router-execution-context.ts:647 — `isObservable(value) && handlerObservable$.next()` appears character-identically in 2 files — packages/core/router/router-execution-context.ts, packages/microservices/context/rpc-context-creator.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/platform-express/multer/multer/multer.utils.ts:57 — `isPlainObject(options.limits) && isPlainObject(localOptions.limits)` appears character-identically in 2 files — packages/platform-express/multer/multer/multer.utils.ts, packages/platform-fastify/multipart/multipart/multipart.utils.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/platform-socket.io/utils/merge-map-bounded.util.ts:65 — `isSourceComplete && !head && active === 0` appears character-identically in 3 files — packages/platform-socket.io/utils/merge-map-bounded.util.ts, packages/platform-ws/utils/merge-map-bounded.util.ts, packages/websockets/utils/merge-map-bounded.util.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 · ×22

Deprecated: @npmcli/move-file REDACTED:3509 — @npmcli/move-file 1.1.2 is resolved in REDACTED and is marked deprecated by its publisher: "This functionality has been moved to @npmcli/fs". 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:3524 — 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: rimraf REDACTED:3559 — rimraf 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:7651 — 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: glob REDACTED:11330 — 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: gulp-util REDACTED:11564 — gulp-util 3.0.8 is resolved in REDACTED and is marked deprecated by its publisher: "gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: fsevents REDACTED:12009 — fsevents 1.2.13 is resolved in REDACTED and is marked deprecated by its publisher: "Upgrade to fsevents v2 to mitigate potential security issues". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: har-validator REDACTED:12270 — har-validator 5.1.5 is resolved in REDACTED and is marked deprecated by its publisher: "this library is no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: inflight REDACTED:12831 — 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: glob REDACTED:13916 — 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: rimraf REDACTED:14115 — rimraf 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: tar REDACTED:14160 — tar 6.2.1 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of tar 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: lodash.template REDACTED:15099 — lodash.template 3.6.2 is resolved in REDACTED and is marked deprecated by its publisher: "This package is deprecated. Use https://socket.dev/npm/package/eta instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: request REDACTED:18418 — request 2.88.2 is resolved in REDACTED and is marked deprecated by its publisher: "request has been deprecated, see https://github.com/request/request/issues/3142". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: uuid REDACTED:18499 — uuid 3.4.0 is resolved in REDACTED and is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: resolve-url REDACTED:18600 — resolve-url 0.2.1 is resolved in REDACTED and is marked deprecated by its publisher: "https://github.com/lydell/resolve-url#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: rimraf REDACTED:18667 — rimraf 2.7.1 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:18681 — 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: source-map-resolve REDACTED:19365 — source-map-resolve 0.5.3 is resolved in REDACTED and is marked deprecated by its publisher: "See https://github.com/lydell/source-map-resolve#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: source-map-resolve REDACTED:19559 — source-map-resolve 0.6.0 is resolved in REDACTED and is marked deprecated by its publisher: "See https://github.com/lydell/source-map-resolve#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: source-map-url REDACTED:19571 — source-map-url 0.4.1 is resolved in REDACTED and is marked deprecated by its publisher: "See https://github.com/lydell/source-map-url#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: urix REDACTED:21307 — urix 0.1.0 is resolved in REDACTED and is marked deprecated by its publisher: "Please see https://github.com/lydell/urix#deprecated". 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 · ×20

Console output used as the logging channel integration/repl/src/repl.ts:8 — `integration/repl/src/repl.ts` reports through `console.*` at line 8 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 integration/nest-application/listen/src/fastify-fd-main.js:28 — `integration/nest-application/listen/src/fastify-fd-main.js` reports through `console.*` at line 28 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 integration/inspector/src/core/interceptors/logging.interceptor.ts:13 — `integration/inspector/src/core/interceptors/logging.interceptor.ts` reports through `console.*` at line 13 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 integration/inspector/src/core/interceptors/logging.interceptor.ts:18 — `integration/inspector/src/core/interceptors/logging.interceptor.ts` reports through `console.*` at line 18 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 integration/inspector/src/common/middleware/logger.middleware.ts:6 — `integration/inspector/src/common/middleware/logger.middleware.ts` reports through `console.*` at line 6 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 integration/discovery/src/my-webhook/cleanup.webhook.ts:7 — `integration/discovery/src/my-webhook/cleanup.webhook.ts` reports through `console.*` at line 7 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 integration/discovery/src/my-webhook/flush.webhook.ts:7 — `integration/discovery/src/my-webhook/flush.webhook.ts` reports through `console.*` at line 7 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 integration/auto-mock/src/foo.service.ts:6 — `integration/auto-mock/src/foo.service.ts` reports through `console.*` at line 6 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/common/services/console-logger.service.ts:462 — `packages/common/services/console-logger.service.ts` reports through `console.*` at line 462 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/common/services/console-logger.service.ts:464 — `packages/common/services/console-logger.service.ts` reports through `console.*` at line 464 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/common/services/console-logger.service.ts:490 — `packages/common/services/console-logger.service.ts` reports through `console.*` at line 490 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/common/services/console-logger.service.ts:492 — `packages/common/services/console-logger.service.ts` reports through `console.*` at line 492 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/common/services/console-logger.service.ts:728 — `packages/common/services/console-logger.service.ts` reports through `console.*` at line 728 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/common/decorators/http/route-params.decorator.ts:224 — `packages/common/decorators/http/route-params.decorator.ts` reports through `console.*` at line 224 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/common/decorators/http/route-params.decorator.ts:241 — `packages/common/decorators/http/route-params.decorator.ts` reports through `console.*` at line 241 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/common/decorators/http/route-params.decorator.ts:261 — `packages/common/decorators/http/route-params.decorator.ts` reports through `console.*` at line 261 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/common/decorators/http/route-params.decorator.ts:281 — `packages/common/decorators/http/route-params.decorator.ts` reports through `console.*` at line 281 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/common/decorators/http/route-params.decorator.ts:307 — `packages/common/decorators/http/route-params.decorator.ts` reports through `console.*` at line 307 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/common/decorators/http/route-params.decorator.ts:324 — `packages/common/decorators/http/route-params.decorator.ts` reports through `console.*` at line 324 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/common/decorators/http/route-params.decorator.ts:343 — `packages/common/decorators/http/route-params.decorator.ts` reports through `console.*` at line 343 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.

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

No app-layer HTTPS enforcement detected integration/graphql-code-first/src/main.ts:8 — `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.)
No app-layer HTTPS enforcement detected integration/graphql-schema-first/src/main.ts:6 — `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.)
No app-layer HTTPS enforcement detected integration/hooks/src/enable-shutdown-hooks-main.ts:41 — `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.)
No app-layer HTTPS enforcement detected integration/lazy-modules/src/main.ts:6 — `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.)
No app-layer HTTPS enforcement detected integration/microservices/src/main.ts:6 — `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.)
No app-layer HTTPS enforcement detected integration/mongoose/src/main.ts:6 — `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.)
No app-layer HTTPS enforcement detected integration/nest-application/listen/src/fastify-fd-main.js:27 — `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.)
No app-layer HTTPS enforcement detected integration/route-conflict/src/main.ts:6 — `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.)
No app-layer HTTPS enforcement detected integration/scopes/src/main.ts:6 — `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.)
No app-layer HTTPS enforcement detected integration/typeorm/src/main.ts:6 — `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.)
No app-layer HTTPS enforcement detected integration/versioning/src/main.ts:12 — `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.)
No app-layer HTTPS enforcement detected REDACTED:172 — `httpServer.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.)

D34 · Knowledge Freshness · Orphaned file · ×10

Orphaned file tools/benchmarks/src/main.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/common/decorators/core/controller.decorator.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/common/interfaces/external/https-options.interface.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file integration/microservices/src/grpc/grpc.controller.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/common/interfaces/modules/provider.interface.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file integration/microservices/src/tcp-tls/app.controller.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/microservices/exceptions/grpc-exception.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/platform-express/interfaces/serve-static-options.interface.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/common/interfaces/external/class-transform-options.interface.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/common/pipes/file/max-file-size.validator.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.

IC1 · Incompleteness & stubs · Disabled test · ×6

Disabled test integration/cors/e2e/fastify.spec.ts:10 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test integration/hello-world/e2e/fastify-multiple.spec.ts:2 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test integration/microservices/e2e/concurrent-kafka.spec.ts:10 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test integration/microservices/e2e/sum-kafka.spec.ts:15 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test integration/send-files/e2e/express.spec.ts:99 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test integration/send-files/e2e/fastify.spec.ts:52 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.

AX6 · Interface segregation · Fat interface · ×3

Fat interface: HttpServer (36 required operations) packages/common/interfaces/http/http-server.interface.ts:190 — `HttpServer` declares 36 required operations: `use`, `use`, `get`, `get`, `post`, `post`, `head`, `head`, `delete`, `delete`, `put`, `put`, `patch`, `patch`, `all`, `all`, `options`, `options`, `listen`, `listen`, `reply`, `status`, `end`, `render`, `redirect`, `isHeadersSent`, `setHeader`, `createMiddlewareFactory`, `getInstance`, `registerParserMiddleware`, `enableCors`, `getHttpServer`, `initHttpServer`, `close`, `getType`, `applyVersionFilter`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. Those 36 declarations carry 26 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 26 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: INestApplicationContext (16 required operations) packages/common/interfaces/nest-application-context.interface.ts:29 — `INestApplicationContext` declares 16 required operations under just 9 distinct name(s): `select`, `get`, `get`, `get`, `get`, `resolve`, `resolve`, `resolve`, `resolve`, `resolve`, `registerRequestByContextId`, `close`, `useLogger`, `flushLogs`, `enableShutdownHooks`, `init`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 16 separate responsibilities: a caller binds to 9 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 16 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
Fat interface: INestApplication (20 required operations) packages/common/interfaces/nest-application.interface.ts:22 — `INestApplication` declares 20 required operations: `use`, `enableCors`, `enableCsrfProtection`, `useSecurityHeaders`, `enableVersioning`, `listen`, `listen`, `getUrl`, `setGlobalPrefix`, `useWebSocketAdapter`, `connectMicroservice`, `getMicroservices`, `getHttpServer`, `getHttpAdapter`, `startAllMicroservices`, `useGlobalFilters`, `useGlobalPipes`, `useGlobalInterceptors`, `useGlobalGuards`, `close`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. Those 20 declarations carry 19 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 19 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.

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

Silent fallback default in catch packages/core/helpers/optional-require.ts:7 — `optionalRequire` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/core/middleware/route-info-path-extractor.ts:107 — `extractExcludedRoutesCoveredBy` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/microservices/helpers/kafka-reply-partition-assigner.ts:230 — `decodePreviousAssignment` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.

C2 · Access Controls · No named authorization policies · ×1

No named authorization policies — Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.

D16 · Bus Factor · Off-boarding risk · ×1

Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 17 significant file(s) lose their only recent owner: packages/core/helpers/external-context-creator.ts, packages/microservices/client/client-proxy.ts, packages/common/serializer/standard-schema-serializer.interceptor.ts, packages/microservices/external/mqtt-options.interface.ts, packages/platform-fastify/multipart/multipart/append-field.util.ts, packages/platform-fastify/multipart/storage/disk.storage.ts, packages/common/serializer/class-serializer.interceptor.ts, packages/core/interceptors/interceptors-context-creator.ts (+9 more). Pair on, review, or document these before any departure.

D16 · Bus Factor · Further sole-owners (lower concentration) · ×1

Further sole-owners (lower concentration) — 4 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (21 single-owned of 186 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 186 of the 1103 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)), anonymized user #3 (1 file(s)), anonymized user #4 (1 file(s)), anonymized user #5 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/microservices/external/redis.interface.ts, packages/core/injector/instance-loader.ts, packages/core/injector/lazy-module-loader/lazy-module-loader.ts, packages/common/utils/http-error-by-code.util.ts.

D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1

Projects may be oversized for their cohesion — 3 of 10 project(s) overshoot their size bounds, lowering Project Cohesion to 4.0/10. The most over is `packages/core` (18534 LoC, 224 module-visible types across 34 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.

D28 · Secrets (history) · Rotate the exposed credentials · ×1

REDACTED

D30 · Dependency Vulnerabilities · Low CVE · ×1

REDACTED

D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1

Orphaned files with no living knowledge — 10 of 187 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 187 of the 1103 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: tools/benchmarks/src/main.ts, packages/common/decorators/core/controller.decorator.ts, packages/common/interfaces/external/https-options.interface.ts, integration/microservices/src/grpc/grpc.controller.ts, packages/common/interfaces/modules/provider.interface.ts, integration/microservices/src/tcp-tls/app.controller.ts, packages/microservices/exceptions/grpc-exception.ts, packages/platform-express/interfaces/serve-static-options.interface.ts (and 2 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.

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.

P4 · Deployment & Rollback · No rollback/health safety · ×1

No rollback/health safety — Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.

P6 · Release Hygiene · No changelog · ×1

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

R8 · Dependency Hygiene · Type-only dependency '@standard-schema/spec' in production deps · ×1

Type-only dependency '@standard-schema/spec' in production deps packages/common/decorators/http/create-route-param-metadata.decorator.ts:1 — Every import is type-only — move it to devDependencies.

R8 · Dependency Hygiene · Test-only dependency 'ws' in production deps · ×1

Test-only dependency 'ws' in production deps packages/platform-ws/package.json:30 — Only test files import it (first: packages/platform-ws/test/ws-adapter-create.spec.ts:2) — move it to devDependencies.

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

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

Null assertions (`!`) reduce the strict null checking score — ~4.8 `!` null assertions per 1k TypeScript source lines — 337 assertion(s) across the 69527 source line(s) of the 1084 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/core/injector/injector.ts (18), packages/core/injector/instance-wrapper.ts (15), packages/core/scanner.ts (14). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

Minor — 117 finding(s)

D10 · Test Quality · Skipped (documented) · ×115

Skipped (documented): (unnamed test) packages/websockets/test/gateway-metadata-explorer.spec.ts:26 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/websockets/test/decorators/ack.decorator.spec.ts:7 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/websockets/test/decorators/connected-socket.decorator.spec.ts:6 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/websockets/test/decorators/message-body.decorator.spec.ts:7 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/websockets/test/decorators/message-body.decorator.spec.ts:60 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/websockets/test/decorators/message-body.decorator.spec.ts:90 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/websockets/test/decorators/message-body.decorator.spec.ts:104 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/platform-fastify/test/decorators/router-config.decorator.spec.ts:9 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/platform-fastify/test/decorators/router-constraints.decorator.spec.ts:10 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/platform-fastify/test/decorators/router-constraints.decorator.spec.ts:27 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/platform-fastify/test/decorators/router-schema.decorator.spec.ts:9 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/microservices/test/decorators/ctx.decorator.spec.ts:6 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/microservices/test/decorators/event-pattern.decorator.spec.ts:16 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/microservices/test/decorators/event-pattern.decorator.spec.ts:60 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/microservices/test/decorators/event-pattern.decorator.spec.ts:64 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/microservices/test/decorators/event-pattern.decorator.spec.ts:68 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/microservices/test/decorators/event-pattern.decorator.spec.ts:72 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/microservices/test/decorators/event-pattern.decorator.spec.ts:84 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/microservices/test/decorators/message-pattern.decorator.spec.ts:20 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/microservices/test/decorators/message-pattern.decorator.spec.ts:42 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/microservices/test/decorators/message-pattern.decorator.spec.ts:46 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/microservices/test/decorators/message-pattern.decorator.spec.ts:50 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/microservices/test/decorators/message-pattern.decorator.spec.ts:54 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/microservices/test/decorators/message-pattern.decorator.spec.ts:66 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/microservices/test/decorators/message-pattern.decorator.spec.ts:167 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
+ 90 more in this group — see findings.md.

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

Outdated (npm): fast-json-stringify — fast-json-stringify is pinned at 7.1.2; registry.npmjs.org publishes 7.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): path-to-regexp — path-to-regexp is pinned at 8.4.2; registry.npmjs.org publishes 9.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.

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-84904c2ffa4747ee96654684548ab4c1/history.json --exit-code 0 --source .	1	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-84904c2ffa4747ee96654684548ab4c1/tree.json --exit-code 0 --source .	1	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 --exclude .arrow --exclude .avro --exclude .csv --exclude .dat --exclude .db --exclude .feather --exclude .geojson --exclude .h5 --exclude .hdf5 --exclude .jsonl --exclude .log --exclude .ndjson --exclude .npy --exclude .npz --exclude .orc --exclude .parquet --exclude .pickle --exclude .pkl --exclude .psv --exclude .sqlite --exclude .sqlite3 --exclude .tfrecord --exclude .tsv --exclude .txt .	18	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	27	artifacts/raw/trivy-fs.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	8	artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 2 file(s) — `packages/common/services/log-levels.constant.ts`, `packages/core/helpers/router-method-factory.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—
D43 · Malicious Dependencies	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	artifacts/raw/trivy-fs.json

Run 01a177f4-cfd6-7bc7-9213-25c4212e68fc · 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 · 65% · Adequate ·

At a glance — Architecture · 55% · Adequate · gated by D5, R9 ·

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

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

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

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

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

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts