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

nestjs/nest

Measured 14 November 2026, 09:17 UTC, at code version 4410584

Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureRepoBuildError).

Test reliability is not measured: The JS/TS suite's lockfile was refused.

Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.

CAI score 50out of 100 At risk Up 2 since the last survey

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

A medium codebase: 85,590 lines of product code in 11 projects, tests not counted · Estimated rebuild effort: about 1.5 person-years · Weakest lens: Production Readiness, 36

Findings by how serious they are

74 critical 600 serious 507 minor

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

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 09:17 UTC

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

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

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

77of 77 dimensions measured by tools.
1129of 1181 findings point to an exact file and line, so you can open each one in the code. The other 52 concern the repository as a whole, such as missing documentation.
77dimensions across 7 lenses, read from 85,590 lines of product code in 11 projects.
Chapters

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 50 out of 100, which the At risk rating leaves unchanged.

Production Readiness, at 36, 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 10 points. Making the three tests that check nothing check their results comes next, worth about 9 points. Raising Production Readiness to 70 would lift the score to about 61.

Fourteen 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 85,590 lines, about €210,000 to rebuild.

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 36 · counts for 46%Architecture 56 · counts for 25%Code Health 58 · counts for 14%Maturity 67 · counts for 8%Security and Compliance 73 · counts for 4%Performance 85 · counts for 2%Domain Modelling 100 · counts for 1%

If Production Readiness rose from 36 to 70, the lowest score rated Strong, the score would rise from 50 to about 61.

Code composition: what the lines of code are
Product code 38%Tests 62%
New since the last survey: 252 findings

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

  • Cyclomatic Complexity · redact.util.createRedactor.<returned closure> (cyclomatic 42) packages/common/services/utils/redact.util.ts
  • Cyclomatic Complexity · ServerGrpc.writeObservableToGrpc (cyclomatic 40) packages/microservices/server/server-grpc.ts
  • Cyclomatic Complexity · NodeRouter.dispatch::next (cyclomatic 38) packages/platform-node/router/node-router.ts
  • Cyclomatic Complexity · NodeAdapter.applyVersionFilter (cyclomatic 31) packages/platform-node/adapters/node-adapter.ts
  • Cyclomatic Complexity · RouteTable.find (cyclomatic 30) packages/platform-node/router/route-table.ts
  • Cyclomatic Complexity · body-parser.createReader.reader (cyclomatic 28) packages/platform-node/body-parser/body-parser.ts
  • Cyclomatic Complexity · body-parser.urlencoded (cyclomatic 28) packages/platform-node/body-parser/body-parser.ts
  • Cyclomatic Complexity · NodeAdapter.reply (cyclomatic 25) packages/platform-node/adapters/node-adapter.ts
  • Cyclomatic Complexity · utils.isMiddlewareRouteExcluded (cyclomatic 23) packages/core/middleware/utils.ts
  • Cyclomatic Complexity · create-route-param-metadata.decorator.createParamDecorator.<returned closure>.<returned closure> (cyclomatic 22) packages/common/decorators/http/create-route-param-metadata.decorator.ts
  • Cyclomatic Complexity · NodeResponse.sendFile (cyclomatic 21) packages/platform-node/adapters/node-request.ts
  • Cyclomatic Complexity · RouteTable.add (cyclomatic 21) packages/platform-node/router/route-table.ts
  • Cyclomatic Complexity · route-table.toFindMyWayPath (cyclomatic 21) packages/platform-node/router/route-table.ts
  • Cyclomatic Complexity · ConsoleLogger.stringifyJsonLogObject (cyclomatic 20) packages/common/services/console-logger.service.ts
  • Cyclomatic Complexity · node-request.preferredRedirectType (cyclomatic 18) packages/platform-node/adapters/node-request.ts
  • Cyclomatic Complexity · RouteTable.lookup (cyclomatic 18) packages/platform-node/router/route-table.ts
  • Cyclomatic Complexity · ValidationPipe.findNestedBinaryValues (cyclomatic 17) packages/common/pipes/validation.pipe.ts
  • Cyclomatic Complexity · Injector.resolveConstructorParams (cyclomatic 17) packages/core/injector/injector.ts
  • Cyclomatic Complexity · multipart.parser.storeFile (cyclomatic 17) packages/platform-fastify/multipart/multipart/multipart.parser.ts
  • Cyclomatic Complexity · RouterExecutionContext.createHandleResponseFn (cyclomatic 16) packages/core/router/router-execution-context.ts
  • Cyclomatic Complexity · ClientNats.mergeHeaders (cyclomatic 16) packages/microservices/client/client-nats.ts
  • Cognitive Complexity · NodeRouter.dispatch::next (cognitive 77) packages/platform-node/router/node-router.ts
  • Cognitive Complexity · NodeAdapter.applyVersionFilter (cognitive 49) packages/platform-node/adapters/node-adapter.ts
  • Cognitive Complexity · RouteTable.find (cognitive 43) packages/platform-node/router/route-table.ts
  • Cognitive Complexity · NodeAdapter.reply (cognitive 33) packages/platform-node/adapters/node-adapter.ts
  • Cognitive Complexity · route-table.toFindMyWayPath (cognitive 32) packages/platform-node/router/route-table.ts
  • Cognitive Complexity · JsonSocket.processBufferedPackets (cognitive 30) packages/microservices/helpers/json-socket.ts
  • Cognitive Complexity · body-parser.urlencoded (cognitive 28) packages/platform-node/body-parser/body-parser.ts
  • Cognitive Complexity · RouteTable.add (cognitive 25) packages/platform-node/router/route-table.ts
  • Cognitive Complexity · NodeResponse.sendFile (cognitive 24) packages/platform-node/adapters/node-request.ts
  • Cognitive Complexity · node-request.preferredRedirectType (cognitive 23) packages/platform-node/adapters/node-request.ts
  • Cognitive Complexity · body-parser.createReader.reader (cognitive 23) packages/platform-node/body-parser/body-parser.ts
  • Cognitive Complexity · redact.util.createRedactor.<returned closure>::redactObject (cognitive 21) packages/common/services/utils/redact.util.ts
  • Cognitive Complexity · utils.isMiddlewareRouteExcluded (cognitive 21) packages/core/middleware/utils.ts
  • Cognitive Complexity · RouteTable.lookup (cognitive 21) packages/platform-node/router/route-table.ts
  • Cognitive Complexity · ConsoleLogger.stringifyJsonLogObject (cognitive 20) packages/common/services/console-logger.service.ts
  • Cognitive Complexity · RouterResponseController.sse (cognitive 20) packages/core/router/router-response-controller.ts
  • Cognitive Complexity · ClientNats.mergeHeaders (cognitive 20) packages/microservices/client/client-nats.ts
  • Cognitive Complexity · WebSocketsController.createRequestScopedEventHandler (cognitive 20) packages/websockets/web-sockets-controller.ts
  • Cognitive Complexity · create-route-param-metadata.decorator.createParamDecorator.<returned closure>.<returned closure> (cognitive 19) packages/common/decorators/http/create-route-param-metadata.decorator.ts
  • Cognitive Complexity · NodeRouter.use (cognitive 19) packages/platform-node/router/node-router.ts
  • Cognitive Complexity · utils.getRawPrefixEnd (cognitive 18) packages/platform-node/router/utils.ts
  • Cognitive Complexity · close-array-gaps.util.closeArrayGaps (cognitive 17) packages/common/utils/close-array-gaps.util.ts
  • Cognitive Complexity · Injector.resolveConstructorParams (cognitive 17) packages/core/injector/injector.ts
  • Cognitive Complexity · RouterExecutionContext.createHandleResponseFn (cognitive 17) packages/core/router/router-execution-context.ts
  • Cognitive Complexity · NestApplication.registerRouter (cognitive 17) packages/core/nest-application.ts
  • Cognitive Complexity · RouteTable.lookupFallback (cognitive 17) packages/platform-node/router/route-table.ts
  • Cognitive Complexity · WsAdapter.ensureHttpServerExists (cognitive 17) REDACTED
  • Cognitive Complexity · ValidationPipe.findNestedBinaryValues (cognitive 16) packages/common/pipes/validation.pipe.ts
  • Cognitive Complexity · Server.send (cognitive 16) packages/microservices/server/server.ts
  • Cognitive Complexity · ServerRMQ.matchRmqPattern (cognitive 16) packages/microservices/server/server-rmq.ts
  • Cognitive Complexity · fastify-adapter.hasTextDecodedByRouter (cognitive 16) REDACTED
  • Cognitive Complexity · utils.hasDecodedText (cognitive 16) packages/platform-node/router/utils.ts
  • Cognitive Complexity · ViewRenderer.resolveFile (cognitive 16) packages/platform-node/views/view-renderer.ts
  • God Classes · TooManyMethods: NodeAdapter packages/platform-node/adapters/node-adapter.ts
  • God Classes · ClassTooLong: NodeAdapter packages/platform-node/adapters/node-adapter.ts
  • God Classes · FileTooLong: adapters/node-adapter.ts packages/platform-node/adapters/node-adapter.ts
  • God Classes · FunctionTooLong: redact.util.createRedactor.<returned closure> packages/common/services/utils/redact.util.ts
  • God Classes · MethodTooLong: NodeRouter.dispatch packages/platform-node/router/node-router.ts
  • God Classes · TooManyMethods: ServerGrpc packages/microservices/server/server-grpc.ts
  • God Classes · TooManyMethods: Server packages/microservices/server/server.ts
  • God Classes · FunctionTooLong: body-parser.createReader packages/platform-node/body-parser/body-parser.ts
  • God Classes · FileTooLong: router/route-table.ts packages/platform-node/router/route-table.ts
  • God Classes · MethodTooLong: RpcContextCreator.create packages/microservices/context/rpc-context-creator.ts
  • God Classes · ClassTooLong: ClientRMQ packages/microservices/client/client-rmq.ts
  • God Classes · MethodTooLong: ConfigurableModuleBuilder.createConfigurableModuleCls packages/common/module-utils/configurable-module.builder.ts
  • God Classes · FileTooLong: body-parser/body-parser.ts packages/platform-node/body-parser/body-parser.ts
  • God Classes · FunctionTooLong: body-parser.createReader.reader packages/platform-node/body-parser/body-parser.ts
  • God Classes · FileTooLong: adapters/express-adapter.ts packages/platform-express/adapters/express-adapter.ts
  • Test Quality · Skipped test: should allow for the client to end the response and be able to make another integration/send-files/e2e/node.spec.ts
  • Test Quality · No assertions: should end the response for a source that has already ended packages/platform-express/test/adapters/express-adapter.spec.ts
  • Test Quality · No assertions: should keep serving when the filter of a %s connection hook throws integration/websockets/e2e/scoped-connection-hook-error.spec.ts
  • Test Quality · Fixed-sleep synchronisation: should let the requests in flight finish when not enabled packages/platform-node/test/adapters/node-adapter.spec.ts
  • Test Quality · Fixed-sleep synchronisation: should keep serving when the filter of a %s connection hook throws integration/websockets/e2e/scoped-connection-hook-error.spec.ts
  • Test Quality · Fixed-sleep synchronisation: should take no new request while it is closing integration/microservices/e2e/graceful-shutdown.spec.ts
  • Test Quality · Fixed-sleep synchronisation: should return 503 for NEW queued requests on existing connections during shutdown integration/graceful-shutdown/e2e/node.spec.ts
  • Churn × Complexity Hotspots · Hotspot: packages/microservices/server/server-grpc.ts packages/microservices/server/server-grpc.ts
  • Churn × Complexity Hotspots · Hotspot: packages/core/injector/injector.ts packages/core/injector/injector.ts
  • Churn × Complexity Hotspots · Hotspot: packages/platform-node/adapters/node-adapter.ts packages/platform-node/adapters/node-adapter.ts
  • Churn × Complexity Hotspots · Hotspot: packages/core/middleware/utils.ts packages/core/middleware/utils.ts
  • Churn × Complexity Hotspots · Hotspot: packages/platform-node/router/node-router.ts packages/platform-node/router/node-router.ts
  • Churn × Complexity Hotspots · Hotspot: packages/core/router/router-execution-context.ts packages/core/router/router-execution-context.ts
  • Churn × Complexity Hotspots · Hotspot: packages/platform-node/adapters/node-request.ts packages/platform-node/adapters/node-request.ts
  • Churn × Complexity Hotspots · Hotspot: packages/platform-fastify/multipart/multipart/multipart.parser.ts packages/platform-fastify/multipart/multipart/multipart.parser.ts
  • Churn × Complexity Hotspots · Hotspot: packages/common/services/console-logger.service.ts packages/common/services/console-logger.service.ts
  • Churn × Complexity Hotspots · Hotspot: packages/platform-node/router/route-table.ts packages/platform-node/router/route-table.ts
  • Churn × Complexity Hotspots · Hotspot: packages/core/router/router-explorer.ts packages/core/router/router-explorer.ts
  • Churn × Complexity Hotspots · Hotspot: packages/common/services/utils/redact.util.ts packages/common/services/utils/redact.util.ts
  • Churn × Complexity Hotspots · Hotspot: packages/platform-node/body-parser/body-parser.ts packages/platform-node/body-parser/body-parser.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/platform-express/multer/multer/multer.utils.ts packages/platform-express/multer/multer/multer.utils.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/core/injector/instance-wrapper.ts packages/core/injector/instance-wrapper.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/platform-node/multer/multer/multer.utils.ts packages/platform-node/multer/multer/multer.utils.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/platform-fastify/multipart/interfaces/multipart-options.interface.ts packages/platform-fastify/multipart/interfaces/multipart-options.interface.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/core/exceptions/base-exception-filter.ts packages/core/exceptions/base-exception-filter.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/platform-node/views/view-renderer.ts packages/platform-node/views/view-renderer.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/common/pipes/standard-schema-validation.pipe.ts packages/common/pipes/standard-schema-validation.pipe.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/platform-express/multer/interfaces/multer-options.interface.ts packages/platform-express/multer/interfaces/multer-options.interface.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/core/exceptions/base-exception-filter-context.ts packages/core/exceptions/base-exception-filter-context.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/websockets/socket-server-provider.ts packages/websockets/socket-server-provider.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/core/injector/lazy-module-loader/lazy-module-loader.ts packages/core/injector/lazy-module-loader/lazy-module-loader.ts

We compare 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: 247 findings

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

  • Cyclomatic Complexity · redact.util.createRedactor (cyclomatic 46) packages/common/services/utils/redact.util.ts
  • Cyclomatic Complexity · create-route-param-metadata.decorator.createParamDecorator (cyclomatic 22) packages/common/decorators/http/create-route-param-metadata.decorator.ts
  • Cognitive Complexity · redact.util.createRedactor (cognitive 58) packages/common/services/utils/redact.util.ts
  • Cognitive Complexity · JsonSocket.processBuffer (cognitive 29) packages/microservices/helpers/json-socket.ts
  • Cognitive Complexity · create-route-param-metadata.decorator.createParamDecorator (cognitive 19) packages/common/decorators/http/create-route-param-metadata.decorator.ts
  • Cognitive Complexity · samples.executeNpmScriptInSamples (cognitive 18) tools/gulp/tasks/samples.ts
  • Test Quality · 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
  • Test Quality · 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
  • Test Quality · 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
  • Churn × Complexity Hotspots · Hotspot: packages/platform-express/multer/multer/multer.utils.ts packages/platform-express/multer/multer/multer.utils.ts
  • Churn × Complexity Hotspots · Hotspot: packages/core/exceptions/base-exception-filter.ts packages/core/exceptions/base-exception-filter.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/core/injector/injector.ts packages/core/injector/injector.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/microservices/server/server-grpc.ts packages/microservices/server/server-grpc.ts
  • Churn × Complexity Hotspots · Repeated repair: packages/core/middleware/utils.ts packages/core/middleware/utils.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/core/interceptors/interceptors-consumer.ts packages/core/interceptors/interceptors-consumer.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
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Code Duplication · Duplication concentrated across 9 sibling directories (44 clone groups) packages/microservices/context/rpc-context-creator.ts
  • Code Duplication · Duplication concentrated across 7 sibling directories (12 clone groups) packages/core/interceptors/interceptors-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 · Duplicated block (61 lines × 3 locations) packages/core/helpers/external-context-creator.ts
  • Code Duplication · Duplicated block with local edits (61 matched lines × 2 locations) packages/core/helpers/external-context-creator.ts
  • Code Duplication · Duplicated block (61 lines × 2 locations) packages/platform-express/multer/multer.module.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 with local edits (29 matched lines × 2 locations) packages/core/injector/module-ref.ts
  • Code Duplication · Duplicated block (29 lines × 2 locations) packages/microservices/client/client-kafka.ts
  • Code Duplication · Duplicated block (28 lines × 2 locations) packages/core/exceptions/base-exception-filter-context.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
  • Code Duplication · Duplicated block (26 lines × 2 locations) integration/hello-world/src/host-array/host-array.controller.ts
  • Code Duplication · Duplicated block (26 lines × 4 locations) packages/core/exceptions/external-exception-filter-context.ts
  • Code Duplication · Duplicated block (24 lines × 3 locations) integration/inspector/src/dogs/dogs.controller.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/middleware/utils.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 with local edits (21 matched lines × 2 locations) packages/microservices/client/client-nats.ts
  • Code Duplication · Duplicated block (21 lines × 2 locations) packages/microservices/server/server-mqtt.ts
  • Code Duplication · Duplicated block with local edits (21 matched lines × 2 locations) packages/platform-fastify/multipart/multipart/multipart-interceptor.factory.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 × 2 locations) packages/microservices/server/server-mqtt.ts
  • Code Duplication · Duplicated block (20 lines × 2 locations) packages/platform-fastify/multipart/multipart/multipart.parser.ts
  • Code Duplication · Duplicated block (19 lines × 2 locations) packages/core/middleware/routes-mapper.ts
  • Code Duplication · Duplicated block (19 lines × 3 locations) packages/core/middleware/utils.ts
  • Code Duplication · Duplicated block (19 lines × 2 locations) packages/microservices/factories/rpc-params-factory.ts
  • Code Duplication · Duplicated block with local edits (19 matched lines × 2 locations) packages/platform-express/multer/multer/multer.constants.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 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 (17 lines × 2 locations) packages/microservices/client/client-redis.ts
  • Code Duplication · Duplicated block (17 lines × 2 locations) packages/microservices/client/client-tcp.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 (16 lines × 2 locations) packages/core/router/router-execution-context.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/microservices/client/client-rmq.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) packages/platform-express/multer/multer/multer.utils.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) packages/websockets/web-sockets-controller.ts
Rebuild cost: about €210,000 · Estimate
Cost to rebuild€71,000 to €350,000, for 1,177 to 3,733 hours of work, about 1.5 person-years for 1 to 3 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 50. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 85,590 lines of product code
What it is notNot 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: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

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

1
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
Raises the score by about 10 points · Low effort · REDACTED Scanning
2
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 9 points · Low effort · Test Quality
3
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
Raises the score by about 6 points · Medium effort · Dependency Hygiene

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 €210,000 to build again, about 1.5 person-years of work. Its weakest lens is Production Readiness, at 36 (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 10 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.

arch @nestjs/common common @nestjs/core core @nestjs/core->@nestjs/common @nestjs/microservices microservices @nestjs/core->@nestjs/microservices @nestjs/platform-express platform-express @nestjs/core->@nestjs/platform-express @nestjs/websockets websockets @nestjs/core->@nestjs/websockets @nestjs/microservices->@nestjs/common @nestjs/microservices->@nestjs/websockets @nestjs/platform-express->@nestjs/common @nestjs/platform-fastify platform-fastify @nestjs/platform-fastify->@nestjs/common @nestjs/platform-fastify->@nestjs/core @nestjs/platform-node platform-node @nestjs/platform-node->@nestjs/common @nestjs/platform-node->@nestjs/core @nestjs/platform-socket.io io @nestjs/platform-socket.io->@nestjs/common @nestjs/platform-ws platform-ws @nestjs/platform-ws->@nestjs/common @nestjs/platform-ws->@nestjs/websockets @nestjs/testing testing @nestjs/testing->@nestjs/common @nestjs/testing->@nestjs/core @nestjs/testing->@nestjs/microservices @nestjs/testing->@nestjs/platform-express @nestjs/websockets->@nestjs/common @nestjs/websockets->@nestjs/platform-socket.io

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.

542 modules, with 917 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; 502 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_enum2 common.exceptions.http_exception3 common.interfaces.features.arguments-host_interface4 common.interfaces.features.pipe-transform_interface5 common.interfaces.modules.injection-token_interface6 common.interfaces.nest-application-options_interface7 common.interfaces.type_interface8 common.interfaces.version-options_interface9 common.services.logger_service10 core.errors.exceptions.runtime_exception11 microservices.interfaces.microservice-configuration_interface12 microservices.interfaces.packet_interface13 common.interfaces.features.execution-context_interface14 common.interfaces.http.http-server_interface15 common.interfaces.modules.dynamic-module_interface16 common.interfaces.modules.provider_interface17 microservices.client.client-proxy18 microservices.server.server19 platform-express.multer.interfaces.files-upload-module_interface20 websockets.context.ws-context-creator21 common.interfaces.features.nest-interceptor_interface22 core.adapters.http-adapter23 core.injector.container24 core.router.router-execution-context25 core.injector.module26 core.injector.instance-wrapper27 core.application-config28 core.helpers.external-context-creator29 core.injector.injector30 core.inspector.graph-inspector31 core.middleware.middleware-module32 core.nest-application-context33 core.router.router-explorer34 core.scanner35 microservices.context.rpc-context-creator36 websockets.web-sockets-controller37 core.nest-application38 core.router.routes-resolver39 microservices.listeners-controller40 testing.testing-module
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_interface1
14 common.interfaces.http.http-server_interface111
15 common.interfaces.modules.dynamic-module_interface1
16 common.interfaces.modules.provider_interface41
17 microservices.client.client-proxy1
18 microservices.server.server11
19 platform-express.multer.interfaces.files-upload-module_interface1
20 websockets.context.ws-context-creator1
21 common.interfaces.features.nest-interceptor_interface1
22 core.adapters.http-adapter1111
23 core.injector.container111111
24 core.router.router-execution-context111
25 core.injector.module11511
26 core.injector.instance-wrapper2111
27 core.application-config111
28 core.helpers.external-context-creator111
29 core.injector.injector11116
30 core.inspector.graph-inspector111
31 core.middleware.middleware-module11112111
32 core.nest-application-context1111
33 core.router.router-explorer2111112111
34 core.scanner2111111
35 microservices.context.rpc-context-creator11
36 websockets.web-sockets-controller1112111
37 core.nest-application11111111
38 core.router.routes-resolver11111111
39 microservices.listeners-controller1112111
40 testing.testing-module111111111
Uses a module listed above itPart of a loopThe module itself
1 common.enums.request-method_enum2 common.exceptions.http_exception3 common.interfaces.features.arguments-host_interface4 common.interfaces.features.pipe-transform_interface5 common.interfaces.modules.injection-token_interface6 common.interfaces.nest-application-options_interface7 common.interfaces.type_interface8 common.interfaces.version-options_interface9 common.services.logger_service10 core.errors.exceptions.runtime_exception11 microservices.interfaces.microservice-configuration_interface12 microservices.interfaces.packet_interface13 common.interfaces.features.execution-context_interface14 common.interfaces.http.http-server_interface15 common.interfaces.modules.dynamic-module_interface16 common.interfaces.modules.provider_interface17 microservices.client.client-proxy18 microservices.server.server19 platform-express.multer.interfaces.files-upload-module_interface20 websockets.context.ws-context-creator21 common.interfaces.features.nest-interceptor_interface22 core.adapters.http-adapter23 core.injector.container24 core.router.router-execution-context25 core.injector.module26 core.injector.instance-wrapper27 core.application-config28 core.helpers.external-context-creator29 core.injector.injector30 core.inspector.graph-inspector31 core.middleware.middleware-module32 core.nest-application-context33 core.router.router-explorer34 core.scanner35 microservices.context.rpc-context-creator36 websockets.web-sockets-controller37 core.nest-application38 core.router.routes-resolver39 microservices.listeners-controller40 testing.testing-modulecommon.enums.request-method_enum1common.exceptions.http_exception2common.interfaces.features.arguments-host_interface3common.interfaces.features.pipe-transform_interface4common.interfaces.modules.injection-token_interface5common.interfaces.nest-application-options_interface6common.interfaces.type_interface7common.interfaces.version-options_interface8common.services.logger_service9core.errors.exceptions.runtime_exception10microservices.interfaces.microservice-configuration_interface11microservices.interfaces.packet_interface12common.interfaces.features.execution-context_interface13common.interfaces.http.http-server_interface14common.interfaces.modules.dynamic-module_interface15common.interfaces.modules.provider_interface16microservices.client.client-proxy17microservices.server.server18platform-express.multer.interfaces.files-upload-module_interface19websockets.context.ws-context-creator20common.interfaces.features.nest-interceptor_interface21core.adapters.http-adapter22core.injector.container23core.router.router-execution-context24core.injector.module25core.injector.instance-wrapper26core.application-config27core.helpers.external-context-creator28core.injector.injector29core.inspector.graph-inspector30core.middleware.middleware-module31core.nest-application-context32core.router.router-explorer33core.scanner34microservices.context.rpc-context-creator35websockets.web-sockets-controller36core.nest-application37core.router.routes-resolver38microservices.listeners-controller39testing.testing-module4011111411111111111111111111115112111111111111161111111211111112111112111211111111111211111111111111111111112111111111111+502 more modules (most-connected shown)

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

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

At a glance — Maturity · 67% · Adequate · gated by M2 ·

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

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

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

At a glance — Performance · 85% · Strong ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures26High / Critical
A05:2025 — Injection19High / Critical
A02:2025 — Security Misconfiguration8High / Critical
A07:2025 — Authentication Failures3High / Critical

Roadmap

Top priorities: Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED; Resolve the 3 No assertions (empty test) finding(s) in Test Quality — start with router-response-controller.spec.ts (2), fastify-multiple.spec.ts; Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.

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

Do thisHelpsEffortDimension
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.+10.2 ptsLowREDACTED 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.+9.1 ptsLowTest Quality
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+5.6 ptsMediumDependency Hygiene
Resolve the 22 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (22).+5.0 ptsMediumDependency Hygiene
Resolve the 1 Circular dependency finding(s) in Coupling — start with package.json.+2.1 ptsLowCoupling
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion.+1.4 ptsLowProject Cohesion
Break each cycle by extracting the shared piece into a module both sides can import.+2.5 ptsMediumCircular Imports
Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.+2.1 ptsMediumOutbound HTTP resilience

File quality

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

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.8SlopIaC & Container Security: High IaC: REDACTED
REDACTED2.5SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.4MixedREDACTED Scanning: Leaked secret: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
packages/platform-express/adapters/express-adapter.ts5.5MixedCyclomatic Complexity: ExpressAdapter.applyVersionFilter (cyclomatic 33)
packages/core/test/router/router-response-controller.spec.ts6.0MixedTest Quality: No assertions (empty test): should close on socket close
packages/microservices/server/server.ts6.3MixedCognitive Complexity: Server.send (cognitive 16)
REDACTED6.4MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.4MixedStatic Analysis (SAST): Medium: REDACTED
package.json6.4MixedPlatform End-of-Life: End-of-life runtime: Node.js 20
integration/send-files/e2e/express.spec.ts6.7MixedExplicit Debt: TodoComment
integration/send-files/e2e/node.spec.ts6.7MixedExplicit Debt: TodoComment
packages/microservices/test/client/client-grpc.spec.ts6.8MixedTest Quality: No assertions: should create grpcService
tools/gulp/tasks/samples.ts6.9MixedExplicit Debt: TodoComment
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
packages/platform-node/router/route-table.ts7.0MixedCyclomatic Complexity: RouteTable.find (cyclomatic 30)
integration/microservices/e2e/concurrent-kafka.spec.ts7.0MixedTest Quality: No assertions: Create kafka topics/partitions
packages/platform-node/adapters/node-adapter.ts7.0MixedCyclomatic Complexity: NodeAdapter.applyVersionFilter (cyclomatic 31)

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

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

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

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

Could not be resolved — 3

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

This survey 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. All 77 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

Every figure here is one of two 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. 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.

What we checked — 77 dimensions across the health lenses
D1D2D3D5D6D10D12D13D14D15D16D17D19D23D24D26D27D28D29D30D31D34D35D37D43D44AX10AX3AX4AX6C2DM6DM9GD1IC1M1M2M3M4P1P10P2P3P4P5P6P7P8PF3R1R10R11R2R3R4R5R6R7R8R9S1X1X12X14X16X17X18X21X23X24X25X28X29X3X30X4X5

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

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1129 of 1181 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

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

Tools & methods

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

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1d959-006a-7e4a-b0ee-7bf945ea8e52.

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.

  • D21 Naming Consistency — not measured this run — We 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 naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • D21 Naming Consistency — not measured this run — We 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We 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.
  • D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We 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 — We 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. User interface: 5 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. Boot: crawled PUBLIC routes only — add a Playwright storageState (e.g. playwright/.auth/user.json) or a test auth-setup to crawl authenticated screens rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:5432: page.goto: net::ERR_EMPTY_RESPONSE at http://127.0.0.1:5432/ Call log: - navigating to "http://127.0.0.1:5432/", waiting until "load" .
  • DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we 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 — We measured this, but not all of it. What we 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), and artefact counts an order of magnitude off. 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 — We measured this, but not all of it. What we 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. 173 further occurrence(s) are not listed individually; the score already reflects all 213.
  • R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 20 further occurrence(s) are not listed individually; the score already reflects all 60.
  • R3 Large Files — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 9 further occurrence(s) are not listed individually; the score already reflects all 49.
  • R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we 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.
  • SC1 Supply-chain hygiene — not measured this run — We 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. 3 further occurrence(s) are not listed individually; the score already reflects all 43.
  • X10 Duplicated predicate — not measured this run — We 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. 26 further occurrence(s) are not listed individually; the score already reflects all 66.
  • X2 Cancellation propagation — not measured this run — We 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, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X4 Structured logging — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 1 further occurrence(s) are not listed individually; the score already reflects all 41.

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

We assess the repository exactly as committed, and only the repository. By design we do 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.
  • 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.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • 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.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • 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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • 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 Complexity6.9 / 10Adequate✓ Tool-verified

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

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

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

35 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was redact.util.createRedactor.<returned closure> at 42. A further 3 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. 3 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/platform-node/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.<returned closure> (cyclomatic 42)packages/common/services/utils/redact.util.ts:67
ServerGrpc.writeObservableToGrpc (cyclomatic 40)packages/microservices/server/server-grpc.ts:503
NodeRouter.dispatch::next (cyclomatic 38)packages/platform-node/router/node-router.ts:527
RouterResponseController.sse (cyclomatic 36)packages/core/router/router-response-controller.ts:465
ExpressAdapter.applyVersionFilter (cyclomatic 33)packages/platform-express/adapters/express-adapter.ts:550

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

What to do

  1. Bring the 35 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with redact.util.createRedactor.<returned closure> (cyclomatic 42), ServerGrpc.writeObservableToGrpc (cyclomatic 40), NodeRouter.dispatch::next (cyclomatic 38). — 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 35 together lifts Cyclomatic Complexity from 6.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D2 · Cognitive Complexity6.3 / 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.3 / 10 · rule-coverage 100% · ceiling Prevented

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

ExpressAdapter.applyVersionFilter::handlerForMediaTypeVersioning (cognitive 17) · ×2packages/platform-express/adapters/express-adapter.ts:619
ParseArrayPipe.transform (cognitive 78)packages/common/pipes/parse-array.pipe.ts:100
NodeRouter.dispatch::next (cognitive 77)packages/platform-node/router/node-router.ts:527
ServerGrpc.writeObservableToGrpc (cognitive 53)packages/microservices/server/server-grpc.ts:503
NodeAdapter.applyVersionFilter (cognitive 49)packages/platform-node/adapters/node-adapter.ts:715

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

What to do

  1. Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with ParseArrayPipe.transform (cognitive 78), NodeRouter.dispatch::next (cognitive 77). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 6.3 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

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

47 god class(es) detected.

TooManyMethods: AbstractHttpAdapter · ×15packages/core/adapters/http-adapter.ts:60
ClassTooLong: Injector · ×12packages/core/injector/injector.ts:124
FileTooLong: injector/injector.ts · ×12packages/core/injector/injector.ts
FunctionTooLong: redact.util.createRedactor · ×4packages/common/services/utils/redact.util.ts:33
MethodTooLong: NodeRouter.dispatch · ×4packages/platform-node/router/node-router.ts:497

What to do

  1. Resolve the 15 TooManyMethods finding(s) in God Classes — start with http-adapter.ts, REDACTED, injector.ts. — One of this dimension's main actionable groups (15 warning-level).
  2. Resolve the 12 ClassTooLong finding(s) in God Classes — start with injector.ts, REDACTED, node-adapter.ts. — One of this dimension's main actionable groups (12 warning-level).
  3. Resolve the 12 FileTooLong finding(s) in God Classes — start with injector.ts, REDACTED, kafka.interface.ts. — One of this dimension's main actionable groups (12 warning-level).

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

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

10 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:57

What to do

  1. Resolve the 1 Circular dependency finding(s) in Coupling — start with package.json. — One of this dimension's main actionable groups (1 issue-level).

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

D6 · Cohesion (LCOM4)9.7 / 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.7 / 10 · rule-coverage 100% · ceiling Verified

4 of 140 classes have LCOM4 above 3.

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

What to do

  1. 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).

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

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

125 skipped (122 with a documented reason), 16 zero-assertion, 6 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 9051 tests.

No assertions (empty test): should close on socket close · ×3packages/core/test/router/router-response-controller.spec.ts:1137
No assertions: should initialize and close without error · ×13packages/testing/test/testing-module.spec.ts:185
Fixed-sleep synchronisation: should let the requests in flight finish when not enabled · ×6packages/platform-node/test/adapters/node-adapter.spec.ts:3034
Skipped test: should allow for the client to end the response and be able to make another · ×3integration/send-files/e2e/express.spec.ts:108
Mock-dominated test: should call "decorateWithNamespace" and not call "createSocketServer" · ×171packages/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

  1. 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).
  2. Resolve the 13 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 (13 warning-level).
  3. Resolve the 6 Fixed-sleep synchronisation finding(s) in Test Quality — start with node-adapter.spec.ts, scoped-connection-hook-error.spec.ts, graceful-shutdown.spec.ts. — One of this dimension's main actionable groups (6 warning-level).

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

D12 · Dependency Hygiene8.8 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

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

13 outdated direct production npm dependency(ies) of 46 graded, 0 pinning defect(s), across 55 package.json (11 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:3322
Outdated (npm): @fastify/cors · ×13

What to do

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

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

D13 · 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

  1. Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

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

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

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

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

0 of 174 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 174 package(s) this repository's committed lockfile installs for a consumer — its 57 production, optional and peer dependency(ies), across 11 product package.json manifest(s), and everything those install in turn. Its 715 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under MIT, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

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

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

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

Top hotspots: REDACTED (57×24=1368); packages/microservices/server/server-grpc.ts (22×40=880); packages/core/router/router-response-controller.ts (24×36=864) Repeated repair below the complexity floor: REDACTED (21 of 22 changes were fixes); packages/microservices/server/server-rmq.ts (19 of 20 changes were fixes); packages/websockets/web-sockets-controller.ts (19 of 19 changes were fixes)

Repeated repair: REDACTED · ×83REDACTED:389
Hotspot: REDACTED · ×21REDACTED:842

What to do

  1. Resolve the 83 Repeated repair finding(s) in Churn × Complexity Hotspots — start with multer.utils.ts (2), REDACTED, server-rmq.ts. — One of this dimension's main actionable groups (83 warning-level).
  2. Resolve the 21 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED, server-grpc.ts, router-response-controller.ts. — One of this dimension's main actionable groups (21 warning-level).

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

D16 · Bus Factor8.4 / 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.4 / 10 · rule-coverage 100% · ceiling Documented

35 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/platform-fastify/multipart/multipart/multipart.parser.ts. Counted over 219 of the 1184 production source files in this repository: 964 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

  1. Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
  2. 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.

D17 · Explicit Debt10.0 / 10Stronggated by 5 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

5 deducted task-comment markers across 85362 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 · ×5tools/gulp/tasks/samples.ts:26

What to do

  1. Resolve the 5 TodoComment finding(s) in Explicit Debt — start with samples.ts (3), express.spec.ts, node.spec.ts. — One of this dimension's main actionable groups (5 warning-level).

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

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

2 of 2 documentation facets pass in full. 15 document(s) read across 12 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D23 · Boundary Type-Coupling10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Verified

2 domain type(s) cross context boundaries across 10 contexts; they are measured and withheld (not published, not scored). Contexts: common, core, microservices, platform-express, platform-fastify, platform-node, platform-socket.io, platform-ws, testing, websockets.

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

D24 · Comment Value9.7 9.6 / 10Exemplary✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

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

6 of 2233 judged comments only repeat the code they sit on (0.3 %). 38 comment(s) in another language or script were not judged.

redundant comment · ×6integration/hello-world/e2e/force-console.spec.ts:49
doc comments repeat the names · ×5packages/common/file-stream/interfaces/streamable-options.interface.ts:2

✓ On the Gold path — maintain.

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

D26 · Project Cohesion4.5 / 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.

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

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

Projects may be oversized for their cohesion

What to do

  1. 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.

D27 · Navigability9.3 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

40 % of calls cross a namespace and 6 % go through an interface, but 82 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.

Pass-through layer · ×11integration/inspector/src/request-chain/request-chain.controller.ts:6

✓ On the Gold path — maintain.

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

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
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. 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.

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

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

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

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

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

19 finding(s): 0 critical, 10 high, 9 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 3 file(s) — `integration/scopes/e2e/durable-request-payload.spec.ts` (line 51), `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
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

26 finding(s): 2 critical, 12 high, 11 medium, 1 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 11 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (11). — One of this dimension's main actionable groups (11 issue-level).
  2. 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).
  3. 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.

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
REDACTED

What to do

  1. 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).
  2. 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.

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

10 of 220 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 220 of the 1184 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.

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.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

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

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported 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. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-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

  1. 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.

Frontend & cross-cutting dimensions

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

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

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

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

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

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:57

What to do

  • Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
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:59

What to do

  • Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).
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:218
  • `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.
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. — packages/core/nest-application.ts:684

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.
DM6 · Domain ↔ infrastructure boundary10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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

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

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

IC1 · Incompleteness & stubs6.9 / 10Adequate✓ Tool-verified

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

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

  • `RecipesService` has 3 unfinished members out of 4 declared members (methods and accessors, whether or not each carries a body) — a scaffolded class that was never implemented. — integration/graphql-code-first/src/recipes/recipes.service.ts:7
  • `findOneById` 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:20
  • `findAll` 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:24
  • `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
  • `TestingLogger` has 4 unfinished members out of 5 declared members (methods and accessors, whether or not each carries a body) — a scaffolded class that was never implemented. — packages/testing/services/testing-logger.service.ts:6
  • `log` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — packages/testing/services/testing-logger.service.ts:11
  • `warn` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — packages/testing/services/testing-logger.service.ts:12
  • `debug` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — packages/testing/services/testing-logger.service.ts:13
  • `verbose` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — packages/testing/services/testing-logger.service.ts:14
  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×8) — integration/cors/e2e/fastify.spec.ts:10, integration/hello-world/e2e/fastify-multiple.spec.ts:2, integration/microservices/e2e/concurrent-kafka.spec.ts:10, …
  • `openGate` has an empty body — confirm it's an intentional no-op and not an unfinished method. — integration/http-adapters/src/streaming/streaming.module.ts:48
  • `remove` has an empty body — confirm it's an intentional no-op and not an unfinished method. — integration/http-adapters/src/wrapped-send/wrapped-send.module.ts:57

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

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

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.
M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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

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

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

What to do

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

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

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

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

P2 · 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 463 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:463
  • `packages/common/services/console-logger.service.ts` reports through `console.*` at line 465 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:465
  • `packages/common/services/console-logger.service.ts` reports through `console.*` at line 491 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:491
  • `packages/common/services/console-logger.service.ts` reports through `console.*` at line 493 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:493
  • `packages/common/services/console-logger.service.ts` reports through `console.*` at line 729 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:729
  • `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.
  • Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling7.0 / 10Strong✓ Tool-verified

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

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

What to do

  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
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).
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.
P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

  • `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — integration/http-adapters/src/streaming/streaming.module.ts:375, integration/http-adapters/src/streaming/streaming.module.ts:380

What to do

  • Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
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.
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 each language's code 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.
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.

R10 · Code Duplication4.3 / 10Weak✓ Tool-verified

React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): 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. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.

  • 71 duplicated blocks under packages/ have copies in at least two of the sibling directories common, core, microservices, platform-express, platform-fastify, platform-node (+4 more sibling(s) not listed) — 56 of them are reported below, and 15 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 71 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 71 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 71 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
  • 23 duplicated blocks under packages/microservices/ have copies in at least two of the sibling directories client, server — 18 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 23 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 23 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 23 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:213
  • 14 duplicated blocks under packages/core/ have copies in at least two of the sibling directories exceptions, guards, helpers, injector, interceptors, middleware (+2 more sibling(s) not listed) — 11 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 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 14 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:19
  • 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:35 — the two spans are one implementation copied and then locally edited — 1104 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/platform-express/multer/multer/multer.utils.ts:6 · packages/platform-node/multer/multer/multer.utils.ts:6 — these 2 files are line-for-line copies of one another — 164 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-express/multer/multer/multer.utils.ts:6
  • packages/core/interceptors/interceptors-context-creator.ts:19 · packages/core/pipes/pipes-context-creator.ts:19 — the two spans are one implementation copied and then locally edited — 577 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:19
  • packages/microservices/server/server-nats.ts:47 · packages/microservices/server/server-redis.ts:44 — the two spans are one implementation copied and then locally edited — 494 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:47
  • packages/microservices/client/client-mqtt.ts:365 · packages/microservices/client/client-redis.ts:379 — the two spans are one implementation copied and then locally edited — 412 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-mqtt.ts:365
  • 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:567 · packages/microservices/nest-microservice.ts:218 — 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:567
  • packages/platform-express/multer/multer.module.ts:14 · packages/platform-node/multer/multer.module.ts:14 — 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
  • 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 — 61 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/platform-socket.io/utils/merge-map-bounded.util.ts:4
  • 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 — 56 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/common/serializer/standard-schema-serializer.interceptor.ts:39 · packages/core/router/router-response-controller.ts:185 — the two spans are one implementation copied and then locally edited — 252 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/common/serializer/standard-schema-serializer.interceptor.ts:39
  • 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/adapters/express-adapter.ts:180 · packages/platform-node/adapters/node-adapter.ts:265 — 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/adapters/express-adapter.ts:180
  • packages/microservices/client/client-proxy.ts:213 · packages/microservices/server/server.ts:509 — 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:213
  • 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
  • packages/core/helpers/external-context-creator.ts:328 · packages/microservices/context/rpc-context-creator.ts:314 · packages/websockets/context/ws-context-creator.ts:238 — the 3 copies are spread across 3 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 3 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/helpers/external-context-creator.ts:328
  • 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 · packages/platform-node/adapters/utils/get-media-type-version.util.ts:5 — the 3 copies are spread across 3 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 3 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/platform-express/adapters/utils/get-media-type-version.util.ts:5
  • packages/microservices/client/client-nats.ts:206 · packages/microservices/server/server-nats.ts:336 — 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:206
  • packages/platform-node/multer/interceptors/file-fields.interceptor.ts:34 · packages/platform-node/multer/interceptors/file.interceptor.ts:32 · packages/platform-node/multer/interceptors/files.interceptor.ts:35 — 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/platform-node/multer/interceptors/file-fields.interceptor.ts:34
  • 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 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/platform-express/multer/interceptors/file-fields.interceptor.ts:33
  • packages/core/guards/guards-context-creator.ts:20 · packages/core/pipes/pipes-context-creator.ts:19 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/core/guards/guards-context-creator.ts:20
  • packages/platform-express/adapters/utils/on-response-close.util.ts:31 · packages/platform-fastify/adapters/utils/on-response-close.util.ts:31 · packages/platform-node/adapters/utils/on-response-close.util.ts:31 — the 3 copies are spread across 3 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 3 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/platform-express/adapters/utils/on-response-close.util.ts:31
  • packages/platform-express/multer/interfaces/multer-options.interface.ts:4 · packages/platform-node/multer/interfaces/multer-options.interface.ts:4 — 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/interfaces/multer-options.interface.ts:4
  • 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/guards/guards-context-creator.ts:69 · packages/core/interceptors/interceptors-context-creator.ts:69 — 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/guards/guards-context-creator.ts:69
  • packages/core/guards/guards-context-creator.ts:118 · packages/core/interceptors/interceptors-context-creator.ts:117 · packages/core/pipes/pipes-context-creator.ts:109 — the 3 copies are spread across 3 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 3 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/guards/guards-context-creator.ts:118
  • packages/platform-express/adapters/express-adapter.ts:785 · packages/platform-node/adapters/node-adapter.ts:1044 — 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/adapters/express-adapter.ts:785
  • 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

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries9.7 / 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:71 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:71
  • packages/platform-node/router/utils.ts:1 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. — packages/platform-node/router/utils.ts:1

What to do

  • Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity8.4 / 10Strong✓ Tool-verified

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

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

  • (anonymous) has cyclomatic complexity 51 and cognitive complexity 55; 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-node/adapters/node-adapter.ts:578
  • next has cyclomatic complexity 38 and cognitive complexity 76; 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-node/router/node-router.ts:527
  • (anonymous) has cyclomatic complexity 37 and cognitive complexity 40; 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:1394
  • find has cyclomatic complexity 30 and cognitive complexity 46; 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-node/router/route-table.ts:668
  • (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
  • (anonymous) 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/platform-express/adapters/express-adapter.ts:426
  • transform has cyclomatic complexity 26 and cognitive complexity 76; 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:100
  • 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
  • transform has cyclomatic complexity 25 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/common/pipes/validation.pipe.ts:176
  • 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
  • toFindMyWayPath has cyclomatic complexity 21 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/platform-node/router/route-table.ts:292
  • writeWaitingValues has cyclomatic complexity 21 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/server/server-grpc.ts:581
  • (anonymous) has cyclomatic complexity 21 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/microservices/client/client-mqtt.ts:356
  • (anonymous) has cyclomatic complexity 20 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/microservices/client/client-nats.ts:315
  • 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:559
  • add has cyclomatic complexity 18 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/platform-node/router/route-table.ts:420
  • lookup has cyclomatic complexity 18 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/platform-node/router/route-table.ts:597
  • (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
  • stream 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/router/router-response-controller.ts:287
  • 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:122
  • 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
  • findNestedBinaryValues has cyclomatic complexity 15 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/common/pipes/validation.pipe.ts:487
  • isMiddlewareRouteExcluded has cyclomatic complexity 15 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/middleware/utils.ts:336
  • urlencoded has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/platform-node/body-parser/body-parser.ts:758
  • processBufferedPackets has cyclomatic complexity 14 and cognitive complexity 30; 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:221
  • 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:187
  • getRawPrefixEnd has cyclomatic complexity 14 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/platform-node/router/utils.ts:228
  • (anonymous) has cyclomatic complexity 14 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/websockets/web-sockets-controller.ts:511
  • next has cyclomatic complexity 14 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/microservices/server/server-grpc.ts:698
  • reader has cyclomatic complexity 14 and cognitive complexity 9; 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-node/body-parser/body-parser.ts:365
  • (anonymous) has cyclomatic complexity 13 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. — REDACTED:1398
  • 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:59
  • (anonymous) has cyclomatic complexity 13 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/common/services/console-logger.service.ts:828
  • UNKNOWN_DEPENDENCIES_MESSAGE has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/errors/messages.ts:63
  • getPathFromAbsoluteUrl has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/platform-node/router/utils.ts:153
  • (anonymous) has cyclomatic complexity 13 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/microservices/server/server-kafka.ts:380
  • closeArrayGaps has cyclomatic complexity 12 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/common/utils/close-array-gaps.util.ts:47
  • scanFromPrototype has cyclomatic complexity 12 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/core/metadata-scanner.ts:16
  • serializeContentSecurityPolicy has cyclomatic complexity 12 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/security/security-headers.ts:136
R3 · Large Files8.3 / 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 2100 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 1928 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/microservices/server/server-grpc.ts has 1126 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/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/platform-node/adapters/node-adapter.ts has 1065 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-node/adapters/node-adapter.ts:1
  • packages/common/services/console-logger.service.ts has 930 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
  • integration/http-adapters/src/streaming/streaming.module.ts has 907 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — integration/http-adapters/src/streaming/streaming.module.ts:1
  • packages/platform-node/router/route-table.ts has 860 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-node/router/route-table.ts:1
  • packages/platform-node/body-parser/body-parser.ts has 846 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-node/body-parser/body-parser.ts:1
  • packages/core/scanner.ts has 834 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/platform-node/adapters/node-request.ts has 802 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-node/adapters/node-request.ts:1
  • packages/core/router/router-execution-context.ts has 784 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/platform-express/adapters/express-adapter.ts has 783 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/websockets/web-sockets-controller.ts has 753 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/common/interfaces/http/http-server.interface.ts has 743 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/core/router/router-response-controller.ts has 741 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-response-controller.ts:1
  • packages/core/nest-application.ts has 704 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/nest-application.ts:1
  • packages/platform-fastify/multipart/multipart/multipart.parser.ts has 703 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/microservices/client/client-rmq.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/microservices/client/client-rmq.ts:1
  • packages/core/injector/instance-wrapper.ts has 683 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
  • REDACTED has 680 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/router/route-conflict-detector.ts has 661 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/route-conflict-detector.ts:1
  • packages/microservices/server/server-kafka.ts has 658 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/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/common/pipes/validation.pipe.ts has 649 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/platform-node/router/node-router.ts has 642 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/platform-node/router/node-router.ts:1
  • packages/microservices/server/server-rmq.ts has 626 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/injector/module.ts has 618 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/server/server.ts has 614 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/microservices/helpers/json-socket.ts has 571 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/helpers/json-socket.ts:1
  • packages/microservices/client/client-kafka.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/microservices/client/client-kafka.ts:1
  • packages/core/middleware/utils.ts has 546 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/middleware/utils.ts:1
  • packages/core/middleware/route-info-path-extractor.ts has 542 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/middleware/route-info-path-extractor.ts:1
  • packages/microservices/client/client-mqtt.ts has 521 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/microservices/client/client-mqtt.ts:1
  • packages/core/router/router-explorer.ts has 511 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/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/interfaces/microservice-configuration.interface.ts has 469 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/interfaces/microservice-configuration.interface.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/microservices/server/server-tcp.ts has 466 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-tcp.ts:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage9.6 / 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. (×35) — integration/_support/register-local-packages.ts:1, integration/microservices/src/rmq/rmq-broadcast.controller.ts:1, integration/inspector/src/durable/durable-context-id.strategy.ts:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
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.

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

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

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

R7 · Dead 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 63 application, 5 tooling and 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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.
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. (×10) — integration/microservices/src/nats/nats.controller.ts:1, integration/inspector/src/chat/dto/update-chat.dto.ts:1, integration/cookies/e2e/cookies.spec.ts:15, …
  • 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. (×14)
  • Every import is type-only — move it to devDependencies. (×2) — packages/common/decorators/http/create-route-param-metadata.decorator.ts:1, packages/platform-node/adapters/node-adapter.ts:35

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
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/errors/messages.ts → packages/core/injector/injector.ts → packages/core/errors/exceptions/index.ts → packages/core/errors/exceptions/invalid-class-scope.exception.ts → packages/core/errors/messages.ts (one verified cycle inside a mutually-dependent group of 51 files) — packages/core/errors/messages.ts:2
  • 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:12
  • 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.
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. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and 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:234

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`.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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.

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

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

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

X17 · Uncapped recursion over a caller-supplied document2.7 / 10Weak✓ Tool-verified

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

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

  • `getServiceNames` is exported, takes a document from its caller (line 211) and hands it to `collectDeepServices`, which calls itself at line 1113 (`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:1113
  • `createUploadModule` is exported, takes a document from its caller (line 99) and hands it to `describeFiles`, which calls itself at line 51 (`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:51

What to do

  • Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×10) — packages/platform-node/views/view-renderer.ts:328, packages/platform-node/multer/multer/multer.utils.ts:320, packages/platform-node/adapters/node-adapter.ts:234, …
  • `.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. (×8) — packages/microservices/client/client-mqtt.ts:235, packages/microservices/client/client-nats.ts:113, packages/microservices/client/client-nats.ts:174, …

What to do

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

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

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

X4 · Structured logging5.0 / 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.

  • `log` at line 74 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/websockets/socket-server-provider.ts:74
  • `warn` at line 149 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/websockets/socket-server-provider.ts:149
  • `error` at line 627 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:627
  • `log` at line 783 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/websockets/web-sockets-controller.ts:783
  • `warn` at line 377 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:377
  • `warn` at line 557 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:557
  • `warn` at line 2057 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:2057
  • `warn` at line 564 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/microservices/server/server-grpc.ts:564
  • `error` at line 414 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:414
  • `error` at line 448 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:448
  • `error` at line 456 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:456
  • `error` at line 461 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:461
  • `error` at line 301 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:301
  • `error` at line 307 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:307
  • `log` at line 329 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:329
  • `log` at line 339 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:339
  • `log` at line 355 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:355
  • `warn` at line 371 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/microservices/server/server-rmq.ts:371
  • `error` at line 435 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-rmq.ts:435
  • `error` at line 314 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:314
  • `error` 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.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:327
  • `error` at line 164 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:164
  • `error` at line 176 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:176
  • `log` at line 191 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:191
  • `debug` at line 202 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:202
  • `log` at line 209 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:209
  • `log` at line 225 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:225
  • `error` at line 332 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:332
  • `debug` at line 351 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-redis.ts:351
  • `error` at line 132 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:132
  • `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 413 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:413
  • `warn` at line 640 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:640
  • `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
  • `warn` at line 353 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/middleware/middleware-module.ts:353
  • `log` at line 1990 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:1990
  • `log` at line 2006 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:2006
  • `log` at line 733 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:733
  • `log` at line 746 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:746
  • `warn` at line 72 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:72

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types5.0 / 10Adequate✓ 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.

  • 42/82 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.4 `!` null assertions per 1k TypeScript source lines — 378 assertion(s) across the 86098 source line(s) of the 1156 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. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.

What to do

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

Reference — by lens

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

LensScoreRatingImpact
Code Health58%AdequateAcceptable, with room to improve.
Architecture56%Adequate — gated by D5, R9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity67%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness36%Weak — gated by R8, P7, P8Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security73%Adequate — gated by D29Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling100%ExemplaryStrongest area.
Performance85%StrongSolid.
Unscored — 5 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 publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). 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 — 2 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'.
  • SC1 Supply-chain hygiene — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 56 check(s) not relevant to this codebase

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

  • AC1 Text alternatives — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC2 Forms & labels — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC3 Page structure — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC4 Keyboard semantics — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC5 ARIA correctness — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC6 Visual & motion safety — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
  • 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 — The runtime tier booted this repository's service, but crawled PUBLIC routes only — add a Playwright storageState (e.g. playwright/.auth/user.json) or a test auth-setup to crawl authenticated screens rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:5432: page.goto: net::ERR_EMPTY_RESPONSE at http://127.0.0.1:5432/ Call log: - navigating to "http://127.0.0.1:5432/", waiting until "load" . This repository also has a user interface (5 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates) that the booted service does not serve, and this scan has no strategy that reaches it — so no WCAG success criterion was verified in a rendered page on this run. That is a gap in OUR tooling, not a finding about your application: nothing here says the interface is inaccessible. The static accessibility checks still ran.
  • AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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 does not read html yet; not measured.
  • D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
  • D25 ADR Conformance — no ADRs to check
  • D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • 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.
  • 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
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • 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 scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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.
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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 — 74 finding(s)
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.
D30 · Dependency Vulnerabilities · High CVE · ×11
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
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
R9 · Circular Imports · Import cycle (4 files) · ×4
  • 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/errors/messages.ts:2 — packages/core/errors/messages.ts → packages/core/injector/injector.ts → packages/core/errors/exceptions/index.ts → packages/core/errors/exceptions/invalid-class-scope.exception.ts → packages/core/errors/messages.ts (one verified cycle inside a mutually-dependent group of 51 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)
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:1137 — 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:1484 — 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.
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:15 — 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:11 — 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.
AX3 · Project dependency cycles · Project dependency cycle · ×1
  • Project dependency cycle packages/core/package.json:57 — 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:59 — `@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:57 — @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.
R8 · Dependency Hygiene · Unlisted import 'qs' · ×1
  • Unlisted import 'qs' integration/http-adapters/e2e/request-options.spec.ts:5 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'ejs' · ×1
  • Unlisted import 'ejs' packages/platform-node/test/views/view-renderer.spec.ts:1 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'handlebars' · ×1
  • Unlisted import 'handlebars' packages/platform-node/test/views/view-renderer.spec.ts:3 — 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:12 — 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)
R9 · Circular Imports · Import cycle (3 files) · ×1
  • 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)
Serious — 600 finding(s)
D15 · Churn × Complexity Hotspots · Repeated repair · ×83
  • Repeated repair: REDACTED REDACTED:389 — REDACTED changed 22 times in last 90 days and 21 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is WsAdapter.bindMessageHandlers at line 389), AT OR 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(ws,socket.io): use the default for adapter limits given as nan”; “fix(websockets,ws,socket.io): open no port for a gateway without one”; “fix(ws): refuse gateways on one port that set different hosts”; “fix(ws): refuse a client whose upgrade check throws”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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:637 — packages/microservices/server/server-rmq.ts changed 20 times in last 90 days and 19 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 ServerRMQ.matchRmqPattern at line 637), AT OR 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): check the routing key of rmq wildcard messages”; “fix(microservices): skip rmq wildcard matching for over-long patterns”; “fix(microservices): reject rmq short strings longer than 255 bytes”; “fix(microservices): validate kafka and rmq request ids before echoing”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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:495 — packages/websockets/web-sockets-controller.ts changed 19 times in last 90 days and 19 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 WebSocketsController.createRequestScopedEventHandler at line 495), AT OR 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,microservices,websockets): drop gateway clients during startup”; “fix(websockets): refuse a gateway whose connection check would not run”; “fix(websockets): count a message as handled until its filter is done”; “fix(websockets): run a scoped gateway's disconnect hook after connect”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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-tcp.ts packages/microservices/server/server-tcp.ts:326 — packages/microservices/server/server-tcp.ts changed 20 times in last 90 days and 18 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 326), AT OR 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 many messages of a tcp peer are handled”; “fix(microservices): end streams of tcp messages emitted without an id”; “fix(microservices): listen on localhost for an empty tcp host option”; “fix(microservices): bound how long a tcp packet may take to arrive”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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/server/server-kafka.ts packages/microservices/server/server-kafka.ts:402 — packages/microservices/server/server-kafka.ts changed 20 times in last 90 days and 18 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 ServerKafka.handleMessage at line 402), AT OR 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): refuse kafka reply topics the server handles itself”; “fix(microservices): send kafka events and replies without reply headers”; “fix(microservices): keep the kafka consumer running after type errors”; “fix(microservices): stop kafka servers from keeping streamed replies”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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-mqtt.ts packages/microservices/client/client-mqtt.ts:353 — packages/microservices/client/client-mqtt.ts changed 19 times in last 90 days and 18 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 353), AT OR 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 topic names with wildcards in clientmqtt”; “fix(microservices): reset the mqtt client state when close fails (#18352)”; “fix(ws,microservices): load packages where bundlers can see them (#18285)”; “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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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: packages/microservices/client/client-rmq.ts packages/microservices/client/client-rmq.ts:351 — packages/microservices/client/client-rmq.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 9 (its worst body is ClientRMQ.setupChannel at line 351), AT OR 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 rmq short strings longer than 255 bytes”; “fix(microservices): limit the size of rmq messages decoded as json”; “fix(microservices): handle a cancelled rmq reply consumer in client (#18499)”; “fix(microservices): fail pending rmq requests when the connection drops (#18491)”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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/platform-express/multer/multer/multer.utils.ts packages/platform-express/multer/multer/multer.utils.ts:178 — packages/platform-express/multer/multer/multer.utils.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 8 (its worst body is multer.utils.runMulter at line 178), AT OR 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(express): remove rejected uploads of pipelined requests on close”; “fix(express,fastify,node): close the array gaps of multipart bodies”; “fix(express,fastify,node): cut off an upload once the response is sent”; “fix(express,fastify,node): fail the request when an upload filter throws”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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.
  • Repeated repair: packages/microservices/server/server-mqtt.ts packages/microservices/server/server-mqtt.ts:268 — packages/microservices/server/server-mqtt.ts changed 16 times in last 90 days and 14 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 268), AT OR 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): match mqtt wildcard filters against the sent topic”; “fix(microservices): ignore an mqtt server's own replies under wildcards (#18418)”; “fix(microservices): await the mqtt close and reset the client state (#18393)”; “fix(microservices): honor mqtt topic filter boundaries (#18221)”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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/core/injector/instance-wrapper.ts packages/core/injector/instance-wrapper.ts:483 — packages/core/injector/instance-wrapper.ts changed 15 times in last 90 days and 13 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is InstanceWrapper.isStatic at line 483), AT OR 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): release removed wrappers from the providers they depended on”; “fix(core): keep create() working after many calls in snapshot mode”; “fix(core): run the hooks of a provider that overrides an alias (#18455)”; “fix(core): apply a provider override whose value is undefined (#18410)”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +01:00' --full-history --no-merges -- packages/core/injector/instance-wrapper.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:237 — packages/core/nest-application.ts changed 15 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 NestApplication.registerRouter at line 237), AT OR 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,microservices,websockets): drop gateway clients during startup”; “fix(core): report shadowed routes that differ only by param names (#18307)”; “fix(core): don't preload @nestjs/platform-express on NestFactory.create() (#18309)”; “fix(core): read the url protocol from the server (#18252)”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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/core/middleware/route-info-path-extractor.ts packages/core/middleware/route-info-path-extractor.ts:268 — packages/core/middleware/route-info-path-extractor.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 15 (its worst body is RouteInfoPathExtractor.extractExcludedRoutesCoveredBy at line 268), AT OR 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): mount middleware on a route path that really ends in "$"”; “fix(core): mount a controller root route without the slash after a tail”; “fix(core): mount middleware where the router serves the covered routes”; “fix(core): compare a prefix exclusion with a trailing slash as served”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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-redis.ts packages/microservices/client/client-redis.ts:370 — packages/microservices/client/client-redis.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 14 (its worst body is ClientRedis.publish at line 370), AT OR 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 redis requests that wait for the subscription”; “fix(microservices): print the id of an unmatched redis reply safely”; “fix(microservices): drop idle reply channels from subscription counts”; “fix(microservices): fail redis listen on rejected subscriptions (#18060)”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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/microservices/server/server-redis.ts packages/microservices/server/server-redis.ts:181 — packages/microservices/server/server-redis.ts changed 14 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 9 (its worst body is ServerRedis.handleMessage at line 181), AT OR 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 redis channels wildcard requests reply on”; “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”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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/server/server.ts packages/microservices/server/server.ts:224 — packages/microservices/server/server.ts changed 14 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 9 (its worst body is Server.send at line 224), AT OR 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): apply the pattern limits before serializing it”; “fix(microservices): end streams of tcp messages emitted without an id”; “fix(microservices): reach handlers whose string pattern reads as json (#18413)”; “fix(microservices): answer requests whose exception filter throws (#18359)”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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/errors/messages.ts packages/core/errors/messages.ts:63 — packages/core/errors/messages.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 13 (its worst body is messages.UNKNOWN_DEPENDENCIES_MESSAGE at line 63), AT OR 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): warn about an exception filter that can't run”; “fix(core): throw for a guard, interceptor or pipe that can't run”; “fix(core): warn when a validation pipe gets no parameter types”; “fix(core,common): warn when decorator metadata is missing (#18429)”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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:221 — packages/microservices/helpers/json-socket.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 14 (its worst body is JsonSocket.processBufferedPackets at line 221), AT OR 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 many messages of a tcp peer are handled”; “fix(microservices): flatten the tcp packet buffer after many small reads”; “fix(microservices): apply the tcp maxbuffersize to each packet”; “fix(microservices): use the default tcp and kafka limits for nan”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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/microservices/interfaces/microservice-configuration.interface.ts packages/microservices/interfaces/microservice-configuration.interface.ts:39 — packages/microservices/interfaces/microservice-configuration.interface.ts changed 13 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 1 (its worst body is useFactory at line 39), AT OR 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 many messages of a tcp peer are handled”; “fix(microservices): listen on localhost for an empty tcp host option”; “fix(microservices): lower the default tcp maxbuffersize to 16 mi”; “fix(microservices): limit the redis channels wildcard requests reply on”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +01:00' --full-history --no-merges -- packages/microservices/interfaces/microservice-configuration.interface.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:122 — packages/core/scanner.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 14 (its worst body is DependenciesScanner.scanForModules at line 122), AT OR 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): warn about an exception filter that can't run”; “fix(core): throw for a guard, interceptor or pipe that can't run”; “fix(core,websockets): read parameter metadata from the declaring class”; “fix(core): resolve a forward reference to a module only once”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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/microservices/client/client-tcp.ts packages/microservices/client/client-tcp.ts:66 — packages/microservices/client/client-tcp.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 6 (its worst body is ClientTCP.connect at line 66), AT OR 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): listen on localhost for an empty tcp host option”; “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)”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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/microservices/server/server-nats.ts packages/microservices/server/server-nats.ts:296 — packages/microservices/server/server-nats.ts changed 11 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 296), AT OR 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): skip nest replies arriving on nats handler subjects”; “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”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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/core/middleware/builder.ts packages/core/middleware/builder.ts:25 — packages/core/middleware/builder.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 2 (its worst body is builder.toServedPath at line 25), AT OR 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): mount middleware where the router serves the covered routes”; “fix(core,fastify): exclude "/x/" only when no other route may serve it”; “fix(core): keep a controller root route next to an optional-tail route”; “fix(core): run middleware on subpaths next to an all-methods route (#18407)”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +01:00' --full-history --no-merges -- packages/core/middleware/builder.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/interfaces/http/http-server.interface.ts packages/common/interfaces/http/http-server.interface.ts:25 — packages/common/interfaces/http/http-server.interface.ts changed 12 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 1 (its worst body is (anonymous) at line 25), AT OR 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,fastify): match the text after an excluded param as written”; “fix(core,fastify): end the excluded path at ";" like the fastify router”; “fix(core,fastify,node): match excluded params up to the router's limit”; “fix(core,fastify): exclude "/x/" only when no other route may serve it”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +01:00' --full-history --no-merges -- packages/common/interfaces/http/http-server.interface.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:183 — REDACTED changed 10 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 11 (its worst body is ClientGrpcProxy.createStreamServiceMethod at line 183), AT OR 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 grpc client calls whose requests emit null”; “fix(microservices): keep grpc from mutating the caller channel options (#18479)”; “fix(microservices): skip nil grpc metadata before call options (#18446)”; “fix(microservices): forward grpc call options on request streams (#18392)”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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/platform-socket.io/adapters/io-adapter.ts packages/platform-socket.io/adapters/io-adapter.ts:128 — packages/platform-socket.io/adapters/io-adapter.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 7 (its worst body is IoAdapter.bindMessageHandlers at line 128), AT OR 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(ws,socket.io): use the default for adapter limits given as nan”; “fix(websockets,ws,socket.io): open no port for a gateway without one”; “fix(websockets,socket.io): stop echoing binary data in error replies”; “fix(socket.io): cap how many messages of a client wait for their turn”. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +01:00' --full-history --no-merges -- packages/platform-socket.io/adapters/io-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.
  • + 58 more in this group — see findings.md.
SC1 · Supply-chain hygiene · JavaScript dependencies are not locked · ×40
  • JavaScript dependencies are not locked sample/01-cats-app/package.json:21 — sample/01-cats-app/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/02-gateways/package.json:21 — sample/02-gateways/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/03-microservices/package.json:21 — sample/03-microservices/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/04-grpc/package.json:21 — sample/04-grpc/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/05-sql-typeorm/package.json:21 — sample/05-sql-typeorm/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/06-mongoose/package.json:21 — sample/06-mongoose/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/07-sequelize/package.json:21 — sample/07-sequelize/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/08-webpack/package.json:14 — sample/08-webpack/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/09-babel-example/package.json:17 — sample/09-babel-example/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/10-fastify/package.json:21 — sample/10-fastify/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/11-swagger/package.json:21 — sample/11-swagger/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/12-graphql-schema-first/package.json:21 — sample/12-graphql-schema-first/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/13-mongo-typeorm/package.json:21 — sample/13-mongo-typeorm/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/14-mongoose-base/package.json:21 — sample/14-mongoose-base/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/15-mvc/package.json:21 — sample/15-mvc/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/16-gateways-ws/package.json:21 — sample/16-gateways-ws/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/17-mvc-fastify/package.json:21 — sample/17-mvc-fastify/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/18-context/package.json:21 — sample/18-context/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/19-auth-jwt/package.json:22 — sample/19-auth-jwt/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/20-cache/package.json:21 — sample/20-cache/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/21-serializer/package.json:21 — sample/21-serializer/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/22-graphql-prisma/package.json:22 — sample/22-graphql-prisma/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/23-graphql-code-first/package.json:21 — sample/23-graphql-code-first/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/24-serve-static/package.json:21 — sample/24-serve-static/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked sample/25-dynamic-modules/package.json:21 — sample/25-dynamic-modules/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • + 15 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×35
  • 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 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 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 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 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.
  • No test reaches this file integration/lazy-modules/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/microservices/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/mongoose/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/scopes/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/typeorm/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/injector/src/app.module.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.module.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.
  • + 10 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Hotspot · ×21
  • Hotspot: REDACTED REDACTED:842 — REDACTED changed 57 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in FastifyAdapter.reply at line 842. 55 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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/microservices/server/server-grpc.ts packages/microservices/server/server-grpc.ts:503 — packages/microservices/server/server-grpc.ts changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in ServerGrpc.writeObservableToGrpc at line 503. 20 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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.
  • Hotspot: packages/core/router/router-response-controller.ts packages/core/router/router-response-controller.ts:465 — packages/core/router/router-response-controller.ts changed 24 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in RouterResponseController.sse at line 465. 23 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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/core/injector/injector.ts packages/core/injector/injector.ts:417 — packages/core/injector/injector.ts changed 33 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in Injector.resolveConstructorParams at line 417. 31 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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.
  • Hotspot: packages/platform-express/adapters/express-adapter.ts packages/platform-express/adapters/express-adapter.ts:168 — packages/platform-express/adapters/express-adapter.ts changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in ExpressAdapter.reply at line 168. 26 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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/common/pipes/validation.pipe.ts packages/common/pipes/validation.pipe.ts:176 — packages/common/pipes/validation.pipe.ts changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in ValidationPipe.transform at line 176. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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/platform-node/adapters/node-adapter.ts packages/platform-node/adapters/node-adapter.ts:242 — packages/platform-node/adapters/node-adapter.ts changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in NodeAdapter.reply at line 242. 11 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +01:00' --full-history --no-merges -- packages/platform-node/adapters/node-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/core/middleware/utils.ts packages/core/middleware/utils.ts:336 — packages/core/middleware/utils.ts changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in utils.isMiddlewareRouteExcluded at line 336. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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.
  • Hotspot: packages/common/pipes/parse-array.pipe.ts packages/common/pipes/parse-array.pipe.ts:100 — packages/common/pipes/parse-array.pipe.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in ParseArrayPipe.transform at line 100. 10 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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/platform-node/router/node-router.ts packages/platform-node/router/node-router.ts:497 — packages/platform-node/router/node-router.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in NodeRouter.dispatch at line 497. 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-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +01:00' --full-history --no-merges -- packages/platform-node/router/node-router.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/router-execution-context.ts packages/core/router/router-execution-context.ts:565 — packages/core/router/router-execution-context.ts changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in RouterExecutionContext.createHandleResponseFn at line 565. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +01:00' --full-history --no-merges -- packages/core/router/router-execution-context.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-node/adapters/node-request.ts packages/platform-node/adapters/node-request.ts:519 — packages/platform-node/adapters/node-request.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in NodeResponse.sendFile at line 519. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +01:00' --full-history --no-merges -- packages/platform-node/adapters/node-request.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:397 — packages/microservices/client/client-nats.ts changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in ClientNats.mergeHeaders at line 397. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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/platform-fastify/multipart/multipart/multipart.parser.ts packages/platform-fastify/multipart/multipart/multipart.parser.ts:203 — packages/platform-fastify/multipart/multipart/multipart.parser.ts changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in multipart.parser.storeFile at line 203. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +01:00' --full-history --no-merges -- packages/platform-fastify/multipart/multipart/multipart.parser.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/services/console-logger.service.ts packages/common/services/console-logger.service.ts:789 — packages/common/services/console-logger.service.ts changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in ConsoleLogger.stringifyJsonLogObject at line 789. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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.
  • Hotspot: packages/platform-node/router/route-table.ts packages/platform-node/router/route-table.ts:668 — packages/platform-node/router/route-table.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in RouteTable.find at line 668. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +01:00' --full-history --no-merges -- packages/platform-node/router/route-table.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/router-explorer.ts packages/core/router/router-explorer.ts:345 — packages/core/router/router-explorer.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in RouterExplorer.applyHostFilter at line 345. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +01:00' --full-history --no-merges -- packages/core/router/router-explorer.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/services/utils/redact.util.ts packages/common/services/utils/redact.util.ts:67 — packages/common/services/utils/redact.util.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in redact.util.createRedactor.<returned closure> at line 67. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +01:00' --full-history --no-merges -- packages/common/services/utils/redact.util.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:44 — packages/common/decorators/http/create-route-param-metadata.decorator.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in create-route-param-metadata.decorator.createParamDecorator.<returned closure>.<returned closure> at line 44. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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/platform-node/body-parser/body-parser.ts packages/platform-node/body-parser/body-parser.ts:365 — packages/platform-node/body-parser/body-parser.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in body-parser.createReader.reader at line 365. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +01:00' --full-history --no-merges -- packages/platform-node/body-parser/body-parser.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. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 09:20:33 +01:00' --until='2026-11-13 09:20:33 +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.
X3 · Exception handling · Swallowed exception (empty catch) · ×18
  • Swallowed exception (empty catch) packages/platform-node/views/view-renderer.ts:328 — 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-node/multer/multer/multer.utils.ts:320 — 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-node/adapters/node-adapter.ts:234 — 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) REDACTED:467 — 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:271 — 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/server/server-redis.ts:135 — 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:84 — 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:324 — 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:235 — `.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:113 — `.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:174 — `.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:185 — `.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:266 — `.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:267 — `.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:437 — `.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/core/security/cross-origin-protection.ts:348 — `.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/core/router/streaming-body.ts:124 — 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/common/pipes/parse-array.pipe.ts:138 — 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.
