Executive summary
raouf-b-dev/ecommerce-store-api falls short of our standard for a preview release, held back most by its Code Health lens, the quality of the code itself. It scores 57 out of 100 and is rated Adequate, and 14 of its 27 critical findings are security problems.
Code Health, at 54, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is replacing the three exposed passwords or keys and switching the old ones off, worth about 3 points. Turning on missing-value checks would lift Code Health itself, worth about 2 points.
Eight passwords or keys in the code's history and three in the code are open to anyone who can read the repository. Two automatic updates take new releases before a bad one can be spotted, and one setting leaves the servers or containers unsafe. Replacing each exposed password or key, setting a waiting period for automatic updates and correcting the unsafe settings would close these risks. The seven loops of files that import each other need breaking.
The product code is 50,579 lines, about €130,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 62 findings
- Cyclomatic Complexity · ProcessRefundUseCase.execute (cyclomatic 17) src/modules/payments/core/application/usecases/process-refund/process-refund.usecase.ts
- Cognitive Complexity · GlobalExceptionFilter.catch (cognitive 21) src/filters/global-exception.filter.ts
- Cognitive Complexity · SeedDemoAuthUsersUseCase.seedUser (cognitive 16) REDACTED
- Test Quality · No assertions: refuses a password change for the read-only viewer test/e2e/security/security-idor.e2e-spec.ts
- Test Quality · No assertions: should return an InfrastructureError when upsertJobScheduler fails src/modules/orders/secondary-adapters/schedulers/bullmq-checkout.scheduler.spec.ts
- Test Quality · No assertions: accepts contact filters for a caller with view_customer_pii src/modules/orders/core/application/usecases/list-orders/list-orders.usecase.spec.ts
- Test Quality · No assertions: allows the owner to cancel a %s order src/modules/orders/core/application/services/cancel-order-access.policy.spec.ts
- Test Quality · No assertions: allows manage_orders to cancel a PROCESSING order src/modules/orders/core/application/services/cancel-order-access.policy.spec.ts
- Test Quality · No assertions: allows the system caller to cancel a PROCESSING order src/modules/orders/core/application/services/cancel-order-access.policy.spec.ts
- Test Quality · No assertions: returns not found for a foreign order src/modules/orders/core/application/services/cancel-order-access.policy.spec.ts
- Test Quality · No assertions: should return failure if repository find fails src/modules/authorization/core/application/usecases/role/find-role-by-id.usecase.spec.ts
- Test Quality · No assertions: accepts a role holding change_own_credentials src/modules/authentication/core/domain/policies/credential-change.policy.spec.ts
- Test Quality · No assertions: accepts an account that already has the expected role src/modules/authentication/core/domain/policies/demo-account-reseed.policy.spec.ts
- Test Quality · No assertions: refuses an account with a different role src/modules/authentication/core/domain/policies/demo-account-reseed.policy.spec.ts
- Test Quality · No assertions: refuses an account with no role src/modules/authentication/core/domain/policies/demo-account-reseed.policy.spec.ts
- Test Quality · No assertions: should fail when the existing credential lookup fails src/modules/authentication/core/application/seed/seed-demo-auth-users.usecase.spec.ts
- Test Quality · No assertions: should fail when the credential reset cannot be saved src/modules/authentication/core/application/seed/seed-demo-auth-users.usecase.spec.ts
- Test Quality · No assertions: should fail loudly when the user rollback after a credential save failure fails src/modules/authentication/core/application/seed/seed-demo-auth-users.usecase.spec.ts
- Test Quality · No assertions: should fail loudly when the user rollback after a role failure fails src/modules/authentication/core/application/seed/seed-demo-auth-users.usecase.spec.ts
- REDACTED Scanning · REDACTED
- Churn × Complexity Hotspots · Hotspot: src/modules/payments/core/application/usecases/process-refund/process-refund.usecase.ts src/modules/payments/core/application/usecases/process-refund/process-refund.usecase.ts
- Churn × Complexity Hotspots · Hotspot: src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts
- Churn × Complexity Hotspots · Hotspot: src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts
- Churn × Complexity Hotspots · Hotspot: 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
- Secrets (history) · REDACTED
- Secrets (history) · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Code Duplication · Duplication concentrated across 10 sibling directories (9 clone groups) src/modules/orders/core/application/usecases/process-order/process-order.usecase.ts
- Code Duplication · Duplication concentrated across 3 sibling directories (6 clone groups) src/modules/payments/core/domain/value-objects/payment-status.ts
- Code Duplication · Duplication concentrated across 6 sibling directories (6 clone groups) src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts
- Code Duplication · Duplicated block with local edits (98 matched lines × 2 locations) src/modules/carts/secondary-adapters/repositories/cached-cart-repository/cached.cart-repository.ts
- Code Duplication · Duplicated block (70 lines × 2 locations) src/modules/carts/secondary-adapters/repositories/postgres-cart-repository/postgres.cart-repository.ts
- Code Duplication · Duplicated block with local edits (63 matched lines × 2 locations) src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts
- Code Duplication · Duplicated block with local edits (54 matched lines × 2 locations) src/modules/products/core/application/usecases/create-product/create-product.usecase.ts
- Code Duplication · Duplicated block with local edits (51 matched lines × 2 locations) src/modules/inventory/secondary-adapters/repositories/postgres-inventory-repository/postgres-inventory-repository.ts
- Code Duplication · Duplicated block with local edits (49 matched lines × 2 locations) src/modules/authorization/secondary-adapter/repositories/postgres-role-repository/postgres-role.repository.ts
- Code Duplication · Duplicated block with local edits (45 matched lines × 2 locations) src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts
- Code Duplication · Duplicated block with local edits (45 matched lines × 2 locations) src/modules/identity/core/application/usecases/address/add-address/add-address.usecase.ts
- Code Duplication · Duplicated block with local edits (44 matched lines × 2 locations) src/modules/authorization/secondary-adapter/repositories/postgres-role-repository/postgres-role.repository.ts
- Code Duplication · Duplicated block (44 lines × 2 locations) src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts
- Code Duplication · Duplicated block (41 lines × 2 locations) src/modules/products/secondary-adapters/query/postgres-product-query.adapter.ts
- Code Duplication · Duplicated block (36 lines × 2 locations) src/modules/products/core/application/usecases/categories/activate-category.usecase.ts
- Code Duplication · Duplicated block with local edits (35 matched lines × 2 locations) src/modules/inventory/secondary-adapters/repositories/cached-inventory-repository/cached-inventory-repository.ts
- Code Duplication · Duplicated block with local edits (34 matched lines × 2 locations) src/modules/products/core/application/usecases/activate-product/activate-product.usecase.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 (30 lines × 2 locations) src/modules/products/core/application/usecases/categories/get-category.usecase.ts
- Code Duplication · Duplicated block (28 lines × 2 locations) src/modules/identity/secondary-adapters/repositories/cached-user-repository/cached-user.repository.ts
- Cyclomatic Complexity · Complex function (top-level) (cyclomatic 27, cognitive 44) src/filters/global-exception.filter.ts
- Cyclomatic Complexity · Complex function (top-level) (cyclomatic 25, cognitive 32) REDACTED
- Cyclomatic Complexity · Complex function (top-level) (cyclomatic 16, cognitive 15) src/modules/orders/core/application/usecases/handle-payment-completed/handle-payment-completed.usecase.ts
- Cyclomatic Complexity · Complex function (top-level) (cyclomatic 15, cognitive 14) src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts
- Large Files · src/modules/orders/core/domain/entities/order.ts: 488 lines of code src/modules/orders/core/domain/entities/order.ts
- Large Files · src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.ts: 419 lines of code src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.ts
- Exception handling · Swallowed exception (empty catch) src/shared-kernel/helpers/lang/app-version.ts
- Aggregate boundaries · Aggregate holds a reference to another aggregate: Payment._refunds src/modules/payments/core/domain/entities/payment.ts
- Aggregate boundaries · Aggregate holds a reference to another aggregate: Payment.refunds src/modules/payments/core/domain/entities/payment.ts
- Aggregate boundaries · Aggregate holds a reference to another aggregate: User._addresses src/modules/identity/core/domain/entities/user.ts
Fixed since the last survey: 392 findings
- Cyclomatic Complexity · generate-envs.buildLinesForEnv (cyclomatic 26) scripts/generate-envs.js
- 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 · setup-bootstrap.runSetup (cyclomatic 16) scripts/lib/setup-bootstrap.js
- 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 · generate-envs.buildLinesForEnv (cognitive 31) scripts/generate-envs.js
- Cognitive Complexity · agent-output.selectVitestCommands (cognitive 21) scripts/agent-output.mjs
- Cognitive Complexity · ascii-prose.findComments (cognitive 19) scripts/ascii-prose.cjs
- God Classes · MethodTooLong: ChangePasswordUseCase.execute src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts
- Code Coverage · Low coverage: src/config/config.module.ts src/config/config.module.ts
- Code Coverage · Low coverage: src/config/configuration.ts src/config/configuration.ts
- Code Coverage · Low coverage: src/config/env-config.service.ts src/config/env-config.service.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/database/number.transformer.ts src/infrastructure/database/number.transformer.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/events/event-emitter2.domain-event-publisher.ts src/infrastructure/events/event-emitter2.domain-event-publisher.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/jobs/job-child-values.ts src/infrastructure/jobs/job-child-values.ts
- Code Coverage · Low coverage: src/infrastructure/jobs/retry-strategy.ts src/infrastructure/jobs/retry-strategy.ts
- Code Coverage · Low coverage: src/infrastructure/jwt/services/jwks.service.ts src/infrastructure/jwt/services/jwks.service.ts
- Code Coverage · Low coverage: src/infrastructure/jwt/services/jwt-verifier.service.ts src/infrastructure/jwt/services/jwt-verifier.service.ts
- Code Coverage · Low coverage: src/infrastructure/logging/winston-logger.service.ts src/infrastructure/logging/winston-logger.service.ts
- Code Coverage · Low coverage: src/infrastructure/logging/middleware/http-logging.middleware.ts src/infrastructure/logging/middleware/http-logging.middleware.ts
- Code Coverage · Low coverage: src/infrastructure/metrics/metrics.controller.ts src/infrastructure/metrics/metrics.controller.ts
- Code Coverage · Low coverage: src/infrastructure/metrics/metrics.middleware.ts src/infrastructure/metrics/metrics.middleware.ts
- Code Coverage · Low coverage: src/infrastructure/metrics/metrics.service.ts src/infrastructure/metrics/metrics.service.ts
- Code Coverage · Low coverage: src/infrastructure/metrics/collectors/infra-metrics.collector.ts src/infrastructure/metrics/collectors/infra-metrics.collector.ts
- Code Coverage · Low coverage: src/infrastructure/metrics/guards/metrics-auth.guard.ts src/infrastructure/metrics/guards/metrics-auth.guard.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/flow-producer.service.ts src/infrastructure/queue/flow-producer.service.ts
- Code Coverage · Low coverage: src/infrastructure/queue/queue-events.service.ts src/infrastructure/queue/queue-events.service.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/redis/testing/mocks/redis-service.mock.ts src/infrastructure/redis/testing/mocks/redis-service.mock.ts
- Code Coverage · Low coverage: src/infrastructure/swagger/swagger-document.config.ts src/infrastructure/swagger/swagger-document.config.ts
- Code Coverage · Low coverage: src/infrastructure/throttler/throttler.module.ts src/infrastructure/throttler/throttler.module.ts
- Code Coverage · Low coverage: src/infrastructure/throttler/user-throttler.guard.ts src/infrastructure/throttler/user-throttler.guard.ts
- Code Coverage · Low coverage: src/infrastructure/tracing/tracing.ts src/infrastructure/tracing/tracing.ts
- Code Coverage · Low coverage: src/infrastructure/websocket/websocket.connection.gateway.ts src/infrastructure/websocket/websocket.connection.gateway.ts
- Code Coverage · Low coverage: src/infrastructure/websocket/adapters/redis-io.adapter.ts src/infrastructure/websocket/adapters/redis-io.adapter.ts
- Code Coverage · Low coverage: src/infrastructure/websocket/guards/ws-auth.guard.ts src/infrastructure/websocket/guards/ws-auth.guard.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/analytics/secondary-adapters/query/postgres-analytics-query.adapter.ts src/modules/analytics/secondary-adapters/query/postgres-analytics-query.adapter.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/primary-adapters/listeners/user-deactivated.listener.ts src/modules/authentication/primary-adapters/listeners/user-deactivated.listener.ts
- Code Coverage · Low coverage: src/modules/authentication/secondary-adapters/adapters/module-authorization.gateway.ts src/modules/authentication/secondary-adapters/adapters/module-authorization.gateway.ts
- Code Coverage · Low coverage: src/modules/authentication/secondary-adapters/adapters/module-identity.gateway.ts src/modules/authentication/secondary-adapters/adapters/module-identity.gateway.ts
- Code Coverage · Low coverage: src/modules/authentication/secondary-adapters/repositories/postgres-credential.repository/postgres-credential.repository.ts src/modules/authentication/secondary-adapters/repositories/postgres-credential.repository/postgres-credential.repository.ts
- Code Coverage · Low coverage: src/modules/authentication/secondary-adapters/repositories/postgres-session-token-repository/postgres-session-token.repository.ts src/modules/authentication/secondary-adapters/repositories/postgres-session-token-repository/postgres-session-token.repository.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/authorization/secondary-adapter/persistence/mappers/permission.mapper.ts src/modules/authorization/secondary-adapter/persistence/mappers/permission.mapper.ts
- Code Coverage · Low coverage: src/modules/authorization/secondary-adapter/persistence/mappers/role.mapper.ts src/modules/authorization/secondary-adapter/persistence/mappers/role.mapper.ts
- Code Coverage · Low coverage: src/modules/authorization/secondary-adapter/persistence/mappers/user-role-assignment.mapper.ts src/modules/authorization/secondary-adapter/persistence/mappers/user-role-assignment.mapper.ts
- Code Coverage · Low coverage: src/modules/authorization/secondary-adapter/repositories/postgres-permission-repository/postgres-permission.repository.ts src/modules/authorization/secondary-adapter/repositories/postgres-permission-repository/postgres-permission.repository.ts
- Code Coverage · Low coverage: src/modules/authorization/secondary-adapter/repositories/postgres-role-repository/postgres-role.repository.ts src/modules/authorization/secondary-adapter/repositories/postgres-role-repository/postgres-role.repository.ts
- Code Coverage · Low coverage: src/modules/authorization/secondary-adapter/repositories/postgres-user-role-assignment-repository/postgres-user-role-assignment.repository.ts src/modules/authorization/secondary-adapter/repositories/postgres-user-role-assignment-repository/postgres-user-role-assignment.repository.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/secondary-adapters/adapters/module-product.gateway.ts src/modules/carts/secondary-adapters/adapters/module-product.gateway.ts
- Code Coverage · Low coverage: src/modules/carts/secondary-adapters/query/postgres-cart-query.adapter.ts src/modules/carts/secondary-adapters/query/postgres-cart-query.adapter.ts
- Code Coverage · Low coverage: src/modules/carts/secondary-adapters/repositories/cached-cart-repository/cached.cart-repository.ts src/modules/carts/secondary-adapters/repositories/cached-cart-repository/cached.cart-repository.ts
- Code Coverage · Low coverage: REDACTED REDACTED
- 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/primary-adapters/decorators/caller-context.decorator.ts src/modules/identity/primary-adapters/decorators/caller-context.decorator.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/identity/secondary-adapters/query/postgres-user-query.adapter.ts src/modules/identity/secondary-adapters/query/postgres-user-query.adapter.ts
- Code Coverage · Low coverage: src/modules/identity/testing/builders/user.builder.ts src/modules/identity/testing/builders/user.builder.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/inventory/core/domain/value-objects/stock-adjustment-reason.ts src/modules/inventory/core/domain/value-objects/stock-adjustment-reason.ts
- Code Coverage · Low coverage: src/modules/inventory/secondary-adapters/query/postgres-inventory-query.adapter.ts src/modules/inventory/secondary-adapters/query/postgres-inventory-query.adapter.ts
- Code Coverage · Low coverage: src/modules/notifications/notifications.controller.ts src/modules/notifications/notifications.controller.ts
- Code Coverage · Low coverage: src/modules/notifications/notifications.processor.ts src/modules/notifications/notifications.processor.ts
- Code Coverage · Low coverage: src/modules/notifications/core/application/services/cleanup-expired-notifications.service.ts src/modules/notifications/core/application/services/cleanup-expired-notifications.service.ts
- Code Coverage · Low coverage: src/modules/notifications/core/application/services/deliver-notification.service.ts src/modules/notifications/core/application/services/deliver-notification.service.ts
- Code Coverage · Low coverage: src/modules/notifications/core/application/services/save-notification-history.service.ts src/modules/notifications/core/application/services/save-notification-history.service.ts
- Code Coverage · Low coverage: src/modules/notifications/core/application/services/update-notification-status.service.ts src/modules/notifications/core/application/services/update-notification-status.service.ts
- Code Coverage · Low coverage: src/modules/notifications/core/application/usecases/get-user-notifications.usecase.ts src/modules/notifications/core/application/usecases/get-user-notifications.usecase.ts
- Code Coverage · Low coverage: src/modules/notifications/core/application/usecases/mark-notification-as-read.usecase.ts src/modules/notifications/core/application/usecases/mark-notification-as-read.usecase.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/notifications/primary-adapters/jobs/cleanup-expired-notifications.process.ts src/modules/notifications/primary-adapters/jobs/cleanup-expired-notifications.process.ts
- Code Coverage · Low coverage: src/modules/notifications/primary-adapters/jobs/deliver-notification.process.ts src/modules/notifications/primary-adapters/jobs/deliver-notification.process.ts
- Code Coverage · Low coverage: src/modules/notifications/primary-adapters/jobs/save-notification-history.process.ts src/modules/notifications/primary-adapters/jobs/save-notification-history.process.ts
- Code Coverage · Low coverage: src/modules/notifications/primary-adapters/jobs/update-notification-status.process.ts src/modules/notifications/primary-adapters/jobs/update-notification-status.process.ts
- Code Coverage · Low coverage: src/modules/notifications/secondary-adapters/gateways/websocket.notification.gateway.ts src/modules/notifications/secondary-adapters/gateways/websocket.notification.gateway.ts
- Code Coverage · Low coverage: src/modules/notifications/secondary-adapters/persistence/mappers/notification.mapper.ts src/modules/notifications/secondary-adapters/persistence/mappers/notification.mapper.ts
Rebuild cost: about €130,000 · Estimate
| Cost to rebuild | €42,000 to €210,000, for 698 to 2,213 hours of work, about 0.9 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | High, 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.8 at a score of 57. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 50,579 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 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_handler | 14 shared-kernel.domain.exceptions.domain_error | 15 shared-kernel.domain.exceptions.infrastructure-error | 16 shared-kernel.domain.exceptions.query_error | 17 shared-kernel.domain.exceptions.repository_error | 18 shared-kernel.domain.exceptions.usecase_error | 19 shared-kernel.domain.interfaces.base_usecase | 20 modules.analytics.core.application.ports.analytics-query_service | 21 modules.authentication.core.application.ports.authorization_gateway | 22 modules.authentication.core.domain.repositories.credential_repository | 23 modules.authorization.core.domain.repositories.role_repository | 24 modules.carts.core.domain.repositories.cart_repository | 25 modules.identity.core.domain.repositories.user_repository | 26 modules.inventory.core.domain.repositories.inventory_repository | 27 modules.orders.core.domain.schedulers.order_scheduler | 28 modules.products.core.domain.repositories.category-repository | 29 shared-kernel.domain.value-objects.money | 30 modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter | 31 modules.authentication.core.application.usecases.change-password.change-password_usecase | 32 modules.authentication.core.application.usecases.login-user.login-user_usecase | 33 modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase | 34 modules.orders.core.domain.entities.order | 35 modules.payments.core.domain.entities.payment | 36 modules.authentication.authentication_controller | 37 modules.orders.core.domain.repositories.order-repository | 38 modules.payments.core.domain.repositories.payment_repository | 39 modules.orders.core.application.usecases.cancel-order.cancel-order_usecase | 40 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_handler | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 shared-kernel.domain.exceptions.domain_error | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 shared-kernel.domain.exceptions.infrastructure-error | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 shared-kernel.domain.exceptions.query_error | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 shared-kernel.domain.exceptions.repository_error | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 shared-kernel.domain.exceptions.usecase_error | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 shared-kernel.domain.interfaces.base_usecase | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 modules.analytics.core.application.ports.analytics-query_service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 modules.authentication.core.application.ports.authorization_gateway | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 modules.authentication.core.domain.repositories.credential_repository | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 modules.authorization.core.domain.repositories.role_repository | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 modules.carts.core.domain.repositories.cart_repository | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 modules.identity.core.domain.repositories.user_repository | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 modules.inventory.core.domain.repositories.inventory_repository | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 modules.orders.core.domain.schedulers.order_scheduler | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 modules.products.core.domain.repositories.category-repository | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 shared-kernel.domain.value-objects.money | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 modules.authentication.core.application.usecases.change-password.change-password_usecase | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 32 modules.authentication.core.application.usecases.login-user.login-user_usecase | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 33 modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 34 modules.orders.core.domain.entities.order | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 35 modules.payments.core.domain.entities.payment | 1 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 modules.authentication.authentication_controller | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 modules.orders.core.domain.repositories.order-repository | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 modules.payments.core.domain.repositories.payment_repository | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 modules.orders.core.application.usecases.cancel-order.cancel-order_usecase | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 modules.orders.orders_controller | 1 | 1 |
13→7 infrastructure.jobs.base-job_handler uses shared-kernel.domain.exceptions.app_error✕
- Connections
- 1 pair of types, where a type in infrastructure.jobs.base-job_handler uses a type in shared-kernel.domain.exceptions.app_error.
- The types involved
src.infrastructure.jobs.base-job_handler.BaseJobHandler→src.shared-kernel.domain.exceptions.app_error.AppError
- Direction
- infrastructure.jobs.base-job_handler uses shared-kernel.domain.exceptions.app_error, so a change to shared-kernel.domain.exceptions.app_error can break infrastructure.jobs.base-job_handler, while a change to infrastructure.jobs.base-job_handler can't break shared-kernel.domain.exceptions.app_error.
- Position
- Below the diagonal: infrastructure.jobs.base-job_handler uses a module listed above it, which is the healthy direction.
13→10 infrastructure.jobs.base-job_handler uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in infrastructure.jobs.base-job_handler uses a type in shared-kernel.domain.result.
- The types involved
src.infrastructure.jobs.base-job_handler.BaseJobHandler→src.shared-kernel.domain.result.Result
- Direction
- infrastructure.jobs.base-job_handler uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break infrastructure.jobs.base-job_handler, while a change to infrastructure.jobs.base-job_handler can't break shared-kernel.domain.result.
- Position
- Below the diagonal: infrastructure.jobs.base-job_handler uses a module listed above it, which is the healthy direction.
14→7 shared-kernel.domain.exceptions.domain_error uses shared-kernel.domain.exceptions.app_error✕
- Connections
- 1 pair of types, where a type in shared-kernel.domain.exceptions.domain_error uses a type in shared-kernel.domain.exceptions.app_error.
- The types involved
src.shared-kernel.domain.exceptions.domain_error.DomainError→src.shared-kernel.domain.exceptions.app_error.AppError
- Direction
- shared-kernel.domain.exceptions.domain_error uses shared-kernel.domain.exceptions.app_error, so a change to shared-kernel.domain.exceptions.app_error can break shared-kernel.domain.exceptions.domain_error, while a change to shared-kernel.domain.exceptions.domain_error can't break shared-kernel.domain.exceptions.app_error.
- Position
- Below the diagonal: shared-kernel.domain.exceptions.domain_error uses a module listed above it, which is the healthy direction.
15→7 shared-kernel.domain.exceptions.infrastructure-error uses shared-kernel.domain.exceptions.app_error✕
- Connections
- 1 pair of types, where a type in shared-kernel.domain.exceptions.infrastructure-error uses a type in shared-kernel.domain.exceptions.app_error.
- The types involved
src.shared-kernel.domain.exceptions.infrastructure-error.InfrastructureError→src.shared-kernel.domain.exceptions.app_error.AppError
- Direction
- shared-kernel.domain.exceptions.infrastructure-error uses shared-kernel.domain.exceptions.app_error, so a change to shared-kernel.domain.exceptions.app_error can break shared-kernel.domain.exceptions.infrastructure-error, while a change to shared-kernel.domain.exceptions.infrastructure-error can't break shared-kernel.domain.exceptions.app_error.
- Position
- Below the diagonal: shared-kernel.domain.exceptions.infrastructure-error uses a module listed above it, which is the healthy direction.
16→7 shared-kernel.domain.exceptions.query_error uses shared-kernel.domain.exceptions.app_error✕
- Connections
- 1 pair of types, where a type in shared-kernel.domain.exceptions.query_error uses a type in shared-kernel.domain.exceptions.app_error.
- The types involved
src.shared-kernel.domain.exceptions.query_error.QueryError→src.shared-kernel.domain.exceptions.app_error.AppError
- Direction
- shared-kernel.domain.exceptions.query_error uses shared-kernel.domain.exceptions.app_error, so a change to shared-kernel.domain.exceptions.app_error can break shared-kernel.domain.exceptions.query_error, while a change to shared-kernel.domain.exceptions.query_error can't break shared-kernel.domain.exceptions.app_error.
- Position
- Below the diagonal: shared-kernel.domain.exceptions.query_error uses a module listed above it, which is the healthy direction.
17→7 shared-kernel.domain.exceptions.repository_error uses shared-kernel.domain.exceptions.app_error✕
- Connections
- 1 pair of types, where a type in shared-kernel.domain.exceptions.repository_error uses a type in shared-kernel.domain.exceptions.app_error.
- The types involved
src.shared-kernel.domain.exceptions.repository_error.RepositoryError→src.shared-kernel.domain.exceptions.app_error.AppError
- Direction
- shared-kernel.domain.exceptions.repository_error uses shared-kernel.domain.exceptions.app_error, so a change to shared-kernel.domain.exceptions.app_error can break shared-kernel.domain.exceptions.repository_error, while a change to shared-kernel.domain.exceptions.repository_error can't break shared-kernel.domain.exceptions.app_error.
- Position
- Below the diagonal: shared-kernel.domain.exceptions.repository_error uses a module listed above it, which is the healthy direction.
18→7 shared-kernel.domain.exceptions.usecase_error uses shared-kernel.domain.exceptions.app_error✕
- Connections
- 1 pair of types, where a type in shared-kernel.domain.exceptions.usecase_error uses a type in shared-kernel.domain.exceptions.app_error.
- The types involved
src.shared-kernel.domain.exceptions.usecase_error.UseCaseError→src.shared-kernel.domain.exceptions.app_error.AppError
- Direction
- shared-kernel.domain.exceptions.usecase_error uses shared-kernel.domain.exceptions.app_error, so a change to shared-kernel.domain.exceptions.app_error can break shared-kernel.domain.exceptions.usecase_error, while a change to shared-kernel.domain.exceptions.usecase_error can't break shared-kernel.domain.exceptions.app_error.
- Position
- Below the diagonal: shared-kernel.domain.exceptions.usecase_error uses a module listed above it, which is the healthy direction.
19→10 shared-kernel.domain.interfaces.base_usecase uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in shared-kernel.domain.interfaces.base_usecase uses a type in shared-kernel.domain.result.
- The types involved
src.shared-kernel.domain.interfaces.base_usecase.UseCase→src.shared-kernel.domain.result.Result
- Direction
- shared-kernel.domain.interfaces.base_usecase uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break shared-kernel.domain.interfaces.base_usecase, while a change to shared-kernel.domain.interfaces.base_usecase can't break shared-kernel.domain.result.
- Position
- Below the diagonal: shared-kernel.domain.interfaces.base_usecase uses a module listed above it, which is the healthy direction.
20→10 modules.analytics.core.application.ports.analytics-query_service uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in modules.analytics.core.application.ports.analytics-query_service uses a type in shared-kernel.domain.result.
- The types involved
src.modules.analytics.core.application.ports.analytics-query_service.AnalyticsQueryService→src.shared-kernel.domain.result.Result
- Direction
- modules.analytics.core.application.ports.analytics-query_service uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break modules.analytics.core.application.ports.analytics-query_service, while a change to modules.analytics.core.application.ports.analytics-query_service can't break shared-kernel.domain.result.
- Position
- Below the diagonal: modules.analytics.core.application.ports.analytics-query_service uses a module listed above it, which is the healthy direction.
20→16 modules.analytics.core.application.ports.analytics-query_service uses shared-kernel.domain.exceptions.query_error✕
- Connections
- 1 pair of types, where a type in modules.analytics.core.application.ports.analytics-query_service uses a type in shared-kernel.domain.exceptions.query_error.
- The types involved
src.modules.analytics.core.application.ports.analytics-query_service.AnalyticsQueryService→src.shared-kernel.domain.exceptions.query_error.QueryError
- Direction
- modules.analytics.core.application.ports.analytics-query_service uses shared-kernel.domain.exceptions.query_error, so a change to shared-kernel.domain.exceptions.query_error can break modules.analytics.core.application.ports.analytics-query_service, while a change to modules.analytics.core.application.ports.analytics-query_service can't break shared-kernel.domain.exceptions.query_error.
- Position
- Below the diagonal: modules.analytics.core.application.ports.analytics-query_service uses a module listed above it, which is the healthy direction.
21→10 modules.authentication.core.application.ports.authorization_gateway uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in modules.authentication.core.application.ports.authorization_gateway uses a type in shared-kernel.domain.result.
- The types involved
src.modules.authentication.core.application.ports.authorization_gateway.AuthorizationGateway→src.shared-kernel.domain.result.Result
- Direction
- modules.authentication.core.application.ports.authorization_gateway uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break modules.authentication.core.application.ports.authorization_gateway, while a change to modules.authentication.core.application.ports.authorization_gateway can't break shared-kernel.domain.result.
- Position
- Below the diagonal: modules.authentication.core.application.ports.authorization_gateway uses a module listed above it, which is the healthy direction.
21→15 modules.authentication.core.application.ports.authorization_gateway uses shared-kernel.domain.exceptions.infrastructure-error✕
- Connections
- 1 pair of types, where a type in modules.authentication.core.application.ports.authorization_gateway uses a type in shared-kernel.domain.exceptions.infrastructure-error.
- The types involved
src.modules.authentication.core.application.ports.authorization_gateway.AuthorizationGateway→src.shared-kernel.domain.exceptions.infrastructure-error.InfrastructureError
- Direction
- modules.authentication.core.application.ports.authorization_gateway uses shared-kernel.domain.exceptions.infrastructure-error, so a change to shared-kernel.domain.exceptions.infrastructure-error can break modules.authentication.core.application.ports.authorization_gateway, while a change to modules.authentication.core.application.ports.authorization_gateway can't break shared-kernel.domain.exceptions.infrastructure-error.
- Position
- Below the diagonal: modules.authentication.core.application.ports.authorization_gateway uses a module listed above it, which is the healthy direction.
22→10 modules.authentication.core.domain.repositories.credential_repository uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in modules.authentication.core.domain.repositories.credential_repository uses a type in shared-kernel.domain.result.
- The types involved
src.modules.authentication.core.domain.repositories.credential_repository.CredentialRepository→src.shared-kernel.domain.result.Result
- Direction
- modules.authentication.core.domain.repositories.credential_repository uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break modules.authentication.core.domain.repositories.credential_repository, while a change to modules.authentication.core.domain.repositories.credential_repository can't break shared-kernel.domain.result.
- Position
- Below the diagonal: modules.authentication.core.domain.repositories.credential_repository uses a module listed above it, which is the healthy direction.
22→17 modules.authentication.core.domain.repositories.credential_repository uses shared-kernel.domain.exceptions.repository_error✕
- Connections
- 1 pair of types, where a type in modules.authentication.core.domain.repositories.credential_repository uses a type in shared-kernel.domain.exceptions.repository_error.
- The types involved
src.modules.authentication.core.domain.repositories.credential_repository.CredentialRepository→src.shared-kernel.domain.exceptions.repository_error.RepositoryError
- Direction
- modules.authentication.core.domain.repositories.credential_repository uses shared-kernel.domain.exceptions.repository_error, so a change to shared-kernel.domain.exceptions.repository_error can break modules.authentication.core.domain.repositories.credential_repository, while a change to modules.authentication.core.domain.repositories.credential_repository can't break shared-kernel.domain.exceptions.repository_error.
- Position
- Below the diagonal: modules.authentication.core.domain.repositories.credential_repository uses a module listed above it, which is the healthy direction.
23→10 modules.authorization.core.domain.repositories.role_repository uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in modules.authorization.core.domain.repositories.role_repository uses a type in shared-kernel.domain.result.
- The types involved
src.modules.authorization.core.domain.repositories.role_repository.RoleRepository→src.shared-kernel.domain.result.Result
- Direction
- modules.authorization.core.domain.repositories.role_repository uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break modules.authorization.core.domain.repositories.role_repository, while a change to modules.authorization.core.domain.repositories.role_repository can't break shared-kernel.domain.result.
- Position
- Below the diagonal: modules.authorization.core.domain.repositories.role_repository uses a module listed above it, which is the healthy direction.
23→17 modules.authorization.core.domain.repositories.role_repository uses shared-kernel.domain.exceptions.repository_error✕
- Connections
- 1 pair of types, where a type in modules.authorization.core.domain.repositories.role_repository uses a type in shared-kernel.domain.exceptions.repository_error.
- The types involved
src.modules.authorization.core.domain.repositories.role_repository.RoleRepository→src.shared-kernel.domain.exceptions.repository_error.RepositoryError
- Direction
- modules.authorization.core.domain.repositories.role_repository uses shared-kernel.domain.exceptions.repository_error, so a change to shared-kernel.domain.exceptions.repository_error can break modules.authorization.core.domain.repositories.role_repository, while a change to modules.authorization.core.domain.repositories.role_repository can't break shared-kernel.domain.exceptions.repository_error.
- Position
- Below the diagonal: modules.authorization.core.domain.repositories.role_repository uses a module listed above it, which is the healthy direction.
24→10 modules.carts.core.domain.repositories.cart_repository uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in modules.carts.core.domain.repositories.cart_repository uses a type in shared-kernel.domain.result.
- The types involved
src.modules.carts.core.domain.repositories.cart_repository.CartRepository→src.shared-kernel.domain.result.Result
- Direction
- modules.carts.core.domain.repositories.cart_repository uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break modules.carts.core.domain.repositories.cart_repository, while a change to modules.carts.core.domain.repositories.cart_repository can't break shared-kernel.domain.result.
- Position
- Below the diagonal: modules.carts.core.domain.repositories.cart_repository uses a module listed above it, which is the healthy direction.
24→17 modules.carts.core.domain.repositories.cart_repository uses shared-kernel.domain.exceptions.repository_error✕
- Connections
- 1 pair of types, where a type in modules.carts.core.domain.repositories.cart_repository uses a type in shared-kernel.domain.exceptions.repository_error.
- The types involved
src.modules.carts.core.domain.repositories.cart_repository.CartRepository→src.shared-kernel.domain.exceptions.repository_error.RepositoryError
- Direction
- modules.carts.core.domain.repositories.cart_repository uses shared-kernel.domain.exceptions.repository_error, so a change to shared-kernel.domain.exceptions.repository_error can break modules.carts.core.domain.repositories.cart_repository, while a change to modules.carts.core.domain.repositories.cart_repository can't break shared-kernel.domain.exceptions.repository_error.
- Position
- Below the diagonal: modules.carts.core.domain.repositories.cart_repository uses a module listed above it, which is the healthy direction.
25→10 modules.identity.core.domain.repositories.user_repository uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in modules.identity.core.domain.repositories.user_repository uses a type in shared-kernel.domain.result.
- The types involved
src.modules.identity.core.domain.repositories.user_repository.UserRepository→src.shared-kernel.domain.result.Result
- Direction
- modules.identity.core.domain.repositories.user_repository uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break modules.identity.core.domain.repositories.user_repository, while a change to modules.identity.core.domain.repositories.user_repository can't break shared-kernel.domain.result.
- Position
- Below the diagonal: modules.identity.core.domain.repositories.user_repository uses a module listed above it, which is the healthy direction.
25→17 modules.identity.core.domain.repositories.user_repository uses shared-kernel.domain.exceptions.repository_error✕
- Connections
- 1 pair of types, where a type in modules.identity.core.domain.repositories.user_repository uses a type in shared-kernel.domain.exceptions.repository_error.
- The types involved
src.modules.identity.core.domain.repositories.user_repository.UserRepository→src.shared-kernel.domain.exceptions.repository_error.RepositoryError
- Direction
- modules.identity.core.domain.repositories.user_repository uses shared-kernel.domain.exceptions.repository_error, so a change to shared-kernel.domain.exceptions.repository_error can break modules.identity.core.domain.repositories.user_repository, while a change to modules.identity.core.domain.repositories.user_repository can't break shared-kernel.domain.exceptions.repository_error.
- Position
- Below the diagonal: modules.identity.core.domain.repositories.user_repository uses a module listed above it, which is the healthy direction.
26→10 modules.inventory.core.domain.repositories.inventory_repository uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in modules.inventory.core.domain.repositories.inventory_repository uses a type in shared-kernel.domain.result.
- The types involved
src.modules.inventory.core.domain.repositories.inventory_repository.InventoryRepository→src.shared-kernel.domain.result.Result
- Direction
- modules.inventory.core.domain.repositories.inventory_repository uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break modules.inventory.core.domain.repositories.inventory_repository, while a change to modules.inventory.core.domain.repositories.inventory_repository can't break shared-kernel.domain.result.
- Position
- Below the diagonal: modules.inventory.core.domain.repositories.inventory_repository uses a module listed above it, which is the healthy direction.
26→17 modules.inventory.core.domain.repositories.inventory_repository uses shared-kernel.domain.exceptions.repository_error✕
- Connections
- 1 pair of types, where a type in modules.inventory.core.domain.repositories.inventory_repository uses a type in shared-kernel.domain.exceptions.repository_error.
- The types involved
src.modules.inventory.core.domain.repositories.inventory_repository.InventoryRepository→src.shared-kernel.domain.exceptions.repository_error.RepositoryError
- Direction
- modules.inventory.core.domain.repositories.inventory_repository uses shared-kernel.domain.exceptions.repository_error, so a change to shared-kernel.domain.exceptions.repository_error can break modules.inventory.core.domain.repositories.inventory_repository, while a change to modules.inventory.core.domain.repositories.inventory_repository can't break shared-kernel.domain.exceptions.repository_error.
- Position
- Below the diagonal: modules.inventory.core.domain.repositories.inventory_repository uses a module listed above it, which is the healthy direction.
27→10 modules.orders.core.domain.schedulers.order_scheduler uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in modules.orders.core.domain.schedulers.order_scheduler uses a type in shared-kernel.domain.result.
- The types involved
src.modules.orders.core.domain.schedulers.order_scheduler.OrderScheduler→src.shared-kernel.domain.result.Result
- Direction
- modules.orders.core.domain.schedulers.order_scheduler uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break modules.orders.core.domain.schedulers.order_scheduler, while a change to modules.orders.core.domain.schedulers.order_scheduler can't break shared-kernel.domain.result.
- Position
- Below the diagonal: modules.orders.core.domain.schedulers.order_scheduler uses a module listed above it, which is the healthy direction.
27→15 modules.orders.core.domain.schedulers.order_scheduler uses shared-kernel.domain.exceptions.infrastructure-error✕
- Connections
- 1 pair of types, where a type in modules.orders.core.domain.schedulers.order_scheduler uses a type in shared-kernel.domain.exceptions.infrastructure-error.
- The types involved
src.modules.orders.core.domain.schedulers.order_scheduler.OrderScheduler→src.shared-kernel.domain.exceptions.infrastructure-error.InfrastructureError
- Direction
- modules.orders.core.domain.schedulers.order_scheduler uses shared-kernel.domain.exceptions.infrastructure-error, so a change to shared-kernel.domain.exceptions.infrastructure-error can break modules.orders.core.domain.schedulers.order_scheduler, while a change to modules.orders.core.domain.schedulers.order_scheduler can't break shared-kernel.domain.exceptions.infrastructure-error.
- Position
- Below the diagonal: modules.orders.core.domain.schedulers.order_scheduler uses a module listed above it, which is the healthy direction.
28→10 modules.products.core.domain.repositories.category-repository uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in modules.products.core.domain.repositories.category-repository uses a type in shared-kernel.domain.result.
- The types involved
src.modules.products.core.domain.repositories.category-repository.CategoryRepository→src.shared-kernel.domain.result.Result
- Direction
- modules.products.core.domain.repositories.category-repository uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break modules.products.core.domain.repositories.category-repository, while a change to modules.products.core.domain.repositories.category-repository can't break shared-kernel.domain.result.
- Position
- Below the diagonal: modules.products.core.domain.repositories.category-repository uses a module listed above it, which is the healthy direction.
28→17 modules.products.core.domain.repositories.category-repository uses shared-kernel.domain.exceptions.repository_error✕
- Connections
- 1 pair of types, where a type in modules.products.core.domain.repositories.category-repository uses a type in shared-kernel.domain.exceptions.repository_error.
- The types involved
src.modules.products.core.domain.repositories.category-repository.CategoryRepository→src.shared-kernel.domain.exceptions.repository_error.RepositoryError
- Direction
- modules.products.core.domain.repositories.category-repository uses shared-kernel.domain.exceptions.repository_error, so a change to shared-kernel.domain.exceptions.repository_error can break modules.products.core.domain.repositories.category-repository, while a change to modules.products.core.domain.repositories.category-repository can't break shared-kernel.domain.exceptions.repository_error.
- Position
- Below the diagonal: modules.products.core.domain.repositories.category-repository uses a module listed above it, which is the healthy direction.
29→10 shared-kernel.domain.value-objects.money uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in shared-kernel.domain.value-objects.money uses a type in shared-kernel.domain.result.
- The types involved
src.shared-kernel.domain.value-objects.money.Money→src.shared-kernel.domain.result.Result
- Direction
- shared-kernel.domain.value-objects.money uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break shared-kernel.domain.value-objects.money, while a change to shared-kernel.domain.value-objects.money can't break shared-kernel.domain.result.
- Position
- Below the diagonal: shared-kernel.domain.value-objects.money uses a module listed above it, which is the healthy direction.
29→14 shared-kernel.domain.value-objects.money uses shared-kernel.domain.exceptions.domain_error✕
- Connections
- 1 pair of types, where a type in shared-kernel.domain.value-objects.money uses a type in shared-kernel.domain.exceptions.domain_error.
- The types involved
src.shared-kernel.domain.value-objects.money.Money→src.shared-kernel.domain.exceptions.domain_error.DomainError
- Direction
- shared-kernel.domain.value-objects.money uses shared-kernel.domain.exceptions.domain_error, so a change to shared-kernel.domain.exceptions.domain_error can break shared-kernel.domain.value-objects.money, while a change to shared-kernel.domain.value-objects.money can't break shared-kernel.domain.exceptions.domain_error.
- Position
- Below the diagonal: shared-kernel.domain.value-objects.money uses a module listed above it, which is the healthy direction.
30→1 modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter uses config.env-config_service✕
- Connections
- 1 pair of types, where a type in modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter uses a type in config.env-config_service.
- The types involved
src.modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter.PostgresAnalyticsQueryAdapter→src.config.env-config_service.EnvConfigService
- Direction
- modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter uses config.env-config_service, so a change to config.env-config_service can break modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter, while a change to modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter can't break config.env-config_service.
- Position
- Below the diagonal: modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter uses a module listed above it, which is the healthy direction.
30→10 modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter uses a type in shared-kernel.domain.result.
- The types involved
src.modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter.PostgresAnalyticsQueryAdapter→src.shared-kernel.domain.result.Result
- Direction
- modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter, while a change to modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter can't break shared-kernel.domain.result.
- Position
- Below the diagonal: modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter uses a module listed above it, which is the healthy direction.
30→16 modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter uses shared-kernel.domain.exceptions.query_error✕
- Connections
- 1 pair of types, where a type in modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter uses a type in shared-kernel.domain.exceptions.query_error.
- The types involved
src.modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter.PostgresAnalyticsQueryAdapter→src.shared-kernel.domain.exceptions.query_error.QueryError
- Direction
- modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter uses shared-kernel.domain.exceptions.query_error, so a change to shared-kernel.domain.exceptions.query_error can break modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter, while a change to modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter can't break shared-kernel.domain.exceptions.query_error.
- Position
- Below the diagonal: modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter uses a module listed above it, which is the healthy direction.
30→20 modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter uses modules.analytics.core.application.ports.analytics-query_service✕
- Connections
- 1 pair of types, where a type in modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter uses a type in modules.analytics.core.application.ports.analytics-query_service.
- The types involved
src.modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter.PostgresAnalyticsQueryAdapter→src.modules.analytics.core.application.ports.analytics-query_service.AnalyticsQueryService
- Direction
- modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter uses modules.analytics.core.application.ports.analytics-query_service, so a change to modules.analytics.core.application.ports.analytics-query_service can break modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter, while a change to modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter can't break modules.analytics.core.application.ports.analytics-query_service.
- Position
- Below the diagonal: modules.analytics.secondary-adapters.query.postgres-analytics-query_adapter uses a module listed above it, which is the healthy direction.
31→10 modules.authentication.core.application.usecases.change-password.change-password_usecase uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in modules.authentication.core.application.usecases.change-password.change-password_usecase uses a type in shared-kernel.domain.result.
- The types involved
src.modules.authentication.core.application.usecases.change-password.change-password_usecase.ChangePasswordUseCase→src.shared-kernel.domain.result.Result
- Direction
- modules.authentication.core.application.usecases.change-password.change-password_usecase uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break modules.authentication.core.application.usecases.change-password.change-password_usecase, while a change to modules.authentication.core.application.usecases.change-password.change-password_usecase can't break shared-kernel.domain.result.
- Position
- Below the diagonal: modules.authentication.core.application.usecases.change-password.change-password_usecase uses a module listed above it, which is the healthy direction.
31→18 modules.authentication.core.application.usecases.change-password.change-password_usecase uses shared-kernel.domain.exceptions.usecase_error✕
- Connections
- 1 pair of types, where a type in modules.authentication.core.application.usecases.change-password.change-password_usecase uses a type in shared-kernel.domain.exceptions.usecase_error.
- The types involved
src.modules.authentication.core.application.usecases.change-password.change-password_usecase.ChangePasswordUseCase→src.shared-kernel.domain.exceptions.usecase_error.UseCaseError
- Direction
- modules.authentication.core.application.usecases.change-password.change-password_usecase uses shared-kernel.domain.exceptions.usecase_error, so a change to shared-kernel.domain.exceptions.usecase_error can break modules.authentication.core.application.usecases.change-password.change-password_usecase, while a change to modules.authentication.core.application.usecases.change-password.change-password_usecase can't break shared-kernel.domain.exceptions.usecase_error.
- Position
- Below the diagonal: modules.authentication.core.application.usecases.change-password.change-password_usecase uses a module listed above it, which is the healthy direction.
31→19 modules.authentication.core.application.usecases.change-password.change-password_usecase uses shared-kernel.domain.interfaces.base_usecase✕
- Connections
- 1 pair of types, where a type in modules.authentication.core.application.usecases.change-password.change-password_usecase uses a type in shared-kernel.domain.interfaces.base_usecase.
- The types involved
src.modules.authentication.core.application.usecases.change-password.change-password_usecase.ChangePasswordUseCase→src.shared-kernel.domain.interfaces.base_usecase.UseCase
- Direction
- modules.authentication.core.application.usecases.change-password.change-password_usecase uses shared-kernel.domain.interfaces.base_usecase, so a change to shared-kernel.domain.interfaces.base_usecase can break modules.authentication.core.application.usecases.change-password.change-password_usecase, while a change to modules.authentication.core.application.usecases.change-password.change-password_usecase can't break shared-kernel.domain.interfaces.base_usecase.
- Position
- Below the diagonal: modules.authentication.core.application.usecases.change-password.change-password_usecase uses a module listed above it, which is the healthy direction.
31→21 modules.authentication.core.application.usecases.change-password.change-password_usecase uses modules.authentication.core.application.ports.authorization_gateway✕
- Connections
- 1 pair of types, where a type in modules.authentication.core.application.usecases.change-password.change-password_usecase uses a type in modules.authentication.core.application.ports.authorization_gateway.
- The types involved
src.modules.authentication.core.application.usecases.change-password.change-password_usecase.ChangePasswordUseCase→src.modules.authentication.core.application.ports.authorization_gateway.AuthorizationGateway
- Direction
- modules.authentication.core.application.usecases.change-password.change-password_usecase uses modules.authentication.core.application.ports.authorization_gateway, so a change to modules.authentication.core.application.ports.authorization_gateway can break modules.authentication.core.application.usecases.change-password.change-password_usecase, while a change to modules.authentication.core.application.usecases.change-password.change-password_usecase can't break modules.authentication.core.application.ports.authorization_gateway.
- Position
- Below the diagonal: modules.authentication.core.application.usecases.change-password.change-password_usecase uses a module listed above it, which is the healthy direction.
31→22 modules.authentication.core.application.usecases.change-password.change-password_usecase uses modules.authentication.core.domain.repositories.credential_repository✕
- Connections
- 1 pair of types, where a type in modules.authentication.core.application.usecases.change-password.change-password_usecase uses a type in modules.authentication.core.domain.repositories.credential_repository.
- The types involved
src.modules.authentication.core.application.usecases.change-password.change-password_usecase.ChangePasswordUseCase→src.modules.authentication.core.domain.repositories.credential_repository.CredentialRepository
- Direction
- modules.authentication.core.application.usecases.change-password.change-password_usecase uses modules.authentication.core.domain.repositories.credential_repository, so a change to modules.authentication.core.domain.repositories.credential_repository can break modules.authentication.core.application.usecases.change-password.change-password_usecase, while a change to modules.authentication.core.application.usecases.change-password.change-password_usecase can't break modules.authentication.core.domain.repositories.credential_repository.
- Position
- Below the diagonal: modules.authentication.core.application.usecases.change-password.change-password_usecase uses a module listed above it, which is the healthy direction.
32→10 modules.authentication.core.application.usecases.login-user.login-user_usecase uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in modules.authentication.core.application.usecases.login-user.login-user_usecase uses a type in shared-kernel.domain.result.
- The types involved
src.modules.authentication.core.application.usecases.login-user.login-user_usecase.LoginUserUseCase→src.shared-kernel.domain.result.Result
- Direction
- modules.authentication.core.application.usecases.login-user.login-user_usecase uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break modules.authentication.core.application.usecases.login-user.login-user_usecase, while a change to modules.authentication.core.application.usecases.login-user.login-user_usecase can't break shared-kernel.domain.result.
- Position
- Below the diagonal: modules.authentication.core.application.usecases.login-user.login-user_usecase uses a module listed above it, which is the healthy direction.
32→18 modules.authentication.core.application.usecases.login-user.login-user_usecase uses shared-kernel.domain.exceptions.usecase_error✕
- Connections
- 1 pair of types, where a type in modules.authentication.core.application.usecases.login-user.login-user_usecase uses a type in shared-kernel.domain.exceptions.usecase_error.
- The types involved
src.modules.authentication.core.application.usecases.login-user.login-user_usecase.LoginUserUseCase→src.shared-kernel.domain.exceptions.usecase_error.UseCaseError
- Direction
- modules.authentication.core.application.usecases.login-user.login-user_usecase uses shared-kernel.domain.exceptions.usecase_error, so a change to shared-kernel.domain.exceptions.usecase_error can break modules.authentication.core.application.usecases.login-user.login-user_usecase, while a change to modules.authentication.core.application.usecases.login-user.login-user_usecase can't break shared-kernel.domain.exceptions.usecase_error.
- Position
- Below the diagonal: modules.authentication.core.application.usecases.login-user.login-user_usecase uses a module listed above it, which is the healthy direction.
32→19 modules.authentication.core.application.usecases.login-user.login-user_usecase uses shared-kernel.domain.interfaces.base_usecase✕
- Connections
- 1 pair of types, where a type in modules.authentication.core.application.usecases.login-user.login-user_usecase uses a type in shared-kernel.domain.interfaces.base_usecase.
- The types involved
src.modules.authentication.core.application.usecases.login-user.login-user_usecase.LoginUserUseCase→src.shared-kernel.domain.interfaces.base_usecase.UseCase
- Direction
- modules.authentication.core.application.usecases.login-user.login-user_usecase uses shared-kernel.domain.interfaces.base_usecase, so a change to shared-kernel.domain.interfaces.base_usecase can break modules.authentication.core.application.usecases.login-user.login-user_usecase, while a change to modules.authentication.core.application.usecases.login-user.login-user_usecase can't break shared-kernel.domain.interfaces.base_usecase.
- Position
- Below the diagonal: modules.authentication.core.application.usecases.login-user.login-user_usecase uses a module listed above it, which is the healthy direction.
32→21 modules.authentication.core.application.usecases.login-user.login-user_usecase uses modules.authentication.core.application.ports.authorization_gateway✕
- Connections
- 1 pair of types, where a type in modules.authentication.core.application.usecases.login-user.login-user_usecase uses a type in modules.authentication.core.application.ports.authorization_gateway.
- The types involved
src.modules.authentication.core.application.usecases.login-user.login-user_usecase.LoginUserUseCase→src.modules.authentication.core.application.ports.authorization_gateway.AuthorizationGateway
- Direction
- modules.authentication.core.application.usecases.login-user.login-user_usecase uses modules.authentication.core.application.ports.authorization_gateway, so a change to modules.authentication.core.application.ports.authorization_gateway can break modules.authentication.core.application.usecases.login-user.login-user_usecase, while a change to modules.authentication.core.application.usecases.login-user.login-user_usecase can't break modules.authentication.core.application.ports.authorization_gateway.
- Position
- Below the diagonal: modules.authentication.core.application.usecases.login-user.login-user_usecase uses a module listed above it, which is the healthy direction.
32→22 modules.authentication.core.application.usecases.login-user.login-user_usecase uses modules.authentication.core.domain.repositories.credential_repository✕
- Connections
- 1 pair of types, where a type in modules.authentication.core.application.usecases.login-user.login-user_usecase uses a type in modules.authentication.core.domain.repositories.credential_repository.
- The types involved
src.modules.authentication.core.application.usecases.login-user.login-user_usecase.LoginUserUseCase→src.modules.authentication.core.domain.repositories.credential_repository.CredentialRepository
- Direction
- modules.authentication.core.application.usecases.login-user.login-user_usecase uses modules.authentication.core.domain.repositories.credential_repository, so a change to modules.authentication.core.domain.repositories.credential_repository can break modules.authentication.core.application.usecases.login-user.login-user_usecase, while a change to modules.authentication.core.application.usecases.login-user.login-user_usecase can't break modules.authentication.core.domain.repositories.credential_repository.
- Position
- Below the diagonal: modules.authentication.core.application.usecases.login-user.login-user_usecase uses a module listed above it, which is the healthy direction.
33→10 modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase uses a type in shared-kernel.domain.result.
- The types involved
src.modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase.RefreshTokenUseCase→src.shared-kernel.domain.result.Result
- Direction
- modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase, while a change to modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase can't break shared-kernel.domain.result.
- Position
- Below the diagonal: modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase uses a module listed above it, which is the healthy direction.
33→18 modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase uses shared-kernel.domain.exceptions.usecase_error✕
- Connections
- 1 pair of types, where a type in modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase uses a type in shared-kernel.domain.exceptions.usecase_error.
- The types involved
src.modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase.RefreshTokenUseCase→src.shared-kernel.domain.exceptions.usecase_error.UseCaseError
- Direction
- modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase uses shared-kernel.domain.exceptions.usecase_error, so a change to shared-kernel.domain.exceptions.usecase_error can break modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase, while a change to modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase can't break shared-kernel.domain.exceptions.usecase_error.
- Position
- Below the diagonal: modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase uses a module listed above it, which is the healthy direction.
33→19 modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase uses shared-kernel.domain.interfaces.base_usecase✕
- Connections
- 1 pair of types, where a type in modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase uses a type in shared-kernel.domain.interfaces.base_usecase.
- The types involved
src.modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase.RefreshTokenUseCase→src.shared-kernel.domain.interfaces.base_usecase.UseCase
- Direction
- modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase uses shared-kernel.domain.interfaces.base_usecase, so a change to shared-kernel.domain.interfaces.base_usecase can break modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase, while a change to modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase can't break shared-kernel.domain.interfaces.base_usecase.
- Position
- Below the diagonal: modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase uses a module listed above it, which is the healthy direction.
33→21 modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase uses modules.authentication.core.application.ports.authorization_gateway✕
- Connections
- 1 pair of types, where a type in modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase uses a type in modules.authentication.core.application.ports.authorization_gateway.
- The types involved
src.modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase.RefreshTokenUseCase→src.modules.authentication.core.application.ports.authorization_gateway.AuthorizationGateway
- Direction
- modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase uses modules.authentication.core.application.ports.authorization_gateway, so a change to modules.authentication.core.application.ports.authorization_gateway can break modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase, while a change to modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase can't break modules.authentication.core.application.ports.authorization_gateway.
- Position
- Below the diagonal: modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase uses a module listed above it, which is the healthy direction.
33→22 modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase uses modules.authentication.core.domain.repositories.credential_repository✕
- Connections
- 1 pair of types, where a type in modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase uses a type in modules.authentication.core.domain.repositories.credential_repository.
- The types involved
src.modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase.RefreshTokenUseCase→src.modules.authentication.core.domain.repositories.credential_repository.CredentialRepository
- Direction
- modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase uses modules.authentication.core.domain.repositories.credential_repository, so a change to modules.authentication.core.domain.repositories.credential_repository can break modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase, while a change to modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase can't break modules.authentication.core.domain.repositories.credential_repository.
- Position
- Below the diagonal: modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase uses a module listed above it, which is the healthy direction.
34→4 modules.orders.core.domain.entities.order uses modules.orders.core.domain.value-objects.order-status_enum✕
- Connections
- 1 pair of types, where a type in modules.orders.core.domain.entities.order uses a type in modules.orders.core.domain.value-objects.order-status_enum.
- The types involved
src.modules.orders.core.domain.entities.order.Order→src.modules.orders.core.domain.value-objects.order-status_enum.OrderStatus
- Direction
- modules.orders.core.domain.entities.order uses modules.orders.core.domain.value-objects.order-status_enum, so a change to modules.orders.core.domain.value-objects.order-status_enum can break modules.orders.core.domain.entities.order, while a change to modules.orders.core.domain.entities.order can't break modules.orders.core.domain.value-objects.order-status_enum.
- Position
- Below the diagonal: modules.orders.core.domain.entities.order uses a module listed above it, which is the healthy direction.
34→10 modules.orders.core.domain.entities.order uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in modules.orders.core.domain.entities.order uses a type in shared-kernel.domain.result.
- The types involved
src.modules.orders.core.domain.entities.order.Order→src.shared-kernel.domain.result.Result
- Direction
- modules.orders.core.domain.entities.order uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break modules.orders.core.domain.entities.order, while a change to modules.orders.core.domain.entities.order can't break shared-kernel.domain.result.
- Position
- Below the diagonal: modules.orders.core.domain.entities.order uses a module listed above it, which is the healthy direction.
34→11 modules.orders.core.domain.entities.order uses shared-kernel.domain.value-objects.payment-method✕
- Connections
- 2 pairs of types, where a type in modules.orders.core.domain.entities.order uses a type in shared-kernel.domain.value-objects.payment-method.
- The types involved
src.modules.orders.core.domain.entities.order.Order→src.shared-kernel.domain.value-objects.payment-method.PaymentMethodTypesrc.modules.orders.core.domain.entities.order.OrderProps→src.shared-kernel.domain.value-objects.payment-method.PaymentMethodType
- Direction
- modules.orders.core.domain.entities.order uses shared-kernel.domain.value-objects.payment-method, so a change to shared-kernel.domain.value-objects.payment-method can break modules.orders.core.domain.entities.order, while a change to modules.orders.core.domain.entities.order can't break shared-kernel.domain.value-objects.payment-method.
- Position
- Below the diagonal: modules.orders.core.domain.entities.order uses a module listed above it, which is the healthy direction.
34→14 modules.orders.core.domain.entities.order uses shared-kernel.domain.exceptions.domain_error✕
- Connections
- 1 pair of types, where a type in modules.orders.core.domain.entities.order uses a type in shared-kernel.domain.exceptions.domain_error.
- The types involved
src.modules.orders.core.domain.entities.order.Order→src.shared-kernel.domain.exceptions.domain_error.DomainError
- Direction
- modules.orders.core.domain.entities.order uses shared-kernel.domain.exceptions.domain_error, so a change to shared-kernel.domain.exceptions.domain_error can break modules.orders.core.domain.entities.order, while a change to modules.orders.core.domain.entities.order can't break shared-kernel.domain.exceptions.domain_error.
- Position
- Below the diagonal: modules.orders.core.domain.entities.order uses a module listed above it, which is the healthy direction.
34→29 modules.orders.core.domain.entities.order uses shared-kernel.domain.value-objects.money✕
- Connections
- 1 pair of types, where a type in modules.orders.core.domain.entities.order uses a type in shared-kernel.domain.value-objects.money.
- The types involved
src.modules.orders.core.domain.entities.order.Order→src.shared-kernel.domain.value-objects.money.Money
- Direction
- modules.orders.core.domain.entities.order uses shared-kernel.domain.value-objects.money, so a change to shared-kernel.domain.value-objects.money can break modules.orders.core.domain.entities.order, while a change to modules.orders.core.domain.entities.order can't break shared-kernel.domain.value-objects.money.
- Position
- Below the diagonal: modules.orders.core.domain.entities.order uses a module listed above it, which is the healthy direction.
35→10 modules.payments.core.domain.entities.payment uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in modules.payments.core.domain.entities.payment uses a type in shared-kernel.domain.result.
- The types involved
src.modules.payments.core.domain.entities.payment.Payment→src.shared-kernel.domain.result.Result
- Direction
- modules.payments.core.domain.entities.payment uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break modules.payments.core.domain.entities.payment, while a change to modules.payments.core.domain.entities.payment can't break shared-kernel.domain.result.
- Position
- Below the diagonal: modules.payments.core.domain.entities.payment uses a module listed above it, which is the healthy direction.
35→11 modules.payments.core.domain.entities.payment uses shared-kernel.domain.value-objects.payment-method✕
- Connections
- 4 pairs of types, where a type in modules.payments.core.domain.entities.payment uses a type in shared-kernel.domain.value-objects.payment-method.
- The types involved
src.modules.payments.core.domain.entities.payment.CreatePaymentProps→src.shared-kernel.domain.value-objects.payment-method.PaymentMethodTypesrc.modules.payments.core.domain.entities.payment.Payment→src.shared-kernel.domain.value-objects.payment-method.PaymentMethodsrc.modules.payments.core.domain.entities.payment.Payment→src.shared-kernel.domain.value-objects.payment-method.PaymentMethodTypesrc.modules.payments.core.domain.entities.payment.PaymentProps→src.shared-kernel.domain.value-objects.payment-method.PaymentMethodType
- Direction
- modules.payments.core.domain.entities.payment uses shared-kernel.domain.value-objects.payment-method, so a change to shared-kernel.domain.value-objects.payment-method can break modules.payments.core.domain.entities.payment, while a change to modules.payments.core.domain.entities.payment can't break shared-kernel.domain.value-objects.payment-method.
- Position
- Below the diagonal: modules.payments.core.domain.entities.payment uses a module listed above it, which is the healthy direction.
35→14 modules.payments.core.domain.entities.payment uses shared-kernel.domain.exceptions.domain_error✕
- Connections
- 1 pair of types, where a type in modules.payments.core.domain.entities.payment uses a type in shared-kernel.domain.exceptions.domain_error.
- The types involved
src.modules.payments.core.domain.entities.payment.Payment→src.shared-kernel.domain.exceptions.domain_error.DomainError
- Direction
- modules.payments.core.domain.entities.payment uses shared-kernel.domain.exceptions.domain_error, so a change to shared-kernel.domain.exceptions.domain_error can break modules.payments.core.domain.entities.payment, while a change to modules.payments.core.domain.entities.payment can't break shared-kernel.domain.exceptions.domain_error.
- Position
- Below the diagonal: modules.payments.core.domain.entities.payment uses a module listed above it, which is the healthy direction.
35→29 modules.payments.core.domain.entities.payment uses shared-kernel.domain.value-objects.money✕
- Connections
- 1 pair of types, where a type in modules.payments.core.domain.entities.payment uses a type in shared-kernel.domain.value-objects.money.
- The types involved
src.modules.payments.core.domain.entities.payment.Payment→src.shared-kernel.domain.value-objects.money.Money
- Direction
- modules.payments.core.domain.entities.payment uses shared-kernel.domain.value-objects.money, so a change to shared-kernel.domain.value-objects.money can break modules.payments.core.domain.entities.payment, while a change to modules.payments.core.domain.entities.payment can't break shared-kernel.domain.value-objects.money.
- Position
- Below the diagonal: modules.payments.core.domain.entities.payment uses a module listed above it, which is the healthy direction.
36→31 modules.authentication.authentication_controller uses modules.authentication.core.application.usecases.change-password.change-password_usecase✕
- Connections
- 1 pair of types, where a type in modules.authentication.authentication_controller uses a type in modules.authentication.core.application.usecases.change-password.change-password_usecase.
- The types involved
src.modules.authentication.authentication_controller.AuthenticationController→src.modules.authentication.core.application.usecases.change-password.change-password_usecase.ChangePasswordUseCase
- Direction
- modules.authentication.authentication_controller uses modules.authentication.core.application.usecases.change-password.change-password_usecase, so a change to modules.authentication.core.application.usecases.change-password.change-password_usecase can break modules.authentication.authentication_controller, while a change to modules.authentication.authentication_controller can't break modules.authentication.core.application.usecases.change-password.change-password_usecase.
- Position
- Below the diagonal: modules.authentication.authentication_controller uses a module listed above it, which is the healthy direction.
36→32 modules.authentication.authentication_controller uses modules.authentication.core.application.usecases.login-user.login-user_usecase✕
- Connections
- 1 pair of types, where a type in modules.authentication.authentication_controller uses a type in modules.authentication.core.application.usecases.login-user.login-user_usecase.
- The types involved
src.modules.authentication.authentication_controller.AuthenticationController→src.modules.authentication.core.application.usecases.login-user.login-user_usecase.LoginUserUseCase
- Direction
- modules.authentication.authentication_controller uses modules.authentication.core.application.usecases.login-user.login-user_usecase, so a change to modules.authentication.core.application.usecases.login-user.login-user_usecase can break modules.authentication.authentication_controller, while a change to modules.authentication.authentication_controller can't break modules.authentication.core.application.usecases.login-user.login-user_usecase.
- Position
- Below the diagonal: modules.authentication.authentication_controller uses a module listed above it, which is the healthy direction.
36→33 modules.authentication.authentication_controller uses modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase✕
- Connections
- 1 pair of types, where a type in modules.authentication.authentication_controller uses a type in modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase.
- The types involved
src.modules.authentication.authentication_controller.AuthenticationController→src.modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase.RefreshTokenUseCase
- Direction
- modules.authentication.authentication_controller uses modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase, so a change to modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase can break modules.authentication.authentication_controller, while a change to modules.authentication.authentication_controller can't break modules.authentication.core.application.usecases.refresh-token.refresh-token_usecase.
- Position
- Below the diagonal: modules.authentication.authentication_controller uses a module listed above it, which is the healthy direction.
37→4 modules.orders.core.domain.repositories.order-repository uses modules.orders.core.domain.value-objects.order-status_enum✕
- Connections
- 2 pairs of types, where a type in modules.orders.core.domain.repositories.order-repository uses a type in modules.orders.core.domain.value-objects.order-status_enum.
- The types involved
src.modules.orders.core.domain.repositories.order-repository.ListOrdersQuery→src.modules.orders.core.domain.value-objects.order-status_enum.OrderStatussrc.modules.orders.core.domain.repositories.order-repository.OrderRepository→src.modules.orders.core.domain.value-objects.order-status_enum.OrderStatus
- Direction
- modules.orders.core.domain.repositories.order-repository uses modules.orders.core.domain.value-objects.order-status_enum, so a change to modules.orders.core.domain.value-objects.order-status_enum can break modules.orders.core.domain.repositories.order-repository, while a change to modules.orders.core.domain.repositories.order-repository can't break modules.orders.core.domain.value-objects.order-status_enum.
- Position
- Below the diagonal: modules.orders.core.domain.repositories.order-repository uses a module listed above it, which is the healthy direction.
37→10 modules.orders.core.domain.repositories.order-repository uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in modules.orders.core.domain.repositories.order-repository uses a type in shared-kernel.domain.result.
- The types involved
src.modules.orders.core.domain.repositories.order-repository.OrderRepository→src.shared-kernel.domain.result.Result
- Direction
- modules.orders.core.domain.repositories.order-repository uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break modules.orders.core.domain.repositories.order-repository, while a change to modules.orders.core.domain.repositories.order-repository can't break shared-kernel.domain.result.
- Position
- Below the diagonal: modules.orders.core.domain.repositories.order-repository uses a module listed above it, which is the healthy direction.
37→17 modules.orders.core.domain.repositories.order-repository uses shared-kernel.domain.exceptions.repository_error✕
- Connections
- 1 pair of types, where a type in modules.orders.core.domain.repositories.order-repository uses a type in shared-kernel.domain.exceptions.repository_error.
- The types involved
src.modules.orders.core.domain.repositories.order-repository.OrderRepository→src.shared-kernel.domain.exceptions.repository_error.RepositoryError
- Direction
- modules.orders.core.domain.repositories.order-repository uses shared-kernel.domain.exceptions.repository_error, so a change to shared-kernel.domain.exceptions.repository_error can break modules.orders.core.domain.repositories.order-repository, while a change to modules.orders.core.domain.repositories.order-repository can't break shared-kernel.domain.exceptions.repository_error.
- Position
- Below the diagonal: modules.orders.core.domain.repositories.order-repository uses a module listed above it, which is the healthy direction.
37→34 modules.orders.core.domain.repositories.order-repository uses modules.orders.core.domain.entities.order✕
- Connections
- 1 pair of types, where a type in modules.orders.core.domain.repositories.order-repository uses a type in modules.orders.core.domain.entities.order.
- The types involved
src.modules.orders.core.domain.repositories.order-repository.OrderRepository→src.modules.orders.core.domain.entities.order.Order
- Direction
- modules.orders.core.domain.repositories.order-repository uses modules.orders.core.domain.entities.order, so a change to modules.orders.core.domain.entities.order can break modules.orders.core.domain.repositories.order-repository, while a change to modules.orders.core.domain.repositories.order-repository can't break modules.orders.core.domain.entities.order.
- Position
- Below the diagonal: modules.orders.core.domain.repositories.order-repository uses a module listed above it, which is the healthy direction.
38→10 modules.payments.core.domain.repositories.payment_repository uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in modules.payments.core.domain.repositories.payment_repository uses a type in shared-kernel.domain.result.
- The types involved
src.modules.payments.core.domain.repositories.payment_repository.PaymentRepository→src.shared-kernel.domain.result.Result
- Direction
- modules.payments.core.domain.repositories.payment_repository uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break modules.payments.core.domain.repositories.payment_repository, while a change to modules.payments.core.domain.repositories.payment_repository can't break shared-kernel.domain.result.
- Position
- Below the diagonal: modules.payments.core.domain.repositories.payment_repository uses a module listed above it, which is the healthy direction.
38→17 modules.payments.core.domain.repositories.payment_repository uses shared-kernel.domain.exceptions.repository_error✕
- Connections
- 1 pair of types, where a type in modules.payments.core.domain.repositories.payment_repository uses a type in shared-kernel.domain.exceptions.repository_error.
- The types involved
src.modules.payments.core.domain.repositories.payment_repository.PaymentRepository→src.shared-kernel.domain.exceptions.repository_error.RepositoryError
- Direction
- modules.payments.core.domain.repositories.payment_repository uses shared-kernel.domain.exceptions.repository_error, so a change to shared-kernel.domain.exceptions.repository_error can break modules.payments.core.domain.repositories.payment_repository, while a change to modules.payments.core.domain.repositories.payment_repository can't break shared-kernel.domain.exceptions.repository_error.
- Position
- Below the diagonal: modules.payments.core.domain.repositories.payment_repository uses a module listed above it, which is the healthy direction.
38→35 modules.payments.core.domain.repositories.payment_repository uses modules.payments.core.domain.entities.payment✕
- Connections
- 1 pair of types, where a type in modules.payments.core.domain.repositories.payment_repository uses a type in modules.payments.core.domain.entities.payment.
- The types involved
src.modules.payments.core.domain.repositories.payment_repository.PaymentRepository→src.modules.payments.core.domain.entities.payment.Payment
- Direction
- modules.payments.core.domain.repositories.payment_repository uses modules.payments.core.domain.entities.payment, so a change to modules.payments.core.domain.entities.payment can break modules.payments.core.domain.repositories.payment_repository, while a change to modules.payments.core.domain.repositories.payment_repository can't break modules.payments.core.domain.entities.payment.
- Position
- Below the diagonal: modules.payments.core.domain.repositories.payment_repository uses a module listed above it, which is the healthy direction.
39→10 modules.orders.core.application.usecases.cancel-order.cancel-order_usecase uses shared-kernel.domain.result✕
- Connections
- 1 pair of types, where a type in modules.orders.core.application.usecases.cancel-order.cancel-order_usecase uses a type in shared-kernel.domain.result.
- The types involved
src.modules.orders.core.application.usecases.cancel-order.cancel-order_usecase.CancelOrderUseCase→src.shared-kernel.domain.result.Result
- Direction
- modules.orders.core.application.usecases.cancel-order.cancel-order_usecase uses shared-kernel.domain.result, so a change to shared-kernel.domain.result can break modules.orders.core.application.usecases.cancel-order.cancel-order_usecase, while a change to modules.orders.core.application.usecases.cancel-order.cancel-order_usecase can't break shared-kernel.domain.result.
- Position
- Below the diagonal: modules.orders.core.application.usecases.cancel-order.cancel-order_usecase uses a module listed above it, which is the healthy direction.
39→19 modules.orders.core.application.usecases.cancel-order.cancel-order_usecase uses shared-kernel.domain.interfaces.base_usecase✕
- Connections
- 1 pair of types, where a type in modules.orders.core.application.usecases.cancel-order.cancel-order_usecase uses a type in shared-kernel.domain.interfaces.base_usecase.
- The types involved
src.modules.orders.core.application.usecases.cancel-order.cancel-order_usecase.CancelOrderUseCase→src.shared-kernel.domain.interfaces.base_usecase.UseCase
- Direction
- modules.orders.core.application.usecases.cancel-order.cancel-order_usecase uses shared-kernel.domain.interfaces.base_usecase, so a change to shared-kernel.domain.interfaces.base_usecase can break modules.orders.core.application.usecases.cancel-order.cancel-order_usecase, while a change to modules.orders.core.application.usecases.cancel-order.cancel-order_usecase can't break shared-kernel.domain.interfaces.base_usecase.
- Position
- Below the diagonal: modules.orders.core.application.usecases.cancel-order.cancel-order_usecase uses a module listed above it, which is the healthy direction.
39→27 modules.orders.core.application.usecases.cancel-order.cancel-order_usecase uses modules.orders.core.domain.schedulers.order_scheduler✕
- Connections
- 1 pair of types, where a type in modules.orders.core.application.usecases.cancel-order.cancel-order_usecase uses a type in modules.orders.core.domain.schedulers.order_scheduler.
- The types involved
src.modules.orders.core.application.usecases.cancel-order.cancel-order_usecase.CancelOrderUseCase→src.modules.orders.core.domain.schedulers.order_scheduler.OrderScheduler
- Direction
- modules.orders.core.application.usecases.cancel-order.cancel-order_usecase uses modules.orders.core.domain.schedulers.order_scheduler, so a change to modules.orders.core.domain.schedulers.order_scheduler can break modules.orders.core.application.usecases.cancel-order.cancel-order_usecase, while a change to modules.orders.core.application.usecases.cancel-order.cancel-order_usecase can't break modules.orders.core.domain.schedulers.order_scheduler.
- Position
- Below the diagonal: modules.orders.core.application.usecases.cancel-order.cancel-order_usecase uses a module listed above it, which is the healthy direction.
39→37 modules.orders.core.application.usecases.cancel-order.cancel-order_usecase uses modules.orders.core.domain.repositories.order-repository✕
- Connections
- 1 pair of types, where a type in modules.orders.core.application.usecases.cancel-order.cancel-order_usecase uses a type in modules.orders.core.domain.repositories.order-repository.
- The types involved
src.modules.orders.core.application.usecases.cancel-order.cancel-order_usecase.CancelOrderUseCase→src.modules.orders.core.domain.repositories.order-repository.OrderRepository
- Direction
- modules.orders.core.application.usecases.cancel-order.cancel-order_usecase uses modules.orders.core.domain.repositories.order-repository, so a change to modules.orders.core.domain.repositories.order-repository can break modules.orders.core.application.usecases.cancel-order.cancel-order_usecase, while a change to modules.orders.core.application.usecases.cancel-order.cancel-order_usecase can't break modules.orders.core.domain.repositories.order-repository.
- Position
- Below the diagonal: modules.orders.core.application.usecases.cancel-order.cancel-order_usecase uses a module listed above it, which is the healthy direction.
40→8 modules.orders.orders_controller uses shared-kernel.domain.interfaces.caller-context_interface✕
- Connections
- 1 pair of types, where a type in modules.orders.orders_controller uses a type in shared-kernel.domain.interfaces.caller-context_interface.
- The types involved
src.modules.orders.orders_controller.OrdersController→src.shared-kernel.domain.interfaces.caller-context_interface.CallerContext
- Direction
- modules.orders.orders_controller uses shared-kernel.domain.interfaces.caller-context_interface, so a change to shared-kernel.domain.interfaces.caller-context_interface can break modules.orders.orders_controller, while a change to modules.orders.orders_controller can't break shared-kernel.domain.interfaces.caller-context_interface.
- Position
- Below the diagonal: modules.orders.orders_controller uses a module listed above it, which is the healthy direction.
40→39 modules.orders.orders_controller uses modules.orders.core.application.usecases.cancel-order.cancel-order_usecase✕
- Connections
- 1 pair of types, where a type in modules.orders.orders_controller uses a type in modules.orders.core.application.usecases.cancel-order.cancel-order_usecase.
- The types involved
src.modules.orders.orders_controller.OrdersController→src.modules.orders.core.application.usecases.cancel-order.cancel-order_usecase.CancelOrderUseCase
- Direction
- modules.orders.orders_controller uses modules.orders.core.application.usecases.cancel-order.cancel-order_usecase, so a change to modules.orders.core.application.usecases.cancel-order.cancel-order_usecase can break modules.orders.orders_controller, while a change to modules.orders.orders_controller can't break modules.orders.core.application.usecases.cancel-order.cancel-order_usecase.
- Position
- Below the diagonal: modules.orders.orders_controller uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 52 | High / Critical |
| A07:2025 — Authentication Failures | 12 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | Medium |
| A02:2025 — Security Misconfiguration | 6 | High / Critical |
Roadmap
Top priorities: Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED; 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 `?`); Interpolated log message defeats structured logging.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED. | +2.7 pts | Low | REDACTED Scanning |
| Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (4). | +1.7 pts | Low | Dependency Hygiene |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +1.5 pts | Low | Project Cohesion |
| 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 `?`). | +2.0 pts | Medium | Nullable reference types |
| Interpolated log message defeats structured logging | +1.8 pts | Medium | Structured logging |
| Resolve the 6 Classify ADR enforcement finding(s) in Architectural Integrity — start with ADR-0004-inventory-integrity-and-concurrency.md, ADR-0005-typed-atomic-occ-update-contract.md, ADR-0006-redis-fail-open-cache-aside.md. | +0.9 pts | Low | Architectural Integrity |
| Break each cycle by extracting the shared piece into a module both sides can import. | +1.7 pts | Medium | Circular Imports |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +1.6 pts | Medium | Dependency Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 1.7 | Slop | Secrets (history): High secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 5.7 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/modules/inventory/secondary-adapters/repositories/postgres-inventory-repository/postgres-inventory-repository.spec.ts | 7.0 | Near-clean | Test Quality: No assertions: should return a RepositoryError when not found |
| src/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.spec.ts | 7.0 | Near-clean | Test Quality: No assertions: should save expensive product |
| src/modules/products/secondary-adapters/repositories/postgres-product-repository/postgres.product-repository.spec.ts | 7.0 | Near-clean | Test Quality: No assertions: should return failure when product not found |
| src/modules/carts/secondary-adapters/repositories/postgres-cart-repository/postgres.cart-repository.spec.ts | 7.0 | Near-clean | Test Quality: No assertions: should return error if cart not found |
| src/modules/orders/secondary-adapters/adapters/module-cart.gateway.spec.ts | 7.1 | Near-clean | Test Quality: No assertions: returns infrastructure error when getCartUseCase fails |
| src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.spec.ts | 7.1 | Near-clean | Test Quality: No assertions: should fail if inventory not found |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 86 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 86 dimensions across the health lenses
- 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, 543 of 576 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for the repository root failed in the analyzer sandbox (npm error code EBADDEVENGINES), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo — a coverage step in CI (`vitest run --shard=${{ matrix.shard }} --coverage`) shows coverage is measured in your own CI. Commit the lcov/Cobertura report it produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for the repository root failed in the analyzer sandbox (npm error code EBADDEVENGINES), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in the repository root was NOT MEASURED: the dependency install for the repository root failed in the analyzer sandbox (npm error code EBADDEVENGINES), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- 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 2022 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.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 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.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (docker-compose.prod.yml). compose up failed (exit 15 — the compose project is invalid) — service "prometheus" has neither an image nor a build context specified: invalid compose project; runtime evidence skipped.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 200 further occurrence(s) are not listed individually; the score already reflects all 240.
- R5 Dependency Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm outdated` failed and answered nothing (EBADDEVENGINES: The developer of this package has specified the following through devEngines Invalid engine "runtime" Invalid semver version ">=26.0.0" does not match "v22.13.0" for "runtime"); nothing here is a statement about the repository.
- R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 6 further occurrence(s) are not listed individually; the score already reflects all 46.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 771 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 155 further occurrence(s) are not listed individually; the score already reflects all 195.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
9 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SeedDemoCatalogUseCase.execute at 25.
What to do
- Bring the 9 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with SeedDemoCatalogUseCase.execute (cyclomatic 25), GlobalExceptionFilter.catch (cyclomatic 25), CartQueryMapper.toPresentationDto (cyclomatic 24). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 9 together lifts Cyclomatic Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
16 method(s) exceeded the cognitive complexity threshold of 15; the worst was SeedDemoCatalogUseCase.execute at 36.
What to do
- Bring the 16 bodies over 15 down to 15 or less in Cognitive Complexity — start with SeedDemoCatalogUseCase.execute (cognitive 36), CartQueryMapper.toPresentationDto (cognitive 35), RoleSystemDataInitializer.onApplicationBootstrap (cognitive 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 16 together lifts Cognitive Complexity from 7.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
1 god class(es) detected.
What to do
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with order.ts. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
2 of 160 classes have LCOM4 above 3.
What to do
- 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).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
What to do
- Resolve the 6 Classify ADR enforcement finding(s) in Architectural Integrity — start with ADR-0004-inventory-integrity-and-concurrency.md, ADR-0005-typed-atomic-occ-update-contract.md, ADR-0006-redis-fail-open-cache-aside.md. — One of this dimension's main actionable groups (6 recommendation-level).
- Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D9 · Test Distribution
1986 test methods: 1915 unit, 8 integration, 0 BDD, 63 e2e. The JavaScript/TypeScript suite contributes 1986 `it`/`test` case(s) across 316 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
2 skipped (2 with a documented reason), 189 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1986 tests.
What to do
- Resolve the 189 No assertions finding(s) in Test Quality — start with postgres-inventory-repository.spec.ts (10), cached.product-repository.spec.ts (8), postgres.product-repository.spec.ts (7). — One of this dimension's main actionable groups (189 warning-level).
- 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).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D12 · Dependency Hygiene
22 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.
What to do
- Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (4). — One of this dimension's main actionable groups (4 recommendation-level).
- Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with package.json. — One of this dimension's main actionable groups (1 warning-level).
D13 · REDACTED Scanning
2 secret(s) detected.
What to do
- Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 434 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 434 package(s) this repository's committed lockfile installs for a consumer — its 43 production, optional and peer dependency(ies), across 1 product package.json manifest(s), and everything those install in turn. Its 40 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: scripts/generate-envs.js (15×26=390); src/modules/products/core/application/seed/seed-demo-catalog.usecase.ts (13×25=325); 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)
What to do
- Resolve the 11 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 (11 warning-level).
- 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).
D17 · Explicit Debt
0 deducted task-comment markers across 48079 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 78 document(s) read across 1 unit(s).
D20 · ADR Quality
0 of 6 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D24 · Comment Value
10 of 212 judged comments only repeat the code they sit on (4.7 %). 8 comment(s) in another language or script were not judged.
What to do
- Resolve the 6 redundant comment finding(s) in Comment Value — start with global-exception.filter.spec.ts, identity-access-gateway.mock.ts, cart-gateway.mock.ts. — One of this dimension's main actionable groups (6 recommendation-level).
D26 · Project Cohesion
1 of 1 build units (npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
63 % of calls cross a namespace and 0 % go through an interface, but 78 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
8 finding(s): 0 critical, 8 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 6 High secret finding(s) in Secrets (history) — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
52 finding(s): 0 critical, 2 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 39–158), `src/modules/carts/secondary-adapters/repositories/postgres-cart-repository/postgres.cart-repository.spec.ts` (line 22), `src/modules/identity/secondary-adapters/repositories/postgres-user-repository/postgres-user.repository.spec.ts` (line 22), `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 24), … (+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.
What to do
- 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).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
6 finding(s): 0 critical, 0 high, 5 medium, 1 low.
What to do
- Resolve the 5 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D31 · IaC & Container Security
6 finding(s): 0 critical, 1 high, 5 medium, 0 low.
What to do
- 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).
- Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 216 of the 848 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: cached.product-repository.ts↔postgres.product-repository.ts 55%
What to do
- 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).
D36 · Supply-chain Provenance & Signing
3/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 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.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
C1 · Data Protection
- 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 Controls
C4 · Data Retention
- 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 boundaries
- `Payment` references the aggregate root `Refund` directly (via `_refunds`) — hold its `RefundId` instead. — src/modules/payments/core/domain/entities/payment.ts:64
- `Payment` references the aggregate root `Refund` directly (via `refunds`) — hold its `RefundId` instead. — src/modules/payments/core/domain/entities/payment.ts:388
- `User` references the aggregate root `Address` directly (via `_addresses`) — hold its `AddressId` instead. — src/modules/identity/core/domain/entities/user.ts:28
What to do
- Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
DM10 · One transaction, one aggregate
- `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:42
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 state
DM2 · Strongly-typed ids
- `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:118
- `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 model
- `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
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 state
- `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 boundary
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
M2 · Architecture documentation
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 structure
M4 · Documentation accuracy
- 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
What to do
- Reconcile the README with reality: docs/data/collections/bruno/README.md links to `../../development/SEEDING.md`, but `docs/data/development/SEEDING.md` does not exist.
P1 · CI/CD gates
P2 · Observability
P3 · Security & performance tooling
- 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 41508 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. — .github/workflows/ci.yml:4
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 & Rollback
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene
P8 · Schema migrations
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 204 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) — 90 of them are reported below, and 114 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 204 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 204 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 204 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
- 9 duplicated blocks under src/modules/orders/core/application/usecases/ have copies in at least two of the sibling directories cancel-order, clear-checkout-cart, confirm-checkout-reservation, confirm-order, deliver-order, handle-payment-completed (+4 more sibling(s) not listed) — 5 of them are reported below, and 4 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 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 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/process-order/process-order.usecase.ts:11
- 6 duplicated blocks under src/ have copies in at least two of the sibling directories infrastructure, modules, shared-kernel — 3 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 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 6 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/payments/core/domain/value-objects/payment-status.ts:12
- 6 duplicated blocks under src/modules/authentication/core/application/usecases/ have copies in at least two of the sibling directories change-password, login-user, logout, logout-all, refresh-token, register-user — 3 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 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 6 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/authentication/core/application/usecases/change-password/change-password.usecase.ts:22
- 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 — 567 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/carts/secondary-adapters/repositories/postgres-cart-repository/postgres.cart-repository.ts:97 · src/modules/orders/secondary-adapters/repositories/postgres-order-repository/postgres.order-repository.ts:86 — 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:97
- 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/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:122 · 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 — 387 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:122
- src/modules/products/core/application/usecases/create-product/create-product.usecase.ts:18 · src/modules/products/core/application/usecases/update-product/update-product.usecase.ts:17 — the two spans are one implementation copied and then locally edited — 258 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:18
- src/modules/inventory/secondary-adapters/repositories/postgres-inventory-repository/postgres-inventory-repository.ts:220 · src/modules/products/secondary-adapters/repositories/postgres-product-repository/postgres.product-repository.ts:40 — the two spans are one implementation copied and then locally edited — 265 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:220
- 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/authorization/secondary-adapter/repositories/postgres-role-repository/postgres-role.repository.ts:61 · 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 — 240 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:61
- src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts:22 · src/modules/authentication/core/application/usecases/login-user/login-user.usecase.ts:18 — the two spans are one implementation copied and then locally edited — 192 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:22
- src/modules/identity/core/application/usecases/address/add-address/add-address.usecase.ts:18 · src/modules/identity/core/application/usecases/address/update-address/update-address.usecase.ts:19 — the two spans are one implementation copied and then locally edited — 218 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/application/usecases/address/add-address/add-address.usecase.ts:18
- src/modules/orders/core/application/usecases/list-orders/list-orders.usecase.ts:19 · src/modules/payments/core/application/usecases/list-payments/list-payments.usecase.ts:19 — 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:19
- src/modules/authorization/secondary-adapter/repositories/postgres-role-repository/postgres-role.repository.ts:46 · src/modules/identity/secondary-adapters/repositories/postgres-user-repository/postgres-user.repository.ts:193 — the two spans are one implementation copied and then locally edited — 248 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/modules/authorization/secondary-adapter/repositories/postgres-role-repository/postgres-role.repository.ts:46
- 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/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/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/inventory/secondary-adapters/schedulers/bullmq-inventory.scheduler.ts:29 · src/modules/inventory/secondary-adapters/schedulers/bullmq-inventory.scheduler.ts:73 · src/modules/orders/secondary-adapters/schedulers/bullmq-checkout.scheduler.ts:250 — 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/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
- 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/products/core/application/usecases/categories/activate-category.usecase.ts:13 · src/modules/products/core/application/usecases/categories/deactivate-category.usecase.ts:13 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/modules/products/core/application/usecases/categories/activate-category.usecase.ts:13
- src/modules/inventory/secondary-adapters/repositories/cached-inventory-repository/cached-inventory-repository.ts:30 · src/modules/inventory/secondary-adapters/repositories/cached-inventory-repository/cached-inventory-repository.ts:257 — the two spans are one implementation copied and then locally edited — 163 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/cached-inventory-repository/cached-inventory-repository.ts:30
- src/modules/carts/carts.module.ts:37 · src/modules/orders/orders.module.ts:100 — 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/products/core/application/usecases/activate-product/activate-product.usecase.ts:12 · src/modules/products/core/application/usecases/deactivate-product/deactivate-product.usecase.ts:12 — the two spans are one implementation copied and then locally edited — 185 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:12
- src/modules/orders/primary-adapters/jobs/create-order.job.ts:17 · src/modules/orders/primary-adapters/jobs/process-payment.job.ts:22 — 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/primary-adapters/jobs/create-order.job.ts:17
- src/modules/carts/core/application/usecases/clear-cart/clear-cart.usecase.ts:20 · src/modules/carts/core/application/usecases/remove-cart-item/remove-cart-item.usecase.ts:23 — 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/core/application/usecases/clear-cart/clear-cart.usecase.ts:20
- src/modules/identity/core/application/usecases/address/delete-address/delete-address.usecase.ts:22 · src/modules/identity/core/application/usecases/address/set-default-address/set-default-address.usecase.ts:21 — 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/delete-address/delete-address.usecase.ts:22
- 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:144 — 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/products/core/application/usecases/categories/get-category.usecase.ts:15 · src/modules/products/core/application/usecases/get-product/get-product.usecase.ts:15 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/modules/products/core/application/usecases/categories/get-category.usecase.ts:15
- 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:134 · src/modules/identity/secondary-adapters/repositories/cached-user-repository/cached-user.repository.ts: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. — src/modules/identity/secondary-adapters/repositories/cached-user-repository/cached-user.repository.ts:134
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 Complexity
- (top-level) has cyclomatic complexity 27 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. — src/filters/global-exception.filter.ts:1
- 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
- (top-level) has cyclomatic complexity 25 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. — REDACTED:1
- (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
- 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
- (top-level) 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. — src/modules/orders/core/application/usecases/handle-payment-completed/handle-payment-completed.usecase.ts:1
- 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
- (top-level) has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts:1
- 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:27
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
- src/modules/orders/core/domain/entities/order.ts has 488 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/orders/core/domain/entities/order.ts:1
- src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.ts has 419 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
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- 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. (×28) — 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).
R6 · Tooling
R7 · Dead Code
- Unreachable from the 35 application, 37 tooling and 406 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 (35 application, 37 tooling, 406 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 (35 application, 37 tooling, 406 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 (×17) — 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 (35 application, 37 tooling, 406 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
- Nothing imports this binding — it is safe to review for removal. (×15) — scripts/agent-output.mjs:124, REDACTED: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
- Nothing ultimately consumes this binding: its only referrer is the re-export in src/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/testing/index.ts in the same commit, or the barrel will import a name that no longer exists. — src/testing/helpers/database-test.helper.ts:8
- Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect. — src/modules/carts/secondary-adapters/repositories/cached-cart-repository/cached.cart-repository.ts:20
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 Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×3) — 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 Imports
- 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:24
- 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 correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `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
- `redactInPlace` is exported and takes `target: unknown` from its caller, and it calls itself at line 216 (`redactInPlace`) with a piece of `target` (and at line 230) — and nowhere in `redactInPlace` 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 `redactInPlace` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/infrastructure/logging/winston-logger.service.ts:216
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 correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- 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. (×3) — src/shared-kernel/helpers/lang/app-version.ts:16, src/infrastructure/redis/redis.service.ts:100, src/infrastructure/redis/cache/cache.service.ts:119
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `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
- `log` 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.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. (×2) — src/modules/products/core/application/usecases/deactivate-product/deactivate-product.usecase.ts:49, src/modules/orders/orders.processor.ts:49
- `log` at line 50 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. (×2) — src/modules/products/core/application/usecases/categories/activate-category.usecase.ts:50, src/modules/products/core/application/usecases/categories/deactivate-category.usecase.ts:50
- `log` at line 56 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/modules/products/core/application/usecases/activate-product/activate-product.usecase.ts:56
- `log` at line 39 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/modules/payments/secondary-adapters/schedulers/bullmq-payment-events.scheduler.ts:39
- `error` at line 44 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/modules/payments/secondary-adapters/schedulers/bullmq-payment-events.scheduler.ts:44
- `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/modules/payments/secondary-adapters/schedulers/bullmq-payment-events.scheduler.ts:68
- `error` at line 73 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/modules/payments/secondary-adapters/schedulers/bullmq-payment-events.scheduler.ts:73
- `log` at line 65 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/modules/payments/secondary-adapters/gateways/fake-stripe-payment.provider.ts:65
- `error` at line 69 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/modules/payments/secondary-adapters/gateways/fake-stripe-payment.provider.ts:69
- `log` at line 22 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/modules/payments/primary-adapters/processors/payments.processor.ts:22
- `log` at line 27 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/modules/payments/primary-adapters/processors/payments.processor.ts:27
- `warn` at line 33 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/modules/payments/primary-adapters/processors/payments.processor.ts:33
- `log` at line 43 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/modules/payments/primary-adapters/jobs/simulate-mock-payment-webhook.job.ts:43
- `debug` at line 70 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/modules/payments/core/application/usecases/handle-stripe-webhook/handle-stripe-webhook.usecase.ts:70
- `error` at line 98 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/modules/payments/core/application/usecases/handle-stripe-webhook/handle-stripe-webhook.usecase.ts:98
- `log` at line 44 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. (×2) — src/modules/payments/core/application/services/handle-payment-webhook/handle-payment-webhook.service.ts:44, src/modules/orders/orders.processor.ts:44
- `log` at line 86 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/modules/payments/core/application/services/handle-payment-webhook/handle-payment-webhook.service.ts:86
- `error` 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.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/modules/payments/core/application/services/handle-payment-webhook/handle-payment-webhook.service.ts:101
- `log` at line 152 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/modules/payments/core/application/services/handle-payment-webhook/handle-payment-webhook.service.ts:152
- `warn` at line 162 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/modules/payments/core/application/services/handle-payment-webhook/handle-payment-webhook.service.ts:162
- `log` at line 205 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/modules/payments/core/application/services/handle-payment-webhook/handle-payment-webhook.service.ts:205
- `log` at line 232 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/modules/payments/core/application/services/handle-payment-webhook/handle-payment-webhook.service.ts:232
- `warn` at line 80 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/modules/orders/orders.processor.ts:80
- `log` 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.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/modules/orders/payment-events.processor.ts:24
- `log` at line 29 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/modules/orders/payment-events.processor.ts:29
- `warn` 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.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/modules/orders/payment-events.processor.ts:37
- `warn` at line 28 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/modules/orders/primary-adapters/listeners/checkout-failure.listener.ts:28
- `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. — src/modules/orders/primary-adapters/listeners/checkout-failure.listener.ts:35
- `debug` at line 40 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/modules/orders/primary-adapters/listeners/checkout-failure.listener.ts:40
- `log` at line 59 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/modules/orders/primary-adapters/listeners/checkout-failure.listener.ts:59
- `log` at line 67 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/modules/orders/primary-adapters/listeners/checkout-failure.listener.ts:67
- `error` at line 74 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.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/modules/orders/primary-adapters/listeners/checkout-failure.listener.ts:74
- `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/modules/orders/primary-adapters/listeners/checkout-failure.listener.ts:81
- `error` 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.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/modules/orders/primary-adapters/listeners/checkout-failure.listener.ts:85
- `log` at line 91 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/modules/orders/primary-adapters/listeners/checkout-failure.listener.ts:91
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- 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.2 `!` null assertions per 1k TypeScript source lines — 607 assertion(s) across the 49625 source line(s) of the 771 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 (27), 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
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 54% | Adequate — gated by X4, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 58% | Adequate — gated by D26, R9 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 84% | Exemplary | Solid. |
| Readiness | 55% | Adequate — gated by D13, R8, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 66% | Adequate — gated by D28, D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 62% | Adequate — gated by DM2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- 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 — 7 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
- 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 — 50 check(s) not relevant to this codebase
- 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 15 — the compose project is invalid) — service "prometheus" has neither an image nor a build context specified: invalid compose project; 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.
- D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
- 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.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript not measured.
- 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+ sibling projects each declaring an entity of their own or taking another project's integration events. 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"]`.
- D25 ADR Conformance — None of 6 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- 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.)
- D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
- 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
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: src/main.ts:28 (NestFactory.create))
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R5 Dependency Freshness — `npm outdated` failed (EBADDEVENGINES: The developer of this package has specified the following through devEngines Invalid engine "runtime" Invalid semver version ">=26.0.0" does not match "v22.13.0" for "runtime") — dependency freshness not measured; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- 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, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, 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. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 27 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Import cycle (2 files) src/modules/authorization/secondary-adapter/orm/role-permission.schema.ts:10
- Import cycle (2 files) src/modules/carts/secondary-adapters/orm/cart-item.schema.ts:10
- Import cycle (2 files) src/modules/identity/secondary-adapters/orm/address.schema.ts:12
- Import cycle (2 files) src/modules/inventory/secondary-adapters/orm/reservation-item.schema.ts:10
- Import cycle (2 files) src/modules/orders/secondary-adapters/orm/order-item.schema.ts:12
- Import cycle (2 files) src/modules/payments/secondary-adapters/orm/payment.schema.ts:12
- REDACTED
- REDACTED
- REDACTED
- Aggregate holds a reference to another aggregate: Payment._refunds src/modules/payments/core/domain/entities/payment.ts:64
- Aggregate holds a reference to another aggregate: Payment.refunds src/modules/payments/core/domain/entities/payment.ts:388
- Aggregate holds a reference to another aggregate: User._addresses src/modules/identity/core/domain/entities/user.ts:28
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unlisted import 'express' src/filters/global-exception.filter.ts:10
- Unlisted import 'ms' src/config/configuration.ts:1
- Unlisted import 'testcontainers' test/integration/redis/redis-chaos.global-setup.ts:1
- Import cycle (3 files) src/modules/orders/testing/factories/order-dto.factory.ts:24
Serious — 413 finding(s)
- No assertions: refuses a password change for the read-only viewer test/e2e/security/security-idor.e2e-spec.ts:290
- No assertions: returns failure for invalid currency code in create src/shared-kernel/domain/value-objects/currency.spec.ts:74
- No assertions: returns failure for removed currency codes XDR and XSU src/shared-kernel/domain/value-objects/currency.spec.ts:83
- No assertions: should return failure when product not found src/modules/products/secondary-adapters/repositories/postgres-product-repository/postgres.product-repository.spec.ts:71
- No assertions: should return not-found when OCC update affects 0 rows and the product is missing src/modules/products/secondary-adapters/repositories/postgres-product-repository/postgres.product-repository.spec.ts:144
- No assertions: should return failure when database save fails src/modules/products/secondary-adapters/repositories/postgres-product-repository/postgres.product-repository.spec.ts:162
- No assertions: should return failure when product not found src/modules/products/secondary-adapters/repositories/postgres-product-repository/postgres.product-repository.spec.ts:195
- No assertions: should return failure when database query fails src/modules/products/secondary-adapters/repositories/postgres-product-repository/postgres.product-repository.spec.ts:209
- No assertions: should return failure when database query fails src/modules/products/secondary-adapters/repositories/postgres-product-repository/postgres.product-repository.spec.ts:253
- No assertions: should return failure when database delete fails src/modules/products/secondary-adapters/repositories/postgres-product-repository/postgres.product-repository.spec.ts:281
- No assertions: returns failure when the query throws src/modules/products/secondary-adapters/repositories/postgres-category-repository/postgres.category-repository.spec.ts:69
- No assertions: returns failure when save throws src/modules/products/secondary-adapters/repositories/postgres-category-repository/postgres.category-repository.spec.ts:119
- No assertions: returns failure when delete throws src/modules/products/secondary-adapters/repositories/postgres-category-repository/postgres.category-repository.spec.ts:143
- No assertions: returns failure when the query throws src/modules/products/secondary-adapters/repositories/postgres-category-repository/postgres.category-repository.spec.ts:195
- No assertions: should save expensive product src/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.spec.ts:59
- No assertions: should return failure if cache.set throws src/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.spec.ts:89
- No assertions: should return failure if cache.delete (IS_CACHED_FLAG) throws src/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.spec.ts:102
- No assertions: should return failure if cache.set throws after postgres success src/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.spec.ts:183
- No assertions: should return failure if cache.setAll throws after postgres success src/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.spec.ts:316
- No assertions: should return failure if cache.set (flag) throws after setAll success src/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.spec.ts:333
- No assertions: should return failure if cache.delete for individual product throws src/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.spec.ts:387
- No assertions: should return failure if cache.delete for IS_CACHED_FLAG throws src/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.spec.ts:407
- No assertions: rejects activate when already active src/modules/products/core/domain/entities/category.spec.ts:36
- No assertions: rejects deactivate when already inactive src/modules/products/core/domain/entities/category.spec.ts:46
- No assertions: rejects negative price src/modules/products/core/domain/entities/product.spec.ts:115
- 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
- No test reaches this file scripts/ascii-prose.cjs:1
- No test reaches this file scripts/db-restore-drill.js:1
- No test reaches this file scripts/audit-openapi.js:1
- No test reaches this file src/main.ts:1
- No test reaches this file scripts/seed-admin.ts:1
- No test reaches this file scripts/seed.ts:1
- No test reaches this file scripts/agent-check.mjs:1
- No test reaches this file scripts/db-restore.js:1
- No test reaches this file src/infrastructure/websocket/adapters/redis-io.adapter.ts:1
- No test reaches this file src/infrastructure/tracing/tracing.ts:1
- No test reaches this file src/modules/orders/primary-adapters/dto/create-order.dto.ts:1
- No test reaches this file scripts/setup.js:1
- No test reaches this file scripts/db-backup.js:1
- No test reaches this file src/modules/inventory/core/domain/value-objects/stock-adjustment-reason.ts:1
- No test reaches this file scripts/docker-migrate.js:1
- No test reaches this file scripts/generate-openapi-spec.ts:1
- No test reaches this file data-source.ts:1
- No test reaches this file src/modules/payments/primary-adapters/dto/payment-method-details.dto.ts:1
- No test reaches this file scripts/agent-run.mjs:1
- No test reaches this file src/infrastructure/websocket/guards/ws-auth.guard.ts:1
- No test reaches this file src/modules/inventory/primary-adapters/dto/stock-reservation-response.dto.ts:1
- No test reaches this file scripts/lint-ascii-prose.cjs:1
- No test reaches this file src/modules/orders/primary-adapters/dto/create-order-item.dto.ts:1
- No test reaches this file src/modules/identity/core/domain/repositories/address.repository.ts:1
- No test reaches this file src/modules/orders/primary-adapters/dto/payment-info.dto.ts:1
- Hotspot: scripts/generate-envs.js scripts/generate-envs.js:59
- Hotspot: src/modules/products/core/application/seed/seed-demo-catalog.usecase.ts src/modules/products/core/application/seed/seed-demo-catalog.usecase.ts:46
- Hotspot: src/modules/carts/secondary-adapters/mappers/query/cart-query.mapper.ts src/modules/carts/secondary-adapters/mappers/query/cart-query.mapper.ts:11
- Hotspot: src/filters/global-exception.filter.ts src/filters/global-exception.filter.ts:29
- Hotspot: src/modules/payments/core/application/usecases/process-refund/process-refund.usecase.ts src/modules/payments/core/application/usecases/process-refund/process-refund.usecase.ts:74
- 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
- Hotspot: src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts:25
- Hotspot: src/modules/products/secondary-adapters/query/postgres-product-query.adapter.ts src/modules/products/secondary-adapters/query/postgres-product-query.adapter.ts:24
- Hotspot: src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts:42
- Hotspot: 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:37
- 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Recursive walk over a caller-supplied document has no depth cap src/infrastructure/redis/redis-error.utils.ts:22
- Recursive walk over a caller-supplied document has no depth cap src/infrastructure/redis/cache/cache-json.ts:22
- Recursive walk over a caller-supplied document has no depth cap src/infrastructure/logging/winston-logger.service.ts:216
- Swallowed exception (empty catch) src/shared-kernel/helpers/lang/app-version.ts:16
- Swallowed exception (empty catch) src/infrastructure/redis/redis.service.ts:100
- Swallowed exception (empty catch) src/infrastructure/redis/cache/cache.service.ts:119
- Low cohesion: ModuleIdentityGateway (LCOM4 5) src/modules/authentication/secondary-adapters/adapters/module-identity.gateway.ts:18
- Low cohesion: ModuleInventoryReservationGateway (LCOM4 4) src/modules/orders/secondary-adapters/adapters/module-inventory-reservation.gateway.ts:15
- Anemic entity: OrderItem src/modules/orders/core/domain/entities/order-items.ts:17
- Anemic entity: ReservationItem src/modules/inventory/core/domain/entities/reservation-item.ts:11
- Duplicated block with local edits (45 matched lines × 2 locations) src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts:22
- Duplicated block with local edits (45 matched lines × 2 locations) src/modules/identity/core/application/usecases/address/add-address/add-address.usecase.ts:18
- Duplicated block with local edits (41 matched lines × 2 locations) src/modules/carts/secondary-adapters/persistence/mappers/cart.mapper.ts:10
- Duplicated block with local edits (41 matched lines × 2 locations) src/modules/identity/primary-adapters/dto/add-address.dto.ts:7
- Duplicated block with local edits (38 matched lines × 2 locations) src/modules/analytics/secondary-adapters/mappers/query/analytics-query.mapper.ts:93
- Duplicated block with local edits (38 matched lines × 2 locations) src/modules/identity/core/domain/entities/address.ts:57
- Duplicated block (37 lines × 2 locations) src/modules/authorization/authorization.module.ts:47
- Duplicated block (37 lines × 2 locations) src/modules/inventory/inventory.processor.ts:16
- Duplicated block with local edits (34 matched lines × 2 locations) src/modules/identity/primary-adapters/dto/address-response.dto.ts:12
- Duplicated block with local edits (34 matched lines × 2 locations) src/modules/products/core/application/usecases/activate-product/activate-product.usecase.ts:12
- Duplicated block (31 lines × 2 locations) src/modules/carts/core/application/usecases/clear-cart/clear-cart.usecase.ts:20
- Duplicated block (31 lines × 2 locations) src/modules/identity/core/application/usecases/address/delete-address/delete-address.usecase.ts:22
- Duplicated block (30 lines × 2 locations) src/modules/orders/primary-adapters/jobs/release-order-stock.job.ts:11
- Duplicated block (30 lines × 2 locations) src/modules/products/core/application/usecases/categories/get-category.usecase.ts:15
- Dead file (~14 LoC) src/modules/orders/primary-adapters/dto/payment-info.dto.ts
- Dead file (~14 LoC) src/modules/payments/core/domain/index.ts
- Dead file (~6 LoC) src/modules/carts/core/application/commands/clear-cart.command.ts
- Dead file (~6 LoC) src/modules/identity/core/application/commands/create-user.command.ts
- SeedDemoCatalogUseCase.execute (cyclomatic 25) src/modules/products/core/application/seed/seed-demo-catalog.usecase.ts:46
- GlobalExceptionFilter.catch (cyclomatic 25) src/filters/global-exception.filter.ts:29
- CartQueryMapper.toPresentationDto (cyclomatic 24) src/modules/carts/secondary-adapters/mappers/query/cart-query.mapper.ts:11
- PostgresPaymentQueryAdapter.list (cyclomatic 19) src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts:25
- CachedOrderRepository.listOrders (cyclomatic 18) src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:27
- ProcessRefundUseCase.execute (cyclomatic 17) src/modules/payments/core/application/usecases/process-refund/process-refund.usecase.ts:74
- CreatePaymentUseCase.execute (cyclomatic 16) src/modules/payments/core/application/usecases/create-payment/create-payment.usecase.ts:33
- CreatePaymentIntentUseCase.execute (cyclomatic 16) src/modules/payments/core/application/usecases/create-payment-intent/create-payment-intent.usecase.ts:37
- PostgresProductQueryAdapter.list (cyclomatic 16) src/modules/products/secondary-adapters/query/postgres-product-query.adapter.ts:24
- Deprecated: prom-client package.json:184
- Repeated repair: src/interceptors/sanitize.interceptor.ts src/interceptors/sanitize.interceptor.ts:39
- 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
- RoleSystemDataInitializer.onApplicationBootstrap (cognitive 25) src/modules/authorization/core/application/lifecycle/role-system-data.initializer.ts:19
- CachedOrderRepository.listOrders (cognitive 24) src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:27
- SeedDemoCategoriesUseCase.execute (cognitive 24) src/modules/products/core/application/seed/seed-demo-categories.usecase.ts:27
- SweepExpiredReservationsUseCase.execute (cognitive 21) src/modules/inventory/core/application/usecases/sweep-expired-reservations/sweep-expired-reservations.usecase.ts:31
- GlobalExceptionFilter.catch (cognitive 21) src/filters/global-exception.filter.ts:29
- CreatePaymentIntentUseCase.execute (cognitive 20) src/modules/payments/core/application/usecases/create-payment-intent/create-payment-intent.usecase.ts:37
- SeedDemoOrdersUseCase.execute (cognitive 20) src/modules/orders/core/application/seed/seed-demo-orders.usecase.ts:53
- PostgresPaymentQueryAdapter.list (cognitive 19) src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts:25
- CheckoutFailureListener.onModuleInit (cognitive 18) src/modules/orders/primary-adapters/listeners/checkout-failure.listener.ts:24
- CreatePaymentUseCase.execute (cognitive 17) src/modules/payments/core/application/usecases/create-payment/create-payment.usecase.ts:33
- money-decimal.minorUnitsFromDecimal (cognitive 16) src/shared-kernel/domain/value-objects/money-decimal.ts:57
- SeedDemoAuthUsersUseCase.seedUser (cognitive 16) REDACTED:138
- UpdateProductUseCase.execute (cognitive 16) src/modules/products/core/application/usecases/update-product/update-product.usecase.ts:31
- winston-logger.service.redactInPlace (cognitive 16) src/infrastructure/logging/winston-logger.service.ts:201
- TooManyMethods: Order src/modules/orders/core/domain/entities/order.ts:50
- Change coupling: cached.product-repository.ts ↔ postgres.product-repository.ts src/modules/products/secondary-adapters/repositories/cached-product-repository/cached.product-repository.ts:1
- One operation mutates 2 aggregates: ChangePasswordUseCase.execute src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts:42
- Mutable entity: Credential src/modules/authentication/core/domain/entities/credential.ts:10
- Coverage collected but not gated
- Duplication concentrated across 10 sibling directories (204 clone groups) src/modules/carts/secondary-adapters/repositories/cached-cart-repository/cached.cart-repository.ts:15
- Duplication concentrated across 10 sibling directories (9 clone groups) src/modules/orders/core/application/usecases/process-order/process-order.usecase.ts:11
- Duplication concentrated across 3 sibling directories (6 clone groups) src/modules/payments/core/domain/value-objects/payment-status.ts:12
- Duplication concentrated across 6 sibling directories (6 clone groups) src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts:22
- Duplicated block with local edits (108 matched lines × 2 locations) src/modules/products/core/domain/entities/category.ts:20
- Duplicated block with local edits (98 matched lines × 2 locations) src/modules/carts/secondary-adapters/repositories/cached-cart-repository/cached.cart-repository.ts:15
- Duplicated block (70 lines × 2 locations) src/modules/carts/secondary-adapters/repositories/postgres-cart-repository/postgres.cart-repository.ts:97
- Duplicated block with local edits (64 matched lines × 2 locations) src/modules/inventory/secondary-adapters/query/postgres-inventory-query.adapter.ts:16
- Duplicated block with local edits (63 matched lines × 2 locations) src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:122
- Duplicated block with local edits (54 matched lines × 2 locations) src/modules/products/core/application/usecases/create-product/create-product.usecase.ts:18
- Duplicated block with local edits (51 matched lines × 2 locations) src/modules/inventory/secondary-adapters/repositories/postgres-inventory-repository/postgres-inventory-repository.ts:220
- Duplicated block with local edits (50 matched lines × 2 locations) src/modules/identity/primary-adapters/dto/add-address.dto.ts:7
- Duplicated block with local edits (49 matched lines × 2 locations) src/modules/authorization/secondary-adapter/repositories/postgres-role-repository/postgres-role.repository.ts:61
- Duplicated block (45 lines × 2 locations) src/modules/orders/core/application/usecases/list-orders/list-orders.usecase.ts:19
- Duplicated block with local edits (44 matched lines × 2 locations) src/modules/authorization/secondary-adapter/repositories/postgres-role-repository/postgres-role.repository.ts:46
- Duplicated block (44 lines × 2 locations) src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts:150
- Duplicated block (41 lines × 2 locations) src/modules/products/secondary-adapters/query/postgres-product-query.adapter.ts:143
- Duplicated block (40 lines × 2 locations) src/modules/carts/secondary-adapters/query/postgres-cart-query.adapter.ts:20
- Duplicated block (40 lines × 3 locations) src/modules/inventory/secondary-adapters/schedulers/bullmq-inventory.scheduler.ts:29
- Duplicated block (36 lines × 2 locations) src/modules/products/core/application/usecases/categories/activate-category.usecase.ts:13
- Duplicated block with local edits (35 matched lines × 2 locations) src/modules/inventory/secondary-adapters/repositories/cached-inventory-repository/cached-inventory-repository.ts:30
- Duplicated block (34 lines × 2 locations) src/modules/carts/carts.module.ts:37
- Duplicated block with local edits (32 matched lines × 2 locations) src/modules/orders/primary-adapters/jobs/create-order.job.ts:17
- Duplicated block with local edits (30 matched lines × 2 locations) src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:65
- Duplicated block (29 lines × 2 locations) src/modules/authentication/secondary-adapters/adapters/module-identity.gateway.ts:38
- Duplicated block (28 lines × 2 locations) src/modules/identity/secondary-adapters/repositories/cached-user-repository/cached-user.repository.ts:134
- Complex function (top-level) (cyclomatic 27, cognitive 44) src/filters/global-exception.filter.ts:1
- Complex function generateEnvs (cyclomatic 26, cognitive 44) scripts/generate-envs.js:169
- Complex function toPresentationDto (cyclomatic 26, cognitive 35) src/modules/carts/secondary-adapters/mappers/query/cart-query.mapper.ts:11
- Complex function (top-level) (cyclomatic 25, cognitive 32) REDACTED:1
- Complex function (anonymous) (cyclomatic 25, cognitive 30) scripts/generate-envs.js:62
- Complex function skipString (cyclomatic 23, cognitive 35) scripts/ascii-prose.cjs:148
- Complex function walk (cyclomatic 22, cognitive 32) scripts/ascii-prose.cjs:54
- Complex function selectVitestCommands (cyclomatic 22, cognitive 21) scripts/agent-output.mjs:78
- Complex function (top-level) (cyclomatic 19, cognitive 18) src/modules/authentication/core/application/usecases/refresh-token/refresh-token.usecase.ts:1
- Complex function list (cyclomatic 19, cognitive 18) src/modules/payments/secondary-adapters/query/postgres-payment-query.adapter.ts:25
- Complex function listOrders (cyclomatic 18, cognitive 24) src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:27
- Complex function (top-level) (cyclomatic 17, cognitive 18) src/modules/payments/core/application/usecases/create-payment/create-payment.usecase.ts:1
- Complex function runSetup (cyclomatic 16, cognitive 15) scripts/lib/setup-bootstrap.js:15
- Complex function (top-level) (cyclomatic 16, cognitive 15) src/modules/orders/core/application/usecases/handle-payment-completed/handle-payment-completed.usecase.ts:1
- Complex function list (cyclomatic 16, cognitive 14) src/modules/products/secondary-adapters/query/postgres-product-query.adapter.ts:24
- Complex function (top-level) (cyclomatic 15, cognitive 14) src/modules/authentication/core/application/usecases/change-password/change-password.usecase.ts:1
- Complex function list (cyclomatic 15, cognitive 12) src/modules/inventory/secondary-adapters/query/postgres-inventory-query.adapter.ts:23
- Complex function findComments (cyclomatic 14, cognitive 18) scripts/ascii-prose.cjs:143
- Complex function (anonymous) (cyclomatic 14, cognitive 18) src/modules/orders/primary-adapters/listeners/checkout-failure.listener.ts:27
- src/modules/orders/core/domain/entities/order.ts: 488 lines of code src/modules/orders/core/domain/entities/order.ts:1
- src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.ts: 419 lines of code src/modules/inventory/secondary-adapters/repositories/postgres-reservation-repository/postgres.reservation-repository.ts:1
- Dead file (~56 LoC) src/modules/orders/primary-adapters/dto/create-order.dto.ts
- Dead file (~47 LoC) src/modules/inventory/core/domain/value-objects/stock-adjustment-reason.ts
- Dead file (~37 LoC) src/modules/payments/primary-adapters/dto/payment-method-details.dto.ts
- Dead file (~29 LoC) src/infrastructure/websocket/guards/ws-auth.guard.ts
- Dead file (~28 LoC) src/modules/inventory/primary-adapters/dto/stock-reservation-response.dto.ts
- Dead file (~25 LoC) src/modules/orders/primary-adapters/dto/create-order-item.dto.ts
- Dead file (~18 LoC) src/modules/identity/core/domain/repositories/address.repository.ts
- Dead file (~17 LoC) src/types/express.ts
- Dead file (~10 LoC) src/infrastructure/tracing/index.ts
- Dead file (~7 LoC) src/modules/carts/core/application/commands/remove-cart-item.command.ts
- Dead file (~5 LoC) src/modules/orders/primary-adapters/dto/update-order.dto.ts
- Dead file (~3 LoC) src/infrastructure/jwt/index.ts
- Dead file (~2 LoC) src/infrastructure/idempotency/index.ts
- Dead file (~1 LoC) src/modules/authentication/primary-adapters/decorators/index.ts
- Dead file (~0 LoC) src/modules/orders/core/domain/services/index.ts
- Unused dependency '@eslint/eslintrc'
- Unused dependency 'source-map-support'
- Unused dependency 'tsconfig-paths'
Minor — 111 finding(s)
- Interpolated log message defeats structured logging src/main.ts:89
- Interpolated log message defeats structured logging src/main.ts:104
- Interpolated log message defeats structured logging src/modules/products/core/application/usecases/deactivate-product/deactivate-product.usecase.ts:49
- Interpolated log message defeats structured logging src/modules/products/core/application/usecases/categories/activate-category.usecase.ts:50
- Interpolated log message defeats structured logging src/modules/products/core/application/usecases/categories/deactivate-category.usecase.ts:50
- Interpolated log message defeats structured logging src/modules/products/core/application/usecases/activate-product/activate-product.usecase.ts:56
- Interpolated log message defeats structured logging src/modules/payments/secondary-adapters/schedulers/bullmq-payment-events.scheduler.ts:39
- Interpolated log message defeats structured logging src/modules/payments/secondary-adapters/schedulers/bullmq-payment-events.scheduler.ts:44
- Interpolated log message defeats structured logging src/modules/payments/secondary-adapters/schedulers/bullmq-payment-events.scheduler.ts:68
- Interpolated log message defeats structured logging src/modules/payments/secondary-adapters/schedulers/bullmq-payment-events.scheduler.ts:73
- Interpolated log message defeats structured logging src/modules/payments/secondary-adapters/gateways/fake-stripe-payment.provider.ts:65
- Interpolated log message defeats structured logging src/modules/payments/secondary-adapters/gateways/fake-stripe-payment.provider.ts:69
- Interpolated log message defeats structured logging src/modules/payments/primary-adapters/processors/payments.processor.ts:22
- Interpolated log message defeats structured logging src/modules/payments/primary-adapters/processors/payments.processor.ts:27
- Interpolated log message defeats structured logging src/modules/payments/primary-adapters/processors/payments.processor.ts:33
- Interpolated log message defeats structured logging src/modules/payments/primary-adapters/jobs/simulate-mock-payment-webhook.job.ts:43
- Interpolated log message defeats structured logging src/modules/payments/core/application/usecases/handle-stripe-webhook/handle-stripe-webhook.usecase.ts:70
- Interpolated log message defeats structured logging src/modules/payments/core/application/usecases/handle-stripe-webhook/handle-stripe-webhook.usecase.ts:98
- Interpolated log message defeats structured logging src/modules/payments/core/application/services/handle-payment-webhook/handle-payment-webhook.service.ts:44
- Interpolated log message defeats structured logging src/modules/payments/core/application/services/handle-payment-webhook/handle-payment-webhook.service.ts:86
- Interpolated log message defeats structured logging src/modules/payments/core/application/services/handle-payment-webhook/handle-payment-webhook.service.ts:101
- Interpolated log message defeats structured logging src/modules/payments/core/application/services/handle-payment-webhook/handle-payment-webhook.service.ts:152
- Interpolated log message defeats structured logging src/modules/payments/core/application/services/handle-payment-webhook/handle-payment-webhook.service.ts:162
- Interpolated log message defeats structured logging src/modules/payments/core/application/services/handle-payment-webhook/handle-payment-webhook.service.ts:205
- Interpolated log message defeats structured logging src/modules/payments/core/application/services/handle-payment-webhook/handle-payment-webhook.service.ts:232
- Primitive id on a domain type: OrderItem.productId src/modules/orders/core/domain/entities/order-items.ts:57
- Primitive id on a domain type: Order.userId src/modules/orders/core/domain/entities/order.ts:118
- Primitive id on a domain type: CartItem.productId src/modules/carts/core/domain/entities/cart-item.ts:86
- Primitive id on a domain type: Cart.userId src/modules/carts/core/domain/entities/cart.ts:52
- Primitive id on a domain type: ReservationItem.productId src/modules/inventory/core/domain/entities/reservation-item.ts:26
- Primitive id on a domain type: Reservation.orderId src/modules/inventory/core/domain/entities/reservation.ts:70
- Primitive id on a domain type: Refund.paymentId src/modules/payments/core/domain/entities/refund.ts:73
- Primitive id on a domain type: Payment.orderId src/modules/payments/core/domain/entities/payment.ts:133
- Primitive id on a domain type: SessionToken.userId src/modules/authentication/core/domain/entities/session-token.ts:35
- Primitive id on a domain type: Credential.userId src/modules/authentication/core/domain/entities/credential.ts:27
- Primitive id on a domain type: UserRoleAssignment.userId src/modules/authorization/core/domain/entities/user-role-assignment.ts:30
- Primitive id on a domain type: UserRoleAssignment.roleId src/modules/authorization/core/domain/entities/user-role-assignment.ts:34
- Primitive id on a domain type: Address.userId src/modules/identity/core/domain/entities/address.ts:99
- Primitive id on a domain type: Inventory.productId src/modules/inventory/core/domain/entities/inventory.ts:81
- Duplicated predicate src/modules/carts/core/application/usecases/create-cart/create-cart.usecase.ts:29
- Duplicated predicate src/modules/products/core/application/usecases/create-product/create-product.usecase.ts:56
- Duplicated predicate src/modules/inventory/core/domain/entities/reservation.ts:49
- Duplicated predicate src/migrations/1787400000005-PaymentProviderAndCardMethod.ts:5
- Duplicated predicate src/shared-kernel/domain/exceptions/to-optional-error.ts:21
- Duplicated predicate src/modules/orders/secondary-adapters/repositories/cached-order-repository/cached.order-repository.ts:54
- Duplicated predicate src/shared-kernel/domain/exceptions/to-optional-error.ts:15
- redundant comment src/filters/global-exception.filter.spec.ts:56
- redundant comment src/modules/authentication/testing/mocks/identity-access-gateway.mock.ts:29
- redundant comment src/modules/orders/testing/mocks/cart-gateway.mock.ts:52
- redundant comment src/modules/orders/testing/mocks/user-gateway.mock.ts:27
- redundant comment src/modules/payments/core/domain/index.ts:4
- redundant comment src/modules/products/testing/mocks/product-repository.mock.ts:100
- Classify ADR enforcement: ADR-0004: Inventory Data Integrity, Concurrency & Schema Optimization docs/architecture/adr/ADR-0004-inventory-integrity-and-concurrency.md
- Classify ADR enforcement: ADR-0005: Typed Atomic OCC Update Contract docs/architecture/adr/ADR-0005-typed-atomic-occ-update-contract.md
- Classify ADR enforcement: ADR-0006: Redis Fail-Open Cache-Aside & Key-Space Generation docs/architecture/adr/ADR-0006-redis-fail-open-cache-aside.md
- Classify ADR enforcement: ADR-0007: Admin Analytics as Query-Only Composition Module docs/architecture/adr/ADR-0007-admin-analytics-query-composition.md
- Classify ADR enforcement: ADR-0008: Money Snapshot, Cart Domain Currency Boundaries, and CQRS Separation docs/architecture/adr/ADR-0008-money-snapshot-and-store-currency.md
- Classify ADR enforcement: ADR-0009: Hosted Demo Reset as Ops Infrastructure docs/architecture/adr/ADR-0009-demo-reset-ops-infrastructure.md
- Mock-dominated test: registers onFailed listener and executes compensation on failure src/modules/orders/primary-adapters/listeners/checkout-failure.listener.spec.ts:74
- Mock-dominated test: looks up reservationId from inventoryGateway when missing in job data src/modules/orders/primary-adapters/listeners/checkout-failure.listener.spec.ts:101
- Mock-dominated test: skips compensation for failed REFUND_PAYMENT jobs src/modules/orders/primary-adapters/listeners/checkout-failure.listener.spec.ts:129
- 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:515
- Deprecated: glob REDACTED:8003
- Deprecated: node-domexception REDACTED:14300
- Deprecated: glob REDACTED:15838
- Deprecated: glob REDACTED:17100
- Partial data-retention evidence
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- README/code drift docs/data/collections/bruno/README.md:14
- No SAST .github/workflows/ci.yml:4
- Unused export 'needsWebBuild' scripts/agent-output.mjs:124
- Unused export 'DEMO_RESET_TOKEN_MIN_LENGTH' REDACTED:155
- Unused export 'HealthIndicatorResultDto' src/infrastructure/health/dto/health-check-response.dto.ts:3
- Unused export 'DEFAULT_RETRY_CONFIG' src/infrastructure/jobs/retry-config.ts:15
- Unused export 'CreateCartInput' src/modules/carts/core/domain/repositories/cart.repository.ts:4
- Unused export 'CartBuilder' REDACTED:5
- Unused export 'CreateUserAddressInput' src/modules/identity/core/application/usecases/user/create-user/create-user.usecase.ts:13
- Unused export 'UserBuilder' src/modules/identity/testing/builders/user.builder.ts:4
- Unused export 'InventoryListItemResult' src/modules/inventory/core/application/queries/results/inventory-list-item.result.ts:12
- Unused export 'BulkCheckStockBodyDto' src/modules/inventory/primary-adapters/dto/bulk-check-stock.dto.ts:17
- Unused export 'OrderDetailResult' src/modules/orders/core/application/queries/results/order-detail.result.ts:22
- Unused export 'OrderItemDetailResult' src/modules/orders/core/application/queries/results/order-item-detail.result.ts:11
- Unused export 'OrderListItemResult' src/modules/orders/core/application/queries/results/order-list-item.result.ts:14
- Unused export 'IOrderEditable' src/modules/orders/core/domain/interfaces/order.interface.ts:28
- Unused export 'OrderItemInput' src/modules/orders/core/domain/repositories/order-repository.ts:5
- Unused export 'PaymentDetailResult' src/modules/payments/core/application/queries/results/payment-detail.result.ts:10
- Unused export 'PaymentListItemResult' src/modules/payments/core/application/queries/results/payment-list-item.result.ts:17
- Unused export 'ProductBuilder' src/modules/products/testing/builders/product.builder.ts:5
- Unused export 'DatabaseTestHelper' src/testing/helpers/database-test.helper.ts:8
- Unused private field 'logger' src/modules/carts/secondary-adapters/repositories/cached-cart-repository/cached.cart-repository.ts:20
- Strict null checking is not enabled everywhere the repository type-checks
- Null assertions (`!`) reduce the strict null checking score
Minor — 25 finding(s)
- Outdated (npm): @nestjs/bullmq
- Outdated (npm): @nestjs/common
- Outdated (npm): @nestjs/config
- Outdated (npm): @nestjs/core
- Outdated (npm): @nestjs/event-emitter
- Outdated (npm): @nestjs/mapped-types
- Outdated (npm): @nestjs/platform-express
- Outdated (npm): @nestjs/platform-socket.io
- Outdated (npm): @nestjs/schedule
- Outdated (npm): @nestjs/swagger
- Outdated (npm): @nestjs/typeorm
- Outdated (npm): @nestjs/websockets
- Outdated (npm): @opentelemetry/auto-instrumentations-node
- Outdated (npm): @opentelemetry/exporter-trace-otlp-grpc
- Outdated (npm): @opentelemetry/resources
- Outdated (npm): @opentelemetry/sdk-node
- Outdated (npm): @opentelemetry/semantic-conventions
- Outdated (npm): bullmq
- Outdated (npm): ioredis
- Outdated (npm): jose
- Outdated (npm): redis
- Outdated (npm): stripe
- 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 (documented): (unnamed test) src/modules/identity/primary-adapters/decorators/current-user.decorator.spec.ts:11
- doc comments repeat the names src/modules/orders/testing/factories/order-entity.factory.ts:65
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-cfe48defbb1941c0be3931e55e877d7e/history.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-cfe48defbb1941c0be3931e55e877d7e/tree.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 52 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 6 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 6 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: 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 Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |