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

raouf-b-dev/ecommerce-store-api

Measured 22 October 2026, 14:25 UTC, at code version 0bc71a5

CAI score 53out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Down 8 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.

Performance 100 Exemplary Domain Modelling 70 Adequate Security and Compliance 69 Adequate Architecture 59 Adequate Maturity 55 Adequate Code Health 54 Adequate Production Readiness 48 Adequate

A medium codebase: 48,746 lines of product code in 1 project, tests not counted · Estimated rebuild effort: about 0.8 person-years · Weakest lens: Production Readiness, 48

Findings by how serious they are

29 critical 558 serious 131 minor

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

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 14:25 UTC

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

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

86of 92 dimensions measured by tools. The other 6 are advisory notes from an AI model, which explain the code but don't count towards the score.
690of 718 findings point to an exact file and line, so you can open each one in the code. The other 28 concern the repository as a whole, such as missing documentation.
92dimensions across 7 lenses, read from 48,746 lines of product code in 1 project.
Chapters

Executive summary

raouf-b-dev/ecommerce-store-api scores 53 out of 100 and is rated Adequate, while six of its seven lenses score higher still: Performance at 100, rated Exemplary, and Domain Modelling at 70, Security and Compliance at 69, Architecture at 59, Maturity at 55 and Code Health at 54, all rated Adequate. The project hasn't declared a stable release yet, so its lenses are rated against a lower bar than a released product's, while the score itself is worked out as for any repository.

The score is lower than those six because the weakest lens counts most, and here that is Production Readiness, which scores 48 and is rated Adequate. Its REDACTED Scanning dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 3 Leaked secret finding(s) in REDACTED Scanning and to resolve the 5 Deprecated finding(s) in Dependency Hygiene, and if Production Readiness rose to 70, the score would rise from 53 to about 58.

29 findings are critical: seven in Circular Imports, six in Secrets (history), five in Change Coupling, four in Dependency Hygiene, three in REDACTED Scanning, one in ADR Conformance, one in Dependency Vulnerabilities, one in IaC & Container Security and one in Static Analysis (SAST).

Watchdog couldn't measure 4 dimensions in this code, among them Internal API Consistency, Navigability and Web-Security Posture, so they are left out of the score. The product code is 48,746 lines, which would take an estimated 0.8 person-years, around €110,000, to rebuild.

Code Health 54 Adequate, capped by Structured logging and Nullable reference types Architecture 59 Adequate, capped by Project Cohesion and Circular Imports Maturity 55 Adequate, capped by Documentation accuracy Production Readiness 48 Adequate, capped by REDACTED Scanning, Dependency Hygiene and Security & performance tooling Security and Compliance 69 Adequate, capped by Static Analysis (SAST) Domain Modelling 70 Adequate, capped by Strongly-typed ids Performance 100 ★ Exemplary

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

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 48 · counts for 46%Code Health 54 · counts for 25%Maturity 55 · counts for 14%Architecture 59 · counts for 8%Security and Compliance 69 · counts for 4%Domain Modelling 70 · counts for 2%Performance 100 · counts for 1%

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

Code composition: what the lines of code are
Product code 58%Tests 42%
New since the last survey: 194 findings

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

  • Cyclomatic Complexity · generate-envs.generateEnvs (cyclomatic 26) scripts/generate-envs.js
  • Cyclomatic Complexity · ascii-prose.findComments::skipString (cyclomatic 23) scripts/ascii-prose.cjs
  • Cyclomatic Complexity · agent-output.selectVitestCommands (cyclomatic 22) scripts/agent-output.mjs
  • Cyclomatic Complexity · ascii-prose.collectFiles::walk (cyclomatic 22) scripts/ascii-prose.cjs
  • Cyclomatic Complexity · CreatePaymentUseCase.execute (cyclomatic 16) src/modules/payments/core/application/usecases/create-payment/create-payment.usecase.ts
  • Cyclomatic Complexity · CreatePaymentIntentUseCase.execute (cyclomatic 16) src/modules/payments/core/application/usecases/create-payment-intent/create-payment-intent.usecase.ts
  • Cognitive Complexity · generate-envs.generateEnvs (cognitive 44) scripts/generate-envs.js
  • Cognitive Complexity · ascii-prose.findComments::skipString (cognitive 36) scripts/ascii-prose.cjs
  • Cognitive Complexity · ascii-prose.collectFiles::walk (cognitive 32) scripts/ascii-prose.cjs
  • Cognitive Complexity · agent-output.selectVitestCommands (cognitive 21) scripts/agent-output.mjs
  • Cognitive Complexity · SweepExpiredReservationsUseCase.execute (cognitive 21) src/modules/inventory/core/application/usecases/sweep-expired-reservations/sweep-expired-reservations.usecase.ts
  • Cognitive Complexity · CreatePaymentIntentUseCase.execute (cognitive 20) src/modules/payments/core/application/usecases/create-payment-intent/create-payment-intent.usecase.ts
  • Cognitive Complexity · money-decimal.minorUnitsFromDecimal (cognitive 16) src/shared-kernel/domain/value-objects/money-decimal.ts
  • Cognitive Complexity · UpdateProductUseCase.execute (cognitive 16) src/modules/products/core/application/usecases/update-product/update-product.usecase.ts
  • Code Coverage · Low coverage: src/config/config.module.ts src/config/config.module.ts
  • Code Coverage · Low coverage: src/config/resolve-env-file-path.ts src/config/resolve-env-file-path.ts
  • Code Coverage · Low coverage: src/infrastructure/infrastructure.module.ts src/infrastructure/infrastructure.module.ts
  • Code Coverage · Low coverage: src/infrastructure/database/database.module.ts src/infrastructure/database/database.module.ts
  • Code Coverage · Low coverage: src/infrastructure/demo/secondary-adapters/adapters/demo-seed-runner.adapter.ts src/infrastructure/demo/secondary-adapters/adapters/demo-seed-runner.adapter.ts
  • Code Coverage · Low coverage: src/infrastructure/health/indicators/process.health-indicator.ts src/infrastructure/health/indicators/process.health-indicator.ts
  • Code Coverage · Low coverage: src/infrastructure/health/indicators/redis.health-indicator.ts src/infrastructure/health/indicators/redis.health-indicator.ts
  • Code Coverage · Low coverage: src/infrastructure/health/indicators/websocket.health-indicator.ts src/infrastructure/health/indicators/websocket.health-indicator.ts
  • Code Coverage · Low coverage: src/infrastructure/metrics/metrics.controller.ts src/infrastructure/metrics/metrics.controller.ts
  • Code Coverage · Low coverage: src/infrastructure/metrics/listeners/business-metrics.listener.ts src/infrastructure/metrics/listeners/business-metrics.listener.ts
  • Code Coverage · Low coverage: src/infrastructure/queue/bullmq-connection.module.ts src/infrastructure/queue/bullmq-connection.module.ts
  • Code Coverage · Low coverage: src/infrastructure/queue/queue.module.ts src/infrastructure/queue/queue.module.ts
  • Code Coverage · Low coverage: src/infrastructure/redis/redis.service.ts src/infrastructure/redis/redis.service.ts
  • Code Coverage · Low coverage: src/infrastructure/throttler/throttler.module.ts src/infrastructure/throttler/throttler.module.ts
  • Code Coverage · Low coverage: src/interceptors/result.interceptor.ts src/interceptors/result.interceptor.ts
  • Code Coverage · Low coverage: src/modules/analytics/primary-adapters/dto/inventory-alerts-query.dto.ts src/modules/analytics/primary-adapters/dto/inventory-alerts-query.dto.ts
  • Code Coverage · Low coverage: src/modules/analytics/primary-adapters/dto/top-products-query.dto.ts src/modules/analytics/primary-adapters/dto/top-products-query.dto.ts
  • Code Coverage · Low coverage: src/modules/authentication/core/application/usecases/revoke-all-for-user/revoke-all-for-user.usecase.ts src/modules/authentication/core/application/usecases/revoke-all-for-user/revoke-all-for-user.usecase.ts
  • Code Coverage · Low coverage: src/modules/authentication/secondary-adapters/services/bcrypt.service.ts src/modules/authentication/secondary-adapters/services/bcrypt.service.ts
  • Code Coverage · Low coverage: src/modules/authorization/authorization.module.ts src/modules/authorization/authorization.module.ts
  • Code Coverage · Low coverage: src/modules/carts/carts.module.ts src/modules/carts/carts.module.ts
  • Code Coverage · Low coverage: src/modules/carts/secondary-adapters/adapters/module-inventory.gateway.ts src/modules/carts/secondary-adapters/adapters/module-inventory.gateway.ts
  • Code Coverage · Low coverage: src/modules/carts/testing/mocks/inventory-gateway.mock.ts src/modules/carts/testing/mocks/inventory-gateway.mock.ts
  • Code Coverage · Low coverage: src/modules/carts/testing/mocks/product-gateway.mock.ts src/modules/carts/testing/mocks/product-gateway.mock.ts
  • Code Coverage · Low coverage: src/modules/identity/identity.module.ts src/modules/identity/identity.module.ts
  • Code Coverage · Low coverage: src/modules/identity/secondary-adapters/adapters/module-authorization.gateway.ts src/modules/identity/secondary-adapters/adapters/module-authorization.gateway.ts
  • Code Coverage · Low coverage: src/modules/inventory/inventory.module.ts src/modules/inventory/inventory.module.ts
  • Code Coverage · Low coverage: src/modules/inventory/core/application/usecases/get-order-reservations/get-order-reservations.usecase.ts src/modules/inventory/core/application/usecases/get-order-reservations/get-order-reservations.usecase.ts
  • Code Coverage · Low coverage: src/modules/notifications/notifications.controller.ts src/modules/notifications/notifications.controller.ts
  • Code Coverage · Low coverage: src/modules/notifications/primary-adapters/dto/get-user-notifications.dto.ts src/modules/notifications/primary-adapters/dto/get-user-notifications.dto.ts
  • Code Coverage · Low coverage: src/modules/orders/orders.module.ts src/modules/orders/orders.module.ts
  • Code Coverage · Low coverage: src/modules/orders/core/application/usecases/clear-checkout-cart/clear-checkout-cart.usecase.ts src/modules/orders/core/application/usecases/clear-checkout-cart/clear-checkout-cart.usecase.ts
  • Code Coverage · Low coverage: src/modules/orders/core/application/usecases/confirm-checkout-reservation/confirm-checkout-reservation.usecase.ts src/modules/orders/core/application/usecases/confirm-checkout-reservation/confirm-checkout-reservation.usecase.ts
  • Code Coverage · Low coverage: src/modules/orders/core/application/usecases/reserve-stock-for-checkout/reserve-stock-for-checkout.usecase.ts src/modules/orders/core/application/usecases/reserve-stock-for-checkout/reserve-stock-for-checkout.usecase.ts
  • Code Coverage · Low coverage: src/modules/orders/primary-adapters/dto/shipping-address.dto.ts src/modules/orders/primary-adapters/dto/shipping-address.dto.ts
  • Code Coverage · Low coverage: src/modules/payments/payments.module.ts src/modules/payments/payments.module.ts
  • Code Coverage · Low coverage: src/modules/payments/core/domain/value-objects/refund-status.ts src/modules/payments/core/domain/value-objects/refund-status.ts
  • Code Coverage · Low coverage: src/modules/payments/primary-adapters/dto/list-payments-query.dto.ts src/modules/payments/primary-adapters/dto/list-payments-query.dto.ts
  • Code Coverage · Low coverage: src/modules/products/products.module.ts src/modules/products/products.module.ts
  • Code Coverage · Low coverage: src/modules/products/primary-adapters/dto/list-products-query.dto.ts src/modules/products/primary-adapters/dto/list-products-query.dto.ts
  • Code Coverage · Low coverage: src/modules/products/secondary-adapters/config/env-supported-currencies.adapter.ts src/modules/products/secondary-adapters/config/env-supported-currencies.adapter.ts
  • Code Coverage · Low coverage: src/modules/products/testing/factories/create-product-input.factory.ts src/modules/products/testing/factories/create-product-input.factory.ts
  • Test Quality · No assertions: returns a failure Result for an unknown currency code src/infrastructure/platform/get-platform-config.query.spec.ts
  • Test Quality · No assertions: returns unauthorized when the refresh token signature is invalid src/modules/authentication/core/application/usecases/refresh-token/refresh-token.usecase.spec.ts
  • Test Quality · No assertions: should return failure if user role assignment not found src/modules/authorization/core/application/usecases/user-role/find-role-by-user-id.usecase.spec.ts
  • Test Quality · No assertions: returns a failure when line items use different currencies src/modules/carts/core/application/mappers/cart-presentation.mapper.spec.ts
  • Test Quality · No assertions: returns failure when repository fails to find expired reservations src/modules/inventory/core/application/usecases/sweep-expired-reservations/sweep-expired-reservations.usecase.spec.ts
  • Test Quality · No assertions: rejects release when in CONFIRMED status src/modules/inventory/core/domain/entities/reservation.spec.ts
  • Test Quality · No assertions: rejects when not confirmed src/modules/inventory/core/domain/entities/reservation.spec.ts
  • Test Quality · No assertions: should fail if inventory not found src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.spec.ts
  • Test Quality · No assertions: should fail if insufficient stock src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.spec.ts
  • Test Quality · No assertions: should return failure if not found src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.spec.ts
  • Test Quality · No assertions: should fail if reservation status in DB is not PENDING src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.spec.ts
  • Test Quality · No assertions: should fail if reservation in DB is expired src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.spec.ts
  • Test Quality · No assertions: should fail if reservation status in DB is not PENDING src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.spec.ts
  • Test Quality · No assertions: should return infrastructure error when queue fails src/modules/inventory/secondary-adapters/schedulers/bullmq-inventory.scheduler.spec.ts
  • Test Quality · No assertions: should return infrastructure error when queue fails src/modules/inventory/secondary-adapters/schedulers/bullmq-inventory.scheduler.spec.ts
  • Test Quality · No assertions: fails when the saved payment has no id src/modules/orders/secondary-adapters/adapters/module-payment.gateway.spec.ts
  • Test Quality · No assertions: returns infrastructure error when getCartUseCase fails src/modules/orders/secondary-adapters/adapters/module-cart.gateway.spec.ts
  • Test Quality · No assertions: returns infrastructure error when cart item has empty currency src/modules/orders/secondary-adapters/adapters/module-cart.gateway.spec.ts
  • Test Quality · No assertions: returns infrastructure error when cart item has invalid currency code src/modules/orders/secondary-adapters/adapters/module-cart.gateway.spec.ts
  • Test Quality · No assertions: passes through use case error when getCartUseCase fails src/modules/orders/secondary-adapters/adapters/module-cart.gateway.spec.ts
  • Test Quality · No assertions: returns infrastructure error on failure src/modules/orders/secondary-adapters/adapters/module-cart.gateway.spec.ts
  • Test Quality · No assertions: returns infrastructure error when clearCartUseCase fails src/modules/orders/secondary-adapters/adapters/module-cart.gateway.spec.ts
  • Test Quality · No assertions: returns an InfrastructureError when flowProducer.add throws src/modules/orders/secondary-adapters/schedulers/bullmq-checkout.scheduler.spec.ts
  • Test Quality · No assertions: propagates failure when handlePaymentWebhookService fails src/modules/payments/core/application/usecases/handle-stripe-webhook/handle-stripe-webhook.usecase.spec.ts
  • Test Quality · No assertions: fails when value is not a string src/modules/payments/core/domain/value-objects/payment-provider-id.spec.ts
  • Test Quality · No assertions: fails when value is empty src/modules/payments/core/domain/value-objects/payment-provider-id.spec.ts
  • Test Quality · No assertions: fails without trimming when value contains whitespace src/modules/payments/core/domain/value-objects/payment-provider-id.spec.ts
  • Test Quality · No assertions: fails when value has underscores or uppercase characters src/modules/payments/core/domain/value-objects/payment-provider-id.spec.ts
  • Test Quality · No assertions: propagates repository lookup failure src/modules/products/core/application/seed/seed-demo-categories.usecase.spec.ts
  • Test Quality · No assertions: should fail when a demo category slug is missing or inactive src/modules/products/core/application/seed/seed-demo-catalog.usecase.spec.ts
  • Test Quality · No assertions: should propagate error if listing existing products fails src/modules/products/core/application/seed/seed-demo-catalog.usecase.spec.ts
  • Test Quality · No assertions: should propagate failure if individual product creation fails src/modules/products/core/application/seed/seed-demo-catalog.usecase.spec.ts
  • Test Quality · No assertions: returns the repository failure when the product is not saved src/modules/products/core/application/usecases/create-product/create-product.usecase.spec.ts
  • Test Quality · No assertions: returns the repository failure when the product is not deleted src/modules/products/core/application/usecases/delete-product/delete-product.usecase.spec.ts
  • Test Quality · No assertions: returns the repository failure when the product is not found src/modules/products/core/application/usecases/update-product/update-product.usecase.spec.ts
  • Test Quality · No assertions: returns failure for invalid currency code in create src/shared-kernel/domain/value-objects/currency.spec.ts
  • Test Quality · No assertions: returns failure for removed currency codes XDR and XSU src/shared-kernel/domain/value-objects/currency.spec.ts
  • Dependency Hygiene · Deprecated: prom-client package.json
  • REDACTED Scanning · REDACTED
  • REDACTED Scanning · REDACTED
  • Churn × Complexity Hotspots · Hotspot: src/modules/payments/core/application/usecases/create-payment/create-payment.usecase.ts src/modules/payments/core/application/usecases/create-payment/create-payment.usecase.ts
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 274 findings

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

  • Cyclomatic Complexity · ascii-prose.findComments (cyclomatic 36) scripts/ascii-prose.cjs
  • Cyclomatic Complexity · ascii-prose.collectFiles (cyclomatic 22) scripts/ascii-prose.cjs
  • Cyclomatic Complexity · seed.bootstrap (cyclomatic 18) scripts/seed.ts
  • Cyclomatic Complexity · CheckoutFailureListener.onModuleInit (cyclomatic 16) src/modules/orders/primary-adapters/listeners/checkout-failure.listener.ts
  • Cognitive Complexity · ascii-prose.collectFiles (cognitive 32) scripts/ascii-prose.cjs
  • Cognitive Complexity · setup-bootstrap.runSetup (cognitive 18) scripts/lib/setup-bootstrap.js
  • Cognitive Complexity · seed.bootstrap (cognitive 18) scripts/seed.ts
  • God Classes · FunctionTooLong: seed.bootstrap scripts/seed.ts
  • Cohesion (LCOM4) · Low cohesion: PaymentsController (LCOM4 4) REDACTED
  • Code Coverage · Low coverage: src/main.ts src/main.ts
  • Code Coverage · Low coverage: src/infrastructure/idempotency/index.ts src/infrastructure/idempotency/index.ts
  • Code Coverage · Low coverage: src/infrastructure/jwt/index.ts src/infrastructure/jwt/index.ts
  • Code Coverage · Low coverage: src/infrastructure/tracing/index.ts src/infrastructure/tracing/index.ts
  • Code Coverage · Low coverage: src/migrations/1787339318490-InitialBaseline.ts src/migrations/1787339318490-InitialBaseline.ts
  • Code Coverage · Low coverage: src/migrations/1787339318500-AddCategoriesTable.ts src/migrations/1787339318500-AddCategoriesTable.ts
  • Code Coverage · Low coverage: src/migrations/1787400000001-AnalyticsQueryIndexes.ts src/migrations/1787400000001-AnalyticsQueryIndexes.ts
  • Code Coverage · Low coverage: src/migrations/1787400000002-AddCartItemCurrency.ts src/migrations/1787400000002-AddCartItemCurrency.ts
  • Code Coverage · Low coverage: src/modules/authentication/core/application/services/jwt-signer.service.ts src/modules/authentication/core/application/services/jwt-signer.service.ts
  • Code Coverage · Low coverage: src/modules/authentication/primary-adapters/decorators/index.ts src/modules/authentication/primary-adapters/decorators/index.ts
  • Code Coverage · Low coverage: src/modules/authentication/secondary-adapters/persistence/mappers/session-token.mapper.ts src/modules/authentication/secondary-adapters/persistence/mappers/session-token.mapper.ts
  • Code Coverage · Low coverage: src/modules/health/indicators/process.health-indicator.ts src/modules/health/indicators/process.health-indicator.ts
  • Code Coverage · Low coverage: src/modules/health/indicators/redis.health-indicator.ts src/modules/health/indicators/redis.health-indicator.ts
  • Code Coverage · Low coverage: src/modules/health/indicators/websocket.health-indicator.ts src/modules/health/indicators/websocket.health-indicator.ts
  • Code Coverage · Low coverage: src/modules/identity/core/domain/repositories/address.repository.ts src/modules/identity/core/domain/repositories/address.repository.ts
  • Code Coverage · Low coverage: src/modules/inventory/inventory.processor.ts src/modules/inventory/inventory.processor.ts
  • Code Coverage · Low coverage: src/modules/inventory/primary-adapters/dto/stock-reservation-response.dto.ts src/modules/inventory/primary-adapters/dto/stock-reservation-response.dto.ts
  • Code Coverage · Low coverage: src/modules/orders/core/application/usecases/handle-payment-completed/handle-payment-completed.usecase.ts src/modules/orders/core/application/usecases/handle-payment-completed/handle-payment-completed.usecase.ts
  • Code Coverage · Low coverage: src/modules/orders/core/application/usecases/refund-checkout-payment/refund-checkout-payment.usecase.ts src/modules/orders/core/application/usecases/refund-checkout-payment/refund-checkout-payment.usecase.ts
  • Code Coverage · Low coverage: src/modules/orders/primary-adapters/dto/create-order-item.dto.ts src/modules/orders/primary-adapters/dto/create-order-item.dto.ts
  • Code Coverage · Low coverage: src/modules/orders/primary-adapters/dto/create-order.dto.ts src/modules/orders/primary-adapters/dto/create-order.dto.ts
  • Code Coverage · Low coverage: src/modules/orders/primary-adapters/dto/order-item-response.dto.ts src/modules/orders/primary-adapters/dto/order-item-response.dto.ts
  • Code Coverage · Low coverage: src/modules/orders/primary-adapters/dto/order-response.dto.ts src/modules/orders/primary-adapters/dto/order-response.dto.ts
  • Code Coverage · Low coverage: src/modules/orders/primary-adapters/dto/payment-info.dto.ts src/modules/orders/primary-adapters/dto/payment-info.dto.ts
  • Code Coverage · Low coverage: src/modules/orders/primary-adapters/dto/update-order.dto.ts src/modules/orders/primary-adapters/dto/update-order.dto.ts
  • Code Coverage · Low coverage: src/modules/orders/primary-adapters/jobs/process-payment.job.ts src/modules/orders/primary-adapters/jobs/process-payment.job.ts
  • Code Coverage · Low coverage: src/modules/orders/primary-adapters/jobs/refund-payment.job.ts src/modules/orders/primary-adapters/jobs/refund-payment.job.ts
  • Code Coverage · Low coverage: src/modules/orders/primary-adapters/listeners/checkout-compensation-job-data.ts src/modules/orders/primary-adapters/listeners/checkout-compensation-job-data.ts
  • Code Coverage · Low coverage: src/modules/orders/primary-adapters/listeners/checkout-failure.listener.ts src/modules/orders/primary-adapters/listeners/checkout-failure.listener.ts
  • Code Coverage · Low coverage: src/modules/orders/secondary-adapters/adapters/module-cart.gateway.ts src/modules/orders/secondary-adapters/adapters/module-cart.gateway.ts
  • Code Coverage · Low coverage: src/modules/orders/secondary-adapters/adapters/module-payment.gateway.ts src/modules/orders/secondary-adapters/adapters/module-payment.gateway.ts
  • Code Coverage · Low coverage: src/modules/payments/core/application/seed/demo-payments.ts src/modules/payments/core/application/seed/demo-payments.ts
  • Code Coverage · Low coverage: src/modules/payments/core/application/usecases/create-payment-intent/create-payment-intent.usecase.ts src/modules/payments/core/application/usecases/create-payment-intent/create-payment-intent.usecase.ts
  • Code Coverage · Low coverage: src/modules/payments/core/domain/index.ts src/modules/payments/core/domain/index.ts
  • Code Coverage · Low coverage: src/modules/payments/primary-adapters/dto/record-cod-payment.dto.ts src/modules/payments/primary-adapters/dto/record-cod-payment.dto.ts
  • Code Coverage · Low coverage: src/modules/payments/secondary-adapters/gateways/payment-gateway.factory.ts src/modules/payments/secondary-adapters/gateways/payment-gateway.factory.ts
  • Code Coverage · Low coverage: src/shared-kernel/domain/value-objects/money.ts src/shared-kernel/domain/value-objects/money.ts
  • Code Coverage · Low coverage: src/testing/helpers/auth-test.helper.ts src/testing/helpers/auth-test.helper.ts
  • Code Coverage · Low coverage: src/testing/helpers/clock-test.helper.ts src/testing/helpers/clock-test.helper.ts
  • Code Coverage · Low coverage: src/testing/helpers/database-test.helper.ts src/testing/helpers/database-test.helper.ts
  • Code Coverage · Low coverage: src/testing/helpers/e2e-catalog.helper.ts src/testing/helpers/e2e-catalog.helper.ts
  • Code Coverage · Low coverage: src/testing/helpers/e2e-checkout.helper.ts src/testing/helpers/e2e-checkout.helper.ts
  • Code Coverage · Low coverage: src/testing/helpers/e2e-inventory.helper.ts src/testing/helpers/e2e-inventory.helper.ts
  • Code Coverage · Low coverage: src/testing/helpers/e2e-order.helper.ts src/testing/helpers/e2e-order.helper.ts
  • Code Coverage · Low coverage: src/testing/helpers/e2e-stripe-webhook.helper.ts src/testing/helpers/e2e-stripe-webhook.helper.ts
  • Code Coverage · Low coverage: src/testing/helpers/e2e-test-app.helper.ts src/testing/helpers/e2e-test-app.helper.ts
  • Code Coverage · Low coverage: src/testing/helpers/http-error-assertion.helper.ts src/testing/helpers/http-error-assertion.helper.ts
  • Code Coverage · Low coverage: src/testing/helpers/poll.helper.ts src/testing/helpers/poll.helper.ts
  • Code Coverage · Low coverage: src/testing/mocks/env-config.service.mock.ts src/testing/mocks/env-config.service.mock.ts
  • Code Coverage · Low coverage: src/testing/mocks/order-scheduler.mock.ts src/testing/mocks/order-scheduler.mock.ts
  • Test Quality · No assertions: should return failure if session is revoked src/modules/authentication/core/application/usecases/refresh-token/refresh-token.usecase.spec.ts
  • Test Quality · No assertions: should return failure if cart is not found by cartId src/modules/carts/core/application/usecases/get-cart/get-cart.usecase.spec.ts
  • Test Quality · No assertions: rejects cancellation when status is %s src/modules/orders/core/domain/entities/order.spec.ts
  • Test Quality · No assertions: should fail if save fails src/modules/payments/core/application/usecases/create-payment/create-payment.usecase.spec.ts
  • Test Quality · No assertions: should fail if refund amount exceeds payment amount src/modules/payments/core/application/usecases/process-refund/process-refund.usecase.spec.ts
  • Test Quality · No assertions: should return Failure(UseCaseError) if product is not created src/modules/products/core/application/usecases/create-product/create-product.usecase.spec.ts
  • Test Quality · No assertions: should return Failure(UseCaseError) if product is not deleted src/modules/products/core/application/usecases/delete-product/delete-product.usecase.spec.ts
  • Test Quality · No assertions: should return Failure(UseCaseError) if product is not found src/modules/products/core/application/usecases/update-product/update-product.usecase.spec.ts
  • Dependency Hygiene · Floating npm dependency: @nestjs/mapped-types
  • Churn × Complexity Hotspots · Hotspot: scripts/seed.ts scripts/seed.ts
  • Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Change Coupling · Boundary-crossing change coupling: cached-inventory-repository.ts ↔ cached.order-repository.ts src/modules/inventory/secondary-adapters/repositories/cached-inventory-repository/cached-inventory-repository.ts
  • Code Duplication · Duplication concentrated across 3 sibling directories (6 clone groups) src/modules/payments/core/domain/entities/payment.ts
  • Code Duplication · Duplication concentrated across 5 sibling directories (5 clone groups) src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts
  • Code Duplication · Duplication concentrated across 6 sibling directories (5 clone groups) src/modules/orders/core/application/usecases/handle-payment-completed/handle-payment-completed.usecase.ts
  • Code Duplication · Duplicated block with local edits (94 matched lines × 2 locations) src/modules/products/core/domain/entities/category.ts
  • Code Duplication · Duplicated block with local edits (57 matched lines × 2 locations) src/modules/inventory/secondary-adapters/repositories/postgres-inventory-repository/postgres-inventory-repository.ts
  • Code Duplication · Duplicated block with local edits (57 matched lines × 2 locations) src/modules/products/core/application/usecases/create-product/create-product.usecase.ts
  • Code Duplication · Duplicated block with local edits (45 matched lines × 2 locations) src/modules/inventory/secondary-adapters/repositories/cached-inventory-repository/cached-inventory-repository.ts
  • Code Duplication · Duplicated block with local edits (42 matched lines × 2 locations) src/modules/carts/core/domain/entities/cart-item.ts
  • Code Duplication · Duplicated block with local edits (40 matched lines × 2 locations) src/modules/carts/secondary-adapters/persistence/mappers/cart.mapper.ts
  • Code Duplication · Duplicated block (38 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (32 lines × 2 locations) src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.ts
  • Code Duplication · Duplicated block with local edits (32 matched lines × 2 locations) src/modules/orders/primary-adapters/jobs/create-order.job.ts
  • Code Duplication · Duplicated block (28 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (28 lines × 2 locations) src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.ts
  • Code Duplication · Duplicated block (28 lines × 2 locations) src/modules/orders/primary-adapters/jobs/create-order.job.ts
  • Code Duplication · Duplicated block (28 lines × 2 locations) src/modules/orders/secondary-adapters/schedulers/bullmq-checkout.scheduler.ts
  • Code Duplication · Duplicated block (28 lines × 2 locations) src/modules/payments/secondary-adapters/schedulers/bullmq-payment-events.scheduler.ts
  • Code Duplication · Duplicated block (27 lines × 2 locations) src/modules/identity/primary-adapters/dto/list-users-query.dto.ts
  • Code Duplication · Duplicated block (26 lines × 2 locations) src/modules/carts/core/application/usecases/clear-cart/clear-cart.usecase.ts
  • Code Duplication · Duplicated block (26 lines × 2 locations) src/modules/identity/core/application/usecases/address/delete-address/delete-address.usecase.ts
  • Code Duplication · Duplicated block (26 lines × 2 locations) src/modules/inventory/secondary-adapters/persistence/mappers/inventory.mapper.ts
  • Code Duplication · Duplicated block (25 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (25 lines × 2 locations) src/modules/carts/secondary-adapters/repositories/cached-cart-repository/cached.cart-repository.ts
  • Code Duplication · Duplicated block (25 lines × 2 locations) src/modules/inventory/secondary-adapters/repositories/postgres-inventory-repository/postgres-inventory-repository.ts
  • Code Duplication · Duplicated block (24 lines × 2 locations) src/modules/orders/primary-adapters/dto/list-orders-query.dto.ts
  • Code Duplication · Duplicated block (24 lines × 2 locations) src/modules/orders/primary-adapters/dto/order-detail-response.dto.ts
  • Code Duplication · Duplicated block (23 lines × 2 locations) src/modules/carts/secondary-adapters/repositories/postgres-cart-repository/postgres.cart-repository.ts
Rebuild cost: about €110,000 · Estimate
Cost to rebuild€37,000 to €190,000, for 614 to 1,948 hours of work, about 0.8 person-years for 1 to 2 engineers
Difficulty of the problemHigh, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 53. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 48,746 lines of product code

How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

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

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

Files that change often carry extra risk · Combined risk
One file is changed often and is hard to read, which makes it the likeliest place for a mistake. It also has under half its code tested, or was written almost entirely by one person, so a mistake there is less likely to be caught, or only one person knows the code well enough to avoid it. A change to this file therefore carries more risk than the overall score suggests.
Based on: Churn × Complexity Hotspots (8 files) · Code Coverage (132 files under half tested) · The files: postgres-product-query.adapter.ts
What to do: Add tests to these files and have a second person review every change to them, starting with postgres-product-query.adapter.ts.
Where the investment is most exposed · Value at risk
This code would cost about €110,000 to build again, about 0.8 person-years of work. Its weakest lens is Production Readiness, at 48 (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.
One cause behind 18 Domain Modelling findings · Common cause
18 findings in the Domain Modelling lens come from the same cause. The code models the business as objects, such as an order or a customer, and each object should guard its own rules: an order, for example, should refuse to be shipped before it has been paid. Here the objects don't do that. Other code can change an object's data directly, so it can put an order into a state the rules forbid. Some objects only hold data, while the rules that should keep that data valid sit elsewhere in the code. Identifiers, such as order numbers and customer numbers, are passed around as plain numbers or text, so nothing stops the code from using one kind where another belongs. Because all of these findings have the same cause, fixing it once, in the business objects themselves, deals with them together.
Based on: Encapsulated state (1 finding) · Rich vs anemic model (3 findings) · Strongly-typed ids (14 findings)
What to do: Give each business object the methods that enforce its rules, such as a method for shipping an order that first checks it has been paid, and let only those methods change its data. Give each kind of identifier a type of its own, so an order number can't be used where a customer number belongs.
If you do one thing first · First action
Resolve the 3 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 5 points for low effort, because it clears the 3 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: 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.

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

The table shows the 40 modules with the most connections; 757 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 config.env-config_service2 infrastructure.logging.correlation.correlation_service3 modules.inventory.inventory_controller4 modules.orders.core.domain.value-objects.order-status_enum5 modules.orders.orders_processor6 modules.orders.testing.factories.order-dto_factory7 shared-kernel.domain.exceptions.app_error8 shared-kernel.domain.interfaces.caller-context_interface9 shared-kernel.domain.interfaces.paginated-query-result_interface10 shared-kernel.domain.result11 shared-kernel.domain.value-objects.payment-method12 types.express13 infrastructure.jobs.base-job_handler14 modules.orders.core.domain.interfaces.order_interface15 shared-kernel.domain.exceptions.domain_error16 shared-kernel.domain.exceptions.infrastructure-error17 shared-kernel.domain.exceptions.query_error18 shared-kernel.domain.exceptions.repository_error19 shared-kernel.domain.exceptions.usecase_error20 shared-kernel.domain.interfaces.base_usecase21 infrastructure.demo.secondary-adapters.adapters.demo-seed-runner_adapter22 modules.analytics.core.application.ports.analytics-query_service23 modules.authentication.core.application.ports.authorization_gateway24 modules.authentication.core.domain.repositories.credential_repository25 modules.authorization.core.domain.repositories.role_repository26 modules.carts.core.domain.repositories.cart_repository27 modules.identity.core.domain.repositories.user_repository28 modules.inventory.core.domain.repositories.inventory_repository29 modules.inventory.core.domain.repositories.reservation_repository30 modules.orders.core.domain.entities.order31 modules.orders.core.domain.schedulers.order_scheduler32 modules.payments.core.domain.entities.payment33 modules.products.core.domain.repositories.category-repository34 modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter35 modules.authentication.core.application.usecases.change-password.change-password_usecase36 modules.authentication.core.application.usecases.login-user.login-user_usecase37 modules.orders.core.domain.repositories.order-repository38 modules.payments.core.domain.repositories.payment_repository39 modules.orders.core.application.usecases.cancel-order.cancel-order_usecase40 modules.orders.orders_controller
1 config.env-config_service
2 infrastructure.logging.correlation.correlation_service
3 modules.inventory.inventory_controller
4 modules.orders.core.domain.value-objects.order-status_enum
5 modules.orders.orders_processor
6 modules.orders.testing.factories.order-dto_factory
7 shared-kernel.domain.exceptions.app_error
8 shared-kernel.domain.interfaces.caller-context_interface
9 shared-kernel.domain.interfaces.paginated-query-result_interface
10 shared-kernel.domain.result
11 shared-kernel.domain.value-objects.payment-method
12 types.express
13 infrastructure.jobs.base-job_handler11
14 modules.orders.core.domain.interfaces.order_interface11
15 shared-kernel.domain.exceptions.domain_error1
16 shared-kernel.domain.exceptions.infrastructure-error1
17 shared-kernel.domain.exceptions.query_error1
18 shared-kernel.domain.exceptions.repository_error1
19 shared-kernel.domain.exceptions.usecase_error1
20 shared-kernel.domain.interfaces.base_usecase1
21 infrastructure.demo.secondary-adapters.adapters.demo-seed-runner_adapter111
22 modules.analytics.core.application.ports.analytics-query_service11
23 modules.authentication.core.application.ports.authorization_gateway11
24 modules.authentication.core.domain.repositories.credential_repository11
25 modules.authorization.core.domain.repositories.role_repository11
26 modules.carts.core.domain.repositories.cart_repository11
27 modules.identity.core.domain.repositories.user_repository11
28 modules.inventory.core.domain.repositories.inventory_repository11
29 modules.inventory.core.domain.repositories.reservation_repository11
30 modules.orders.core.domain.entities.order11211
31 modules.orders.core.domain.schedulers.order_scheduler11
32 modules.payments.core.domain.entities.payment141
33 modules.products.core.domain.repositories.category-repository11
34 modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter1111
35 modules.authentication.core.application.usecases.change-password.change-password_usecase11111
36 modules.authentication.core.application.usecases.login-user.login-user_usecase11111
37 modules.orders.core.domain.repositories.order-repository2111
38 modules.payments.core.domain.repositories.payment_repository111
39 modules.orders.core.application.usecases.cancel-order.cancel-order_usecase1111111
40 modules.orders.orders_controller11
Uses a module listed above itPart of a loopThe module itself
1 config.env-config_service2 infrastructure.logging.correlation.correlation_service3 modules.inventory.inventory_controller4 modules.orders.core.domain.value-objects.order-status_enum5 modules.orders.orders_processor6 modules.orders.testing.factories.order-dto_factory7 shared-kernel.domain.exceptions.app_error8 shared-kernel.domain.interfaces.caller-context_interface9 shared-kernel.domain.interfaces.paginated-query-result_interface10 shared-kernel.domain.result11 shared-kernel.domain.value-objects.payment-method12 types.express13 infrastructure.jobs.base-job_handler14 modules.orders.core.domain.interfaces.order_interface15 shared-kernel.domain.exceptions.domain_error16 shared-kernel.domain.exceptions.infrastructure-error17 shared-kernel.domain.exceptions.query_error18 shared-kernel.domain.exceptions.repository_error19 shared-kernel.domain.exceptions.usecase_error20 shared-kernel.domain.interfaces.base_usecase21 infrastructure.demo.secondary-adapters.adapters.demo-seed-runner_adapter22 modules.analytics.core.application.ports.analytics-query_service23 modules.authentication.core.application.ports.authorization_gateway24 modules.authentication.core.domain.repositories.credential_repository25 modules.authorization.core.domain.repositories.role_repository26 modules.carts.core.domain.repositories.cart_repository27 modules.identity.core.domain.repositories.user_repository28 modules.inventory.core.domain.repositories.inventory_repository29 modules.inventory.core.domain.repositories.reservation_repository30 modules.orders.core.domain.entities.order31 modules.orders.core.domain.schedulers.order_scheduler32 modules.payments.core.domain.entities.payment33 modules.products.core.domain.repositories.category-repository34 modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter35 modules.authentication.core.application.usecases.change-password.change-password_usecase36 modules.authentication.core.application.usecases.login-user.login-user_usecase37 modules.orders.core.domain.repositories.order-repository38 modules.payments.core.domain.repositories.payment_repository39 modules.orders.core.application.usecases.cancel-order.cancel-order_usecase40 modules.orders.orders_controllerconfig.env-config_service1infrastructure.logging.correlation.correlation_service2modules.inventory.inventory_controller3modules.orders.core.domain.value-objects.order-status_enum4modules.orders.orders_processor5modules.orders.testing.factories.order-dto_factory6shared-kernel.domain.exceptions.app_error7shared-kernel.domain.interfaces.caller-context_interface8shared-kernel.domain.interfaces.paginated-query-result_interface9shared-kernel.domain.result10shared-kernel.domain.value-objects.payment-method11types.express12infrastructure.jobs.base-job_handler13modules.orders.core.domain.interfaces.order_interface14shared-kernel.domain.exceptions.domain_error15shared-kernel.domain.exceptions.infrastructure-error16shared-kernel.domain.exceptions.query_error17shared-kernel.domain.exceptions.repository_error18shared-kernel.domain.exceptions.usecase_error19shared-kernel.domain.interfaces.base_usecase20infrastructure.demo.secondary-adapters.adapters.demo-seed-runner_adapter21modules.analytics.core.application.ports.analytics-query_service22modules.authentication.core.application.ports.authorization_gateway23modules.authentication.core.domain.repositories.credential_repository24modules.authorization.core.domain.repositories.role_repository25modules.carts.core.domain.repositories.cart_repository26modules.identity.core.domain.repositories.user_repository27modules.inventory.core.domain.repositories.inventory_repository28modules.inventory.core.domain.repositories.reservation_repository29modules.orders.core.domain.entities.order30modules.orders.core.domain.schedulers.order_scheduler31modules.payments.core.domain.entities.payment32modules.products.core.domain.repositories.category-repository33modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter34modules.authentication.core.application.usecases.change-password.change-password_usecase35modules.authentication.core.application.usecases.login-user.login-user_usecase36modules.orders.core.domain.repositories.order-repository37modules.payments.core.domain.repositories.payment_repository38modules.orders.core.application.usecases.cancel-order.cancel-order_usecase39modules.orders.orders_controller4011111111111111111111111111111112111114111111111111111112111111111111111+757 more modules (most-connected shown)

At a glance — Code Health · 54% · Adequate · gated by X4, X5 ·

The Good
D1 · TypeScript Cyclomatic Complexity 8.3 D2 · TypeScript Cognitive Complexity 7.3 D3 · TypeScript God Classes 9.8 D17 · TypeScript Explicit Debt 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 9.0 R1 · React / TS Type Safety 9.7 R10 · React / TS Code Duplication 7.8 R2 · React / TS Cyclomatic Complexity 9.3 R3 · React / TS Large Files 10.0 R7 · React / TS Dead Code 8.6 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X2 · Repo Cancellation propagation 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X3 · Repo Exception handling 7.3 X30 · Repo Support guard that admits what it rejects 10.0
The Ugly
X4 · Repo Structured logging 2.5 X5 · Repo Nullable reference types 1.2

At a glance — Architecture · 59% · Adequate · gated by D26, R9 ·

The Good
D6 · TypeScript Cohesion (LCOM4) 9.8 D7 · TypeScript Architectural Integrity 10.0 D35 · TypeScript Change Coupling 9.9 AX10 · Repo Code composition 7.1 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0
The Ugly
D26 · TypeScript Project Cohesion 0.0 R9 · React / TS Circular Imports 0.0

At a glance — Maturity · 55% · Adequate · gated by M4 ·

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

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

The Good
D8 · TypeScript Code Coverage 9.7 D9 · TypeScript Test Distribution 9.6 D10 · TypeScript Test Quality 8.4 D11 · TypeScript Test Reliability 10.0 D12 · TypeScript Dependency Hygiene 8.7 D14 · TypeScript License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P2 · Repo Observability 10.0 P4 · Repo Deployment & Rollback 8.0 P5 · Repo DR & Backup 7.0 P6 · Repo Release Hygiene 10.0 P7 · Repo Outbound HTTP resilience 10.0 P8 · Repo Schema migrations 10.0 P9 · Repo Domain vs controller coverage 8.8 R4 · React / TS Test Coverage 9.5 R5 · React / TS Dependency Freshness 7.4 R6 · React / TS Tooling 10.0
The Ugly
D13 · TypeScript REDACTED Scanning 0.0 P3 · Repo Security & performance tooling 3.0 R8 · React / TS Dependency Hygiene 0.5

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

The Good
D30 · TypeScript Dependency Vulnerabilities 9.2 D31 · TypeScript IaC & Container Security 8.9 D36 · TypeScript Supply-chain Provenance & Signing 7.5 D37 · TypeScript Vulnerability-disclosure Policy 10.0 D43 · TypeScript Malicious Dependencies 10.0 D44 · TypeScript Platform End-of-Life 10.0 C2 · Repo Access Controls 10.0 C4 · Repo Data Retention 9.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0
The Ugly
D28 · TypeScript Secrets (history) 4.0 D29 · TypeScript Static Analysis (SAST) 0.6 C1 · Repo Data Protection 4.0 X17 · Repo Uncapped recursion over a caller-supplied document 2.7

At a glance — Domain Modelling · 70% · Adequate · gated by DM2 ·

The Good
DM1 · Repo Aggregate boundaries 10.0 DM10 · Repo One transaction, one aggregate 9.9 DM11 · Repo Constructible invalid state 10.0 DM4 · Repo Rich vs anemic model 8.9 DM6 · Repo Domain ↔ infrastructure boundary 10.0 DM9 · Repo Scattered domain decisions 10.0
The Bad
DM5 · Repo Encapsulated state 6.2
The Ugly
DM2 · Repo Strongly-typed ids 3.0

At a glance — Performance · 100% · Exemplary ·

The Good
PF3 · Repo Async & latency hygiene 10.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection51High / Critical
A07:2025 — Authentication Failures10High / Critical
A02:2025 — Security Misconfiguration9High / Critical
A03:2025 — Software Supply Chain Failures4High / Critical

Roadmap

Immediately resolve the three leaked secrets in REDACTED, REDACTED, and REDACTED to secure the codebase. Clean up dependencies by removing unused packages, explicitly declaring imports, and moving type- or test-only packages to devDependencies, while also addressing five deprecated dependencies. Strengthen security by adding a SAST step to CI to fail builds on regressions, and improve test reliability by fixing the 188 test cases that lack assertions, starting with the postgres and cart repository specs.

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

Do thisHelpsEffortDimension
Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED.+5.0 ptsLowREDACTED Scanning
Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (5).+3.5 ptsLowDependency Hygiene
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+3.8 ptsMediumDependency Hygiene
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.+3.2 ptsMediumSecurity & performance tooling
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion.+1.0 ptsLowProject Cohesion
Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests; docs/architecture/DDD-HEXAGONAL.md names `core/domain/models/`, but no file or folder `core/domain/models` exists; docs/architecture/DDD-HEXAGONAL.md names `core/domain/events/`, but no file or folder `core/domain/events` exists; docs/development/SEEDING.md documents the environment variable `NEXT_PUBLIC_API_BASE_URL`, but no code, script or configuration file names it; docs/development/SEEDING.md documents the environment variable `NEXT_PUBLIC_IMAGE_ALLOWED_HOSTS`, but no code, script or configuration file names it.+1.7 ptsMediumDocumentation accuracy
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 `?`).+1.6 ptsMediumNullable reference types
Interpolated log message defeats structured logging+1.3 ptsMediumStructured logging

File quality

Per-file score 0–10 — a quality signature. Of 259 files carrying findings, judged against the Preview bar: 1% slop · 6% mixed · 93% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED1.7SlopSecrets (history): High secret: REDACTED
REDACTED4.4MixedREDACTED Scanning: Leaked secret: REDACTED
src/modules/carts/secondary-adapters/repositories/cached-cart-repository/cached.cart-repository.ts5.5MixedChange Coupling: Boundary-crossing change coupling: cached.cart-repository.ts ↔ cached-inventory-repository.ts
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.1MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.1MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.1MixedStatic Analysis (SAST): Medium: REDACTED
src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts6.3MixedCyclomatic Complexity: PostgresPaymentQueryAdapter.list (cyclomatic 19)
REDACTED6.3MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.3MixedIaC & Container Security: Medium IaC: REDACTED
REDACTED6.4MixedStatic Analysis (SAST): Medium: REDACTED
src/modules/products/secondary-adapters/query/postgres-product-query.adapter.ts7.0Near-cleanCyclomatic Complexity: PostgresProductQueryAdapter.list (cyclomatic 16)
src/infrastructure/logging/winston-logger.service.ts7.0Near-cleanCognitive Complexity: winston-logger.service.redactInPlace (cognitive 16)
src/modules/authentication/secondary-adapters/adapters/module-identity.gateway.ts7.0Near-cleanCohesion (LCOM4): Low cohesion: ModuleIdentityGateway (LCOM4 5)

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

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

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

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

Could not be resolved — 6

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

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 86 of 92 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 6 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 92 dimensions across the health lenses
D1D2D3D6D7D8D9D10D11D12D13D14D15D17D19D20D21D25D26D28D29D30D31D34D35D36D37D43D44AX10AX3AX4AX5AX6C1C2C4DM1DM10DM11DM2DM4DM5DM6DM9GD1IC1M1M2M3M4P1P2P3P4P5P6P7P8P9PF3R1R10R2R3R4R5R6R7R8R9X1X12X13X14X15X16X17X18X19X2X21X22X23X24X25X28X29X3X30X4X5

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, 690 of 718 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

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

Tools & methods

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

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a16400-9bad-772d-a7a8-c3b1a4a4d58f.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 1925 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 2 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
  • D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — time="2026-10-22T14:26:03Z" level=warning msg="The \"REDIS_PASSWORD\" variable is not set. Defaulting to a blank string." postgres Pulling redis Pulling redis Error Get "https://registry-1.docker.io/v2/": Forbidden postgres Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: time="2026-10-22T14:26:03Z" level=warning msg="The \"REDIS_PASSWORD\" variable is not set. Defaulting to a blank string." redis Pulling postgres Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden redis Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
  • DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
  • R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 183 further occurrence(s) are not listed individually; the score already reflects all 223.
  • R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 8 further occurrence(s) are not listed individually; the score already reflects all 48.
  • S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 771 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation and obsolete TLS versions, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
  • X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 162 further occurrence(s) are not listed individually; the score already reflects all 202.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 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.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D25 ADR Conformance: ADR conformance is the LLM-scored fraction of sampled code that follows recorded decisions — it checks the decisions that were written down and the slices it sampled, not unrecorded rules or the whole tree.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
  • DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
  • DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

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

Dimensions

D1 · Cyclomatic Complexity8.3 / 10Strong✓ Tool-verified

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

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

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

14 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was generate-envs.buildLinesForEnv at 26. A further 1 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 agent-output.isDoc at 18 — they are counted neither in the figure above nor in this dimension's score.

generate-envs.buildLinesForEnv (cyclomatic 26)scripts/generate-envs.js:59
generate-envs.generateEnvs (cyclomatic 26)scripts/generate-envs.js:169
SeedDemoCatalogUseCase.execute (cyclomatic 25)src/modules/products/core/application/seed/seed-demo-catalog.usecase.ts:46
CartQueryMapper.toPresentationDto (cyclomatic 24)src/modules/carts/secondary-adapters/mappers/query/cart-query.mapper.ts:11
ascii-prose.findComments::skipString (cyclomatic 23)scripts/ascii-prose.cjs:148

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

What to do

  1. Bring the 14 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with generate-envs.buildLinesForEnv (cyclomatic 26), generate-envs.generateEnvs (cyclomatic 26), SeedDemoCatalogUseCase.execute (cyclomatic 25). — 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 14 together lifts Cyclomatic Complexity from 8.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D2 · Cognitive Complexity7.3 / 10Strong✓ Tool-verified

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

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

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

20 method(s) exceeded the cognitive complexity threshold of 15; the worst was generate-envs.generateEnvs at 44.

generate-envs.generateEnvs (cognitive 44)scripts/generate-envs.js:169
ascii-prose.findComments::skipString (cognitive 36)scripts/ascii-prose.cjs:148
SeedDemoCatalogUseCase.execute (cognitive 36)src/modules/products/core/application/seed/seed-demo-catalog.usecase.ts:46
CartQueryMapper.toPresentationDto (cognitive 35)src/modules/carts/secondary-adapters/mappers/query/cart-query.mapper.ts:11
ascii-prose.collectFiles::walk (cognitive 32)scripts/ascii-prose.cjs:54

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

What to do

  1. Bring the 20 bodies over 15 down to 15 or less in Cognitive Complexity — start with generate-envs.generateEnvs (cognitive 44), ascii-prose.findComments::skipString (cognitive 36), SeedDemoCatalogUseCase.execute (cognitive 36). — 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 20 together lifts Cognitive Complexity from 7.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D3 · God Classes9.8 / 10Stronggated by 2 serious findings✓ 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 9.8 / 10 · rule-coverage 100% · ceiling Prevented

2 god class(es) detected.

TooManyMethods: Ordersrc/modules/orders/core/domain/entities/order.ts:35
MethodTooLong: ChangePasswordUseCase.executesrc/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts:40

What to do

  1. Resolve the 1 TooManyMethods finding(s) in God Classes — start with order.ts. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 MethodTooLong finding(s) in God Classes — start with change-password.usecase.ts. — One of this dimension's main actionable groups (1 warning-level).
  3. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D6 · Cohesion (LCOM4)9.8 / 10Stronggated by 2 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.8 / 10 · rule-coverage 100% · ceiling Verified

2 of 156 classes have LCOM4 above 3.

Low cohesion: ModuleIdentityGateway (LCOM4 5) · ×2src/modules/authentication/secondary-adapters/adapters/module-identity.gateway.ts:18

What to do

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

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

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

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

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

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

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

Checkable ADR rule enforced only by prose: ADR-0009: Hosted Demo Reset as Ops Infrastructuredocs/architecture/adr/ADR-0009-demo-reset-ops-infrastructure.md

✓ On the Gold path — maintain.

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

D8 · Code Coverage9.7 / 10Stronggated by 133 serious findings✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

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

Line coverage 69.1% — 133 file(s) below 50%. Measured from the JavaScript/TypeScript suite (vitest + @vitest/coverage-v8 via `npm ci --ignore-scripts` in the repository root).

Low coverage: src/config/config.module.ts · ×133src/config/config.module.ts:1

What to do

  1. Resolve the 133 Low coverage finding(s) in Code Coverage — start with module-authorization.gateway.ts (2), config.module.ts, configuration.ts. — One of this dimension's main actionable groups (133 warning-level).
  2. Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D9 · Test Distribution9.6 / 10Exemplary✓ Tool-verified

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality8.4 / 10Strong✓ 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 8.4 / 10 · rule-coverage 100% · ceiling Prevented

2 skipped (2 with a documented reason), 188 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1765 tests.

No assertions: returns a failure Result for an unknown currency code · ×188src/infrastructure/platform/get-platform-config.query.spec.ts:51
Mock-dominated test: returns unauthorized without revoking others when logout wins the rotation race · ×4src/modules/authentication/core/application/usecases/refresh-token/refresh-token.usecase.spec.ts:523
Skipped (documented): (unnamed test) · ×2src/modules/identity/primary-adapters/decorators/current-user.decorator.spec.ts:11

What to do

  1. Resolve the 188 No assertions finding(s) in Test Quality — start with postgres-inventory-repository.spec.ts (10), cached.product-repository.spec.ts (8), postgres.cart-repository.spec.ts (7). — One of this dimension's main actionable groups (188 warning-level).
  2. Resolve the 4 Mock-dominated test finding(s) in Test Quality — start with checkout-failure.listener.spec.ts (3), refresh-token.usecase.spec.ts. — One of this dimension's main actionable groups (4 recommendation-level).
  3. Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `npm ci --ignore-scripts` in the repository root (1754 tests)): measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

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

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

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

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

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

Deprecated: prom-clientpackage.json:171
Deprecated: glob · ×5REDACTED:7897
Outdated (npm): @nestjs/common · ×16

What to do

  1. Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (5). — One of this dimension's main actionable groups (5 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 Scanning0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Prevented

3 secret(s) detected.

REDACTED

What to do

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

Top hotspots: scripts/generate-envs.js (15×26=390); src/modules/products/core/application/seed/seed-demo-catalog.usecase.ts (12×25=300); src/modules/carts/secondary-adapters/mappers/query/cart-query.mapper.ts (12×24=288) Repeated repair below the complexity floor: src/interceptors/sanitize.interceptor.ts (5 of 8 changes were fixes)

Hotspot: scripts/generate-envs.js · ×7scripts/generate-envs.js:59
Repeated repair: src/interceptors/sanitize.interceptor.tssrc/interceptors/sanitize.interceptor.ts:39

What to do

  1. Resolve the 7 Hotspot finding(s) in Churn × Complexity Hotspots — start with generate-envs.js, seed-demo-catalog.usecase.ts, cart-query.mapper.ts. — One of this dimension's main actionable groups (7 warning-level).
  2. Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with sanitize.interceptor.ts. — One of this dimension's main actionable groups (1 warning-level).

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

D19 · Documentation QualityExemplary◐ Sampled · advisory

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

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

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

The repository's root README and the docs/README directories form a complete documentation suite. The root README (903 words) gives an overview of the project as 'E-commerce Store API', links to CI, coverage, TypeScript, NestJS, PostgreSQL, Redis, BullMQ, Vite, Docker, and a license badge, then dives into What this is before stating what it does or how to use its modules. The docs/README directory (857 words) is an index of the architecture documentation, covering System & Domain Architecture, Project Implementation Patterns, Domain Architecture, Architecture Decision Records (ADRs), and more, with a full outline; each section named in the outline exists. A separate docs/ai README (241 words) explains how to maintain the AI guidance folder while referencing the root AGENTS.md entry point. The only unshown element is the missing overview/installation for the repository's root README, which would fall under the 'missing-overview' category but is instead covered by the project-level docs/README. This is a comprehensive project documentation set: the READMEs and architecture/Docs markdown files together provide an overview (roadmap, anti-patterns, architectural invariants), installation/build/contribution guidance for the repository root, and detailed per-document coverage of every phase, task, and deliverable. The roadmap file alone is a living document that is both well-structured and self-navigating; it is clipped mid-sentence but its outline (feature phases, completed phases, pending work) exists and must not be flagged as missing. This project is a comprehensive architecture and design reference with an outstanding overview document (docs/assets/ARCHITECTURE-OVERVIEW.md) that maps high-level context to the detailed DDD/Hexagonal architecture documents. The core structure is a single 'System Architecture' document containing a full table of contents for strategic domain-driven design, component dependencies, SAGA compensation flow, payment event handling, idempotency logic, and a notification system architecture, with each section named in the outline present (e.g. 'Key Patterns Implemented', 'Payment Methods (Current Scope)', 'SAGA Compensation Flow (Failure Handling)'). The CQRS, DDD/Hexagonal, and rate-limiting documents are also fully outlined within the Architecture docs, covering academic origins, core capabilities, dependency rules, and implementation mapping. A dedicated Engineering & Architectural Principles document defines a strict set of design principles with evaluation criteria for every rule in the architecture.

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR QualityExemplary◐ Sampled · advisory

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d20_recommendation.md.

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

D25 · ADR ConformanceAdequategated by 1 critical finding◐ Sampled · advisory

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

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

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

3 conform / 1 violate across 6 ADRs.

ADR not followed: ADR-0004: Inventory Data Integrity, Concurrency & Schema Optimizationdocs/architecture/adr/ADR-0004-inventory-integrity-and-concurrency.md
ADR not followed: ADR-0005: Typed Atomic OCC Update Contract · ×3docs/architecture/adr/ADR-0005-typed-atomic-occ-update-contract.md:41detected by adr-prohibition

What to do

  1. Resolve the 1 ADR not followed finding(s) in ADR Conformance — start with ADR-0004-inventory-integrity-and-concurrency.md. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 3 ADR not followed finding(s) in ADR Conformance — start with ADR-0005-typed-atomic-occ-update-contract.md, ADR-0006-redis-fail-open-cache-aside.md, ADR-0009-demo-reset-ops-infrastructure.md. — One of this dimension's main actionable groups (3 recommendation-level).
  3. Enforce ADR Conformance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D26 · Project Cohesion0.0 / 10Critical✓ Tool-verified

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

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

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

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

D28 · Secrets (history)4.0 / 10Weak✓ 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 4.0 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 4 High secret finding(s) in Secrets (history) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
  2. Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  3. 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)0.6 / 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 0.6 / 10 · rule-coverage 100% · ceiling Documented

51 finding(s): 0 critical, 1 high, 50 medium, 0 low. semgrep hit a parse error in 6 file(s) — `src/modules/authentication/secondary-adapters/repositories/postgres-session-token-repository/postgres-session-token.repository.spec.ts` (lines 38–157), `src/modules/carts/secondary-adapters/repositories/postgres-cart-repository/postgres.cart-repository.spec.ts` (line 21), `src/modules/identity/secondary-adapters/repositories/postgres-user-repository/postgres-user.repository.spec.ts` (line 21), `src/modules/inventory/testing/mocks/inventory-repository.mock.ts` (line 42, line 49), `src/modules/orders/secondary-adapters/repositories/postgres-order-repository/postgres.order-repository.spec.ts` (line 23), … (+1 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 47 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED (5), REDACTED (5). — One of this dimension's main actionable groups (47 warning-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. Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).

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

D30 · Dependency Vulnerabilities9.2 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

REDACTED
REDACTED

What to do

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

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

D31 · IaC & Container Security8.9 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

REDACTED
REDACTED

What to do

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

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling9.9 / 10Adequategated by 5 critical findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: cached-user.repository.ts↔cached-inventory-repository.ts 55%; cached-user.repository.ts↔cached.product-repository.ts 55%; cached.product-repository.ts↔postgres.product-repository.ts 55%

Boundary-crossing change coupling: cached-user.repository.ts ↔ cached-inventory-repository.ts · ×5src/modules/identity/secondary-adapters/repositories/cached-user-repository/cached-user.repository.ts:1
Change coupling: cached.product-repository.ts ↔ postgres.product-repository.tssrc/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.ts:1

What to do

  1. Resolve the 5 Boundary-crossing change coupling finding(s) in Change Coupling — start with cached-user.repository.ts (2), cached.cart-repository.ts (2), cached-inventory-repository.ts. — One of this dimension's main actionable groups (5 issue-level).
  2. Resolve the 1 Change coupling finding(s) in Change Coupling — start with cached.product-repository.ts. — One of this dimension's main actionable groups (1 warning-level).

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

D36 · Supply-chain Provenance & Signing7.5 / 10Strong✓ Tool-verified

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

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

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

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

REDACTED
REDACTED

What to do

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

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

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

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AX10 · Code composition7.1 / 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 cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

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

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

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

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

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

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

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

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

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

C1 · Data Protection4.0 / 10Weak✓ Tool-verified

Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.

Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.

  • No in-app HTTPS enforcement, but a trusted-proxy setting ('trust proxy' / trustProxy) indicates a reverse-proxy topology — terminating TLS in the app would be wrong in this layout. Verify the reverse proxy enforces TLS. — src/main.ts:70

What to do

  • Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, Azure Key Vault, GCP KMS / REDACTED Manager, HashiCorp Vault) and encrypt the most sensitive columns (typeorm-encrypted, prisma-field-encryption, mongoose-field-encryption or MongoDB CSFLE) — partial coverage still leaves gaps.
C2 · Access Controls10.0 / 10Exemplary○ Nothing flagged

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.

C4 · Data Retention9.0 / 10Exemplary✓ Tool-verified

Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).

Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.

  • A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a documented retention period / data-expiry.

What to do

  • Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
DM1 · Aggregate boundaries10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.

Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.

Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.

DM10 · One transaction, one aggregate9.9 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.

Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.

  • `ChangePasswordUseCase.execute` saves `CredentialRepository`, `SessionTokenRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts:40

What to do

  • Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.
DM11 · Constructible invalid state10.0 / 10Exemplary○ Nothing flagged

Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.

Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule), on a type that also offers no static Create/Of/From/New factory. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.

DM2 · Strongly-typed ids3.0 / 10Weak✓ Tool-verified

Other · Domain Modelling — How much of the domain uses strongly-typed ids vs raw Guid/string/int — adoption curve, not all-or-nothing.

Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.

Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.

  • `OrderItem.productId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that. — src/modules/orders/core/domain/entities/order-items.ts:57
  • `Order.userId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that. — src/modules/orders/core/domain/entities/order.ts:103
  • `CartItem.productId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that. — src/modules/carts/core/domain/entities/cart-item.ts:86
  • `Cart.userId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that. — src/modules/carts/core/domain/entities/cart.ts:52
  • `ReservationItem.productId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that. — src/modules/inventory/core/domain/entities/reservation-item.ts:26
  • `Reservation.orderId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that. — src/modules/inventory/core/domain/entities/reservation.ts:70
  • `Refund.paymentId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that. — src/modules/payments/core/domain/entities/refund.ts:73
  • `Payment.orderId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that. — src/modules/payments/core/domain/entities/payment.ts:133
  • `SessionToken.userId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that. — src/modules/authentication/core/domain/entities/session-token.ts:35
  • `Credential.userId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that. — src/modules/authentication/core/domain/entities/credential.ts:27
  • `UserRoleAssignment.userId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that. — src/modules/authorization/core/domain/entities/user-role-assignment.ts:30
  • `UserRoleAssignment.roleId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that. — src/modules/authorization/core/domain/entities/user-role-assignment.ts:34
  • `Address.userId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that. — src/modules/identity/core/domain/entities/address.ts:99
  • `Inventory.productId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that. — src/modules/inventory/core/domain/entities/inventory.ts:81

What to do

  • Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model8.9 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.

Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.

Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.

  • `OrderItem` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/modules/orders/core/domain/entities/order-items.ts:17
  • `ReservationItem` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/modules/inventory/core/domain/entities/reservation-item.ts:11
  • `Permission` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/modules/authorization/core/domain/entities/permission.ts:13

What to do

  • Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state6.2 / 10Adequate✓ Tool-verified

Other · Domain Modelling — Whether entities protect their state — private/init-only setters, and collections handed out as read-only views rather than the mutable backing collection — instead of exposing writable state that bypasses invariants. Softened when a rehydration framework (Marten/EF) is present.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

  • `Credential` exposes publicly writable state (passwordHash, mustChangePassword). — src/modules/authentication/core/domain/entities/credential.ts:10

What to do

  • Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
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 & stubs9.0 / 10Exemplary✓ 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.

  • Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — scripts/ascii-prose.cjs:328

What to do

  • Remove the dead code that still moves this score: delete dead if(false) branches and either do the real async work or drop the async keyword from fake-async functions.
M1 · Documentation (README)7.3 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

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

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

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

What to do

  • Grow the ADR log (currently 7) — reach 8 to raise the maturity tier; document significant decisions as they're made.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

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

M4 · Documentation accuracy0.0 / 10Critical◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

  • README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong. — README.md:40
  • docs/architecture/DDD-HEXAGONAL.md names `core/domain/models/`, but no file or folder `core/domain/models` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/architecture/DDD-HEXAGONAL.md:111
  • docs/architecture/DDD-HEXAGONAL.md names `core/domain/events/`, but no file or folder `core/domain/events` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/architecture/DDD-HEXAGONAL.md:116
  • docs/development/SEEDING.md documents the environment variable `NEXT_PUBLIC_API_BASE_URL`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/development/SEEDING.md:142
  • docs/development/SEEDING.md documents the environment variable `NEXT_PUBLIC_IMAGE_ALLOWED_HOSTS`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/development/SEEDING.md:142
  • docs/security/ADMIN-BOOTSTRAP.md documents the environment variable `ADMIN_EMAIL`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/security/ADMIN-BOOTSTRAP.md:25
  • docs/security/ADMIN-BOOTSTRAP.md documents the environment variable `ADMIN_PASSWORD`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/security/ADMIN-BOOTSTRAP.md:25
  • docs/security/ADMIN-BOOTSTRAP.md documents the environment variable `KEYCLOAK_ADMIN`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/security/ADMIN-BOOTSTRAP.md:62
  • docs/security/SECRET-ROTATION.md documents the environment variable `STRIPE_SECRET_KEY`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/security/SECRET-ROTATION.md:202
  • docs/infrastructure/cicd/PROJECT-PIPELINE.md names `actions/setup-node`, but no file or folder `actions/setup-node` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/infrastructure/cicd/PROJECT-PIPELINE.md:57
  • docs/infrastructure/cicd/PROJECT-PIPELINE.md links to `../../.github/actions/prepare-test-env/action.yml`, but `docs/.github/actions/prepare-test-env/action.yml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/infrastructure/cicd/PROJECT-PIPELINE.md:93
  • docs/infrastructure/cicd/PROJECT-PIPELINE.md links to `../../.github/actions/prepare-db-env/action.yml`, but `docs/.github/actions/prepare-db-env/action.yml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/infrastructure/cicd/PROJECT-PIPELINE.md:110
  • docs/data/collections/bruno/README.md links to `../../development/SEEDING.md`, but `docs/data/development/SEEDING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/data/collections/bruno/README.md:14
  • docs/infrastructure/cicd/pipeline/PIPELINE-OPTIMIZATION.md names `Cargo.toml`, but no file or folder `Cargo.toml` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/infrastructure/cicd/pipeline/PIPELINE-OPTIMIZATION.md:43

What to do

  • Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests; docs/architecture/DDD-HEXAGONAL.md names `core/domain/models/`, but no file or folder `core/domain/models` exists; docs/architecture/DDD-HEXAGONAL.md names `core/domain/events/`, but no file or folder `core/domain/events` exists; docs/development/SEEDING.md documents the environment variable `NEXT_PUBLIC_API_BASE_URL`, but no code, script or configuration file names it; docs/development/SEEDING.md documents the environment variable `NEXT_PUBLIC_IMAGE_ALLOWED_HOSTS`, but no code, script or configuration file names it.
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.

P2 · Observability10.0 / 10Exemplary○ Nothing flagged

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.

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

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

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

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

What to do

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

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

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

What to do

  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup7.0 / 10Strong✓ 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).
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

P7 · Outbound HTTP resilience10.0 / 10Exemplary○ Nothing flagged

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.

P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

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.

P9 · Domain vs controller coverage8.8 / 10Exemplary✓ Tool-verified

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

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

What to do

  • Raise domain coverage toward 100% — cover the remaining aggregates / value objects / domain services where the business invariants and costly bugs live.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

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

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

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

What to do

  • Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication7.8 / 10Strong✓ Tool-verified

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

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

  • 198 duplicated blocks under src/modules/ have copies in at least two of the sibling directories analytics, authentication, authorization, carts, identity, inventory (+4 more sibling(s) not listed) — 81 of them are reported below, and 117 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 198 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 198 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 198 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. — src/modules/carts/secondary-adapters/repositories/cached-cart-repository/cached.cart-repository.ts:15
  • 5 duplicated blocks under src/modules/orders/core/application/usecases/ have copies in at least two of the sibling directories cancel-order, confirm-order, deliver-order, handle-payment-completed, handle-payment-failed, process-order (+1 more sibling(s) not listed) — 3 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/modules/orders/core/application/usecases/handle-payment-completed/handle-payment-completed.usecase.ts:16
  • src/modules/products/core/domain/entities/category.ts:20 · src/modules/products/core/domain/entities/product.ts:41 — the two spans are one implementation copied and then locally edited — 646 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. — src/modules/products/core/domain/entities/category.ts:20
  • src/modules/carts/secondary-adapters/repositories/cached-cart-repository/cached.cart-repository.ts:15 · src/modules/payments/secondary-adapters/repositories/cached-payment-repository/cached.payment-repository.ts:16 — the two spans are one implementation copied and then locally edited — 550 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. — src/modules/carts/secondary-adapters/repositories/cached-cart-repository/cached.cart-repository.ts:15
  • src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts:20 · src/modules/authentication/core/application/usecases/login-user/login-user.usecase.ts:17 — the two spans are one implementation copied and then locally edited — 321 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. — src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts:20
  • src/modules/inventory/secondary-adapters/query/postgres-inventory-query.adapter.ts:16 · src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts:18 — the two spans are one implementation copied and then locally edited — 321 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. — src/modules/inventory/secondary-adapters/query/postgres-inventory-query.adapter.ts:16
  • src/modules/inventory/secondary-adapters/repositories/postgres-inventory-repository/postgres-inventory-repository.ts:208 · src/modules/products/secondary-adapters/repositories/postgres-product-repository/postgres.product-repository.ts:31 — the two spans are one implementation copied and then locally edited — 298 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/modules/inventory/secondary-adapters/repositories/postgres-inventory-repository/postgres-inventory-repository.ts:208
  • src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:120 · src/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.ts:21 — the two spans are one implementation copied and then locally edited — 372 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. — src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:120
  • src/modules/inventory/secondary-adapters/repositories/cached-inventory-repository/cached-inventory-repository.ts:179 · src/modules/payments/secondary-adapters/repositories/cached-payment-repository/cached.payment-repository.ts:46 — the two spans are one implementation copied and then locally edited — 292 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. — src/modules/inventory/secondary-adapters/repositories/cached-inventory-repository/cached-inventory-repository.ts:179
  • src/modules/carts/secondary-adapters/repositories/postgres-cart-repository/postgres.cart-repository.ts:86 · src/modules/orders/secondary-adapters/repositories/postgres-order-repository/postgres.order-repository.ts:83 — 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. — src/modules/carts/secondary-adapters/repositories/postgres-cart-repository/postgres.cart-repository.ts:86
  • src/modules/identity/primary-adapters/dto/add-address.dto.ts:7 · src/modules/identity/primary-adapters/dto/update-address.dto.ts:6 — the two spans are one implementation copied and then locally edited — 161 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. — src/modules/identity/primary-adapters/dto/add-address.dto.ts:7
  • src/modules/payments/core/domain/value-objects/payment-status.ts:11 · src/modules/payments/core/domain/value-objects/refund-status.ts:9 — the two spans are one implementation copied and then locally edited — 229 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. — src/modules/payments/core/domain/value-objects/payment-status.ts:11
  • src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts:150 · src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts:195 — 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. — src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts:150
  • src/modules/inventory/secondary-adapters/repositories/cached-inventory-repository/cached-inventory-repository.ts:104 · src/modules/inventory/secondary-adapters/repositories/postgres-inventory-repository/postgres-inventory-repository.ts:60 — the two spans are one implementation copied and then locally edited — 216 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. — src/modules/inventory/secondary-adapters/repositories/cached-inventory-repository/cached-inventory-repository.ts:104
  • src/modules/inventory/secondary-adapters/schedulers/bullmq-inventory.scheduler.ts:29 · src/modules/inventory/secondary-adapters/schedulers/bullmq-inventory.scheduler.ts:76 · src/modules/orders/secondary-adapters/schedulers/bullmq-checkout.scheduler.ts:249 — 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. — src/modules/inventory/secondary-adapters/schedulers/bullmq-inventory.scheduler.ts:29
  • src/modules/orders/core/application/usecases/handle-payment-completed/handle-payment-completed.usecase.ts:16 · src/modules/orders/core/application/usecases/handle-payment-failed/handle-payment-failed.usecase.ts:15 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/modules/orders/core/application/usecases/handle-payment-completed/handle-payment-completed.usecase.ts:16
  • src/modules/authorization/secondary-adapter/repositories/postgres-role-repository/postgres-role.repository.ts:51 · src/modules/products/secondary-adapters/repositories/postgres-category-repository/postgres.category-repository.ts:21 — the two spans are one implementation copied and then locally edited — 222 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. — src/modules/authorization/secondary-adapter/repositories/postgres-role-repository/postgres-role.repository.ts:51
  • src/modules/carts/secondary-adapters/persistence/mappers/cart.mapper.ts:10 · src/modules/orders/secondary-adapters/persistence/mappers/order.mapper.ts:15 — 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. — src/modules/carts/secondary-adapters/persistence/mappers/cart.mapper.ts:10
  • src/modules/identity/primary-adapters/dto/add-address.dto.ts:7 · src/modules/identity/primary-adapters/dto/address-response.dto.ts:12 — the two spans are one implementation copied and then locally edited — 148 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. — src/modules/identity/primary-adapters/dto/add-address.dto.ts:7
  • src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.ts:276 · src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.ts:350 — the two spans are one implementation copied and then locally edited — 267 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. — src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.ts:276
  • src/modules/products/secondary-adapters/query/postgres-product-query.adapter.ts:143 · src/modules/products/secondary-adapters/query/postgres-product-query.adapter.ts:185 — 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. — src/modules/products/secondary-adapters/query/postgres-product-query.adapter.ts:143
  • src/modules/carts/secondary-adapters/query/postgres-cart-query.adapter.ts:20 · src/modules/carts/secondary-adapters/query/postgres-cart-query.adapter.ts:61 — 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. — src/modules/carts/secondary-adapters/query/postgres-cart-query.adapter.ts:20
  • src/modules/analytics/secondary-adapters/mappers/query/analytics-query.mapper.ts:93 · src/modules/analytics/secondary-adapters/mappers/query/analytics-query.mapper.ts:188 — the two spans are one implementation copied and then locally edited — 204 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. — src/modules/analytics/secondary-adapters/mappers/query/analytics-query.mapper.ts:93
  • src/modules/identity/core/domain/entities/address.ts:57 · src/modules/orders/core/domain/value-objects/shipping-address.ts:39 — the two spans are one implementation copied and then locally edited — 203 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. — src/modules/identity/core/domain/entities/address.ts:57
  • REDACTED:111 · REDACTED:111 — 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. — REDACTED:111
  • src/modules/authorization/authorization.module.ts:47 · src/modules/inventory/inventory.module.ts:81 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/modules/authorization/authorization.module.ts:47
  • src/modules/inventory/inventory.processor.ts:16 · src/modules/notifications/notifications.processor.ts:20 — 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. — src/modules/inventory/inventory.processor.ts:16
  • src/modules/orders/core/application/usecases/list-orders/list-orders.usecase.ts:16 · src/modules/payments/core/application/usecases/list-payments/list-payments.usecase.ts:15 — 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. — src/modules/orders/core/application/usecases/list-orders/list-orders.usecase.ts:16
  • src/modules/products/core/application/usecases/activate-product/activate-product.usecase.ts:11 · src/modules/products/core/application/usecases/deactivate-product/deactivate-product.usecase.ts:11 — the two spans are one implementation copied and then locally edited — 183 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. — src/modules/products/core/application/usecases/activate-product/activate-product.usecase.ts:11
  • src/modules/products/core/application/usecases/categories/activate-category.usecase.ts:11 · src/modules/products/core/application/usecases/categories/deactivate-category.usecase.ts:11 — 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. — src/modules/products/core/application/usecases/categories/activate-category.usecase.ts:11
  • src/modules/products/core/application/usecases/create-product/create-product.usecase.ts:49 · src/modules/products/core/application/usecases/update-product/update-product.usecase.ts:41 — the two spans are one implementation copied and then locally edited — 191 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. — src/modules/products/core/application/usecases/create-product/create-product.usecase.ts:49
  • src/modules/carts/carts.module.ts:37 · src/modules/orders/orders.module.ts:99 — 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. — src/modules/carts/carts.module.ts:37
  • src/modules/identity/primary-adapters/dto/address-response.dto.ts:12 · src/modules/identity/primary-adapters/dto/update-address.dto.ts:6 — the two spans are one implementation copied and then locally edited — 106 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. — src/modules/identity/primary-adapters/dto/address-response.dto.ts:12
  • src/modules/identity/core/application/usecases/address/add-address/add-address.usecase.ts:17 · src/modules/identity/core/application/usecases/address/update-address/update-address.usecase.ts:16 — 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. — src/modules/identity/core/application/usecases/address/add-address/add-address.usecase.ts:17
  • src/modules/payments/core/application/usecases/get-payment-by-order-id/get-payment-by-order-id.usecase.ts:17 · src/modules/payments/core/application/usecases/get-payment/get-payment.usecase.ts:17 — the two spans are one implementation copied and then locally edited — 128 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. — src/modules/payments/core/application/usecases/get-payment-by-order-id/get-payment-by-order-id.usecase.ts:17
  • src/modules/orders/primary-adapters/jobs/release-order-stock.job.ts:11 · src/modules/orders/primary-adapters/jobs/release-stock.job.ts:12 — 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. — src/modules/orders/primary-adapters/jobs/release-order-stock.job.ts:11
  • src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:65 · src/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.ts:141 — the two spans are one implementation copied and then locally edited — 167 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. — src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:65
  • src/modules/authentication/secondary-adapters/adapters/module-identity.gateway.ts:38 · src/modules/authentication/secondary-adapters/adapters/module-identity.gateway.ts:68 — all 2 copies are in the same file, 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. — src/modules/authentication/secondary-adapters/adapters/module-identity.gateway.ts:38
  • src/modules/identity/secondary-adapters/repositories/cached-user-repository/cached-user.repository.ts:124 · src/modules/identity/secondary-adapters/repositories/cached-user-repository/cached-user.repository.ts:164 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/modules/identity/secondary-adapters/repositories/cached-user-repository/cached-user.repository.ts:124
  • REDACTED:85 · REDACTED:173 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:85

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.
R2 · Cyclomatic Complexity9.3 / 10Exemplary✓ Tool-verified

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

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

  • generateEnvs has cyclomatic complexity 26 and cognitive complexity 44; 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. — scripts/generate-envs.js:169
  • toPresentationDto has cyclomatic complexity 26 and cognitive complexity 35; 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. — src/modules/carts/secondary-adapters/mappers/query/cart-query.mapper.ts:11
  • (anonymous) has cyclomatic complexity 25 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. — scripts/generate-envs.js:62
  • skipString has cyclomatic complexity 23 and cognitive complexity 35; 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. — scripts/ascii-prose.cjs:148
  • walk has cyclomatic complexity 22 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. — scripts/ascii-prose.cjs:54
  • (top-level) has cyclomatic complexity 22 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/filters/global-exception.filter.ts:1
  • selectVitestCommands has cyclomatic complexity 22 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 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. — scripts/agent-output.mjs:78
  • (top-level) has cyclomatic complexity 19 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. — src/modules/authentication/core/application/usecases/refresh-token/refresh-token.usecase.ts:1
  • list has cyclomatic complexity 19 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. — src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts:25
  • listOrders 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. — src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:27
  • (top-level) has cyclomatic complexity 17 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. — src/modules/payments/core/application/usecases/create-payment/create-payment.usecase.ts:1
  • runSetup has cyclomatic complexity 16 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 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. — scripts/lib/setup-bootstrap.js:15
  • list has cyclomatic complexity 16 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. — src/modules/products/secondary-adapters/query/postgres-product-query.adapter.ts:24
  • list has cyclomatic complexity 15 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. — src/modules/inventory/secondary-adapters/query/postgres-inventory-query.adapter.ts:23
  • findComments has cyclomatic complexity 14 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/ascii-prose.cjs:143
  • (anonymous) has cyclomatic complexity 14 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/modules/orders/primary-adapters/listeners/checkout-failure.listener.ts:26
  • redactInPlace 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. — src/infrastructure/logging/winston-logger.service.ts:197
  • (top-level) has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts:1, src/modules/identity/core/application/usecases/address/update-address/update-address.usecase.ts:1

What to do

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

  • src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.ts has 404 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.ts:1
R4 · Test Coverage9.5 / 10Exemplary✓ Tool-verified

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

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

  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×30) — scripts/ascii-prose.cjs:1, scripts/db-restore-drill.js:1, scripts/audit-openapi.js:1, …

What to do

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

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

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

What to do

  • Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

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

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

R7 · Dead Code8.6 / 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 29 application, 35 tooling and 385 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 (29 application, 35 tooling, 385 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/modules/orders/primary-adapters/dto/update-order.dto.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 — src/modules/orders/primary-adapters/dto/create-order.dto.ts
  • no import path from any entry point (29 application, 35 tooling, 385 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 (×18) — src/modules/inventory/core/domain/value-objects/stock-adjustment-reason.ts, src/modules/payments/primary-adapters/dto/payment-method-details.dto.ts, src/infrastructure/websocket/guards/ws-auth.guard.ts, …
  • no import path from any entry point (29 application, 35 tooling, 385 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/modules/orders/primary-adapters/dto/create-order.dto.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 — src/modules/orders/primary-adapters/dto/create-order-item.dto.ts
  • no import path from any entry point (29 application, 35 tooling, 385 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/modules/orders/primary-adapters/dto/order-response.dto.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 — src/modules/orders/primary-adapters/dto/order-item-response.dto.ts
  • Nothing imports this binding — it is safe to review for removal. (×15) — scripts/agent-output.mjs:124, src/config/validate-env.ts:155, src/infrastructure/health/dto/health-check-response.dto.ts:3, …
  • Nothing ultimately consumes this binding: its only referrer is the re-export in src/modules/carts/testing/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/modules/carts/testing/index.ts in the same commit, or the barrel will import a name that no longer exists. — REDACTED:5
  • Nothing ultimately consumes this binding: its only referrer is the re-export in src/modules/identity/testing/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/modules/identity/testing/index.ts in the same commit, or the barrel will import a name that no longer exists. — src/modules/identity/testing/builders/user.builder.ts:4
  • Nothing ultimately consumes this binding: its only referrer is the re-export in src/modules/products/testing/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/modules/products/testing/index.ts in the same commit, or the barrel will import a name that no longer exists. — src/modules/products/testing/builders/product.builder.ts:5

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.5 / 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. (×4) — src/filters/global-exception.filter.ts:10, src/config/configuration.ts:1, test/integration/redis/redis-chaos.global-setup.ts:1, …
  • Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)

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.

  • src/modules/authorization/secondary-adapter/orm/role-permission.schema.ts → src/modules/authorization/secondary-adapter/orm/role.schema.ts → src/modules/authorization/secondary-adapter/orm/role-permission.schema.ts — src/modules/authorization/secondary-adapter/orm/role-permission.schema.ts:10
  • src/modules/carts/secondary-adapters/orm/cart-item.schema.ts → src/modules/carts/secondary-adapters/orm/cart.schema.ts → src/modules/carts/secondary-adapters/orm/cart-item.schema.ts — src/modules/carts/secondary-adapters/orm/cart-item.schema.ts:10
  • src/modules/identity/secondary-adapters/orm/address.schema.ts → src/modules/identity/secondary-adapters/orm/user.schema.ts → src/modules/identity/secondary-adapters/orm/address.schema.ts — src/modules/identity/secondary-adapters/orm/address.schema.ts:12
  • src/modules/inventory/secondary-adapters/orm/reservation-item.schema.ts → src/modules/inventory/secondary-adapters/orm/reservation.schema.ts → src/modules/inventory/secondary-adapters/orm/reservation-item.schema.ts — src/modules/inventory/secondary-adapters/orm/reservation-item.schema.ts:10
  • src/modules/orders/secondary-adapters/orm/order-item.schema.ts → src/modules/orders/secondary-adapters/orm/order.schema.ts → src/modules/orders/secondary-adapters/orm/order-item.schema.ts — src/modules/orders/secondary-adapters/orm/order-item.schema.ts:12
  • src/modules/orders/testing/factories/order-dto.factory.ts → src/testing/factories/auth-payload.factory.ts → src/testing/helpers/test-data.helper.ts → src/modules/orders/testing/factories/order-dto.factory.ts — src/modules/orders/testing/factories/order-dto.factory.ts:22
  • src/modules/payments/secondary-adapters/orm/payment.schema.ts → src/modules/payments/secondary-adapters/orm/refund.schema.ts → src/modules/payments/secondary-adapters/orm/payment.schema.ts — src/modules/payments/secondary-adapters/orm/payment.schema.ts:12

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

X14 · Bypassable address 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.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

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

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

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

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

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

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

  • `isKnownRedisConnectionError` is exported and takes `err: unknown` from its caller, and it calls itself at line 22 (`isKnownRedisConnectionError`) with a piece of `err` — and nowhere in `isKnownRedisConnectionError` 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 `isKnownRedisConnectionError` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/infrastructure/redis/redis-error.utils.ts:22
  • `isRedisJson` is exported and takes `value: unknown` from its caller, and it calls itself at line 22 (`isRedisJson`) with a piece of `value` (and at line 26) — and nowhere in `isRedisJson` 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 `isRedisJson` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/infrastructure/redis/cache/cache-json.ts:22

What to do

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

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

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

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

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

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

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

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

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

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

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

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

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

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

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

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

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 handling7.3 / 10Strong✓ Tool-verified

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

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

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×6) — scripts/db-restore-drill.js:158, scripts/lib/pg.js:584, scripts/lib/pg.js:591, …
  • `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — scripts/ascii-prose.cjs:58

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 logging2.5 / 10Weak✓ 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 219 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. — scripts/generate-envs.js:219
  • `log` at line 239 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. — scripts/generate-envs.js:239
  • `log` at line 246 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. — scripts/generate-envs.js:246
  • `log` at line 255 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. — scripts/generate-envs.js:255
  • `error` at line 262 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. — scripts/generate-envs.js:262
  • `log` at line 270 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. — scripts/generate-envs.js:270
  • `error` at line 279 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. — scripts/generate-envs.js:279
  • `error` at line 35 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. — scripts/lib/cli.js:35
  • `error` at line 37 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. — scripts/lib/cli.js:37
  • `log` at line 89 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. — src/main.ts:89
  • `log` at line 104 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. — src/main.ts:104
  • `warn` at line 54 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. — src/filters/global-exception.filter.ts:54
  • `warn` at line 75 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. — src/filters/global-exception.filter.ts:75
  • `warn` at line 87 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. — src/filters/global-exception.filter.ts:87
  • `warn` at line 99 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. — src/filters/global-exception.filter.ts:99
  • `error` at line 105 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. — src/filters/global-exception.filter.ts:105
  • `error` at line 112 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. — src/filters/global-exception.filter.ts:112
  • `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. — src/infrastructure/events/event-emitter2.domain-event-publisher.ts:23
  • `warn` at line 49 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. — src/infrastructure/idempotency/idempotency.service.ts:49
  • `log` at line 63 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.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. — src/infrastructure/idempotency/idempotency.service.ts:63
  • `log` at line 77 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. — src/infrastructure/idempotency/idempotency.service.ts:77
  • `log` at line 81 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. — src/infrastructure/idempotency/idempotency.service.ts:81
  • `warn` at line 85 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. — src/infrastructure/idempotency/idempotency.service.ts:85
  • `warn` at line 93 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. — src/infrastructure/idempotency/idempotency.service.ts:93
  • `warn` at line 101 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. — src/infrastructure/idempotency/idempotency.service.ts:101
  • `warn` at line 107 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. — src/infrastructure/idempotency/idempotency.service.ts:107
  • `warn` at line 112 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. — src/infrastructure/idempotency/idempotency.service.ts:112
  • `log` at line 144 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. — src/infrastructure/idempotency/idempotency.service.ts:144
  • `error` at line 146 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. — src/infrastructure/idempotency/idempotency.service.ts:146
  • `log` at line 156 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. — src/infrastructure/idempotency/idempotency.service.ts:156
  • `error` at line 158 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. — src/infrastructure/idempotency/idempotency.service.ts:158
  • `log` at line 57 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. — src/infrastructure/jobs/base-job.handler.ts:57
  • `log` at line 61 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. — src/infrastructure/jobs/base-job.handler.ts:61
  • `error` at line 75 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. — src/infrastructure/jobs/base-job.handler.ts:75
  • `log` at line 85 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. — src/infrastructure/jobs/base-job.handler.ts:85
  • `error` at line 92 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. — src/infrastructure/jobs/base-job.handler.ts:92
  • `log` at line 68 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. — src/infrastructure/jwt/services/jwks.service.ts:68
  • `info` at line 177 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/infrastructure/logging/winston-logger.service.ts:177
  • `http` at line 24 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.http({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.http('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. — src/infrastructure/logging/middleware/http-logging.middleware.ts:24
  • `warn` at line 53 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. — src/infrastructure/metrics/collectors/infra-metrics.collector.ts:53

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types1.2 / 10Critical✓ Tool-verified

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

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

  • 0/1 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.
  • ~12.6 `!` null assertions per 1k TypeScript source lines — 606 assertion(s) across the 48012 source line(s) of the 749 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: src/modules/orders/primary-adapters/dto/order-detail-response.dto.ts (28), src/modules/products/primary-adapters/dto/product-response.dto.ts (26), src/modules/inventory/primary-adapters/dto/inventory-response.dto.ts (22). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

What to do

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

Reference — by lens

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

LensScoreRatingImpact
Code Health54%Adequate — gated by X4, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture59%Adequate — gated by D26, R9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity55%Adequate — gated by M4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness48%Adequate — gated by D13, R8, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security69%Adequate — gated by D29Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling70%Adequate — gated by DM2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 2 check(s) recorded observations but carry no score

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

  • P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • X10 Duplicated predicate — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for

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

  • C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model, an ORM write hook that records changes — a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware — or a change-history plugin such as mongoose-history or sequelize-paper-trail) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
  • C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 44 check(s) not relevant to this codebase

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

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — Not applicable: NestJS makes a provider that injects a request-scoped one request-scoped itself (scope bubbles up the injection chain), and gives every consumer its own transient instance by contract.
  • AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — time="2026-10-22T14:26:03Z" level=warning msg="The \"REDIS_PASSWORD\" variable is not set. Defaulting to a blank string." postgres Pulling redis Pulling redis Error Get "https://registry-1.docker.io/v2/": Forbidden postgres Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: time="2026-10-22T14:26:03Z" level=warning msg="The \"REDIS_PASSWORD\" variable is not set. Defaulting to a blank string." redis Pulling postgres Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden redis Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — No inline comments to assess — comment value is not applicable here.
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.cjs,.js,.mjs,.ts), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • 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.
  • D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
  • 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
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • S1 Web-Security Posture — Not assessed: 771 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
  • X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 29 finding(s)
R9 · Circular Imports · Import cycle (2 files) · ×6
  • Import cycle (2 files) src/modules/authorization/secondary-adapter/orm/role-permission.schema.ts:10 — src/modules/authorization/secondary-adapter/orm/role-permission.schema.ts → src/modules/authorization/secondary-adapter/orm/role.schema.ts → src/modules/authorization/secondary-adapter/orm/role-permission.schema.ts
  • Import cycle (2 files) src/modules/carts/secondary-adapters/orm/cart-item.schema.ts:10 — src/modules/carts/secondary-adapters/orm/cart-item.schema.ts → src/modules/carts/secondary-adapters/orm/cart.schema.ts → src/modules/carts/secondary-adapters/orm/cart-item.schema.ts
  • Import cycle (2 files) src/modules/identity/secondary-adapters/orm/address.schema.ts:12 — src/modules/identity/secondary-adapters/orm/address.schema.ts → src/modules/identity/secondary-adapters/orm/user.schema.ts → src/modules/identity/secondary-adapters/orm/address.schema.ts
  • Import cycle (2 files) src/modules/inventory/secondary-adapters/orm/reservation-item.schema.ts:10 — src/modules/inventory/secondary-adapters/orm/reservation-item.schema.ts → src/modules/inventory/secondary-adapters/orm/reservation.schema.ts → src/modules/inventory/secondary-adapters/orm/reservation-item.schema.ts
  • Import cycle (2 files) src/modules/orders/secondary-adapters/orm/order-item.schema.ts:12 — src/modules/orders/secondary-adapters/orm/order-item.schema.ts → src/modules/orders/secondary-adapters/orm/order.schema.ts → src/modules/orders/secondary-adapters/orm/order-item.schema.ts
  • Import cycle (2 files) src/modules/payments/secondary-adapters/orm/payment.schema.ts:12 — src/modules/payments/secondary-adapters/orm/payment.schema.ts → src/modules/payments/secondary-adapters/orm/refund.schema.ts → src/modules/payments/secondary-adapters/orm/payment.schema.ts
D35 · Change Coupling · Boundary-crossing change coupling · ×5
  • Boundary-crossing change coupling: cached-user.repository.ts ↔ cached-inventory-repository.ts src/modules/identity/secondary-adapters/repositories/cached-user-repository/cached-user.repository.ts:1 — `src/modules/identity/secondary-adapters/repositories/cached-user-repository/cached-user.repository.ts` (context identity) and `src/modules/inventory/secondary-adapters/repositories/cached-inventory-repository/cached-inventory-repository.ts` (context inventory) sit in DIFFERENT parts of the tree yet change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `ea2cb1ed` ES-165: Refactor cached repositories to improve error handling and fa…; `403f343e` ES-164: Enhance cache mappers to handle null values and improve error…; `f354ecec` ES-164: Enhance cache mappers to handle null values and improve error… — run `git show` on any of them.
  • Boundary-crossing change coupling: cached-user.repository.ts ↔ cached.product-repository.ts src/modules/identity/secondary-adapters/repositories/cached-user-repository/cached-user.repository.ts:1 — `src/modules/identity/secondary-adapters/repositories/cached-user-repository/cached-user.repository.ts` (context identity) and `src/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.ts` (context products) sit in DIFFERENT parts of the tree yet change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `ea2cb1ed` ES-165: Refactor cached repositories to improve error handling and fa…; `403f343e` ES-164: Enhance cache mappers to handle null values and improve error…; `f354ecec` ES-164: Enhance cache mappers to handle null values and improve error… — run `git show` on any of them.
  • Boundary-crossing change coupling: cached-inventory-repository.ts ↔ cached.product-repository.ts src/modules/inventory/secondary-adapters/repositories/cached-inventory-repository/cached-inventory-repository.ts:1 — `src/modules/inventory/secondary-adapters/repositories/cached-inventory-repository/cached-inventory-repository.ts` (context inventory) and `src/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.ts` (context products) sit in DIFFERENT parts of the tree yet change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `ea2cb1ed` ES-165: Refactor cached repositories to improve error handling and fa…; `403f343e` ES-164: Enhance cache mappers to handle null values and improve error…; `f354ecec` ES-164: Enhance cache mappers to handle null values and improve error… — run `git show` on any of them.
  • Boundary-crossing change coupling: cached.cart-repository.ts ↔ cached-inventory-repository.ts src/modules/carts/secondary-adapters/repositories/cached-cart-repository/cached.cart-repository.ts:1 — `src/modules/carts/secondary-adapters/repositories/cached-cart-repository/cached.cart-repository.ts` (context carts) and `src/modules/inventory/secondary-adapters/repositories/cached-inventory-repository/cached-inventory-repository.ts` (context inventory) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `403f343e` ES-164: Enhance cache mappers to handle null values and improve error…; `f354ecec` ES-164: Enhance cache mappers to handle null values and improve error…; `acd21b9c` ES-164: Refactor CachePort imports across modules to use shared-kerne… — run `git show` on any of them.
  • Boundary-crossing change coupling: cached.cart-repository.ts ↔ cached.product-repository.ts src/modules/carts/secondary-adapters/repositories/cached-cart-repository/cached.cart-repository.ts:1 — `src/modules/carts/secondary-adapters/repositories/cached-cart-repository/cached.cart-repository.ts` (context carts) and `src/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.ts` (context products) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `403f343e` ES-164: Enhance cache mappers to handle null values and improve error…; `f354ecec` ES-164: Enhance cache mappers to handle null values and improve error…; `acd21b9c` ES-164: Refactor CachePort imports across modules to use shared-kerne… — run `git show` on any of them.
D28 · Secrets (history) · High secret · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D13 · REDACTED Scanning · Leaked secret · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · REDACTED · ×2
  • REDACTED
  • REDACTED
D25 · ADR Conformance · ADR not followed · ×1
  • ADR not followed: ADR-0004: Inventory Data Integrity, Concurrency & Schema Optimization docs/architecture/adr/ADR-0004-inventory-integrity-and-concurrency.md — The summary shows InventoryEntity has a Column() totalQuantity field, contradicting the ADR's decision to remove persisted totalQuantity. (docs/architecture/adr/ADR-0004-inventory-integrity-and-concurrency.md)
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High CVE · ×1
  • REDACTED
D31 · IaC & Container Security · High IaC · ×1
  • REDACTED
R8 · Dependency Hygiene · Unlisted import 'express' · ×1
  • Unlisted import 'express' src/filters/global-exception.filter.ts:10 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'ms' · ×1
  • Unlisted import 'ms' src/config/configuration.ts:1 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'testcontainers' · ×1
  • Unlisted import 'testcontainers' test/integration/redis/redis-chaos.global-setup.ts:1 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'uuid' · ×1
  • Unlisted import 'uuid' src/infrastructure/jobs/job-config.service.ts:8 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R9 · Circular Imports · Import cycle (3 files) · ×1
  • Import cycle (3 files) src/modules/orders/testing/factories/order-dto.factory.ts:22 — src/modules/orders/testing/factories/order-dto.factory.ts → src/testing/factories/auth-payload.factory.ts → src/testing/helpers/test-data.helper.ts → src/modules/orders/testing/factories/order-dto.factory.ts
Serious — 558 finding(s)
D10 · Test Quality · No assertions · ×188
  • No assertions: returns a failure Result for an unknown currency code src/infrastructure/platform/get-platform-config.query.spec.ts:51 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should return failure if user is not found src/modules/authentication/core/application/usecases/login-user/login-user.usecase.spec.ts:103 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should return failure if password is incorrect src/modules/authentication/core/application/usecases/login-user/login-user.usecase.spec.ts:118 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should return failure if user is deactivated src/modules/authentication/core/application/usecases/login-user/login-user.usecase.spec.ts:133 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should return failure if user has no assigned role src/modules/authentication/core/application/usecases/login-user/login-user.usecase.spec.ts:151 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: returns unauthorized when the refresh token signature is invalid src/modules/authentication/core/application/usecases/refresh-token/refresh-token.usecase.spec.ts:372 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should register a user successfully src/modules/authentication/core/application/usecases/register-user/register-user.usecase.spec.ts:51 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should return failure if email already exists src/modules/authentication/core/application/usecases/register-user/register-user.usecase.spec.ts:63 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: save rejects a second credential for the same userId src/modules/authentication/secondary-adapters/repositories/postgres-credential.repository/postgres-credential.repository.integration.spec.ts:37 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should return an error if repository fails src/modules/authorization/core/application/usecases/permissions/find-all-permissions/find-all-permissions.usecase.spec.ts:47 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should return failure if updating role in repository fails src/modules/authorization/core/application/usecases/role/update-role.usecase.spec.ts:89 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should return failure if role is not found src/modules/authorization/core/application/usecases/role/find-role-by-id.usecase.spec.ts:46 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should return failure if repository fails src/modules/authorization/core/application/usecases/role/find-all-roles.usecase.spec.ts:46 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should return failure if deleting role fails in repository src/modules/authorization/core/application/usecases/role/delete-role.usecase.spec.ts:78 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should return failure if user role assignment not found src/modules/authorization/core/application/usecases/user-role/find-role-by-user-id.usecase.spec.ts:64 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should validate successfully for deletion of non-system role src/modules/authorization/core/domain/entities/role.spec.ts:84 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should return DomainError when validating deletion of a system role src/modules/authorization/core/domain/entities/role.spec.ts:100 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: saveMany rejects a duplicate permission code src/modules/authorization/secondary-adapter/repositories/postgres-permission-repository/postgres-permission.repository.integration.spec.ts:48 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: update returns not-found when role id is missing src/modules/authorization/secondary-adapter/repositories/postgres-role-repository/postgres-role.repository.integration.spec.ts:84 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: save rejects a duplicate role code src/modules/authorization/secondary-adapter/repositories/postgres-role-repository/postgres-role.repository.integration.spec.ts:102 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: save rejects a second assignment for the same userId src/modules/authorization/secondary-adapter/repositories/postgres-user-role-assignment-repository/postgres-user-role-assignment.repository.integration.spec.ts:47 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: returns a failure when line items use different currencies src/modules/carts/core/application/mappers/cart-presentation.mapper.spec.ts:84 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should add item to cart successfully for admin src/modules/carts/core/application/usecases/add-cart-item/add-cart-item.usecase.spec.ts:41 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should add item to cart successfully for owning customer src/modules/carts/core/application/usecases/add-cart-item/add-cart-item.usecase.spec.ts:65 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should return failure (404) when customer does not own the cart src/modules/carts/core/application/usecases/add-cart-item/add-cart-item.usecase.spec.ts:122 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • + 163 more in this group — see findings.md.
D8 · Code Coverage · Low coverage · ×133
  • Low coverage: src/config/config.module.ts src/config/config.module.ts:1 — 0.0% line coverage (0/1).
  • Low coverage: src/config/configuration.ts src/config/configuration.ts:1 — 0.0% line coverage (0/3).
  • Low coverage: src/config/env-config.service.ts src/config/env-config.service.ts:1 — 4.2% line coverage (1/24).
  • Low coverage: src/config/resolve-env-file-path.ts src/config/resolve-env-file-path.ts:1 — 33.3% line coverage (2/6).
  • Low coverage: src/infrastructure/infrastructure.module.ts src/infrastructure/infrastructure.module.ts:1 — 0.0% line coverage (0/1).
  • Low coverage: src/infrastructure/database/database.module.ts src/infrastructure/database/database.module.ts:1 — 0.0% line coverage (0/3).
  • Low coverage: src/infrastructure/database/number.transformer.ts src/infrastructure/database/number.transformer.ts:1 — 20.0% line coverage (1/5).
  • Low coverage: src/infrastructure/demo/secondary-adapters/adapters/demo-seed-runner.adapter.ts src/infrastructure/demo/secondary-adapters/adapters/demo-seed-runner.adapter.ts:1 — 0.0% line coverage (0/71).
  • Low coverage: src/infrastructure/events/event-emitter2.domain-event-publisher.ts src/infrastructure/events/event-emitter2.domain-event-publisher.ts:1 — 0.0% line coverage (0/5).
  • Low coverage: src/infrastructure/health/indicators/process.health-indicator.ts src/infrastructure/health/indicators/process.health-indicator.ts:1 — 9.1% line coverage (2/22).
  • Low coverage: src/infrastructure/health/indicators/redis.health-indicator.ts src/infrastructure/health/indicators/redis.health-indicator.ts:1 — 0.0% line coverage (0/15).
  • Low coverage: src/infrastructure/health/indicators/websocket.health-indicator.ts src/infrastructure/health/indicators/websocket.health-indicator.ts:1 — 0.0% line coverage (0/14).
  • Low coverage: src/infrastructure/jobs/job-child-values.ts src/infrastructure/jobs/job-child-values.ts:1 — 0.0% line coverage (0/5).
  • Low coverage: src/infrastructure/jobs/retry-strategy.ts src/infrastructure/jobs/retry-strategy.ts:1 — 7.7% line coverage (1/13).
  • Low coverage: src/infrastructure/jwt/services/jwks.service.ts src/infrastructure/jwt/services/jwks.service.ts:1 — 13.0% line coverage (3/23).
  • Low coverage: src/infrastructure/jwt/services/jwt-verifier.service.ts src/infrastructure/jwt/services/jwt-verifier.service.ts:1 — 6.3% line coverage (2/32).
  • Low coverage: src/infrastructure/logging/winston-logger.service.ts src/infrastructure/logging/winston-logger.service.ts:1 — 5.7% line coverage (4/70).
  • Low coverage: src/infrastructure/logging/middleware/http-logging.middleware.ts src/infrastructure/logging/middleware/http-logging.middleware.ts:1 — 0.0% line coverage (0/12).
  • Low coverage: src/infrastructure/metrics/metrics.controller.ts src/infrastructure/metrics/metrics.controller.ts:1 — 0.0% line coverage (0/3).
  • Low coverage: src/infrastructure/metrics/metrics.middleware.ts src/infrastructure/metrics/metrics.middleware.ts:1 — 0.0% line coverage (0/17).
  • Low coverage: src/infrastructure/metrics/metrics.service.ts src/infrastructure/metrics/metrics.service.ts:1 — 0.0% line coverage (0/27).
  • Low coverage: src/infrastructure/metrics/collectors/infra-metrics.collector.ts src/infrastructure/metrics/collectors/infra-metrics.collector.ts:1 — 0.0% line coverage (0/17).
  • Low coverage: src/infrastructure/metrics/guards/metrics-auth.guard.ts src/infrastructure/metrics/guards/metrics-auth.guard.ts:1 — 0.0% line coverage (0/25).
  • Low coverage: src/infrastructure/metrics/listeners/business-metrics.listener.ts src/infrastructure/metrics/listeners/business-metrics.listener.ts:1 — 0.0% line coverage (0/12).
  • Low coverage: src/infrastructure/queue/bullmq-connection.module.ts src/infrastructure/queue/bullmq-connection.module.ts:1 — 0.0% line coverage (0/1).
  • + 108 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 22 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×30
  • No test reaches this file scripts/ascii-prose.cjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/db-restore-drill.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/audit-openapi.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file 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 scripts/seed-admin.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/agent-check.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/seed.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/db-restore.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/infrastructure/websocket/adapters/redis-io.adapter.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/infrastructure/tracing/tracing.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 src/modules/orders/primary-adapters/dto/create-order.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 scripts/setup.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/db-backup.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/modules/inventory/core/domain/value-objects/stock-adjustment-reason.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/docker-migrate.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/generate-openapi-spec.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 data-source.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 src/modules/payments/primary-adapters/dto/payment-method-details.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 scripts/agent-run.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/infrastructure/websocket/guards/ws-auth.guard.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 src/modules/inventory/primary-adapters/dto/stock-reservation-response.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 scripts/lint-ascii-prose.cjs: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 src/modules/orders/primary-adapters/dto/order-response.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 src/modules/orders/primary-adapters/dto/create-order-item.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 src/modules/identity/core/domain/repositories/address.repository.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.
  • + 5 more in this group — see findings.md.
D31 · IaC & Container Security · Medium IaC · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D15 · Churn × Complexity Hotspots · Hotspot · ×7
  • Hotspot: scripts/generate-envs.js scripts/generate-envs.js:59 — scripts/generate-envs.js changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in generate-envs.buildLinesForEnv at line 59. 3 of those changes were fix/bug commits, and the other 12 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-21..2026-10-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-21 15:27:05 +01:00' --until='2026-10-19 15:27:05 +01:00' --full-history --no-merges -- scripts/generate-envs.js`: 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: src/modules/products/core/application/seed/seed-demo-catalog.usecase.ts src/modules/products/core/application/seed/seed-demo-catalog.usecase.ts:46 — src/modules/products/core/application/seed/seed-demo-catalog.usecase.ts changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in SeedDemoCatalogUseCase.execute at line 46. 1 of those changes was a fix/bug commit, and the other 11 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-21..2026-10-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-21 15:27:05 +01:00' --until='2026-10-19 15:27:05 +01:00' --full-history --no-merges -- src/modules/products/core/application/seed/seed-demo-catalog.usecase.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: src/modules/carts/secondary-adapters/mappers/query/cart-query.mapper.ts src/modules/carts/secondary-adapters/mappers/query/cart-query.mapper.ts:11 — src/modules/carts/secondary-adapters/mappers/query/cart-query.mapper.ts changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in CartQueryMapper.toPresentationDto at line 11. 5 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-21..2026-10-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-21 15:27:05 +01:00' --until='2026-10-19 15:27:05 +01:00' --full-history --no-merges -- src/modules/carts/secondary-adapters/mappers/query/cart-query.mapper.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: src/filters/global-exception.filter.ts src/filters/global-exception.filter.ts:27 — src/filters/global-exception.filter.ts changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in GlobalExceptionFilter.catch at line 27. 1 of those changes was a fix/bug commit, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-21..2026-10-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-21 15:27:05 +01:00' --until='2026-10-19 15:27:05 +01:00' --full-history --no-merges -- src/filters/global-exception.filter.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:27 — src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in CachedOrderRepository.listOrders at line 27. 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-07-21..2026-10-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-21 15:27:05 +01:00' --until='2026-10-19 15:27:05 +01:00' --full-history --no-merges -- src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.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: src/modules/products/secondary-adapters/query/postgres-product-query.adapter.ts src/modules/products/secondary-adapters/query/postgres-product-query.adapter.ts:24 — src/modules/products/secondary-adapters/query/postgres-product-query.adapter.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in PostgresProductQueryAdapter.list at line 24. 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-07-21..2026-10-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-21 15:27:05 +01:00' --until='2026-10-19 15:27:05 +01:00' --full-history --no-merges -- src/modules/products/secondary-adapters/query/postgres-product-query.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: src/modules/payments/core/application/usecases/create-payment/create-payment.usecase.ts src/modules/payments/core/application/usecases/create-payment/create-payment.usecase.ts:33 — src/modules/payments/core/application/usecases/create-payment/create-payment.usecase.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in CreatePaymentUseCase.execute at line 33. 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-07-21..2026-10-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-21 15:27:05 +01:00' --until='2026-10-19 15:27:05 +01:00' --full-history --no-merges -- src/modules/payments/core/application/usecases/create-payment/create-payment.usecase.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) · ×6
  • Swallowed exception (empty catch) scripts/db-restore-drill.js:158 — 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) scripts/lib/pg.js:584 — 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) scripts/lib/pg.js:591 — 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) src/infrastructure/redis/redis.service.ts:100 — 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) src/infrastructure/redis/cache/cache.service.ts:119 — 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) src/shared-kernel/infra/lang/app-version.ts:16 — 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.
R10 · Code Duplication · Duplicated block with local edits (41 matched lines × 2 locations) · ×4
  • Duplicated block with local edits (41 matched lines × 2 locations) src/modules/authorization/secondary-adapter/repositories/postgres-role-repository/postgres-role.repository.ts:51 — src/modules/authorization/secondary-adapter/repositories/postgres-role-repository/postgres-role.repository.ts:51 · src/modules/products/secondary-adapters/repositories/postgres-category-repository/postgres.category-repository.ts:21 — the two spans are one implementation copied and then locally edited — 222 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.
  • Duplicated block with local edits (41 matched lines × 2 locations) src/modules/carts/secondary-adapters/persistence/mappers/cart.mapper.ts:10 — src/modules/carts/secondary-adapters/persistence/mappers/cart.mapper.ts:10 · src/modules/orders/secondary-adapters/persistence/mappers/order.mapper.ts:15 — 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.
  • Duplicated block with local edits (41 matched lines × 2 locations) src/modules/identity/primary-adapters/dto/add-address.dto.ts:7 — src/modules/identity/primary-adapters/dto/add-address.dto.ts:7 · src/modules/identity/primary-adapters/dto/address-response.dto.ts:12 — the two spans are one implementation copied and then locally edited — 148 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.
  • Duplicated block with local edits (41 matched lines × 2 locations) src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.ts:276 — src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.ts:276 · src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.ts:350 — the two spans are one implementation copied and then locally edited — 267 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
DM4 · Rich vs anemic model · Anemic entity · ×3
  • Anemic entity: OrderItem src/modules/orders/core/domain/entities/order-items.ts:17 — `OrderItem` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: ReservationItem src/modules/inventory/core/domain/entities/reservation-item.ts:11 — `ReservationItem` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Permission src/modules/authorization/core/domain/entities/permission.ts:13 — `Permission` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
R10 · Code Duplication · Duplicated block (37 lines × 2 locations) · ×3
  • Duplicated block (37 lines × 2 locations) src/modules/authorization/authorization.module.ts:47 — src/modules/authorization/authorization.module.ts:47 · src/modules/inventory/inventory.module.ts:81 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
  • Duplicated block (37 lines × 2 locations) src/modules/inventory/inventory.processor.ts:16 — src/modules/inventory/inventory.processor.ts:16 · src/modules/notifications/notifications.processor.ts:20 — 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) src/modules/orders/core/application/usecases/list-orders/list-orders.usecase.ts:16 — src/modules/orders/core/application/usecases/list-orders/list-orders.usecase.ts:16 · src/modules/payments/core/application/usecases/list-payments/list-payments.usecase.ts:15 — 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 (29 lines × 2 locations) · ×3
  • Duplicated block (29 lines × 2 locations) src/modules/authentication/secondary-adapters/adapters/module-identity.gateway.ts:38 — src/modules/authentication/secondary-adapters/adapters/module-identity.gateway.ts:38 · src/modules/authentication/secondary-adapters/adapters/module-identity.gateway.ts:68 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
  • Duplicated block (29 lines × 2 locations) src/modules/identity/secondary-adapters/repositories/cached-user-repository/cached-user.repository.ts:124 — src/modules/identity/secondary-adapters/repositories/cached-user-repository/cached-user.repository.ts:124 · src/modules/identity/secondary-adapters/repositories/cached-user-repository/cached-user.repository.ts:164 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (29 lines × 2 locations) REDACTED:85 — REDACTED:85 · REDACTED:173 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
D6 · Cohesion (LCOM4) · Low cohesion · ×2
  • Low cohesion: ModuleIdentityGateway (LCOM4 5) src/modules/authentication/secondary-adapters/adapters/module-identity.gateway.ts:18 — ModuleIdentityGateway's methods fall into 5 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 5 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: ModuleInventoryReservationGateway (LCOM4 4) src/modules/orders/secondary-adapters/adapters/module-inventory-reservation.gateway.ts:15 — ModuleInventoryReservationGateway'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.