D3 · God Classes · TooManyMethods · ×15
  • 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:297 — TooManyMethods — 94 methods. The bar is 30 methods; this is 64 over it, 3.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Injector packages/core/injector/injector.ts:124 — TooManyMethods — 69 methods. The bar is 30 methods; this is 39 over it, 2.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: NodeAdapter packages/platform-node/adapters/node-adapter.ts:145 — TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.77× 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:70 — 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: ConsoleLogger packages/common/services/console-logger.service.ts:178 — 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:84 — 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: DependenciesScanner packages/core/scanner.ts:91 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× 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:21 — 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: NestContainer packages/core/injector/container.ts:32 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 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.
  • TooManyMethods: ServerGrpc packages/microservices/server/server-grpc.ts:140 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 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.
  • TooManyMethods: Server packages/microservices/server/server.ts:76 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 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.
  • 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.
D10 · Test Quality · No assertions · ×13
  • 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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 end the response for a source that has already ended packages/platform-express/test/adapters/express-adapter.spec.ts:659 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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:482 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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:68 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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:93 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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 keep serving when the filter of a %s connection hook throws integration/websockets/e2e/scoped-connection-hook-error.spec.ts:213 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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.
D3 · God Classes · ClassTooLong · ×12
  • ClassTooLong: Injector packages/core/injector/injector.ts:124 — ClassTooLong — 1264 significant lines (blank, comment-only and punctuation-only lines excluded), 69 methods. The bar is 400 significant lines; this is 864 over it, 3.16× 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:297 — ClassTooLong — 1117 significant lines (blank, comment-only and punctuation-only lines excluded), 94 methods. The bar is 400 significant lines; this is 717 over it, 2.79× 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: NodeAdapter packages/platform-node/adapters/node-adapter.ts:145 — ClassTooLong — 569 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. The bar is 400 significant lines; this is 169 over it, 1.42× 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:91 — ClassTooLong — 554 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 400 significant lines; this is 154 over it, 1.39× 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 — 524 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 124 over it, 1.31× 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:100 — ClassTooLong — 511 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 111 over it, 1.28× 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:178 — ClassTooLong — 503 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 400 significant lines; this is 103 over it, 1.26× 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 — 442 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 400 significant lines; this is 42 over it, 1.11× 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:70 — ClassTooLong — 434 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 400 significant lines; this is 34 over it, 1.09× 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 — 429 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 400 significant lines; this is 29 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: InstanceWrapper packages/core/injector/instance-wrapper.ts:84 — ClassTooLong — 424 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 400 significant lines; this is 24 over it, 1.06× 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: ClientRMQ packages/microservices/client/client-rmq.ts:88 — ClassTooLong — 421 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 21 over it, 1.05× 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.
D3 · God Classes · FileTooLong · ×12
  • FileTooLong: injector/injector.ts packages/core/injector/injector.ts — FileTooLong — 1332 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: Injector (124-2055). The bar is 500 significant lines; this is 832 over it, 2.66× 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 — 1329 significant lines (blank, comment-only and punctuation-only lines excluded), about 84% of them inside a single declaration: FastifyAdapter (297-2239). The bar is 500 significant lines; this is 829 over it, 2.66× 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: server/server-grpc.ts packages/microservices/server/server-grpc.ts — FileTooLong — 712 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 212 over it, 1.42× 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: adapters/node-adapter.ts packages/platform-node/adapters/node-adapter.ts — FileTooLong — 694 significant lines (blank, comment-only and punctuation-only lines excluded), about 82% of them inside a single declaration: NodeAdapter (145-1117). The bar is 500 significant lines; this is 194 over it, 1.39× 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: core/scanner.ts packages/core/scanner.ts — FileTooLong — 637 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: DependenciesScanner (91-906). The bar is 500 significant lines; this is 137 over it, 1.27× 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 — 605 significant lines (blank, comment-only and punctuation-only lines excluded), about 84% of them inside a single declaration: RouterExecutionContext (100-826). The bar is 500 significant lines; this is 105 over it, 1.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: websockets/web-sockets-controller.ts packages/websockets/web-sockets-controller.ts — FileTooLong — 570 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: WebSocketsController (48-788). The bar is 500 significant lines; this is 70 over it, 1.14× 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: services/console-logger.service.ts packages/common/services/console-logger.service.ts — FileTooLong — 557 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: ConsoleLogger (179-1006). The bar is 500 significant lines; this is 57 over it, 1.11× 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/route-table.ts packages/platform-node/router/route-table.ts — FileTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded), about 63% of them inside a single declaration: RouteTable (387-902). 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: body-parser/body-parser.ts packages/platform-node/body-parser/body-parser.ts — FileTooLong — 518 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 18 over it, 1.04× 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: adapters/express-adapter.ts packages/platform-express/adapters/express-adapter.ts — FileTooLong — 504 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: ExpressAdapter (70-844). The bar is 500 significant lines; this is 4 over it, 1.01× 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.
D30 · Dependency Vulnerabilities · Medium CVE · ×11
  • REDACTED
  • 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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.
D10 · Test Quality · Fixed-sleep synchronisation · ×6
  • Fixed-sleep synchronisation: should let the requests in flight finish when not enabled packages/platform-node/test/adapters/node-adapter.spec.ts:3034 — This test starts work it did not wait for (`response`, still running when the sleep starts) and then orders itself against it with `new Promise(resolve => setTimeout(resolve, 50))` — 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 keep serving when the filter of a %s connection hook throws integration/websockets/e2e/scoped-connection-hook-error.spec.ts:213 — This test starts work it did not wait for (`connectAndClose`, still running when the sleep starts) and then orders itself against it with `new Promise(resolve => setTimeout(resolve, 50))` — 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 take no new request while it is closing integration/microservices/e2e/graceful-shutdown.spec.ts:151 — This test starts work it did not wait for (`closing`, 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.
  • 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.
  • Fixed-sleep synchronisation: should return 503 for NEW queued requests on existing connections during shutdown integration/graceful-shutdown/e2e/node.spec.ts:94 — 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.
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.
R7 · Dead Code · Dead file (~8 LoC) · ×6
  • Dead file (~8 LoC) integration/graphql-schema-first/src/main.ts — no import path from any entry point (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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) · ×6
  • Dead file (~1 LoC) integration/inspector/src/chat/entities/chat.entity.ts — no import path from any entry point (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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/repl/src/users/entities/user.entity.ts — no import path from any entry point (63 application, 5 tooling, 646 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 · ×5
  • 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:107 — // 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.
  • TodoComment integration/send-files/e2e/node.spec.ts:95 — // 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.
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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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
D3 · God Classes · FunctionTooLong · ×4
  • FunctionTooLong: redact.util.createRedactor packages/common/services/utils/redact.util.ts:33 — FunctionTooLong — createRedactor runs 152 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: redact.util.createRedactor.<returned closure> packages/common/services/utils/redact.util.ts:67 — FunctionTooLong — createRedactor.<returned closure> runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: body-parser.createReader packages/platform-node/body-parser/body-parser.ts:360 — FunctionTooLong — createReader runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: body-parser.createReader.reader packages/platform-node/body-parser/body-parser.ts:365 — FunctionTooLong — createReader.reader runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D3 · God Classes · MethodTooLong · ×4
  • MethodTooLong: NodeRouter.dispatch packages/platform-node/router/node-router.ts:497 — MethodTooLong — dispatch runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: RouterExecutionContext.create packages/core/router/router-execution-context.ts:118 — MethodTooLong — create runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: RpcContextCreator.create packages/microservices/context/rpc-context-creator.ts:89 — MethodTooLong — create runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ConfigurableModuleBuilder.createConfigurableModuleCls packages/common/module-utils/configurable-module.builder.ts:205 — MethodTooLong — createConfigurableModuleCls runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
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:70 — 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 7) REDACTED:297 — FastifyAdapter's methods fall into 7 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 7 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:76 — 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.
IC1 · Incompleteness & stubs · Empty method body · ×4
  • Empty method body — does nothing with its inputs packages/testing/services/testing-logger.service.ts:11 — `log` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs packages/testing/services/testing-logger.service.ts:12 — `warn` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs packages/testing/services/testing-logger.service.ts:13 — `debug` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs packages/testing/services/testing-logger.service.ts:14 — `verbose` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
R11 · Import Boundaries · Boundary violation [package · ×4
  • 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:71 — REDACTED:71 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.
  • Boundary violation [package:third-party-deep-import] packages/platform-node/router/utils.ts:1 — packages/platform-node/router/utils.ts:1 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.
D10 · Test Quality · Skipped test · ×3
  • Skipped test: should allow for the client to end the response and be able to make another integration/send-files/e2e/express.spec.ts:108 — 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
  • Skipped test: should allow for the client to end the response and be able to make another integration/send-files/e2e/node.spec.ts:96 — Skipped — switched off by it.skip
IC1 · Incompleteness & stubs · Hollow method · ×3
  • Hollow method — returns a constant without doing the work integration/graphql-code-first/src/recipes/recipes.service.ts:20 — `findOneById` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
  • Hollow method — returns a constant without doing the work integration/graphql-code-first/src/recipes/recipes.service.ts:24 — `findAll` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
  • Hollow method — returns a constant without doing the work 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.
D2 · Cognitive Complexity · ExpressAdapter.applyVersionFilter · ×2
  • ExpressAdapter.applyVersionFilter::handlerForMediaTypeVersioning (cognitive 17) packages/platform-express/adapters/express-adapter.ts:619 — 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:661 — 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.
IC1 · Incompleteness & stubs · Skeleton type · ×2
  • Skeleton type — most members are unfinished integration/graphql-code-first/src/recipes/recipes.service.ts:7 — `RecipesService` has 3 unfinished members out of 4 declared members (methods and accessors, whether or not each carries a body) — a scaffolded class that was never implemented.
  • Skeleton type — most members are unfinished packages/testing/services/testing-logger.service.ts:6 — `TestingLogger` has 4 unfinished members out of 5 declared members (methods and accessors, whether or not each carries a body) — a scaffolded class that was never implemented.
P12 · CI test-gate honesty · Runner config excludes tests no gate runs · ×2
  • Runner config excludes tests no gate runs vitest.config.integration.mts:54 — `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:56 — `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.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×2
  • Outbound HTTP without resilience integration/http-adapters/src/streaming/streaming.module.ts:375 — `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience integration/http-adapters/src/streaming/streaming.module.ts:380 — `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
R10 · Code Duplication · Duplicated block (37 lines × 2 locations) · ×2
  • Duplicated block (37 lines × 2 locations) packages/core/guards/guards-context-creator.ts:20 — packages/core/guards/guards-context-creator.ts:20 · packages/core/pipes/pipes-context-creator.ts:19 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (37 lines × 2 locations) packages/platform-express/multer/interfaces/multer-options.interface.ts:4 — packages/platform-express/multer/interfaces/multer-options.interface.ts:4 · packages/platform-node/multer/interfaces/multer-options.interface.ts:4 — 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 (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.
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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×2
  • Recursive walk over a caller-supplied document has no depth cap packages/microservices/server/server-grpc.ts:1113 — `getServiceNames` is exported, takes a document from its caller (line 211) and hands it to `collectDeepServices`, which calls itself at line 1113 (`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 integration/file-upload/src/upload.module.ts:51 — `createUploadModule` is exported, takes a document from its caller (line 99) and hands it to `describeFiles`, which calls itself at line 51 (`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.
D1 · Cyclomatic Complexity · redact.util.createRedactor.<returned closure> (cyclomatic 42) · ×1
  • redact.util.createRedactor.<returned closure> (cyclomatic 42) packages/common/services/utils/redact.util.ts:67 — redact.util.createRedactor.<returned closure> has cyclomatic complexity 42 (threshold 15). Most of this is not in the body itself: 2 of the 42 points are its own statements and the rest belongs to 8 function items inside it that branch (redactObject, visit, a function literal at line 83, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · ServerGrpc.writeObservableToGrpc (cyclomatic 40) · ×1
  • ServerGrpc.writeObservableToGrpc (cyclomatic 40) packages/microservices/server/server-grpc.ts:503 — ServerGrpc.writeObservableToGrpc has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 1 of the 40 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 581, 509, 555, …). 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 · NodeRouter.dispatch · ×1
  • NodeRouter.dispatch::next (cyclomatic 38) packages/platform-node/router/node-router.ts:527 — NodeRouter.dispatch::next has cyclomatic complexity 38 (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 · RouterResponseController.sse (cyclomatic 36) · ×1
  • RouterResponseController.sse (cyclomatic 36) packages/core/router/router-response-controller.ts:465 — RouterResponseController.sse has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 2 of the 36 points are its own statements and the rest belongs to 16 function literals inside it that branch (lines 605, 687, 539, …). 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:550 — 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 · ParseArrayPipe.transform (cyclomatic 31) · ×1
  • ParseArrayPipe.transform (cyclomatic 31) packages/common/pipes/parse-array.pipe.ts:100 — ParseArrayPipe.transform has cyclomatic complexity 31 (threshold 15). Of this number, 26 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · NodeAdapter.applyVersionFilter (cyclomatic 31) · ×1
  • NodeAdapter.applyVersionFilter (cyclomatic 31) packages/platform-node/adapters/node-adapter.ts:715 — NodeAdapter.applyVersionFilter has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 6 of the 31 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 738, a function literal at line 770, a function literal at line 793, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · RouteTable.find (cyclomatic 30) · ×1
  • RouteTable.find (cyclomatic 30) packages/platform-node/router/route-table.ts:668 — RouteTable.find has cyclomatic complexity 30 (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 · body-parser.createReader.reader (cyclomatic 28) · ×1
  • body-parser.createReader.reader (cyclomatic 28) packages/platform-node/body-parser/body-parser.ts:365 — body-parser.createReader.reader has cyclomatic complexity 28 (threshold 15). Of this number, 14 points are the body's own statements and 14 belong to 6 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · body-parser.urlencoded (cyclomatic 28) · ×1
  • body-parser.urlencoded (cyclomatic 28) packages/platform-node/body-parser/body-parser.ts:758 — body-parser.urlencoded has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 13 of the 28 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 816, decoder, a function literal at line 814). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · 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 · ValidationPipe.transform (cyclomatic 25) · ×1
  • ValidationPipe.transform (cyclomatic 25) packages/common/pipes/validation.pipe.ts:176 — ValidationPipe.transform has cyclomatic complexity 25 (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 · 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 · NodeAdapter.reply (cyclomatic 25) · ×1
  • NodeAdapter.reply (cyclomatic 25) packages/platform-node/adapters/node-adapter.ts:242 — NodeAdapter.reply has cyclomatic complexity 25 (threshold 15). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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 · FastifyAdapter.reply (cyclomatic 24) · ×1
  • FastifyAdapter.reply (cyclomatic 24) REDACTED:842 — FastifyAdapter.reply has cyclomatic complexity 24 (threshold 15). Of this number, 23 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 · utils.isMiddlewareRouteExcluded (cyclomatic 23) · ×1
  • utils.isMiddlewareRouteExcluded (cyclomatic 23) packages/core/middleware/utils.ts:336 — utils.isMiddlewareRouteExcluded has cyclomatic complexity 23 (threshold 15). Of this number, 16 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · create-route-param-metadata.decorator.createParamDecorator.<returned closure>.<returned closure> (cyclomatic 22) · ×1
  • create-route-param-metadata.decorator.createParamDecorator.<returned closure>.<returned closure> (cyclomatic 22) packages/common/decorators/http/create-route-param-metadata.decorator.ts:44 — create-route-param-metadata.decorator.createParamDecorator.<returned closure>.<returned closure> has cyclomatic complexity 22 (threshold 15). Of this number, 18 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · 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 · NodeResponse.sendFile (cyclomatic 21) · ×1
  • NodeResponse.sendFile (cyclomatic 21) packages/platform-node/adapters/node-request.ts:519 — NodeResponse.sendFile has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 574, reportThrown, report). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · RouteTable.add (cyclomatic 21) · ×1
  • RouteTable.add (cyclomatic 21) packages/platform-node/router/route-table.ts:420 — RouteTable.add has cyclomatic complexity 21 (threshold 15). Of this number, 18 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · route-table.toFindMyWayPath (cyclomatic 21) · ×1
  • route-table.toFindMyWayPath (cyclomatic 21) packages/platform-node/router/route-table.ts:292 — route-table.toFindMyWayPath has cyclomatic complexity 21 (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 · ConsoleLogger.stringifyJsonLogObject (cyclomatic 20) · ×1
  • ConsoleLogger.stringifyJsonLogObject (cyclomatic 20) packages/common/services/console-logger.service.ts:789 — ConsoleLogger.stringifyJsonLogObject 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 5 function items inside it that branch (a function literal at line 828, toHolder, hasToJSON, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · FastifyAdapter.constructor (cyclomatic 19) · ×1
  • FastifyAdapter.constructor (cyclomatic 19) REDACTED:442 — 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 526, 578, 590, …). 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.createMiddlewareFactory (cyclomatic 19) · ×1
  • FastifyAdapter.createMiddlewareFactory (cyclomatic 19) REDACTED:1392 — FastifyAdapter.createMiddlewareFactory has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 1398, 1427). 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 · node-request.preferredRedirectType (cyclomatic 18) · ×1
  • node-request.preferredRedirectType (cyclomatic 18) packages/platform-node/adapters/node-request.ts:741 — node-request.preferredRedirectType has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (rank, a function literal at line 747, a function literal at line 778). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · RouteTable.lookup (cyclomatic 18) · ×1
  • RouteTable.lookup (cyclomatic 18) packages/platform-node/router/route-table.ts:597 — RouteTable.lookup has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FileTypeValidator.isValid (cyclomatic 17) · ×1
  • FileTypeValidator.isValid (cyclomatic 17) packages/common/pipes/file/file-type.validator.ts:150 — 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 · ValidationPipe.findNestedBinaryValues (cyclomatic 17) · ×1
  • ValidationPipe.findNestedBinaryValues (cyclomatic 17) packages/common/pipes/validation.pipe.ts:487 — ValidationPipe.findNestedBinaryValues has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Injector.resolveConstructorParams (cyclomatic 17) · ×1
  • Injector.resolveConstructorParams (cyclomatic 17) packages/core/injector/injector.ts:417 — Injector.resolveConstructorParams has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to one function item inside it that branches (resolveParam). 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 · RouterExplorer.applyHostFilter (cyclomatic 17) · ×1
  • RouterExplorer.applyHostFilter (cyclomatic 17) packages/core/router/router-explorer.ts:345 — RouterExplorer.applyHostFilter has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 378, 355, 394). 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.reply (cyclomatic 17) · ×1
  • ExpressAdapter.reply (cyclomatic 17) packages/platform-express/adapters/express-adapter.ts:168 — 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.storeFile (cyclomatic 17) · ×1
  • multipart.parser.storeFile (cyclomatic 17) packages/platform-fastify/multipart/multipart/multipart.parser.ts:203 — multipart.parser.storeFile has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 249, 217, 243, …). 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 · multipart.parser.processMultipart (cyclomatic 17) · ×1
  • multipart.parser.processMultipart (cyclomatic 17) packages/platform-fastify/multipart/multipart/multipart.parser.ts:559 — 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 · RouterExecutionContext.createHandleResponseFn (cyclomatic 16) · ×1
  • RouterExecutionContext.createHandleResponseFn (cyclomatic 16) packages/core/router/router-execution-context.ts:565 — RouterExecutionContext.createHandleResponseFn has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 612, 590, 631, …). 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 · ClientNats.mergeHeaders (cyclomatic 16) · ×1
  • ClientNats.mergeHeaders (cyclomatic 16) packages/microservices/client/client-nats.ts:397 — ClientNats.mergeHeaders has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
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 78) · ×1
  • ParseArrayPipe.transform (cognitive 78) packages/common/pipes/parse-array.pipe.ts:100 — ParseArrayPipe.transform has cognitive complexity 78 (threshold 15). Drivers by points: if/else 19 (42 pts), loops 3 (11 pts), error handling 3 (10 pts), ternaries 2 (9 pts), boolean chains 6 (nesting depth added 45). Of this number, 70 points are the body's own statements and 8 belong to 2 function items inside it that branch. 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 · NodeRouter.dispatch · ×1
  • NodeRouter.dispatch::next (cognitive 77) packages/platform-node/router/node-router.ts:527 — NodeRouter.dispatch::next has cognitive complexity 77 (threshold 15). Drivers by points: if/else 24 (57 pts), error handling 3 (9 pts), boolean chains 5, ternaries 2 (5 pts), loops 1 (nesting depth added 42). 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 · ServerGrpc.writeObservableToGrpc (cognitive 53) · ×1
  • ServerGrpc.writeObservableToGrpc (cognitive 53) packages/microservices/server/server-grpc.ts:503 — ServerGrpc.writeObservableToGrpc has cognitive complexity 53 (threshold 15). Drivers by points: if/else 32 (44 pts), boolean chains 8, loops 1 (nesting depth added 12). None of this is in the body itself: all 53 points belong to 6 function literals inside it that branch (lines 581, 509, 555, …). 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 · NodeAdapter.applyVersionFilter (cognitive 49) · ×1
  • NodeAdapter.applyVersionFilter (cognitive 49) packages/platform-node/adapters/node-adapter.ts:715 — NodeAdapter.applyVersionFilter has cognitive complexity 49 (threshold 15). Drivers by points: if/else 21 (40 pts), boolean chains 9 (nesting depth added 19). Most of this is not in the body itself: 5 of the 49 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 738, a function literal at line 770, a function literal at line 793, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · RouteTable.find (cognitive 43) · ×1
  • RouteTable.find (cognitive 43) packages/platform-node/router/route-table.ts:668 — RouteTable.find has cognitive complexity 43 (threshold 15). Drivers by points: if/else 10 (19 pts), ternaries 5 (10 pts), boolean chains 8, loops 4 (6 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FastifyAdapter.reply (cognitive 34) · ×1
  • FastifyAdapter.reply (cognitive 34) REDACTED:842 — FastifyAdapter.reply has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (25 pts), boolean chains 8, ternaries 1 (nesting depth added 12). Of this number, 30 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NodeAdapter.reply (cognitive 33) · ×1
  • NodeAdapter.reply (cognitive 33) packages/platform-node/adapters/node-adapter.ts:242 — NodeAdapter.reply has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (22 pts), boolean chains 6, ternaries 2 (5 pts) (nesting depth added 10). Of this number, 31 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 · route-table.toFindMyWayPath (cognitive 32) · ×1
  • route-table.toFindMyWayPath (cognitive 32) packages/platform-node/router/route-table.ts:292 — route-table.toFindMyWayPath has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (20 pts), boolean chains 8, match/switch 1 (2 pts), loops 1, ternaries 1 (nesting depth added 13). 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 · 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.processBufferedPackets (cognitive 30) · ×1
  • JsonSocket.processBufferedPackets (cognitive 30) packages/microservices/helpers/json-socket.ts:221 — JsonSocket.processBufferedPackets has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (27 pts), boolean chains 2, 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 29) · ×1
  • RouterExplorer.applyHostFilter (cognitive 29) packages/core/router/router-explorer.ts:345 — RouterExplorer.applyHostFilter has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 2 (5 pts), boolean chains 2, error handling 1 (2 pts), ternaries 2 (nesting depth added 13). Most of this is not in the body itself: 3 of the 29 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 378, 355, 394). 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 · body-parser.urlencoded (cognitive 28) · ×1
  • body-parser.urlencoded (cognitive 28) packages/platform-node/body-parser/body-parser.ts:758 — body-parser.urlencoded has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 9, ternaries 5, error handling 1, loops 1 (nesting depth added 3). Most of this is not in the body itself: 12 of the 28 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 816, decoder, a function literal at line 814). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · ValidationPipe.transform (cognitive 25) · ×1
  • ValidationPipe.transform (cognitive 25) packages/common/pipes/validation.pipe.ts:176 — ValidationPipe.transform has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 8, ternaries 2 (3 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · RouteTable.add (cognitive 25) · ×1
  • RouteTable.add (cognitive 25) packages/platform-node/router/route-table.ts:420 — RouteTable.add has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 4, loops 3 (4 pts), ternaries 3 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · 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:442 — 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 526, 578, 507, …). 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 · NodeResponse.sendFile (cognitive 24) · ×1
  • NodeResponse.sendFile (cognitive 24) packages/platform-node/adapters/node-request.ts:519 — NodeResponse.sendFile has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 4, error handling 1 (2 pts), loops 1 (2 pts), ternaries 1 (nesting depth added 5). Most of this is not in the body itself: 9 of the 24 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 574, report, reportThrown). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · multipart.parser.processMultipart (cognitive 23) · ×1
  • multipart.parser.processMultipart (cognitive 23) packages/platform-fastify/multipart/multipart/multipart.parser.ts:559 — 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 · node-request.preferredRedirectType (cognitive 23) · ×1
  • node-request.preferredRedirectType (cognitive 23) packages/platform-node/adapters/node-request.ts:741 — node-request.preferredRedirectType has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 7 (13 pts), boolean chains 6, if/else 2 (3 pts), loops 1 (nesting depth added 7). Most of this is not in the body itself: 5 of the 23 points are its own statements and the rest belongs to 3 function items inside it that branch (rank, a function literal at line 747, a function literal at line 778). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · body-parser.createReader.reader (cognitive 23) · ×1
  • body-parser.createReader.reader (cognitive 23) packages/platform-node/body-parser/body-parser.ts:365 — body-parser.createReader.reader has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11, boolean chains 6, error handling 3 (4 pts), ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 9 of the 23 points are its own statements and the rest belongs to 6 function items inside it that branch (onEnd, fail, onError, …). 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.
D2 · Cognitive Complexity · redact.util.createRedactor.<returned closure> · ×1
  • redact.util.createRedactor.<returned closure>::redactObject (cognitive 21) packages/common/services/utils/redact.util.ts:187 — redact.util.createRedactor.<returned closure>::redactObject has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 4 (6 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · utils.isMiddlewareRouteExcluded (cognitive 21) · ×1
  • utils.isMiddlewareRouteExcluded (cognitive 21) packages/core/middleware/utils.ts:336 — utils.isMiddlewareRouteExcluded has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (8 pts), ternaries 3 (nesting depth added 2). Of this number, 16 points are the body's own statements and 5 belong to 3 function items inside it that branch. 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 · RouteTable.lookup (cognitive 21) · ×1
  • RouteTable.lookup (cognitive 21) packages/platform-node/router/route-table.ts:597 — RouteTable.lookup has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 3, ternaries 2 (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 · ConsoleLogger.stringifyJsonLogObject (cognitive 20) · ×1
  • ConsoleLogger.stringifyJsonLogObject (cognitive 20) packages/common/services/console-logger.service.ts:789 — ConsoleLogger.stringifyJsonLogObject has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 5 (8 pts), boolean chains 6, if/else 4, error handling 1, loops 1 (nesting depth added 3). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 828, toHolder, hasToJSON, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · FileTypeValidator.isValid (cognitive 20) · ×1
  • FileTypeValidator.isValid (cognitive 20) packages/common/pipes/file/file-type.validator.ts:150 — 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 · RouterResponseController.sse (cognitive 20) · ×1
  • RouterResponseController.sse (cognitive 20) packages/core/router/router-response-controller.ts:465 — RouterResponseController.sse has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11, boolean chains 6, error handling 2, ternaries 1. Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 16 function literals inside it that branch (lines 605, 754, 539, …). 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 · ClientNats.mergeHeaders (cognitive 20) · ×1
  • ClientNats.mergeHeaders (cognitive 20) packages/microservices/client/client-nats.ts:397 — ClientNats.mergeHeaders has cognitive complexity 20 (threshold 15). Drivers by points: loops 5 (9 pts), if/else 5 (7 pts), boolean chains 3, ternaries 1 (nesting depth added 6). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · ExpressAdapter.reply (cognitive 20) · ×1
  • ExpressAdapter.reply (cognitive 20) packages/platform-express/adapters/express-adapter.ts:168 — 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 · WebSocketsController.createRequestScopedEventHandler (cognitive 20) · ×1
  • WebSocketsController.createRequestScopedEventHandler (cognitive 20) packages/websockets/web-sockets-controller.ts:495 — WebSocketsController.createRequestScopedEventHandler has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (10 pts), error handling 2 (4 pts), ternaries 3 (4 pts), boolean chains 2 (nesting depth added 6). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to one function literal inside it that branches (line 511). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · create-route-param-metadata.decorator.createParamDecorator.<returned closure>.<returned closure> (cognitive 19) · ×1
  • create-route-param-metadata.decorator.createParamDecorator.<returned closure>.<returned closure> (cognitive 19) packages/common/decorators/http/create-route-param-metadata.decorator.ts:44 — create-route-param-metadata.decorator.createParamDecorator.<returned closure>.<returned closure> 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). Of this number, 16 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · ClientNats.handleStatusUpdates (cognitive 19) · ×1
  • ClientNats.handleStatusUpdates (cognitive 19) packages/microservices/client/client-nats.ts:156 — 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 · FastifyAdapter.createMiddlewareFactory (cognitive 19) · ×1
  • FastifyAdapter.createMiddlewareFactory (cognitive 19) REDACTED:1392 — FastifyAdapter.createMiddlewareFactory has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, ternaries 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 1398, 1427). 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 · NodeRouter.use (cognitive 19) · ×1
  • NodeRouter.use (cognitive 19) packages/platform-node/router/node-router.ts:369 — NodeRouter.use has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 6 (8 pts), if/else 2 (6 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 8). Of this number, 10 points are the body's own statements and 9 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · 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 · utils.getRawPrefixEnd (cognitive 18) · ×1
  • utils.getRawPrefixEnd (cognitive 18) packages/platform-node/router/utils.ts:228 — utils.getRawPrefixEnd has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (4 pts), boolean chains 3, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · close-array-gaps.util.closeArrayGaps (cognitive 17) · ×1
  • close-array-gaps.util.closeArrayGaps (cognitive 17) packages/common/utils/close-array-gaps.util.ts:47 — close-array-gaps.util.closeArrayGaps has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Injector.resolveConstructorParams (cognitive 17) · ×1
  • Injector.resolveConstructorParams (cognitive 17) packages/core/injector/injector.ts:417 — Injector.resolveConstructorParams has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 6, error handling 2, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to one function item inside it that branches (resolveParam). 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.