R10 · Code Duplication · Duplicated block with local edits (57 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (57 matched lines × 2 locations) src/modules/inventory/secondary-adapters/repositories/postgres-inventory-repository/postgres-inventory-repository.ts:208 — src/modules/inventory/secondary-adapters/repositories/postgres-inventory-repository/postgres-inventory-repository.ts:208 · src/modules/products/secondary-adapters/repositories/postgres-product-repository/postgres.product-repository.ts:31 — the two spans are one implementation copied and then locally edited — 298 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (57 matched lines × 2 locations) src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:120 — src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:120 · src/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.ts:21 — the two spans are one implementation copied and then locally edited — 372 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 (38 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (38 matched lines × 2 locations) src/modules/analytics/secondary-adapters/mappers/query/analytics-query.mapper.ts:93 — src/modules/analytics/secondary-adapters/mappers/query/analytics-query.mapper.ts:93 · src/modules/analytics/secondary-adapters/mappers/query/analytics-query.mapper.ts:188 — the two spans are one implementation copied and then locally edited — 204 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 (38 matched lines × 2 locations) src/modules/identity/core/domain/entities/address.ts:57 — src/modules/identity/core/domain/entities/address.ts:57 · src/modules/orders/core/domain/value-objects/shipping-address.ts:39 — the two spans are one implementation copied and then locally edited — 203 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.
R2 · Cyclomatic Complexity · Complex function (top-level) (cyclomatic 14, cognitive 13) · ×2
  • Complex function (top-level) (cyclomatic 14, cognitive 13) src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts:1 — (top-level) has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function (top-level) (cyclomatic 14, cognitive 13) src/modules/identity/core/application/usecases/address/update-address/update-address.usecase.ts:1 — (top-level) has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R7 · Dead Code · Dead file (~14 LoC) · ×2
  • Dead file (~14 LoC) src/modules/orders/primary-adapters/dto/payment-info.dto.ts — no import path from any entry point (29 application, 35 tooling, 385 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 (~14 LoC) src/modules/payments/core/domain/index.ts — no import path from any entry point (29 application, 35 tooling, 385 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 (~6 LoC) · ×2
  • Dead file (~6 LoC) src/modules/carts/core/application/commands/clear-cart.command.ts — no import path from any entry point (29 application, 35 tooling, 385 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 (~6 LoC) src/modules/identity/core/application/commands/create-user.command.ts — no import path from any entry point (29 application, 35 tooling, 385 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 src/infrastructure/redis/redis-error.utils.ts:22 — `isKnownRedisConnectionError` is exported and takes `err: unknown` from its caller, and it calls itself at line 22 (`isKnownRedisConnectionError`) with a piece of `err` — and nowhere in `isKnownRedisConnectionError` 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 `isKnownRedisConnectionError` 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 src/infrastructure/redis/cache/cache-json.ts:22 — `isRedisJson` is exported and takes `value: unknown` from its caller, and it calls itself at line 22 (`isRedisJson`) with a piece of `value` (and at line 26) — and nowhere in `isRedisJson` 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 `isRedisJson` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
D1 · Cyclomatic Complexity · generate-envs.buildLinesForEnv (cyclomatic 26) · ×1
  • generate-envs.buildLinesForEnv (cyclomatic 26) scripts/generate-envs.js:59 — generate-envs.buildLinesForEnv has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 2 of the 26 points are its own statements and the rest belongs to one function literal inside it that branches (line 62). 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.
D1 · Cyclomatic Complexity · generate-envs.generateEnvs (cyclomatic 26) · ×1
  • generate-envs.generateEnvs (cyclomatic 26) scripts/generate-envs.js:169 — generate-envs.generateEnvs has cyclomatic complexity 26 (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 · SeedDemoCatalogUseCase.execute (cyclomatic 25) · ×1
  • SeedDemoCatalogUseCase.execute (cyclomatic 25) src/modules/products/core/application/seed/seed-demo-catalog.usecase.ts:46 — SeedDemoCatalogUseCase.execute 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 · CartQueryMapper.toPresentationDto (cyclomatic 24) · ×1
  • CartQueryMapper.toPresentationDto (cyclomatic 24) src/modules/carts/secondary-adapters/mappers/query/cart-query.mapper.ts:11 — CartQueryMapper.toPresentationDto has cyclomatic complexity 24 (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 · ascii-prose.findComments · ×1
  • ascii-prose.findComments::skipString (cyclomatic 23) scripts/ascii-prose.cjs:148 — ascii-prose.findComments::skipString has cyclomatic complexity 23 (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.
D1 · Cyclomatic Complexity · agent-output.selectVitestCommands (cyclomatic 22) · ×1
  • agent-output.selectVitestCommands (cyclomatic 22) scripts/agent-output.mjs:78 — agent-output.selectVitestCommands has cyclomatic complexity 22 (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 · ascii-prose.collectFiles · ×1
  • ascii-prose.collectFiles::walk (cyclomatic 22) scripts/ascii-prose.cjs:54 — ascii-prose.collectFiles::walk has cyclomatic complexity 22 (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 · GlobalExceptionFilter.catch (cyclomatic 20) · ×1
  • GlobalExceptionFilter.catch (cyclomatic 20) src/filters/global-exception.filter.ts:27 — GlobalExceptionFilter.catch has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · PostgresPaymentQueryAdapter.list (cyclomatic 19) · ×1
  • PostgresPaymentQueryAdapter.list (cyclomatic 19) src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts:25 — PostgresPaymentQueryAdapter.list has cyclomatic complexity 19 (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 · CachedOrderRepository.listOrders (cyclomatic 18) · ×1
  • CachedOrderRepository.listOrders (cyclomatic 18) src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:27 — CachedOrderRepository.listOrders has cyclomatic complexity 18 (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.
D1 · Cyclomatic Complexity · CreatePaymentUseCase.execute (cyclomatic 16) · ×1
  • CreatePaymentUseCase.execute (cyclomatic 16) src/modules/payments/core/application/usecases/create-payment/create-payment.usecase.ts:33 — CreatePaymentUseCase.execute has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CreatePaymentIntentUseCase.execute (cyclomatic 16) · ×1
  • CreatePaymentIntentUseCase.execute (cyclomatic 16) src/modules/payments/core/application/usecases/create-payment-intent/create-payment-intent.usecase.ts:37 — CreatePaymentIntentUseCase.execute has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PostgresProductQueryAdapter.list (cyclomatic 16) · ×1
  • PostgresProductQueryAdapter.list (cyclomatic 16) src/modules/products/secondary-adapters/query/postgres-product-query.adapter.ts:24 — PostgresProductQueryAdapter.list has cyclomatic complexity 16 (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 · setup-bootstrap.runSetup (cyclomatic 16) · ×1
  • setup-bootstrap.runSetup (cyclomatic 16) scripts/lib/setup-bootstrap.js:15 — setup-bootstrap.runSetup has cyclomatic complexity 16 (threshold 15). 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.
D12 · Dependency Hygiene · Deprecated · ×1
  • Deprecated: prom-client package.json:171 — prom-client 15.1.3, declared in package.json, is marked deprecated by its publisher: "prom-client has been replaced by @prometheus-io/client". Replace it with the package or version that message names, or record why this one must stay.
D15 · Churn × Complexity Hotspots · Repeated repair · ×1
  • Repeated repair: src/interceptors/sanitize.interceptor.ts src/interceptors/sanitize.interceptor.ts:39 — src/interceptors/sanitize.interceptor.ts changed 8 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is sanitize.interceptor.sanitizeDeep at line 39), 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(security): preserve password on registration and assert webhook payload fidelity”; “fix(security): resolve reviewer feedback on sanitize interceptor and tests”; “fix(security): scope sanitize interceptor to handler level and target dependabot to master”; “fix(security): scope sanitize interceptor to handler level, preserve passwords, and refine config”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-21..2026-10-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-21 15:27:05 +01:00' --until='2026-10-19 15:27:05 +01:00' --full-history --no-merges -- src/interceptors/sanitize.interceptor.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D2 · Cognitive Complexity · generate-envs.generateEnvs (cognitive 44) · ×1
  • generate-envs.generateEnvs (cognitive 44) scripts/generate-envs.js:169 — generate-envs.generateEnvs has cognitive complexity 44 (threshold 15). Drivers by points: if/else 12 (25 pts), boolean chains 10, ternaries 2 (5 pts), loops 2 (4 pts) (nesting depth added 18). 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 · ascii-prose.findComments · ×1
  • ascii-prose.findComments::skipString (cognitive 36) scripts/ascii-prose.cjs:148 — ascii-prose.findComments::skipString has cognitive complexity 36 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 4 (14 pts), boolean chains 8 (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. This shape REPEATS in the file: one other method here (ascii-prose.findComments) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · SeedDemoCatalogUseCase.execute (cognitive 36) · ×1
  • SeedDemoCatalogUseCase.execute (cognitive 36) src/modules/products/core/application/seed/seed-demo-catalog.usecase.ts:46 — SeedDemoCatalogUseCase.execute has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (25 pts), loops 7, boolean chains 3, ternaries 1 (nesting depth added 12). Of this number, 35 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 · CartQueryMapper.toPresentationDto (cognitive 35) · ×1
  • CartQueryMapper.toPresentationDto (cognitive 35) src/modules/carts/secondary-adapters/mappers/query/cart-query.mapper.ts:11 — CartQueryMapper.toPresentationDto has cognitive complexity 35 (threshold 15). Drivers by points: if/else 13 (22 pts), ternaries 5 (8 pts), boolean chains 4, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ascii-prose.collectFiles · ×1
  • ascii-prose.collectFiles::walk (cognitive 32) scripts/ascii-prose.cjs:54 — ascii-prose.collectFiles::walk has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (24 pts), boolean chains 6, error handling 1, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · generate-envs.buildLinesForEnv (cognitive 31) · ×1
  • generate-envs.buildLinesForEnv (cognitive 31) scripts/generate-envs.js:59 — generate-envs.buildLinesForEnv has cognitive complexity 31 (threshold 15). Drivers by points: if/else 19 (24 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 6). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to one function literal inside it that branches (line 62). 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 · RoleSystemDataInitializer.onApplicationBootstrap (cognitive 25) · ×1
  • RoleSystemDataInitializer.onApplicationBootstrap (cognitive 25) src/modules/authorization/core/application/lifecycle/role-system-data.initializer.ts:19 — RoleSystemDataInitializer.onApplicationBootstrap has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (18 pts), ternaries 2 (5 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CachedOrderRepository.listOrders (cognitive 24) · ×1
  • CachedOrderRepository.listOrders (cognitive 24) src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:27 — CachedOrderRepository.listOrders has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 3 (5 pts), boolean chains 4, loops 1 (3 pts) (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 · SeedDemoCategoriesUseCase.execute (cognitive 24) · ×1
  • SeedDemoCategoriesUseCase.execute (cognitive 24) src/modules/products/core/application/seed/seed-demo-categories.usecase.ts:27 — SeedDemoCategoriesUseCase.execute has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (23 pts), loops 1 (nesting depth added 14). 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 · agent-output.selectVitestCommands (cognitive 21) · ×1
  • agent-output.selectVitestCommands (cognitive 21) scripts/agent-output.mjs:78 — agent-output.selectVitestCommands has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 6 (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 · SweepExpiredReservationsUseCase.execute (cognitive 21) · ×1
  • SweepExpiredReservationsUseCase.execute (cognitive 21) src/modules/inventory/core/application/usecases/sweep-expired-reservations/sweep-expired-reservations.usecase.ts:31 — SweepExpiredReservationsUseCase.execute has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 2 (3 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CreatePaymentIntentUseCase.execute (cognitive 20) · ×1
  • CreatePaymentIntentUseCase.execute (cognitive 20) src/modules/payments/core/application/usecases/create-payment-intent/create-payment-intent.usecase.ts:37 — CreatePaymentIntentUseCase.execute has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (17 pts), ternaries 1 (2 pts), boolean chains 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 · SeedDemoOrdersUseCase.execute (cognitive 20) · ×1
  • SeedDemoOrdersUseCase.execute (cognitive 20) src/modules/orders/core/application/seed/seed-demo-orders.usecase.ts:53 — SeedDemoOrdersUseCase.execute has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 3 (4 pts), boolean chains 2 (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 · ascii-prose.findComments (cognitive 19) · ×1
  • ascii-prose.findComments (cognitive 19) scripts/ascii-prose.cjs:143 — ascii-prose.findComments has cognitive complexity 19 (threshold 15). Drivers by points: loops 7 (21 pts), if/else 11 (20 pts), boolean chains 14 (nesting depth added 23). 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 (ascii-prose.findComments::skipString) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · PostgresPaymentQueryAdapter.list (cognitive 19) · ×1
  • PostgresPaymentQueryAdapter.list (cognitive 19) src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts:25 — PostgresPaymentQueryAdapter.list has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 4, error handling 1, ternaries 1 (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 · CheckoutFailureListener.onModuleInit (cognitive 18) · ×1
  • CheckoutFailureListener.onModuleInit (cognitive 18) src/modules/orders/primary-adapters/listeners/checkout-failure.listener.ts:23 — CheckoutFailureListener.onModuleInit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3, error handling 1 (nesting depth added 5). None of this is in the body itself: all 18 points belong to one function literal inside it that branches (line 26). 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 · CreatePaymentUseCase.execute (cognitive 17) · ×1
  • CreatePaymentUseCase.execute (cognitive 17) src/modules/payments/core/application/usecases/create-payment/create-payment.usecase.ts:33 — CreatePaymentUseCase.execute has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 2, ternaries 2, match/switch 1 (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 · money-decimal.minorUnitsFromDecimal (cognitive 16) · ×1
  • money-decimal.minorUnitsFromDecimal (cognitive 16) src/shared-kernel/domain/value-objects/money-decimal.ts:57 — money-decimal.minorUnitsFromDecimal has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 3, boolean chains 2 (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, 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 · UpdateProductUseCase.execute (cognitive 16) · ×1
  • UpdateProductUseCase.execute (cognitive 16) src/modules/products/core/application/usecases/update-product/update-product.usecase.ts:30 — UpdateProductUseCase.execute has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 1, error handling 1 (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 · winston-logger.service.redactInPlace (cognitive 16) · ×1
  • winston-logger.service.redactInPlace (cognitive 16) src/infrastructure/logging/winston-logger.service.ts:197 — winston-logger.service.redactInPlace has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 3, loops 2 (3 pts) (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.
D3 · God Classes · TooManyMethods · ×1
  • TooManyMethods: Order src/modules/orders/core/domain/entities/order.ts:35 — TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D3 · God Classes · MethodTooLong · ×1
  • MethodTooLong: ChangePasswordUseCase.execute src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts:40 — MethodTooLong — execute runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D30 · Dependency Vulnerabilities · Medium CVE · ×1
  • REDACTED
D35 · Change Coupling · Change coupling · ×1
  • Change coupling: cached.product-repository.ts ↔ postgres.product-repository.ts src/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.ts:1 — `src/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.ts` and `src/modules/products/secondary-adapters/repositories/postgres-product-repository/postgres.product-repository.ts` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `3f33c4e7` ES-147: Add findByIds method to product repositories and enhance cach…; `cf13f844` ES-142: Implement versioning support in Product entity and repository…; `bb0e295a` ES-131: refactor(arch): harden DDD boundaries and hexagonal isolation — run `git show` on any of them.
DM10 · One transaction, one aggregate · One operation mutates 2 aggregates · ×1
  • One operation mutates 2 aggregates: ChangePasswordUseCase.execute src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts:40 — `ChangePasswordUseCase.execute` saves `CredentialRepository`, `SessionTokenRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
DM5 · Encapsulated state · Mutable entity · ×1
  • Mutable entity: Credential src/modules/authentication/core/domain/entities/credential.ts:10 — `Credential` exposes publicly writable state (passwordHash, mustChangePassword).
IC1 · Incompleteness & stubs · Both branches are identical · ×1
  • Both branches are identical — the condition decides nothing scripts/ascii-prose.cjs:328 — Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
P12 · CI test-gate honesty · Coverage collected but not gated · ×1
  • Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
R10 · Code Duplication · Duplication concentrated across 10 sibling directories (198 clone groups) · ×1
  • Duplication concentrated across 10 sibling directories (198 clone groups) src/modules/carts/secondary-adapters/repositories/cached-cart-repository/cached.cart-repository.ts:15 — 198 duplicated blocks under src/modules/ have copies in at least two of the sibling directories analytics, authentication, authorization, carts, identity, inventory (+4 more sibling(s) not listed) — 81 of them are reported below, and 117 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 198 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 198 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 198 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 7 sibling directories (5 clone groups) · ×1
  • Duplication concentrated across 7 sibling directories (5 clone groups) src/modules/orders/core/application/usecases/handle-payment-completed/handle-payment-completed.usecase.ts:16 — 5 duplicated blocks under src/modules/orders/core/application/usecases/ have copies in at least two of the sibling directories cancel-order, confirm-order, deliver-order, handle-payment-completed, handle-payment-failed, process-order (+1 more sibling(s) not listed) — 3 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplicated block with local edits (108 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (108 matched lines × 2 locations) src/modules/products/core/domain/entities/category.ts:20 — src/modules/products/core/domain/entities/category.ts:20 · src/modules/products/core/domain/entities/product.ts:41 — the two spans are one implementation copied and then locally edited — 646 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 (92 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (92 matched lines × 2 locations) src/modules/carts/secondary-adapters/repositories/cached-cart-repository/cached.cart-repository.ts:15 — src/modules/carts/secondary-adapters/repositories/cached-cart-repository/cached.cart-repository.ts:15 · src/modules/payments/secondary-adapters/repositories/cached-payment-repository/cached.payment-repository.ts:16 — the two spans are one implementation copied and then locally edited — 550 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 (84 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (84 matched lines × 2 locations) src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts:20 — src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts:20 · src/modules/authentication/core/application/usecases/login-user/login-user.usecase.ts:17 — the two spans are one implementation copied and then locally edited — 321 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (64 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (64 matched lines × 2 locations) src/modules/inventory/secondary-adapters/query/postgres-inventory-query.adapter.ts:16 — src/modules/inventory/secondary-adapters/query/postgres-inventory-query.adapter.ts:16 · src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts:18 — the two spans are one implementation copied and then locally edited — 321 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 (55 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (55 matched lines × 2 locations) src/modules/inventory/secondary-adapters/repositories/cached-inventory-repository/cached-inventory-repository.ts:179 — src/modules/inventory/secondary-adapters/repositories/cached-inventory-repository/cached-inventory-repository.ts:179 · src/modules/payments/secondary-adapters/repositories/cached-payment-repository/cached.payment-repository.ts:46 — the two spans are one implementation copied and then locally edited — 292 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 (54 lines × 2 locations) · ×1
  • Duplicated block (54 lines × 2 locations) src/modules/carts/secondary-adapters/repositories/postgres-cart-repository/postgres.cart-repository.ts:86 — src/modules/carts/secondary-adapters/repositories/postgres-cart-repository/postgres.cart-repository.ts:86 · src/modules/orders/secondary-adapters/repositories/postgres-order-repository/postgres.order-repository.ts:83 — 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 (50 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (50 matched lines × 2 locations) src/modules/identity/primary-adapters/dto/add-address.dto.ts:7 — src/modules/identity/primary-adapters/dto/add-address.dto.ts:7 · src/modules/identity/primary-adapters/dto/update-address.dto.ts:6 — the two spans are one implementation copied and then locally edited — 161 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 (44 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (44 matched lines × 2 locations) src/modules/payments/core/domain/value-objects/payment-status.ts:11 — src/modules/payments/core/domain/value-objects/payment-status.ts:11 · src/modules/payments/core/domain/value-objects/refund-status.ts:9 — the two spans are one implementation copied and then locally edited — 229 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) src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts:150 — src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts:150 · src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts:195 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block with local edits (43 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (43 matched lines × 2 locations) src/modules/inventory/secondary-adapters/repositories/cached-inventory-repository/cached-inventory-repository.ts:104 — src/modules/inventory/secondary-adapters/repositories/cached-inventory-repository/cached-inventory-repository.ts:104 · src/modules/inventory/secondary-adapters/repositories/postgres-inventory-repository/postgres-inventory-repository.ts:60 — the two spans are one implementation copied and then locally edited — 216 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 (43 lines × 3 locations) · ×1
  • Duplicated block (43 lines × 3 locations) src/modules/inventory/secondary-adapters/schedulers/bullmq-inventory.scheduler.ts:29 — src/modules/inventory/secondary-adapters/schedulers/bullmq-inventory.scheduler.ts:29 · src/modules/inventory/secondary-adapters/schedulers/bullmq-inventory.scheduler.ts:76 · src/modules/orders/secondary-adapters/schedulers/bullmq-checkout.scheduler.ts:249 — 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 (42 lines × 2 locations) · ×1
  • Duplicated block (42 lines × 2 locations) src/modules/orders/core/application/usecases/handle-payment-completed/handle-payment-completed.usecase.ts:16 — src/modules/orders/core/application/usecases/handle-payment-completed/handle-payment-completed.usecase.ts:16 · src/modules/orders/core/application/usecases/handle-payment-failed/handle-payment-failed.usecase.ts:15 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (41 lines × 2 locations) · ×1
  • Duplicated block (41 lines × 2 locations) src/modules/products/secondary-adapters/query/postgres-product-query.adapter.ts:143 — src/modules/products/secondary-adapters/query/postgres-product-query.adapter.ts:143 · src/modules/products/secondary-adapters/query/postgres-product-query.adapter.ts:185 — 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 (40 lines × 2 locations) · ×1
  • Duplicated block (40 lines × 2 locations) src/modules/carts/secondary-adapters/query/postgres-cart-query.adapter.ts:20 — src/modules/carts/secondary-adapters/query/postgres-cart-query.adapter.ts:20 · src/modules/carts/secondary-adapters/query/postgres-cart-query.adapter.ts:61 — 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 (38 lines × 2 locations) · ×1
  • Duplicated block (38 lines × 2 locations) REDACTED:111 — REDACTED:111 · REDACTED:111 — 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 (36 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (36 matched lines × 2 locations) src/modules/products/core/application/usecases/activate-product/activate-product.usecase.ts:11 — src/modules/products/core/application/usecases/activate-product/activate-product.usecase.ts:11 · src/modules/products/core/application/usecases/deactivate-product/deactivate-product.usecase.ts:11 — the two spans are one implementation copied and then locally edited — 183 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 (35 lines × 2 locations) · ×1
  • Duplicated block (35 lines × 2 locations) src/modules/products/core/application/usecases/categories/activate-category.usecase.ts:11 — src/modules/products/core/application/usecases/categories/activate-category.usecase.ts:11 · src/modules/products/core/application/usecases/categories/deactivate-category.usecase.ts:11 — 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 (35 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (35 matched lines × 2 locations) src/modules/products/core/application/usecases/create-product/create-product.usecase.ts:49 — src/modules/products/core/application/usecases/create-product/create-product.usecase.ts:49 · src/modules/products/core/application/usecases/update-product/update-product.usecase.ts:41 — the two spans are one implementation copied and then locally edited — 191 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 (34 lines × 2 locations) · ×1
  • Duplicated block (34 lines × 2 locations) src/modules/carts/carts.module.ts:37 — src/modules/carts/carts.module.ts:37 · src/modules/orders/orders.module.ts:99 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (34 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (34 matched lines × 2 locations) src/modules/identity/primary-adapters/dto/address-response.dto.ts:12 — src/modules/identity/primary-adapters/dto/address-response.dto.ts:12 · src/modules/identity/primary-adapters/dto/update-address.dto.ts:6 — the two spans are one implementation copied and then locally edited — 106 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 (33 lines × 2 locations) · ×1
  • Duplicated block (33 lines × 2 locations) src/modules/identity/core/application/usecases/address/add-address/add-address.usecase.ts:17 — src/modules/identity/core/application/usecases/address/add-address/add-address.usecase.ts:17 · src/modules/identity/core/application/usecases/address/update-address/update-address.usecase.ts:16 — 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 (31 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (31 matched lines × 2 locations) src/modules/payments/core/application/usecases/get-payment-by-order-id/get-payment-by-order-id.usecase.ts:17 — src/modules/payments/core/application/usecases/get-payment-by-order-id/get-payment-by-order-id.usecase.ts:17 · src/modules/payments/core/application/usecases/get-payment/get-payment.usecase.ts:17 — the two spans are one implementation copied and then locally edited — 128 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 (30 lines × 2 locations) · ×1
  • Duplicated block (30 lines × 2 locations) src/modules/orders/primary-adapters/jobs/release-order-stock.job.ts:11 — src/modules/orders/primary-adapters/jobs/release-order-stock.job.ts:11 · src/modules/orders/primary-adapters/jobs/release-stock.job.ts:12 — 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) · ×1
  • Duplicated block with local edits (30 matched lines × 2 locations) src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:65 — src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:65 · src/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.ts:141 — the two spans are one implementation copied and then locally edited — 167 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.
R2 · Cyclomatic Complexity · Complex function generateEnvs (cyclomatic 26, cognitive 44) · ×1
  • Complex function generateEnvs (cyclomatic 26, cognitive 44) scripts/generate-envs.js:169 — generateEnvs has cyclomatic complexity 26 and cognitive complexity 44; 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 toPresentationDto (cyclomatic 26, cognitive 35) · ×1
  • Complex function toPresentationDto (cyclomatic 26, cognitive 35) src/modules/carts/secondary-adapters/mappers/query/cart-query.mapper.ts:11 — toPresentationDto has cyclomatic complexity 26 and cognitive complexity 35; 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 25, cognitive 30) · ×1
  • Complex function (anonymous) (cyclomatic 25, cognitive 30) scripts/generate-envs.js:62 — (anonymous) has cyclomatic complexity 25 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 skipString (cyclomatic 23, cognitive 35) · ×1
  • Complex function skipString (cyclomatic 23, cognitive 35) scripts/ascii-prose.cjs:148 — skipString has cyclomatic complexity 23 and cognitive complexity 35; 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 walk (cyclomatic 22, cognitive 32) · ×1
  • Complex function walk (cyclomatic 22, cognitive 32) scripts/ascii-prose.cjs:54 — walk has cyclomatic complexity 22 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 (top-level) (cyclomatic 22, cognitive 31) · ×1
  • Complex function (top-level) (cyclomatic 22, cognitive 31) src/filters/global-exception.filter.ts:1 — (top-level) has cyclomatic complexity 22 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function selectVitestCommands (cyclomatic 22, cognitive 21) · ×1
  • Complex function selectVitestCommands (cyclomatic 22, cognitive 21) scripts/agent-output.mjs:78 — selectVitestCommands has cyclomatic complexity 22 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 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 (top-level) (cyclomatic 19, cognitive 18) · ×1
  • Complex function (top-level) (cyclomatic 19, cognitive 18) src/modules/authentication/core/application/usecases/refresh-token/refresh-token.usecase.ts:1 — (top-level) has cyclomatic complexity 19 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 list (cyclomatic 19, cognitive 18) · ×1
  • Complex function list (cyclomatic 19, cognitive 18) src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts:25 — list has cyclomatic complexity 19 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 listOrders (cyclomatic 18, cognitive 24) · ×1
  • Complex function listOrders (cyclomatic 18, cognitive 24) src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:27 — listOrders 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 (top-level) (cyclomatic 17, cognitive 18) · ×1
  • Complex function (top-level) (cyclomatic 17, cognitive 18) src/modules/payments/core/application/usecases/create-payment/create-payment.usecase.ts:1 — (top-level) has cyclomatic complexity 17 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 runSetup (cyclomatic 16, cognitive 15) · ×1
  • Complex function runSetup (cyclomatic 16, cognitive 15) scripts/lib/setup-bootstrap.js:15 — runSetup has cyclomatic complexity 16 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 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 list (cyclomatic 16, cognitive 14) · ×1
  • Complex function list (cyclomatic 16, cognitive 14) src/modules/products/secondary-adapters/query/postgres-product-query.adapter.ts:24 — list has cyclomatic complexity 16 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 list (cyclomatic 15, cognitive 12) · ×1
  • Complex function list (cyclomatic 15, cognitive 12) src/modules/inventory/secondary-adapters/query/postgres-inventory-query.adapter.ts:23 — list has cyclomatic complexity 15 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 findComments (cyclomatic 14, cognitive 18) · ×1
  • Complex function findComments (cyclomatic 14, cognitive 18) scripts/ascii-prose.cjs:143 — findComments has cyclomatic complexity 14 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 14, cognitive 18) · ×1
  • Complex function (anonymous) (cyclomatic 14, cognitive 18) src/modules/orders/primary-adapters/listeners/checkout-failure.listener.ts:26 — (anonymous) has cyclomatic complexity 14 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function redactInPlace (cyclomatic 14, cognitive 16) · ×1
  • Complex function redactInPlace (cyclomatic 14, cognitive 16) src/infrastructure/logging/winston-logger.service.ts:197 — redactInPlace 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.
R3 · Large Files · src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.ts · ×1
  • src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.ts: 404 lines of code src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.ts:1 — src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.ts has 404 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 (~56 LoC) · ×1
  • Dead file (~56 LoC) src/modules/orders/primary-adapters/dto/create-order.dto.ts — no import path from any entry point (29 application, 35 tooling, 385 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/modules/orders/primary-adapters/dto/update-order.dto.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 (~47 LoC) · ×1
  • Dead file (~47 LoC) src/modules/inventory/core/domain/value-objects/stock-adjustment-reason.ts — no import path from any entry point (29 application, 35 tooling, 385 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 (~37 LoC) · ×1
  • Dead file (~37 LoC) src/modules/payments/primary-adapters/dto/payment-method-details.dto.ts — no import path from any entry point (29 application, 35 tooling, 385 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 (~29 LoC) · ×1
  • Dead file (~29 LoC) src/infrastructure/websocket/guards/ws-auth.guard.ts — no import path from any entry point (29 application, 35 tooling, 385 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 (~28 LoC) · ×1
  • Dead file (~28 LoC) src/modules/inventory/primary-adapters/dto/stock-reservation-response.dto.ts — no import path from any entry point (29 application, 35 tooling, 385 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 (~26 LoC) · ×1
  • Dead file (~26 LoC) src/modules/orders/primary-adapters/dto/order-response.dto.ts — no import path from any entry point (29 application, 35 tooling, 385 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 (~25 LoC) · ×1
  • Dead file (~25 LoC) src/modules/orders/primary-adapters/dto/create-order-item.dto.ts — no import path from any entry point (29 application, 35 tooling, 385 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/modules/orders/primary-adapters/dto/create-order.dto.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 (~18 LoC) · ×1
  • Dead file (~18 LoC) src/modules/identity/core/domain/repositories/address.repository.ts — no import path from any entry point (29 application, 35 tooling, 385 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 (~17 LoC) · ×1
  • Dead file (~17 LoC) src/types/express.ts — no import path from any entry point (29 application, 35 tooling, 385 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 (~10 LoC) · ×1
  • Dead file (~10 LoC) src/infrastructure/tracing/index.ts — no import path from any entry point (29 application, 35 tooling, 385 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 (~9 LoC) · ×1
  • Dead file (~9 LoC) src/modules/orders/primary-adapters/dto/order-item-response.dto.ts — no import path from any entry point (29 application, 35 tooling, 385 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/modules/orders/primary-adapters/dto/order-response.dto.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 (~7 LoC) · ×1
  • Dead file (~7 LoC) src/modules/carts/core/application/commands/remove-cart-item.command.ts — no import path from any entry point (29 application, 35 tooling, 385 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 (~5 LoC) · ×1
  • Dead file (~5 LoC) src/modules/orders/primary-adapters/dto/update-order.dto.ts — no import path from any entry point (29 application, 35 tooling, 385 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 (~3 LoC) · ×1
  • Dead file (~3 LoC) src/infrastructure/jwt/index.ts — no import path from any entry point (29 application, 35 tooling, 385 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) · ×1
  • Dead file (~2 LoC) src/infrastructure/idempotency/index.ts — no import path from any entry point (29 application, 35 tooling, 385 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) · ×1
  • Dead file (~1 LoC) src/modules/authentication/primary-adapters/decorators/index.ts — no import path from any entry point (29 application, 35 tooling, 385 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 (~0 LoC) · ×1
  • Dead file (~0 LoC) src/modules/orders/core/domain/services/index.ts — no import path from any entry point (29 application, 35 tooling, 385 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
R8 · Dependency Hygiene · Unused dependency '@eslint/eslintrc' · ×1
  • Unused dependency '@eslint/eslintrc' — 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 'source-map-support' · ×1
  • Unused dependency 'source-map-support' — 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 'tsconfig-paths' · ×1
  • Unused dependency 'tsconfig-paths' — 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.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×1
  • Swallowed exception (caught, then discarded) scripts/ascii-prose.cjs:58 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Minor — 113 finding(s)
X4 · Structured logging · Interpolated log message defeats structured logging · ×40
  • Interpolated log message defeats structured logging scripts/generate-envs.js:219 — `log` at line 219 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 scripts/generate-envs.js:239 — `log` at line 239 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 scripts/generate-envs.js:246 — `log` at line 246 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 scripts/generate-envs.js:255 — `log` at line 255 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 scripts/generate-envs.js:262 — `error` at line 262 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 scripts/generate-envs.js:270 — `log` at line 270 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 scripts/generate-envs.js:279 — `error` at line 279 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 scripts/lib/cli.js:35 — `error` at line 35 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 scripts/lib/cli.js:37 — `error` at line 37 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 src/main.ts:89 — `log` at line 89 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 src/main.ts:104 — `log` at line 104 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 src/filters/global-exception.filter.ts:54 — `warn` at line 54 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 src/filters/global-exception.filter.ts:75 — `warn` at line 75 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 src/filters/global-exception.filter.ts:87 — `warn` at line 87 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 src/filters/global-exception.filter.ts:99 — `warn` at line 99 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 src/filters/global-exception.filter.ts:105 — `error` at line 105 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 src/filters/global-exception.filter.ts:112 — `error` at line 112 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 src/infrastructure/events/event-emitter2.domain-event-publisher.ts:23 — `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.
  • Interpolated log message defeats structured logging src/infrastructure/idempotency/idempotency.service.ts:49 — `warn` at line 49 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 src/infrastructure/idempotency/idempotency.service.ts:63 — `log` at line 63 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.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 src/infrastructure/idempotency/idempotency.service.ts:77 — `log` at line 77 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 src/infrastructure/idempotency/idempotency.service.ts:81 — `log` at line 81 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 src/infrastructure/idempotency/idempotency.service.ts:85 — `warn` at line 85 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 src/infrastructure/idempotency/idempotency.service.ts:93 — `warn` at line 93 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 src/infrastructure/idempotency/idempotency.service.ts:101 — `warn` at line 101 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.
  • + 15 more in this group — see findings.md.
DM2 · Strongly-typed ids · Primitive id on a domain type · ×14
  • Primitive id on a domain type: OrderItem.productId src/modules/orders/core/domain/entities/order-items.ts:57 — `OrderItem.productId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that.
  • Primitive id on a domain type: Order.userId src/modules/orders/core/domain/entities/order.ts:103 — `Order.userId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that.
  • Primitive id on a domain type: CartItem.productId src/modules/carts/core/domain/entities/cart-item.ts:86 — `CartItem.productId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that.
  • Primitive id on a domain type: Cart.userId src/modules/carts/core/domain/entities/cart.ts:52 — `Cart.userId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that.
  • Primitive id on a domain type: ReservationItem.productId src/modules/inventory/core/domain/entities/reservation-item.ts:26 — `ReservationItem.productId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that.
  • Primitive id on a domain type: Reservation.orderId src/modules/inventory/core/domain/entities/reservation.ts:70 — `Reservation.orderId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that.
  • Primitive id on a domain type: Refund.paymentId src/modules/payments/core/domain/entities/refund.ts:73 — `Refund.paymentId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that.
  • Primitive id on a domain type: Payment.orderId src/modules/payments/core/domain/entities/payment.ts:133 — `Payment.orderId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that.
  • Primitive id on a domain type: SessionToken.userId src/modules/authentication/core/domain/entities/session-token.ts:35 — `SessionToken.userId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that.
  • Primitive id on a domain type: Credential.userId src/modules/authentication/core/domain/entities/credential.ts:27 — `Credential.userId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that.
  • Primitive id on a domain type: UserRoleAssignment.userId src/modules/authorization/core/domain/entities/user-role-assignment.ts:30 — `UserRoleAssignment.userId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that.
  • Primitive id on a domain type: UserRoleAssignment.roleId src/modules/authorization/core/domain/entities/user-role-assignment.ts:34 — `UserRoleAssignment.roleId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that.
  • Primitive id on a domain type: Address.userId src/modules/identity/core/domain/entities/address.ts:99 — `Address.userId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that.
  • Primitive id on a domain type: Inventory.productId src/modules/inventory/core/domain/entities/inventory.ts:81 — `Inventory.productId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that.
M4 · Documentation accuracy · README/code drift · ×14
  • README/code drift README.md:40 — README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.
  • README/code drift docs/architecture/DDD-HEXAGONAL.md:111 — docs/architecture/DDD-HEXAGONAL.md names `core/domain/models/`, but no file or folder `core/domain/models` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/architecture/DDD-HEXAGONAL.md:116 — docs/architecture/DDD-HEXAGONAL.md names `core/domain/events/`, but no file or folder `core/domain/events` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/development/SEEDING.md:142 — docs/development/SEEDING.md documents the environment variable `NEXT_PUBLIC_API_BASE_URL`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/development/SEEDING.md:142 — docs/development/SEEDING.md documents the environment variable `NEXT_PUBLIC_IMAGE_ALLOWED_HOSTS`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/security/ADMIN-BOOTSTRAP.md:25 — docs/security/ADMIN-BOOTSTRAP.md documents the environment variable `ADMIN_EMAIL`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/security/ADMIN-BOOTSTRAP.md:25 — docs/security/ADMIN-BOOTSTRAP.md documents the environment variable `ADMIN_PASSWORD`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/security/ADMIN-BOOTSTRAP.md:62 — docs/security/ADMIN-BOOTSTRAP.md documents the environment variable `KEYCLOAK_ADMIN`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/security/SECRET-ROTATION.md:202 — docs/security/SECRET-ROTATION.md documents the environment variable `STRIPE_SECRET_KEY`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/infrastructure/cicd/PROJECT-PIPELINE.md:57 — docs/infrastructure/cicd/PROJECT-PIPELINE.md names `actions/setup-node`, but no file or folder `actions/setup-node` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/infrastructure/cicd/PROJECT-PIPELINE.md:93 — docs/infrastructure/cicd/PROJECT-PIPELINE.md links to `../../.github/actions/prepare-test-env/action.yml`, but `docs/.github/actions/prepare-test-env/action.yml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/infrastructure/cicd/PROJECT-PIPELINE.md:110 — docs/infrastructure/cicd/PROJECT-PIPELINE.md links to `../../.github/actions/prepare-db-env/action.yml`, but `docs/.github/actions/prepare-db-env/action.yml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/data/collections/bruno/README.md:14 — docs/data/collections/bruno/README.md links to `../../development/SEEDING.md`, but `docs/data/development/SEEDING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/infrastructure/cicd/pipeline/PIPELINE-OPTIMIZATION.md:43 — docs/infrastructure/cicd/pipeline/PIPELINE-OPTIMIZATION.md names `Cargo.toml`, but no file or folder `Cargo.toml` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
X10 · Duplicated predicate · Duplicated predicate · ×6
  • Duplicated predicate src/modules/carts/core/application/usecases/create-cart/create-cart.usecase.ts:29 — `!callerContext || callerContext.userId === null || !callerContext.permissions.has('manage_own_cart')` appears character-identically in 2 files — src/modules/carts/core/application/usecases/create-cart/create-cart.usecase.ts, src/modules/orders/core/application/usecases/validate-checkout/validate-checkout.usecase.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 src/modules/products/core/application/usecases/create-product/create-product.usecase.ts:55 — `!categoryResult.value || !categoryResult.value.isActive` appears character-identically in 2 files — src/modules/products/core/application/usecases/create-product/create-product.usecase.ts, src/modules/products/core/application/usecases/update-product/update-product.usecase.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 src/modules/inventory/core/domain/entities/reservation.ts:49 — `!props.items || props.items.length === 0` appears character-identically in 2 files — src/modules/inventory/core/domain/entities/reservation.ts, src/modules/orders/core/domain/entities/order.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 src/migrations/1787400000005-PaymentProviderAndCardMethod.ts:5 — `Array.isArray(result) && result.length > 0 && typeof result[0] === 'object' && result[0] !== null && 'count' in result[0]` appears character-identically in 5 files — src/migrations/1787400000005-PaymentProviderAndCardMethod.ts, src/migrations/1787400000006-WidenMoneyColumnsToScaleThree.ts, src/migrations/1787400000007-AlignCurrencyColumns.ts, src/migrations/1787400000009-RequireOrderItemProductName.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 src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:54 — `isCachedFlag === true || isCachedFlag === 'true'` appears character-identically in 2 files — src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts, src/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.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 src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts:123 — `userResult.isFailure || !userResult.value` appears character-identically in 2 files — src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts, src/modules/identity/core/application/usecases/user/deactivate-user/deactivate-user.usecase.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D12 · Dependency Hygiene · Deprecated · ×5
  • Deprecated: glob REDACTED:7897 — glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: node-domexception REDACTED:14249 — node-domexception 1.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native DOMException instead". 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:15809 — glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: glob REDACTED:17103 — glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: glob REDACTED:17792 — glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
D10 · Test Quality · Mock-dominated test · ×4
  • Mock-dominated test: returns unauthorized without revoking others when logout wins the rotation race src/modules/authentication/core/application/usecases/refresh-token/refresh-token.usecase.spec.ts:523 — This test sets up 3 test doubles (for example `jest.spyOn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: registers onFailed listener and executes compensation on failure src/modules/orders/primary-adapters/listeners/checkout-failure.listener.spec.ts:74 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) 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: looks up reservationId from inventoryGateway when missing in job data src/modules/orders/primary-adapters/listeners/checkout-failure.listener.spec.ts:100 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) 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: skips compensation for failed REFUND_PAYMENT jobs src/modules/orders/primary-adapters/listeners/checkout-failure.listener.spec.ts:127 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) 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.
D25 · ADR Conformance · ADR not followed · ×3
  • ADR not followed: ADR-0005: Typed Atomic OCC Update Contract docs/architecture/adr/ADR-0005-typed-atomic-occ-update-contract.md:41 — docs/architecture/adr/ADR-0005-typed-atomic-occ-update-contract.md:41 rules out `version` in Domain, entities, but production code uses it: REDACTED:11, src/modules/orders/testing/factories/order-entity.factory.ts:33, src/modules/orders/testing/factories/order-entity.factory.ts:56, src/modules/products/testing/factories/product-entity.factory.ts:20
  • ADR not followed: ADR-0006: Redis Fail-Open Cache-Aside & Key-Space Generation docs/architecture/adr/ADR-0006-redis-fail-open-cache-aside.md:38 — docs/architecture/adr/ADR-0006-redis-fail-open-cache-aside.md:38 rules out `isReady`, but production code uses it: src/infrastructure/health/indicators/redis.health-indicator.ts:16, src/infrastructure/metrics/collectors/infra-metrics.collector.ts:33, src/infrastructure/redis/redis.service.ts:88, src/infrastructure/redis/redis.service.ts:90, src/infrastructure/redis/redis.service.ts:93 (+21 more)
  • ADR not followed: ADR-0009: Hosted Demo Reset as Ops Infrastructure docs/architecture/adr/ADR-0009-demo-reset-ops-infrastructure.md:38 — docs/architecture/adr/ADR-0009-demo-reset-ops-infrastructure.md:38 rules out `InfrastructureModule`, but production code uses it: src/app.module.ts:14, src/app.module.ts:34, src/infrastructure/infrastructure.module.ts:62
C4 · Data Retention · Partial data-retention evidence · ×1
  • Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a documented retention period / data-expiry.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 1 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `(repository root)` (48746 LoC, 1074 module-visible types across 384 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
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D7 · Architectural Integrity · Checkable ADR rule enforced only by prose · ×1
  • Checkable ADR rule enforced only by prose: ADR-0009: Hosted Demo Reset as Ops Infrastructure docs/architecture/adr/ADR-0009-demo-reset-ops-infrastructure.md — ADR 'ADR-0009: Hosted Demo Reset as Ops Infrastructure' declares `enforcement: prose` but states a rule a test or analyzer can check: "Do not nest it under the global `InfrastructureModule` that domain modules already depend on for Redis/DB." Nothing in the build fails when the code breaks it — add an architecture test or analyzer (and `enforcement: test|analyzer` with an `enforcement_link`).
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 43636 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
R7 · Dead Code · Unused export 'needsWebBuild' · ×1
  • Unused export 'needsWebBuild' scripts/agent-output.mjs:124 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'DEMO_RESET_TOKEN_MIN_LENGTH' · ×1
  • Unused export 'DEMO_RESET_TOKEN_MIN_LENGTH' src/config/validate-env.ts:155 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'HealthIndicatorResultDto' · ×1
  • Unused export 'HealthIndicatorResultDto' src/infrastructure/health/dto/health-check-response.dto.ts:3 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'DEFAULT_RETRY_CONFIG' · ×1
  • Unused export 'DEFAULT_RETRY_CONFIG' src/infrastructure/jobs/retry-config.ts:15 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'CreateCartInput' · ×1
  • Unused export 'CreateCartInput' src/modules/carts/core/domain/repositories/cart.repository.ts:4 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'CartBuilder' · ×1
  • Unused export 'CartBuilder' REDACTED:5 — Nothing ultimately consumes this binding: its only referrer is the re-export in src/modules/carts/testing/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/modules/carts/testing/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'CreateUserAddressInput' · ×1
  • Unused export 'CreateUserAddressInput' src/modules/identity/core/application/usecases/user/create-user/create-user.usecase.ts:13 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'UserBuilder' · ×1
  • Unused export 'UserBuilder' src/modules/identity/testing/builders/user.builder.ts:4 — Nothing ultimately consumes this binding: its only referrer is the re-export in src/modules/identity/testing/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/modules/identity/testing/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'InventoryListItemResult' · ×1
  • Unused export 'InventoryListItemResult' src/modules/inventory/core/application/queries/results/inventory-list-item.result.ts:12 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'BulkCheckStockBodyDto' · ×1
  • Unused export 'BulkCheckStockBodyDto' src/modules/inventory/primary-adapters/dto/bulk-check-stock.dto.ts:17 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'OrderDetailResult' · ×1
  • Unused export 'OrderDetailResult' src/modules/orders/core/application/queries/results/order-detail.result.ts:23 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'OrderItemDetailResult' · ×1
  • Unused export 'OrderItemDetailResult' src/modules/orders/core/application/queries/results/order-item-detail.result.ts:11 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'OrderListItemResult' · ×1
  • Unused export 'OrderListItemResult' src/modules/orders/core/application/queries/results/order-list-item.result.ts:14 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'IOrderEditable' · ×1
  • Unused export 'IOrderEditable' src/modules/orders/core/domain/interfaces/order.interface.ts:28 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'OrderItemInput' · ×1
  • Unused export 'OrderItemInput' src/modules/orders/core/domain/repositories/order-repository.ts:5 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'PaymentDetailResult' · ×1
  • Unused export 'PaymentDetailResult' src/modules/payments/core/application/queries/results/payment-detail.result.ts:10 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'PaymentListItemResult' · ×1
  • Unused export 'PaymentListItemResult' src/modules/payments/core/application/queries/results/payment-list-item.result.ts:17 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'ProductBuilder' · ×1
  • Unused export 'ProductBuilder' src/modules/products/testing/builders/product.builder.ts:5 — Nothing ultimately consumes this binding: its only referrer is the re-export in src/modules/products/testing/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/modules/products/testing/index.ts in the same commit, or the barrel will import a name that no longer exists.
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 — 0/1 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
X5 · Nullable reference types · Null assertions (`!`) reduce the strict null checking score · ×1
  • Null assertions (`!`) reduce the strict null checking score — ~12.6 `!` null assertions per 1k TypeScript source lines — 606 assertion(s) across the 48012 source line(s) of the 749 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: src/modules/orders/primary-adapters/dto/order-detail-response.dto.ts (28), src/modules/products/primary-adapters/dto/product-response.dto.ts (26), src/modules/inventory/primary-adapters/dto/inventory-response.dto.ts (22). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Minor — 18 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×16
  • Outdated (npm): @nestjs/common — @nestjs/common is pinned at 12.1.3; registry.npmjs.org publishes 12.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @nestjs/core — @nestjs/core is pinned at 12.1.3; registry.npmjs.org publishes 12.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @nestjs/platform-express — @nestjs/platform-express is pinned at 12.1.3; registry.npmjs.org publishes 12.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @nestjs/platform-socket.io — @nestjs/platform-socket.io is pinned at 12.1.3; registry.npmjs.org publishes 12.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @nestjs/swagger — @nestjs/swagger is pinned at 12.0.2; registry.npmjs.org publishes 12.0.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/websockets — @nestjs/websockets is pinned at 12.1.3; registry.npmjs.org publishes 12.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @opentelemetry/api — @opentelemetry/api is pinned at 1.9.1; registry.npmjs.org publishes 1.10.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @opentelemetry/auto-instrumentations-node — @opentelemetry/auto-instrumentations-node is pinned at 0.81.0; registry.npmjs.org publishes 0.82.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @opentelemetry/exporter-trace-otlp-grpc — @opentelemetry/exporter-trace-otlp-grpc is pinned at 0.223.0; registry.npmjs.org publishes 0.300.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @opentelemetry/resources — @opentelemetry/resources is pinned at 2.12.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): @opentelemetry/sdk-node — @opentelemetry/sdk-node is pinned at 0.223.0; registry.npmjs.org publishes 0.300.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): bullmq — bullmq is pinned at 5.65.1; registry.npmjs.org publishes 6.4.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): ioredis — ioredis is pinned at 5.10.1; registry.npmjs.org publishes 6.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): jose — jose is pinned at 6.2.12; registry.npmjs.org publishes 6.2.13 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): sanitize-html — sanitize-html is pinned at 2.18.0; registry.npmjs.org publishes 2.18.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): typeorm — typeorm is pinned at 0.3.31; registry.npmjs.org publishes 1.1.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
D10 · Test Quality · Skipped (documented) · ×2
  • Skipped (documented): (unnamed test) src/modules/identity/primary-adapters/decorators/current-user.decorator.spec.ts:11 — 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): succeeded event for a FAILED payment, needs a product decision src/modules/payments/core/application/services/handle-payment-webhook/handle-payment-webhook.service.spec.ts:391 — Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-50edc72642a941dbb05a178186393c64/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/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-50edc72642a941dbb05a178186393c64/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/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .51artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update2artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .9artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a16400-9bad-772d-a7a8-c3b1a4a4d58f · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 29 · Warnings: 558 · Recommendations: 113 · Info: 18 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 14:25 UTC.

Downloadable artifacts

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

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