D2 · Cognitive Complexity · RouterExecutionContext.createHandleResponseFn (cognitive 17) · ×1
  • RouterExecutionContext.createHandleResponseFn (cognitive 17) packages/core/router/router-execution-context.ts:565 — RouterExecutionContext.createHandleResponseFn has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 4, error handling 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 3). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 612, 590, 667, …). 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 · NestApplication.registerRouter (cognitive 17) · ×1
  • NestApplication.registerRouter (cognitive 17) packages/core/nest-application.ts:237 — NestApplication.registerRouter has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 3 (6 pts), boolean chains 3 (nesting depth added 6). Of this number, 12 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ClientGrpcProxy.createUnaryServiceMethod (cognitive 17) · ×1
  • ClientGrpcProxy.createUnaryServiceMethod (cognitive 17) REDACTED:249 — ClientGrpcProxy.createUnaryServiceMethod has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3 (nesting depth added 7). None of this is in the body itself: all 17 points belong to 5 function literals inside it that branch (lines 263, 253, 290, …). 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:296 — 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 · RouteTable.lookupFallback (cognitive 17) · ×1
  • RouteTable.lookupFallback (cognitive 17) packages/platform-node/router/route-table.ts:817 — RouteTable.lookupFallback has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1, ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WsAdapter.ensureHttpServerExists (cognitive 17) · ×1
  • WsAdapter.ensureHttpServerExists (cognitive 17) REDACTED:616 — WsAdapter.ensureHttpServerExists has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), error handling 2, boolean chains 1, loops 1 (nesting depth added 5). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 2 function items inside it that branch (upgradeListener, a function literal at line 667). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · ValidationPipe.findNestedBinaryValues (cognitive 16) · ×1
  • ValidationPipe.findNestedBinaryValues (cognitive 16) packages/common/pipes/validation.pipe.ts:487 — ValidationPipe.findNestedBinaryValues has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (6 pts), ternaries 2 (5 pts), boolean chains 4, loops 1 (nesting depth added 5). 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 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 · Server.send (cognitive 16) · ×1
  • Server.send (cognitive 16) packages/microservices/server/server.ts:224 — Server.send has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), error handling 1 (3 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 7). None of this is in the body itself: all 16 points belong to 2 function items inside it that branch (a function literal at line 247, scheduleOnNextTick). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · ServerRMQ.matchRmqPattern (cognitive 16) · ×1
  • ServerRMQ.matchRmqPattern (cognitive 16) packages/microservices/server/server-rmq.ts:637 — ServerRMQ.matchRmqPattern has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (6 pts), boolean chains 5, loops 2 (3 pts), ternaries 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · fastify-adapter.hasTextDecodedByRouter (cognitive 16) · ×1
  • fastify-adapter.hasTextDecodedByRouter (cognitive 16) REDACTED:264 — fastify-adapter.hasTextDecodedByRouter has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · utils.hasDecodedText (cognitive 16) · ×1
  • utils.hasDecodedText (cognitive 16) packages/platform-node/router/utils.ts:20 — utils.hasDecodedText has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ViewRenderer.resolveFile (cognitive 16) · ×1
  • ViewRenderer.resolveFile (cognitive 16) packages/platform-node/views/view-renderer.ts:300 — ViewRenderer.resolveFile has cognitive complexity 16 (threshold 15). Drivers by points: if/else 2 (6 pts), error handling 1 (3 pts), loops 2 (3 pts), boolean chains 2, ternaries 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · 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
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
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.
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 10 sibling directories (71 clone groups) · ×1
  • Duplication concentrated across 10 sibling directories (71 clone groups) packages/microservices/context/rpc-context-creator.ts:60 — 71 duplicated blocks under packages/ have copies in at least two of the sibling directories common, core, microservices, platform-express, platform-fastify, platform-node (+4 more sibling(s) not listed) — 56 of them are reported below, and 15 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 71 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 71 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 71 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 (23 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (23 clone groups) packages/microservices/client/client-proxy.ts:213 — 23 duplicated blocks under packages/microservices/ have copies in at least two of the sibling directories client, server — 18 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 23 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 23 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 23 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 8 sibling directories (14 clone groups) · ×1
  • Duplication concentrated across 8 sibling directories (14 clone groups) packages/core/interceptors/interceptors-context-creator.ts:19 — 14 duplicated blocks under packages/core/ have copies in at least two of the sibling directories exceptions, guards, helpers, injector, interceptors, middleware (+2 more sibling(s) not listed) — 11 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 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 14 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 (224 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (224 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:35 — the two spans are one implementation copied and then locally edited — 1104 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 (164 identical lines × 2 files) · ×1
  • Wholesale file copy (164 identical lines × 2 files) packages/platform-express/multer/multer/multer.utils.ts:6 — packages/platform-express/multer/multer/multer.utils.ts:6 · packages/platform-node/multer/multer/multer.utils.ts:6 — these 2 files are line-for-line copies of one another — 164 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 (109 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (109 matched lines × 2 locations) packages/core/interceptors/interceptors-context-creator.ts:19 — packages/core/interceptors/interceptors-context-creator.ts:19 · packages/core/pipes/pipes-context-creator.ts:19 — the two spans are one implementation copied and then locally edited — 577 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 (94 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (94 matched lines × 2 locations) packages/microservices/server/server-nats.ts:47 — packages/microservices/server/server-nats.ts:47 · packages/microservices/server/server-redis.ts:44 — the two spans are one implementation copied and then locally edited — 494 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 (78 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (78 matched lines × 2 locations) packages/microservices/client/client-mqtt.ts:365 — packages/microservices/client/client-mqtt.ts:365 · packages/microservices/client/client-redis.ts:379 — the two spans are one implementation copied and then locally edited — 412 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:567 — packages/core/nest-application.ts:567 · packages/microservices/nest-microservice.ts:218 — 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 × 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-node/multer/multer.module.ts:14 — 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 · Wholesale file copy (61 identical lines × 3 files) · ×1
  • Wholesale file copy (61 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 — 61 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
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 (56 identical lines × 2 files) · ×1
  • Wholesale file copy (56 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 — 56 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 (50 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (50 matched lines × 2 locations) packages/common/serializer/standard-schema-serializer.interceptor.ts:39 — packages/common/serializer/standard-schema-serializer.interceptor.ts:39 · packages/core/router/router-response-controller.ts:185 — the two spans are one implementation copied and then locally edited — 252 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 (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 (48 lines × 2 locations) · ×1
  • Duplicated block (48 lines × 2 locations) packages/platform-express/adapters/express-adapter.ts:180 — packages/platform-express/adapters/express-adapter.ts:180 · packages/platform-node/adapters/node-adapter.ts:265 — 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 (44 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (44 matched lines × 2 locations) packages/microservices/client/client-proxy.ts:213 — packages/microservices/client/client-proxy.ts:213 · packages/microservices/server/server.ts:509 — 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 (43 lines × 3 locations) · ×1
  • Duplicated block (43 lines × 3 locations) packages/core/helpers/external-context-creator.ts:328 — packages/core/helpers/external-context-creator.ts:328 · packages/microservices/context/rpc-context-creator.ts:314 · packages/websockets/context/ws-context-creator.ts:238 — the 3 copies are spread across 3 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 3 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 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 × 3 locations) · ×1
  • Duplicated block (41 lines × 3 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 · packages/platform-node/adapters/utils/get-media-type-version.util.ts:5 — the 3 copies are spread across 3 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 3 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 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:206 — packages/microservices/client/client-nats.ts:206 · packages/microservices/server/server-nats.ts:336 — 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 (39 lines × 3 locations) · ×1
  • Duplicated block (39 lines × 3 locations) packages/platform-node/multer/interceptors/file-fields.interceptor.ts:34 — packages/platform-node/multer/interceptors/file-fields.interceptor.ts:34 · packages/platform-node/multer/interceptors/file.interceptor.ts:32 · packages/platform-node/multer/interceptors/files.interceptor.ts:35 — 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 (38 lines × 3 locations) · ×1
  • Duplicated block (38 lines × 3 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 · packages/platform-express/multer/interceptors/files.interceptor.ts:34 — 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 (37 lines × 3 locations) · ×1
  • Duplicated block (37 lines × 3 locations) packages/platform-express/adapters/utils/on-response-close.util.ts:31 — packages/platform-express/adapters/utils/on-response-close.util.ts:31 · packages/platform-fastify/adapters/utils/on-response-close.util.ts:31 · packages/platform-node/adapters/utils/on-response-close.util.ts:31 — the 3 copies are spread across 3 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 3 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 (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 (33 lines × 2 locations) · ×1
  • Duplicated block (33 lines × 2 locations) packages/core/guards/guards-context-creator.ts:69 — packages/core/guards/guards-context-creator.ts:69 · packages/core/interceptors/interceptors-context-creator.ts:69 — 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 (32 lines × 3 locations) · ×1
  • Duplicated block (32 lines × 3 locations) packages/core/guards/guards-context-creator.ts:118 — packages/core/guards/guards-context-creator.ts:118 · packages/core/interceptors/interceptors-context-creator.ts:117 · packages/core/pipes/pipes-context-creator.ts:109 — the 3 copies are spread across 3 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 3 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 (32 lines × 2 locations) · ×1
  • Duplicated block (32 lines × 2 locations) packages/platform-express/adapters/express-adapter.ts:785 — packages/platform-express/adapters/express-adapter.ts:785 · packages/platform-node/adapters/node-adapter.ts:1044 — 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 (29 lines × 2 locations) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 51, cognitive 55) · ×1
  • Complex function (anonymous) (cyclomatic 51, cognitive 55) packages/platform-node/adapters/node-adapter.ts:578 — (anonymous) has cyclomatic complexity 51 and cognitive complexity 55; 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 next (cyclomatic 38, cognitive 76) · ×1
  • Complex function next (cyclomatic 38, cognitive 76) packages/platform-node/router/node-router.ts:527 — next has cyclomatic complexity 38 and cognitive complexity 76; 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 37, cognitive 40) · ×1
  • Complex function (anonymous) (cyclomatic 37, cognitive 40) REDACTED:1394 — (anonymous) has cyclomatic complexity 37 and cognitive complexity 40; 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 find (cyclomatic 30, cognitive 46) · ×1
  • Complex function find (cyclomatic 30, cognitive 46) packages/platform-node/router/route-table.ts:668 — find has cyclomatic complexity 30 and cognitive complexity 46; 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 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 (anonymous) (cyclomatic 29, cognitive 29) · ×1
  • Complex function (anonymous) (cyclomatic 29, cognitive 29) packages/platform-express/adapters/express-adapter.ts:426 — (anonymous) 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 transform (cyclomatic 26, cognitive 76) · ×1
  • Complex function transform (cyclomatic 26, cognitive 76) packages/common/pipes/parse-array.pipe.ts:100 — transform has cyclomatic complexity 26 and cognitive complexity 76; 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 transform (cyclomatic 25, cognitive 26) · ×1
  • Complex function transform (cyclomatic 25, cognitive 26) packages/common/pipes/validation.pipe.ts:176 — transform has cyclomatic complexity 25 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function 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 toFindMyWayPath (cyclomatic 21, cognitive 32) · ×1
  • Complex function toFindMyWayPath (cyclomatic 21, cognitive 32) packages/platform-node/router/route-table.ts:292 — toFindMyWayPath has cyclomatic complexity 21 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 writeWaitingValues (cyclomatic 21, cognitive 29) · ×1
  • Complex function writeWaitingValues (cyclomatic 21, cognitive 29) packages/microservices/server/server-grpc.ts:581 — writeWaitingValues has cyclomatic complexity 21 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 21, cognitive 21) · ×1
  • Complex function (anonymous) (cyclomatic 21, cognitive 21) packages/microservices/client/client-mqtt.ts:356 — (anonymous) has cyclomatic complexity 21 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 20, cognitive 25) · ×1
  • Complex function (anonymous) (cyclomatic 20, cognitive 25) packages/microservices/client/client-nats.ts:315 — (anonymous) has cyclomatic complexity 20 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 processMultipart (cyclomatic 19, cognitive 25) · ×1
  • Complex function processMultipart (cyclomatic 19, cognitive 25) packages/platform-fastify/multipart/multipart/multipart.parser.ts:559 — 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 add (cyclomatic 18, cognitive 24) · ×1
  • Complex function add (cyclomatic 18, cognitive 24) packages/platform-node/router/route-table.ts:420 — add has cyclomatic complexity 18 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function lookup (cyclomatic 18, cognitive 21) · ×1
  • Complex function lookup (cyclomatic 18, cognitive 21) packages/platform-node/router/route-table.ts:597 — lookup has cyclomatic complexity 18 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 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 stream (cyclomatic 16, cognitive 17) · ×1
  • Complex function stream (cyclomatic 16, cognitive 17) packages/core/router/router-response-controller.ts:287 — stream 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 scanForModules (cyclomatic 16, cognitive 17) · ×1
  • Complex function scanForModules (cyclomatic 16, cognitive 17) packages/core/scanner.ts:122 — 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 findNestedBinaryValues (cyclomatic 15, cognitive 15) · ×1
  • Complex function findNestedBinaryValues (cyclomatic 15, cognitive 15) packages/common/pipes/validation.pipe.ts:487 — findNestedBinaryValues has cyclomatic complexity 15 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function isMiddlewareRouteExcluded (cyclomatic 15, cognitive 15) · ×1
  • Complex function isMiddlewareRouteExcluded (cyclomatic 15, cognitive 15) packages/core/middleware/utils.ts:336 — isMiddlewareRouteExcluded has cyclomatic complexity 15 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function urlencoded (cyclomatic 15, cognitive 14) · ×1
  • Complex function urlencoded (cyclomatic 15, cognitive 14) packages/platform-node/body-parser/body-parser.ts:758 — urlencoded has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function processBufferedPackets (cyclomatic 14, cognitive 30) · ×1
  • Complex function processBufferedPackets (cyclomatic 14, cognitive 30) packages/microservices/helpers/json-socket.ts:221 — processBufferedPackets has cyclomatic complexity 14 and cognitive complexity 30; 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:187 — 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 getRawPrefixEnd (cyclomatic 14, cognitive 20) · ×1
  • Complex function getRawPrefixEnd (cyclomatic 14, cognitive 20) packages/platform-node/router/utils.ts:228 — getRawPrefixEnd has cyclomatic complexity 14 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 (anonymous) (cyclomatic 14, cognitive 20) · ×1
  • Complex function (anonymous) (cyclomatic 14, cognitive 20) packages/websockets/web-sockets-controller.ts:511 — (anonymous) has cyclomatic complexity 14 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 next (cyclomatic 14, cognitive 16) · ×1
  • Complex function next (cyclomatic 14, cognitive 16) packages/microservices/server/server-grpc.ts:698 — next has cyclomatic complexity 14 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 reader (cyclomatic 14, cognitive 9) · ×1
  • Complex function reader (cyclomatic 14, cognitive 9) packages/platform-node/body-parser/body-parser.ts:365 — reader has cyclomatic complexity 14 and cognitive complexity 9; 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 13, cognitive 15) · ×1
  • Complex function (anonymous) (cyclomatic 13, cognitive 15) REDACTED:1398 — (anonymous) has cyclomatic complexity 13 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 transformException (cyclomatic 13, cognitive 14) · ×1
  • Complex function transformException (cyclomatic 13, cognitive 14) packages/platform-fastify/multipart/multipart/multipart.utils.ts:59 — 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 13, cognitive 13) · ×1
  • Complex function (anonymous) (cyclomatic 13, cognitive 13) packages/common/services/console-logger.service.ts:828 — (anonymous) has cyclomatic complexity 13 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function UNKNOWN_DEPENDENCIES_MESSAGE (cyclomatic 13, cognitive 12) · ×1
  • Complex function UNKNOWN_DEPENDENCIES_MESSAGE (cyclomatic 13, cognitive 12) packages/core/errors/messages.ts:63 — UNKNOWN_DEPENDENCIES_MESSAGE has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function getPathFromAbsoluteUrl (cyclomatic 13, cognitive 12) · ×1
  • Complex function getPathFromAbsoluteUrl (cyclomatic 13, cognitive 12) packages/platform-node/router/utils.ts:153 — getPathFromAbsoluteUrl has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 13, cognitive 11) · ×1
  • Complex function (anonymous) (cyclomatic 13, cognitive 11) packages/microservices/server/server-kafka.ts:380 — (anonymous) has cyclomatic complexity 13 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function closeArrayGaps (cyclomatic 12, cognitive 18) · ×1
  • Complex function closeArrayGaps (cyclomatic 12, cognitive 18) packages/common/utils/close-array-gaps.util.ts:47 — closeArrayGaps has cyclomatic complexity 12 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 scanFromPrototype (cyclomatic 12, cognitive 16) · ×1
  • Complex function scanFromPrototype (cyclomatic 12, cognitive 16) packages/core/metadata-scanner.ts:16 — scanFromPrototype has cyclomatic complexity 12 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 serializeContentSecurityPolicy (cyclomatic 12, cognitive 15) · ×1
  • Complex function serializeContentSecurityPolicy (cyclomatic 12, cognitive 15) packages/core/security/security-headers.ts:136 — serializeContentSecurityPolicy has cyclomatic complexity 12 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 2100 lines of code REDACTED:1 — REDACTED has 2100 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: 1928 lines of code packages/core/injector/injector.ts:1 — packages/core/injector/injector.ts has 1928 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/microservices/server/server-grpc.ts · ×1
  • packages/microservices/server/server-grpc.ts: 1126 lines of code packages/microservices/server/server-grpc.ts:1 — packages/microservices/server/server-grpc.ts has 1126 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/platform-node/adapters/node-adapter.ts · ×1
  • packages/platform-node/adapters/node-adapter.ts: 1065 lines of code packages/platform-node/adapters/node-adapter.ts:1 — packages/platform-node/adapters/node-adapter.ts has 1065 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: 930 lines of code packages/common/services/console-logger.service.ts:1 — packages/common/services/console-logger.service.ts has 930 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 · integration/http-adapters/src/streaming/streaming.module.ts · ×1
  • integration/http-adapters/src/streaming/streaming.module.ts: 907 lines of code integration/http-adapters/src/streaming/streaming.module.ts:1 — integration/http-adapters/src/streaming/streaming.module.ts has 907 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-node/router/route-table.ts · ×1
  • packages/platform-node/router/route-table.ts: 860 lines of code packages/platform-node/router/route-table.ts:1 — packages/platform-node/router/route-table.ts has 860 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-node/body-parser/body-parser.ts · ×1
  • packages/platform-node/body-parser/body-parser.ts: 846 lines of code packages/platform-node/body-parser/body-parser.ts:1 — packages/platform-node/body-parser/body-parser.ts has 846 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: 834 lines of code packages/core/scanner.ts:1 — packages/core/scanner.ts has 834 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-node/adapters/node-request.ts · ×1
  • packages/platform-node/adapters/node-request.ts: 802 lines of code packages/platform-node/adapters/node-request.ts:1 — packages/platform-node/adapters/node-request.ts has 802 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: 784 lines of code packages/core/router/router-execution-context.ts:1 — packages/core/router/router-execution-context.ts has 784 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: 783 lines of code packages/platform-express/adapters/express-adapter.ts:1 — packages/platform-express/adapters/express-adapter.ts has 783 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: 753 lines of code packages/websockets/web-sockets-controller.ts:1 — packages/websockets/web-sockets-controller.ts has 753 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: 743 lines of code packages/common/interfaces/http/http-server.interface.ts:1 — packages/common/interfaces/http/http-server.interface.ts has 743 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-response-controller.ts · ×1
  • packages/core/router/router-response-controller.ts: 741 lines of code packages/core/router/router-response-controller.ts:1 — packages/core/router/router-response-controller.ts has 741 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: 704 lines of code packages/core/nest-application.ts:1 — packages/core/nest-application.ts has 704 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/platform-fastify/multipart/multipart/multipart.parser.ts · ×1
  • packages/platform-fastify/multipart/multipart/multipart.parser.ts: 703 lines of code packages/platform-fastify/multipart/multipart/multipart.parser.ts:1 — packages/platform-fastify/multipart/multipart/multipart.parser.ts has 703 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: 686 lines of code packages/microservices/client/client-rmq.ts:1 — packages/microservices/client/client-rmq.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/injector/instance-wrapper.ts · ×1
  • packages/core/injector/instance-wrapper.ts: 683 lines of code packages/core/injector/instance-wrapper.ts:1 — packages/core/injector/instance-wrapper.ts has 683 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: 680 lines of code REDACTED:1 — REDACTED has 680 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/route-conflict-detector.ts · ×1
  • packages/core/router/route-conflict-detector.ts: 661 lines of code packages/core/router/route-conflict-detector.ts:1 — packages/core/router/route-conflict-detector.ts has 661 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: 658 lines of code packages/microservices/server/server-kafka.ts:1 — packages/microservices/server/server-kafka.ts has 658 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/common/pipes/validation.pipe.ts · ×1
  • packages/common/pipes/validation.pipe.ts: 649 lines of code packages/common/pipes/validation.pipe.ts:1 — packages/common/pipes/validation.pipe.ts has 649 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-node/router/node-router.ts · ×1
  • packages/platform-node/router/node-router.ts: 642 lines of code packages/platform-node/router/node-router.ts:1 — packages/platform-node/router/node-router.ts has 642 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/microservices/server/server-rmq.ts · ×1
  • packages/microservices/server/server-rmq.ts: 626 lines of code packages/microservices/server/server-rmq.ts:1 — packages/microservices/server/server-rmq.ts has 626 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: 618 lines of code packages/core/injector/module.ts:1 — packages/core/injector/module.ts has 618 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: 614 lines of code packages/microservices/server/server.ts:1 — packages/microservices/server/server.ts has 614 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/helpers/json-socket.ts · ×1
  • packages/microservices/helpers/json-socket.ts: 571 lines of code packages/microservices/helpers/json-socket.ts:1 — packages/microservices/helpers/json-socket.ts has 571 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: 549 lines of code packages/microservices/client/client-kafka.ts:1 — packages/microservices/client/client-kafka.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/middleware/utils.ts · ×1
  • packages/core/middleware/utils.ts: 546 lines of code packages/core/middleware/utils.ts:1 — packages/core/middleware/utils.ts has 546 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/middleware/route-info-path-extractor.ts · ×1
  • packages/core/middleware/route-info-path-extractor.ts: 542 lines of code packages/core/middleware/route-info-path-extractor.ts:1 — packages/core/middleware/route-info-path-extractor.ts has 542 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/microservices/client/client-mqtt.ts · ×1
  • packages/microservices/client/client-mqtt.ts: 521 lines of code packages/microservices/client/client-mqtt.ts:1 — packages/microservices/client/client-mqtt.ts has 521 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/core/router/router-explorer.ts · ×1
  • packages/core/router/router-explorer.ts: 511 lines of code packages/core/router/router-explorer.ts:1 — packages/core/router/router-explorer.ts has 511 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/interfaces/microservice-configuration.interface.ts · ×1
  • packages/microservices/interfaces/microservice-configuration.interface.ts: 469 lines of code packages/microservices/interfaces/microservice-configuration.interface.ts:1 — packages/microservices/interfaces/microservice-configuration.interface.ts has 469 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/microservices/server/server-tcp.ts · ×1
  • packages/microservices/server/server-tcp.ts: 466 lines of code packages/microservices/server/server-tcp.ts:1 — packages/microservices/server/server-tcp.ts has 466 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 (~70 LoC) · ×1
  • Dead file (~70 LoC) integration/_support/register-local-packages.ts — no import path from any entry point (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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 (63 application, 5 tooling, 646 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.
R8 · Dependency Hygiene · Unused dependency 'fast-json-stringify' · ×1
  • Unused dependency 'fast-json-stringify' — 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 'fastify-plugin' · ×1
  • Unused dependency 'fastify-plugin' — 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 'gulp-clang-format' · ×1
  • Unused dependency 'gulp-clang-format' — 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 'gulp-sourcemaps' · ×1
  • Unused dependency 'gulp-sourcemaps' — 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 'gulp-typescript' · ×1
  • Unused dependency 'gulp-typescript' — 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 'gulp-watch' · ×1
  • Unused dependency 'gulp-watch' — 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 'lerna' · ×1
  • Unused dependency 'lerna' — 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 'markdown-table' · ×1
  • Unused dependency 'markdown-table' — 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 'nats' · ×1
  • Unused dependency 'nats' — 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 'rxjs-compat' · ×1
  • Unused dependency 'rxjs-compat' — 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 'uuid' · ×1
  • Unused dependency 'uuid' — 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 — 367 finding(s)
D10 · Test Quality · Mock-dominated test · ×171
  • 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:592 — 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:914 — 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:1134 — 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 resolve the exception filters of a default-scoped gateway in the static context packages/websockets/test/web-sockets-controller.spec.ts:1183 — This test sets up 3 test doubles (for example `vi .spyOn`) 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 create its enhancers in the context of the connection before its filters handle the error packages/websockets/test/web-sockets-controller.spec.ts:1240 — 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 close a client instead of handling it until clients are accepted packages/websockets/test/web-sockets-controller.spec.ts:1644 — This test sets up 4 test doubles (for example `vi .spyOn`) against 0 real object(s) of its own, and its only verification is 7 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:1966 — 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 terminate a client that can be terminated (ws) packages/websockets/test/adapters/ws-adapter.spec.ts:16 — This test sets up 3 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 close the underlying connection of a client that has one (socket.io) packages/websockets/test/adapters/ws-adapter.spec.ts:24 — This test sets up 4 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 close a client once more than "maxSendBufferSize" bytes are queued for it packages/platform-ws/test/ws-adapter.spec.ts:408 — 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:425 — 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:440 — 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 disconnect a client with more than "maxWaitingMessages" messages of an event waiting packages/platform-socket.io/test/io-adapter.spec.ts:122 — This test sets up 3 test doubles (for example `vi .spyOn`) against 1 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should let 10000 messages of an event wait by default packages/platform-socket.io/test/io-adapter.spec.ts:144 — 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 disconnect the client without handling the message packages/platform-socket.io/test/io-adapter.spec.ts:207 — This test sets up 3 test doubles (for example `vi .spyOn`) 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 register only one disconnect listener regardless of call count packages/platform-socket.io/test/io-adapter.spec.ts:233 — 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 let a sibling wildcard take the request packages/platform-node/test/router/node-router.spec.ts:541 — This test sets up 3 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 not let a route with an empty parameter skip its middleware packages/platform-node/test/router/node-router.spec.ts:740 — This test sets up 3 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 not match "//" with the route %s, as its middleware does not packages/platform-node/test/router/node-router.spec.ts:753 — This test sets up 3 test doubles (for example `vi.fn`) against 0 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 pass a malformed URL to the error handlers as a URIError packages/platform-node/test/router/node-router.spec.ts:933 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 6 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:169 — 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:221 — 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 fall back to the static filters when the filters fail to resolve packages/microservices/test/listeners-controller.spec.ts:362 — This test sets up 3 test doubles (for example `vi.spyOn`) against 2 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should 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.
  • + 146 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×40
  • Duplicated predicate packages/core/exceptions/external-exception-filter-context.ts:71 — `!!host && this.isInstantiated(wrapper, host)` appears character-identically in 2 files — packages/core/exceptions/external-exception-filter-context.ts, packages/core/router/router-exception-filters.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:85 — `!(active < concurrent) && !(waiting < maxWaiting)` 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/platform-express/multer/multer/multer.utils.ts:294 — `!error || error instanceof HttpException` appears character-identically in 3 files — packages/platform-express/multer/multer/multer.utils.ts, packages/platform-fastify/multipart/multipart/multipart.utils.ts, packages/platform-node/multer/multer/multer.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/core/helpers/context-creator.ts:86 — `!instanceWrapper.isTransient && instanceWrapper.isDependencyTreeDurable()` appears character-identically in 2 files — packages/core/helpers/context-creator.ts, packages/core/injector/injector.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:220 — `'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:130 — `(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:599 — `(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/platform-express/multer/multer/multer.utils.ts:228 — `Array.isArray(container) && values.length < container.length` appears character-identically in 3 files — packages/platform-express/multer/multer/multer.utils.ts, packages/platform-fastify/multipart/multipart/append-field.util.ts, packages/platform-node/multer/multer/multer.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-express/adapters/express-adapter.ts:600 — `Array.isArray(extractedVersion) && extractedVersion.includes(version)` appears character-identically in 2 files — packages/platform-express/adapters/express-adapter.ts, packages/platform-node/adapters/node-adapter.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/common/utils/map-streaming-body.util.ts:61 — `ArrayBuffer.isView(value) || types.isAnyArrayBuffer(value)` appears character-identically in 2 files — packages/common/utils/map-streaming-body.util.ts, packages/core/router/streaming-body.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/utils/extend-metadata.util.ts:37 — `arg.index !== index || arg !== inherited[argKey]` appears character-identically in 3 files — packages/common/utils/extend-metadata.util.ts, packages/microservices/utils/get-param-args-metadata.util.ts, packages/websockets/utils/get-param-args-metadata.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/platform-express/adapters/express-adapter.ts:215 — `body instanceof Error && response.statusCode >= HttpStatus.BAD_REQUEST` appears character-identically in 2 files — packages/platform-express/adapters/express-adapter.ts, packages/platform-node/adapters/node-adapter.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/microservices/client/client-kafka.ts:123 — `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:128 — `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:129 — `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/platform-express/adapters/express-adapter.ts:703 — `error instanceof SyntaxError || error instanceof URIError` appears character-identically in 2 files — packages/platform-express/adapters/express-adapter.ts, packages/platform-node/adapters/node-adapter.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/core/helpers/external-context-creator.ts:191 — `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:49 — `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:712 — `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.
  • + 15 more in this group — see findings.md.
X4 · Structured logging · Interpolated log message defeats structured logging · ×40
  • Interpolated log message defeats structured logging packages/websockets/socket-server-provider.ts:74 — `log` at line 74 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/websockets/socket-server-provider.ts:149 — `warn` at line 149 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/websockets/web-sockets-controller.ts:627 — `error` at line 627 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:783 — `log` at line 783 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:377 — `warn` at line 377 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 REDACTED:557 — `warn` at line 557 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 REDACTED:2057 — `warn` at line 2057 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-grpc.ts:564 — `warn` at line 564 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:414 — `error` at line 414 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:448 — `error` at line 448 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:456 — `error` at line 456 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:461 — `error` at line 461 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:301 — `error` at line 301 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:307 — `error` at line 307 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:329 — `log` at line 329 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:339 — `log` at line 339 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:355 — `log` at line 355 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-rmq.ts:371 — `warn` at line 371 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-rmq.ts:435 — `error` at line 435 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-kafka.ts:314 — `error` at line 314 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:327 — `error` 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.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:164 — `error` at line 164 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:176 — `error` at line 176 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:191 — `log` at line 191 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:202 — `debug` at line 202 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.
  • + 15 more in this group — see findings.md.
D12 · Dependency Hygiene · Deprecated · ×22
  • Deprecated: @npmcli/move-file REDACTED:3322 — @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:3337 — 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:3372 — 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:7354 — 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:11010 — 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:11244 — 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:11689 — 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:11950 — 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:12500 — 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:13572 — 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:13771 — 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:13816 — 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:14755 — 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:18075 — 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:18156 — 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:18257 — 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:18324 — 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:18338 — 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:19022 — 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:19216 — 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:19228 — 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:20933 — 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:463 — `packages/common/services/console-logger.service.ts` reports through `console.*` at line 463 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:465 — `packages/common/services/console-logger.service.ts` reports through `console.*` at line 465 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:491 — `packages/common/services/console-logger.service.ts` reports through `console.*` at line 491 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:493 — `packages/common/services/console-logger.service.ts` reports through `console.*` at line 493 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:729 — `packages/common/services/console-logger.service.ts` reports through `console.*` at line 729 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:234 — `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.)
D27 · Navigability · Pass-through layer · ×11
  • Pass-through layer integration/inspector/src/request-chain/request-chain.controller.ts:6 — RequestChainController: its one public method forwards its arguments unchanged to chainService, in a chain of such forwarders, and adds no behaviour — an extra hop to trace through. Call chainService directly, or give the layer a job.
  • Pass-through layer integration/inspector/src/request-chain/request-chain.service.ts:5 — RequestChainService: its one public method forwards its arguments unchanged to helperService, in a chain of such forwarders, and adds no behaviour — an extra hop to trace through. Call helperService directly, or give the layer a job.
  • Pass-through layer integration/scopes/src/request-chain/request-chain.controller.ts:6 — RequestChainController: its one public method forwards its arguments unchanged to chainService, in a chain of such forwarders, and adds no behaviour — an extra hop to trace through. Call chainService directly, or give the layer a job.
  • Pass-through layer integration/scopes/src/request-chain/request-chain.service.ts:5 — RequestChainService: its one public method forwards its arguments unchanged to helperService, in a chain of such forwarders, and adds no behaviour — an extra hop to trace through. Call helperService directly, or give the layer a job.
  • Pass-through layer integration/send-files/src/app.controller.ts:7 — AppController: all 9 public methods forward their arguments unchanged to appService and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call appService directly, or give the layer a job.
  • Pass-through layer integration/typeorm/src/photo/photo.controller.ts:6 — PhotoController: all 2 public methods forward their arguments unchanged to photoService and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call photoService directly, or give the layer a job.
  • Pass-through layer sample/05-sql-typeorm/src/users/users.controller.ts:15 — UsersController: all 4 public methods forward their arguments unchanged to usersService and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call usersService directly, or give the layer a job.
  • Pass-through layer sample/06-mongoose/src/cats/cats.controller.ts:8 — CatsController: all 5 public methods forward their arguments unchanged to catsService and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call catsService directly, or give the layer a job.
  • Pass-through layer sample/07-sequelize/src/users/users.controller.ts:7 — UsersController: all 4 public methods forward their arguments unchanged to usersService and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call usersService directly, or give the layer a job.
  • Pass-through layer sample/13-mongo-typeorm/src/photo/photo.controller.ts:6 — PhotoController: its one public method forwards its arguments unchanged to photoService, in a chain of such forwarders, and adds no behaviour — an extra hop to trace through. Call photoService directly, or give the layer a job.
  • Pass-through layer sample/13-mongo-typeorm/src/photo/photo.service.ts:7 — PhotoService: its one public method forwards its arguments unchanged to photoRepository, in a chain of such forwarders, and adds no behaviour — an extra hop to trace through. Call photoRepository directly, or give the layer a job.
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 · ×8
  • 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/packet-metadata-kafka.spec.ts:57 — 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:108 — 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.
  • Disabled test integration/send-files/e2e/node.spec.ts:96 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
X7 · Silent fallback defaults · Silent fallback default in catch · ×7
  • 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/utils.ts:165 — `mapToServedRoutes` 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:147 — `extractControllerRoutesCoveredBy` 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:292 — `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-logger.ts:18 — `stringifyLogEntry` swallows every exception into `return '[unserializable log entry]'` — 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:229 — `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.
  • Silent fallback default in catch packages/platform-node/router/utils.ts:97 — `getLiteralPrefix` 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.
D24 · Comment Value · redundant comment · ×6
  • redundant comment integration/hello-world/e2e/force-console.spec.ts:49 — "Verify console.log was called with the message" repeats the code it sits on: 4 of its 5 words (console, log, called, message) are already in `const consoleLogCalls = consoleLogSpy.mock.calls.filter(args =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment integration/hello-world/e2e/force-console.spec.ts:62 — "Verify console.error was called with the message" repeats the code it sits on: 4 of its 5 words (console, error, called, message) are already in `const consoleErrorCalls = consoleErrorSpy.mock.calls.filter(args =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment integration/microservices/e2e/concurrent-kafka.spec.ts:206 — "close the controller clients" repeats the code it sits on: 3 of its 3 words (close, controller, clients) are already in `await controller.client.close();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment integration/microservices/e2e/concurrent-kafka.spec.ts:249 — "connect the controller client" repeats the code it sits on: 3 of its 3 words (connect, controller, client) are already in `await controller.client.connect();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/common/pipes/file/file-type.validator.ts:157 — "Skip magic number validation if set" repeats the code it sits on: 4 of its 5 words (skip, magic, number, validation) are already in `if (this.validationOptions.skipMagicNumbersValidation)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/platform-fastify/test/adapters/fastify-adapter.spec.ts:381 — "The chunk first, last and in between" repeats the code it sits on: 3 of its 3 words (chunk, first, last) are already in `const sources = [`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
AX6 · Interface segregation · Fat interface · ×3
  • Fat interface: HttpServer (36 required operations) packages/common/interfaces/http/http-server.interface.ts:218 — `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.
IC1 · Incompleteness & stubs · Empty method body · ×2
  • Empty method body integration/http-adapters/src/streaming/streaming.module.ts:48 — `openGate` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body integration/http-adapters/src/wrapped-send/wrapped-send.module.ts:57 — `remove` has an empty body — confirm it's an intentional no-op and not an unfinished method.
C2 · Access Controls · No named authorization policies · ×1
  • No named authorization policies packages/core/nest-application.ts:684 — 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, 33 significant file(s) lose their only recent owner: packages/platform-fastify/multipart/multipart/multipart.parser.ts, packages/core/helpers/external-context-creator.ts, packages/common/services/utils/redact.util.ts, packages/microservices/client/client-proxy.ts, packages/websockets/socket-server-provider.ts, packages/common/serializer/standard-schema-serializer.interceptor.ts, packages/microservices/utils/transform-pattern.utils.ts, packages/websockets/socket-module.ts (+25 more). Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 2 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 (35 single-owned of 219 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; 219 of the 1184 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)), anonymized user #3 (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/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 11 project(s) overshoot their size bounds, lowering Project Cohesion to 4.5/10. The most over is `packages/core` (21333 LoC, 232 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 220 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; 220 of the 1184 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 · Type-only dependency 'light-my-request' in production deps · ×1
  • Type-only dependency 'light-my-request' in production deps packages/platform-node/adapters/node-adapter.ts:35 — Every import is type-only — 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 — 42/82 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 (`!`) override strict null checking · ×1
  • Null assertions (`!`) override strict null checking — ~4.4 `!` null assertions per 1k TypeScript source lines — 378 assertion(s) across the 86098 source line(s) of the 1156 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. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Minor — 140 finding(s)
D10 · Test Quality · Skipped (documented) · ×122
  • Skipped (documented): (unnamed test) packages/websockets/test/gateway-metadata-explorer.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/websockets/test/utils/param.utils.spec.ts:15 — 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/utils/param.utils.spec.ts:18 — 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/utils/param.utils.spec.ts:15 — 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/utils/param.utils.spec.ts:18 — 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
  • + 97 more in this group — see findings.md.
D12 · Dependency Hygiene · Outdated (npm) · ×13
  • Outdated (npm): @fastify/cors — @fastify/cors is pinned at 11.4.1; registry.npmjs.org publishes 11.4.3 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): @nestjs/common — @nestjs/common is pinned at 12.4.2; registry.npmjs.org publishes 12.5.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): @nestjs/core — @nestjs/core is pinned at 12.4.1; registry.npmjs.org publishes 12.5.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): @nestjs/platform-express — @nestjs/platform-express is pinned at 12.4.1; registry.npmjs.org publishes 12.5.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): @nestjs/platform-fastify — @nestjs/platform-fastify is pinned at 12.4.1; registry.npmjs.org publishes 12.5.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): @nestjs/platform-node — @nestjs/platform-node is pinned at 12.4.1; registry.npmjs.org publishes 12.5.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): content-type — content-type is pinned at 2.1.0; registry.npmjs.org publishes 3.1.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): cookie — cookie is pinned at 0.7.2; registry.npmjs.org publishes 2.0.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): encodeurl — encodeurl is pinned at 2.0.1; registry.npmjs.org publishes 3.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): fast-json-stringify — fast-json-stringify is pinned at 7.3.4; registry.npmjs.org publishes 7.3.5 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.
  • Outdated (npm): type-is — type-is is pinned at 2.1.0; registry.npmjs.org publishes 3.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): ws — ws is pinned at 8.22.1; registry.npmjs.org publishes 8.23.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.
D24 · Comment Value · doc comments repeat the names · ×5
  • doc comments repeat the names packages/common/file-stream/interfaces/streamable-options.interface.ts:2 — 3 of 189 documented parameters and 10 of 661 summaries in `@nestjs/common` only repeat the member or parameter name (e.g. "Options for `StreamableFile`" for `StreamableFileOptions`). 3 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/core/discovery/discoverable-meta-host-collection.ts:36 — 5 of 107 documented parameters and 0 of 486 summaries in `@nestjs/core` only repeat the member or parameter name (e.g. "The metadata key." for `metadataKey`). 9 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/microservices/ctx-host/kafka.context.ts:35 — 0 of 58 documented parameters and 3 of 301 summaries in `@nestjs/microservices` only repeat the member or parameter name (e.g. "Returns the partition." for `getPartition`). 5 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/platform-express/multer/interceptors/any-files.interceptor.ts:25 — 0 of 10 documented parameters and 0 of 75 summaries in `@nestjs/platform-express` only repeat the member or parameter name (e.g. "" for `localOptions`). 9 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/platform-node/interfaces/node-adapter-options.interface.ts:15 — 0 of 12 documented parameters and 2 of 234 summaries in `@nestjs/platform-node` only repeat the member or parameter name (e.g. "Options of the `NodeAdapter` (`new NodeAdapter(options)`)." for `NodeAdapterOptions`). 9 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-86ccf4fd78ff492a826e791143005ffc/history.json --exit-code 0 --source .1artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-86ccf4fd78ff492a826e791143005ffc/tree.json --exit-code 0 --source .1artifacts/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/canine-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 .19artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .26artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .8artifacts/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 Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1d959-006a-7e4a-b0ee-7bf945ea8e52 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

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

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