Executive summary
proyecto26/projectx is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 46 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 31, is the weakest lens and 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 11 points. Replacing the six deprecated dependencies comes next, worth about 9 points. Raising Production Readiness to 70 would lift the score to about 59.
Forty-five known security holes in the packages the code depends on can be used by attackers. Three passwords or keys in the code and two in the code's history are open to anyone who can read the repository, and fifteen form fields can't be read by a screen reader. Updating the vulnerable packages, replacing each exposed password or key and labelling the form fields would close these risks. Fixing the weaknesses the scanner points to would fix the two security weaknesses in the code, and the three unsafe settings in infrastructure or container files need changing to safe values. The two buttons or links with no name need a name, even when they only show an icon.
The product code is 21,233 lines, about €23,000 to rebuild.
If Production Readiness rose from 31 to 70, the lowest score rated Strong, the score would rise from 46 to about 59.
New since the last survey: 73 findings
- Cyclomatic Complexity · process-payment.workflow.processPayment (cyclomatic 26) apps/order/src/workflows/process-payment.workflow.ts
- Cyclomatic Complexity · checkout.Checkout (cyclomatic 19) apps/web/src/routes/checkout.tsx
- Cyclomatic Complexity · useWorkflow.useWorkflow (cyclomatic 18) packages/workflow-client/src/react/useWorkflow.ts
- Cognitive Complexity · process-payment.workflow.processPayment (cognitive 29) apps/order/src/workflows/process-payment.workflow.ts
- Cognitive Complexity · fallback.createFallbackTransport.recover (cognitive 27) packages/workflow-client/src/transports/fallback.ts
- Cognitive Complexity · sse.parseSse (cognitive 26) packages/workflow-client/src/sse.ts
- Cognitive Complexity · WorkflowSession.#follow (cognitive 23) packages/workflow-client/src/session.ts
- Cognitive Complexity · order.workflow.createOrder (cognitive 21) apps/order/src/workflows/order.workflow.ts
- Cognitive Complexity · WorkflowRegistry.hydrate (cognitive 17) packages/workflow-client/src/registry.ts
- Cognitive Complexity · useWorkflow.useWorkflow (cognitive 16) packages/workflow-client/src/react/useWorkflow.ts
- Cognitive Complexity · temporal.workflowStreamEvents (cognitive 16) packages/workflow-client/src/server/temporal.ts
- God Classes · FunctionTooLong: CheckoutPage.CheckoutPage apps/web/src/pages/CheckoutPage.tsx
- God Classes · FunctionTooLong: http-stream.createHttpStreamTransport packages/workflow-client/src/transports/http-stream.ts
- Coupling · Off the main sequence: @proyecto26/temporal-workflows
- Test Quality · Fixed-sleep synchronisation: doesn't count a slow reader as an idle stream packages/workflow-client/src/transports/transports.spec.ts
- Secret Scanning · REDACTED
- Churn × Complexity Hotspots · Hotspot: packages/workflow-client/src/react/useWorkflow.ts packages/workflow-client/src/react/useWorkflow.ts
- Churn × Complexity Hotspots · Hotspot: apps/order/src/workflows/process-payment.workflow.ts apps/order/src/workflows/process-payment.workflow.ts
- Churn × Complexity Hotspots · Hotspot: apps/order/src/workflows/order.workflow.ts apps/order/src/workflows/order.workflow.ts
- Churn × Complexity Hotspots · Hotspot: apps/web/src/routes/checkout.tsx apps/web/src/routes/checkout.tsx
- Secrets (history) · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- IaC & Container Security · REDACTED
- IaC & Container Security · REDACTED
- IaC & Container Security · REDACTED
- Code Duplication · Duplicated block (29 lines × 3 locations) apps/web/src/services/admin-orders.ts
- Cyclomatic Complexity · Complex function parseSse (cyclomatic 14, cognitive 28) packages/workflow-client/src/sse.ts
- Cyclomatic Complexity · Complex function recover (cyclomatic 14, cognitive 27) packages/workflow-client/src/transports/fallback.ts
- Cyclomatic Complexity · Complex function workflowStreamEvents (cyclomatic 13, cognitive 18) packages/workflow-client/src/server/temporal.ts
- Cyclomatic Complexity · Complex function CheckoutPage (cyclomatic 13, cognitive 14) apps/web/src/pages/CheckoutPage.tsx
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 12, cognitive 13) apps/order/src/workflows/process-payment.workflow.ts
- Cyclomatic Complexity · Complex function handleWebhook (cyclomatic 12, cognitive 12) apps/order/src/app/app.service.ts
- Cyclomatic Complexity · Complex function useWorkflow (cyclomatic 12, cognitive 11) packages/workflow-client/src/react/useWorkflow.ts
- Large Files · apps/web/src/pages/admin/Orders.tsx: 1096 lines of code apps/web/src/pages/admin/Orders.tsx
- Large Files · apps/order/src/app/order/order.service.ts: 514 lines of code apps/order/src/app/order/order.service.ts
- Test Coverage · No test reaches this file packages/workflow-client/src/react/types.test-d.tsx
- Test Coverage · No test reaches this file apps/web/src/providers/workflows/orderWorkflow.ts
- Dead Code · Dead file (~224 LoC) packages/workflow-client/src/react/types.test-d.tsx
- Cancellation propagation · Async function without AbortSignal: action apps/web/src/routes/login.tsx
- Exception handling · Swallowed exception (empty catch) packages/workflow-client/src/registry.ts
- Exception handling · Swallowed exception (caught, then discarded) packages/workflow-client/src/session.ts
- Forms & labels · <OtpInput> field component without a label apps/web/src/pages/LoginPage.tsx
Fixed since the last survey: 390 findings
- Cyclomatic Complexity · useOrderWorkflow.useOrderWorkflow (cyclomatic 16) apps/web/src/providers/workflows/internal/useOrderWorkflow.ts
- Cognitive Complexity · useOrderWorkflow.useOrderWorkflow (cognitive 26) apps/web/src/providers/workflows/internal/useOrderWorkflow.ts
- Coupling · Off the main sequence: @projectx/payment
- Coupling · Off the main sequence: @projectx/core
- Boundary Type-Coupling · Cross-context type PaymentStatus (models → db) packages/db/src/lib/payment/payment-repository.service.ts
- Boundary Type-Coupling · Cross-context type ProductStatus (models → db) packages/db/src/lib/product/product-repository.service.ts
- Static Analysis (SAST) · High: npm-missing-minimum-release-age .npmrc
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High vulnerability: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High vulnerability: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] apps/auth/package.json
- Dependency Vulnerabilities · Medium CVE: REDACTED packages/core/package.json
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- IaC & Container Security · Medium IaC: REDACTED REDACTED
- IaC & Container Security · Medium IaC: REDACTED REDACTED
- IaC & Container Security · Medium IaC: REDACTED REDACTED
- IaC & Container Security · Medium IaC: REDACTED REDACTED
- Code Duplication · Duplicated block (25 lines × 2 locations) apps/web/src/services/admin-orders.ts
- Code Duplication · Duplicated block (23 lines × 2 locations) apps/order/src/app/order/order.service.ts
- Code Duplication · Duplicated block (14 lines × 2 locations) apps/web/src/providers/workflows/services/order.ts
- Code Duplication · Duplicated block (14 lines × 2 locations) apps/web/src/services/admin-orders.ts
- Code Duplication · Duplicated block (14 lines × 3 locations) apps/web/src/services/admin-orders.ts
- Code Duplication · Duplicated block (13 lines × 2 locations) apps/web/src/services/admin-orders.ts
- Code Duplication · Duplicated block (13 lines × 2 locations) packages/payment/src/lib/stripe/stripe.service.ts
- Code Duplication · Duplicated block (12 lines × 2 locations) apps/web/src/pages/HomePage.tsx
- Code Duplication · Duplicated block (12 lines × 2 locations) apps/web/src/pages/PrivacyPage.tsx
- Code Duplication · Duplicated block (12 lines × 2 locations) REDACTED
- Code Duplication · Duplicated block (12 lines × 2 locations) packages/cli/src/commands/info.ts
- Code Duplication · Duplicated block (11 lines × 2 locations) apps/auth/src/app/app.service.ts
- Code Duplication · Duplicated block (11 lines × 2 locations) apps/order/src/app/order/order.service.ts
- Code Duplication · Duplicated block (11 lines × 2 locations) apps/web/src/hooks/useAdminOrders.ts
- Code Duplication · Duplicated block (11 lines × 2 locations) apps/web/src/pages/ProductDetail.tsx
- Code Duplication · Duplicated block (11 lines × 2 locations) apps/web/src/pages/ProductDetail.tsx
- Code Duplication · Duplicated block (11 lines × 2 locations) apps/web/src/pages/admin/Dashboard.tsx
- Code Duplication · Duplicated block (11 lines × 2 locations) packages/cli/src/utils/paths.ts
- Code Duplication · Duplicated block (10 lines × 2 locations) apps/web/src/hooks/useAdminOrders.ts
- Code Duplication · Duplicated block with local edits (9 matched lines × 2 locations) apps/web/src/cookies/auth.server.ts
- Code Duplication · Duplicated block (9 lines × 2 locations) apps/web/src/pages/CheckoutPage.tsx
- Code Duplication · Duplicated block (9 lines × 2 locations) apps/web/src/routes/admin/layout.tsx
- Code Duplication · Duplicated block (9 lines × 4 locations) packages/models/src/order/order.dto.ts
- Code Duplication · Duplicated block (8 lines × 2 locations) packages/cli/src/utils/paths.ts
- Code Duplication · Duplicated block (7 lines × 3 locations) packages/db/src/lib/order/order-repository.service.ts
- Code Duplication · Duplicated block (6 lines × 2 locations) apps/order/src/config/app.config.ts
- Code Duplication · Duplicated block (6 lines × 2 locations) packages/cli/src/commands/init.ts
- Cyclomatic Complexity · Complex function queryFn (cyclomatic 16, cognitive 26) apps/web/src/providers/workflows/internal/useOrderWorkflow.ts
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 11, cognitive 9) apps/web/src/providers/workflows/store/reducer.ts
Rebuild cost: about €23,000 · Estimate
| Cost to rebuild | €7,600 to €38,000, for 126 to 401 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 46. 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: 21,233 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 — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 apps.order.src.app.order.dto.admin-order-counts_dto | 2 apps.order.src.app.order.dto.admin-order-list_dto | 3 apps.order.src.app.order.dto.admin-stats_dto | 4 apps.web.src.pages.admin.Dashboard | 5 apps.web.src.providers.workflows.types.order | 6 packages.core.src.lib.user.user_interface | 7 packages.db.src.lib.prisma_service | 8 packages.models.src.auth.login_dto | 9 packages.models.src.order.create-order_dto | 10 packages.models.src.product.product_dto | 11 packages.models.src.user.update-user_dto | 12 packages.models.src.user.user_dto | 13 packages.workflow-client.src.types | 14 apps.auth.src.app.app_service | 15 apps.order.src.app.app_service | 16 apps.order.src.app.order.dto.admin-order-detail_dto | 17 apps.order.src.app.order.dto.update-order-status_dto | 18 apps.web.src.hooks | 19 packages.db.src.lib.payment.payment-repository_service | 20 packages.db.src.lib.product.product-repository_service | 21 packages.db.src.lib.user.user-repository_service | 22 packages.models.src.auth.auth_dto | 23 packages.models.src.order.order_dto | 24 packages.workflow-client.src.server | 25 packages.workflow-client.src.session | 26 packages.workflow-client.src.transports | 27 apps.auth.src.app.app_controller | 28 apps.auth.src.app.user.user_service | 29 apps.web.src.services | 30 packages.db.src.lib.order.order-repository_service | 31 packages.models.src.order.order-summary_dto | 32 packages.workflow-client.src.registry | 33 apps.auth.src.app.activities.activities_service | 34 apps.auth.src.app.user.user_controller | 35 apps.order.src.app.order.order_service | 36 packages.workflow-client.src.client | 37 apps.order.src.app.app_controller | 38 apps.order.src.app.order.order-admin_controller | 39 packages.workflow-client.src | 40 packages.workflows.src.lib |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 apps.order.src.app.order.dto.admin-order-counts_dto | ||||||||||||||||||||||||||||||||||||||||
| 2 apps.order.src.app.order.dto.admin-order-list_dto | ||||||||||||||||||||||||||||||||||||||||
| 3 apps.order.src.app.order.dto.admin-stats_dto | ||||||||||||||||||||||||||||||||||||||||
| 4 apps.web.src.pages.admin.Dashboard | ||||||||||||||||||||||||||||||||||||||||
| 5 apps.web.src.providers.workflows.types.order | ||||||||||||||||||||||||||||||||||||||||
| 6 packages.core.src.lib.user.user_interface | ||||||||||||||||||||||||||||||||||||||||
| 7 packages.db.src.lib.prisma_service | ||||||||||||||||||||||||||||||||||||||||
| 8 packages.models.src.auth.login_dto | ||||||||||||||||||||||||||||||||||||||||
| 9 packages.models.src.order.create-order_dto | ||||||||||||||||||||||||||||||||||||||||
| 10 packages.models.src.product.product_dto | ||||||||||||||||||||||||||||||||||||||||
| 11 packages.models.src.user.update-user_dto | ||||||||||||||||||||||||||||||||||||||||
| 12 packages.models.src.user.user_dto | ||||||||||||||||||||||||||||||||||||||||
| 13 packages.workflow-client.src.types | ||||||||||||||||||||||||||||||||||||||||
| 14 apps.auth.src.app.app_service | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 apps.order.src.app.app_service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 apps.order.src.app.order.dto.admin-order-detail_dto | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 apps.order.src.app.order.dto.update-order-status_dto | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 apps.web.src.hooks | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 19 packages.db.src.lib.payment.payment-repository_service | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 packages.db.src.lib.product.product-repository_service | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 21 packages.db.src.lib.user.user-repository_service | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 packages.models.src.auth.auth_dto | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 packages.models.src.order.order_dto | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 packages.workflow-client.src.server | 3 | |||||||||||||||||||||||||||||||||||||||
| 25 packages.workflow-client.src.session | 4 | |||||||||||||||||||||||||||||||||||||||
| 26 packages.workflow-client.src.transports | 7 | |||||||||||||||||||||||||||||||||||||||
| 27 apps.auth.src.app.app_controller | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 apps.auth.src.app.user.user_service | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 apps.web.src.services | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 packages.db.src.lib.order.order-repository_service | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 packages.models.src.order.order-summary_dto | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 packages.workflow-client.src.registry | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 33 apps.auth.src.app.activities.activities_service | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 apps.auth.src.app.user.user_controller | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 apps.order.src.app.order.order_service | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||
| 36 packages.workflow-client.src.client | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 apps.order.src.app.app_controller | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 apps.order.src.app.order.order-admin_controller | 1 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 39 packages.workflow-client.src | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 packages.workflows.src.lib | 1 |
14→8 apps.auth.src.app.app_service uses packages.models.src.auth.login_dto✕
- Connections
- 2 pairs of types, where a type in apps.auth.src.app.app_service uses a type in packages.models.src.auth.login_dto.
- The types involved
apps.auth.src.app.app_service.AppService→packages.models.src.auth.login_dto.AuthLoginDtoapps.auth.src.app.app_service.AppService→packages.models.src.auth.login_dto.AuthVerifyDto
- Direction
- apps.auth.src.app.app_service uses packages.models.src.auth.login_dto, so a change to packages.models.src.auth.login_dto can break apps.auth.src.app.app_service, while a change to apps.auth.src.app.app_service can't break packages.models.src.auth.login_dto.
- Position
- Below the diagonal: apps.auth.src.app.app_service uses a module listed above it, which is the healthy direction.
15→6 apps.order.src.app.app_service uses packages.core.src.lib.user.user_interface✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.app_service uses a type in packages.core.src.lib.user.user_interface.
- The types involved
apps.order.src.app.app_service.AppService→packages.core.src.lib.user.user_interface.AuthUser
- Direction
- apps.order.src.app.app_service uses packages.core.src.lib.user.user_interface, so a change to packages.core.src.lib.user.user_interface can break apps.order.src.app.app_service, while a change to apps.order.src.app.app_service can't break packages.core.src.lib.user.user_interface.
- Position
- Below the diagonal: apps.order.src.app.app_service uses a module listed above it, which is the healthy direction.
15→9 apps.order.src.app.app_service uses packages.models.src.order.create-order_dto✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.app_service uses a type in packages.models.src.order.create-order_dto.
- The types involved
apps.order.src.app.app_service.AppService→packages.models.src.order.create-order_dto.CreateOrderDto
- Direction
- apps.order.src.app.app_service uses packages.models.src.order.create-order_dto, so a change to packages.models.src.order.create-order_dto can break apps.order.src.app.app_service, while a change to apps.order.src.app.app_service can't break packages.models.src.order.create-order_dto.
- Position
- Below the diagonal: apps.order.src.app.app_service uses a module listed above it, which is the healthy direction.
16→4 apps.order.src.app.order.dto.admin-order-detail_dto uses apps.web.src.pages.admin.Dashboard✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.order.dto.admin-order-detail_dto uses a type in apps.web.src.pages.admin.Dashboard.
- The types involved
apps.order.src.app.order.dto.admin-order-detail_dto.AdminOrderDetailDto→apps.web.src.pages.admin.Dashboard.OrderStatus
- Direction
- apps.order.src.app.order.dto.admin-order-detail_dto uses apps.web.src.pages.admin.Dashboard, so a change to apps.web.src.pages.admin.Dashboard can break apps.order.src.app.order.dto.admin-order-detail_dto, while a change to apps.order.src.app.order.dto.admin-order-detail_dto can't break apps.web.src.pages.admin.Dashboard.
- Position
- Below the diagonal: apps.order.src.app.order.dto.admin-order-detail_dto uses a module listed above it, which is the healthy direction.
17→4 apps.order.src.app.order.dto.update-order-status_dto uses apps.web.src.pages.admin.Dashboard✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.order.dto.update-order-status_dto uses a type in apps.web.src.pages.admin.Dashboard.
- The types involved
apps.order.src.app.order.dto.update-order-status_dto.UpdateOrderStatusDto→apps.web.src.pages.admin.Dashboard.OrderStatus
- Direction
- apps.order.src.app.order.dto.update-order-status_dto uses apps.web.src.pages.admin.Dashboard, so a change to apps.web.src.pages.admin.Dashboard can break apps.order.src.app.order.dto.update-order-status_dto, while a change to apps.order.src.app.order.dto.update-order-status_dto can't break apps.web.src.pages.admin.Dashboard.
- Position
- Below the diagonal: apps.order.src.app.order.dto.update-order-status_dto uses a module listed above it, which is the healthy direction.
18→1 apps.web.src.hooks uses apps.order.src.app.order.dto.admin-order-counts_dto✕
- Connections
- 1 pair of types, where a type in apps.web.src.hooks uses a type in apps.order.src.app.order.dto.admin-order-counts_dto.
- The types involved
apps.web.src.hooks.useAdminOrders→apps.order.src.app.order.dto.admin-order-counts_dto.AdminOrderCountsDto
- Direction
- apps.web.src.hooks uses apps.order.src.app.order.dto.admin-order-counts_dto, so a change to apps.order.src.app.order.dto.admin-order-counts_dto can break apps.web.src.hooks, while a change to apps.web.src.hooks can't break apps.order.src.app.order.dto.admin-order-counts_dto.
- Position
- Below the diagonal: apps.web.src.hooks uses a module listed above it, which is the healthy direction.
18→2 apps.web.src.hooks uses apps.order.src.app.order.dto.admin-order-list_dto✕
- Connections
- 2 pairs of types, where a type in apps.web.src.hooks uses a type in apps.order.src.app.order.dto.admin-order-list_dto.
- The types involved
apps.web.src.hooks.useAdminOrders→apps.order.src.app.order.dto.admin-order-list_dto.AdminOrderListQueryDtoapps.web.src.hooks.useAdminOrders→apps.order.src.app.order.dto.admin-order-list_dto.AdminOrderListResponseDto
- Direction
- apps.web.src.hooks uses apps.order.src.app.order.dto.admin-order-list_dto, so a change to apps.order.src.app.order.dto.admin-order-list_dto can break apps.web.src.hooks, while a change to apps.web.src.hooks can't break apps.order.src.app.order.dto.admin-order-list_dto.
- Position
- Below the diagonal: apps.web.src.hooks uses a module listed above it, which is the healthy direction.
18→3 apps.web.src.hooks uses apps.order.src.app.order.dto.admin-stats_dto✕
- Connections
- 1 pair of types, where a type in apps.web.src.hooks uses a type in apps.order.src.app.order.dto.admin-stats_dto.
- The types involved
apps.web.src.hooks.useAdminOrders→apps.order.src.app.order.dto.admin-stats_dto.AdminStatsDto
- Direction
- apps.web.src.hooks uses apps.order.src.app.order.dto.admin-stats_dto, so a change to apps.order.src.app.order.dto.admin-stats_dto can break apps.web.src.hooks, while a change to apps.web.src.hooks can't break apps.order.src.app.order.dto.admin-stats_dto.
- Position
- Below the diagonal: apps.web.src.hooks uses a module listed above it, which is the healthy direction.
18→10 apps.web.src.hooks uses packages.models.src.product.product_dto✕
- Connections
- 1 pair of types, where a type in apps.web.src.hooks uses a type in packages.models.src.product.product_dto.
- The types involved
apps.web.src.hooks.useProduct→packages.models.src.product.product_dto.ProductDto
- Direction
- apps.web.src.hooks uses packages.models.src.product.product_dto, so a change to packages.models.src.product.product_dto can break apps.web.src.hooks, while a change to apps.web.src.hooks can't break packages.models.src.product.product_dto.
- Position
- Below the diagonal: apps.web.src.hooks uses a module listed above it, which is the healthy direction.
19→7 packages.db.src.lib.payment.payment-repository_service uses packages.db.src.lib.prisma_service✕
- Connections
- 1 pair of types, where a type in packages.db.src.lib.payment.payment-repository_service uses a type in packages.db.src.lib.prisma_service.
- The types involved
packages.db.src.lib.payment.payment-repository_service.PaymentRepositoryService→packages.db.src.lib.prisma_service.PrismaService
- Direction
- packages.db.src.lib.payment.payment-repository_service uses packages.db.src.lib.prisma_service, so a change to packages.db.src.lib.prisma_service can break packages.db.src.lib.payment.payment-repository_service, while a change to packages.db.src.lib.payment.payment-repository_service can't break packages.db.src.lib.prisma_service.
- Position
- Below the diagonal: packages.db.src.lib.payment.payment-repository_service uses a module listed above it, which is the healthy direction.
20→7 packages.db.src.lib.product.product-repository_service uses packages.db.src.lib.prisma_service✕
- Connections
- 1 pair of types, where a type in packages.db.src.lib.product.product-repository_service uses a type in packages.db.src.lib.prisma_service.
- The types involved
packages.db.src.lib.product.product-repository_service.ProductRepositoryService→packages.db.src.lib.prisma_service.PrismaService
- Direction
- packages.db.src.lib.product.product-repository_service uses packages.db.src.lib.prisma_service, so a change to packages.db.src.lib.prisma_service can break packages.db.src.lib.product.product-repository_service, while a change to packages.db.src.lib.product.product-repository_service can't break packages.db.src.lib.prisma_service.
- Position
- Below the diagonal: packages.db.src.lib.product.product-repository_service uses a module listed above it, which is the healthy direction.
20→10 packages.db.src.lib.product.product-repository_service uses packages.models.src.product.product_dto✕
- Connections
- 2 pairs of types, where a type in packages.db.src.lib.product.product-repository_service uses a type in packages.models.src.product.product_dto.
- The types involved
packages.db.src.lib.product.product-repository_service.ProductRepositoryService→packages.models.src.product.product_dto.ProductListResponseDtopackages.db.src.lib.product.product-repository_service.ProductRepositoryService→packages.models.src.product.product_dto.ProductStatus
- Direction
- packages.db.src.lib.product.product-repository_service uses packages.models.src.product.product_dto, so a change to packages.models.src.product.product_dto can break packages.db.src.lib.product.product-repository_service, while a change to packages.db.src.lib.product.product-repository_service can't break packages.models.src.product.product_dto.
- Position
- Below the diagonal: packages.db.src.lib.product.product-repository_service uses a module listed above it, which is the healthy direction.
21→7 packages.db.src.lib.user.user-repository_service uses packages.db.src.lib.prisma_service✕
- Connections
- 1 pair of types, where a type in packages.db.src.lib.user.user-repository_service uses a type in packages.db.src.lib.prisma_service.
- The types involved
packages.db.src.lib.user.user-repository_service.UserRepositoryService→packages.db.src.lib.prisma_service.PrismaService
- Direction
- packages.db.src.lib.user.user-repository_service uses packages.db.src.lib.prisma_service, so a change to packages.db.src.lib.prisma_service can break packages.db.src.lib.user.user-repository_service, while a change to packages.db.src.lib.user.user-repository_service can't break packages.db.src.lib.prisma_service.
- Position
- Below the diagonal: packages.db.src.lib.user.user-repository_service uses a module listed above it, which is the healthy direction.
21→11 packages.db.src.lib.user.user-repository_service uses packages.models.src.user.update-user_dto✕
- Connections
- 1 pair of types, where a type in packages.db.src.lib.user.user-repository_service uses a type in packages.models.src.user.update-user_dto.
- The types involved
packages.db.src.lib.user.user-repository_service.UserRepositoryService→packages.models.src.user.update-user_dto.UpdateUserDto
- Direction
- packages.db.src.lib.user.user-repository_service uses packages.models.src.user.update-user_dto, so a change to packages.models.src.user.update-user_dto can break packages.db.src.lib.user.user-repository_service, while a change to packages.db.src.lib.user.user-repository_service can't break packages.models.src.user.update-user_dto.
- Position
- Below the diagonal: packages.db.src.lib.user.user-repository_service uses a module listed above it, which is the healthy direction.
21→12 packages.db.src.lib.user.user-repository_service uses packages.models.src.user.user_dto✕
- Connections
- 1 pair of types, where a type in packages.db.src.lib.user.user-repository_service uses a type in packages.models.src.user.user_dto.
- The types involved
packages.db.src.lib.user.user-repository_service.UserRepositoryService→packages.models.src.user.user_dto.UserDto
- Direction
- packages.db.src.lib.user.user-repository_service uses packages.models.src.user.user_dto, so a change to packages.models.src.user.user_dto can break packages.db.src.lib.user.user-repository_service, while a change to packages.db.src.lib.user.user-repository_service can't break packages.models.src.user.user_dto.
- Position
- Below the diagonal: packages.db.src.lib.user.user-repository_service uses a module listed above it, which is the healthy direction.
22→8 packages.models.src.auth.auth_dto uses packages.models.src.auth.login_dto✕
- Connections
- 1 pair of types, where a type in packages.models.src.auth.auth_dto uses a type in packages.models.src.auth.login_dto.
- The types involved
packages.models.src.auth.auth_dto.AuthPayload→packages.models.src.auth.login_dto.AuthLoginDto
- Direction
- packages.models.src.auth.auth_dto uses packages.models.src.auth.login_dto, so a change to packages.models.src.auth.login_dto can break packages.models.src.auth.auth_dto, while a change to packages.models.src.auth.auth_dto can't break packages.models.src.auth.login_dto.
- Position
- Below the diagonal: packages.models.src.auth.auth_dto uses a module listed above it, which is the healthy direction.
22→12 packages.models.src.auth.auth_dto uses packages.models.src.user.user_dto✕
- Connections
- 1 pair of types, where a type in packages.models.src.auth.auth_dto uses a type in packages.models.src.user.user_dto.
- The types involved
packages.models.src.auth.auth_dto.AuthResponseDto→packages.models.src.user.user_dto.UserDto
- Direction
- packages.models.src.auth.auth_dto uses packages.models.src.user.user_dto, so a change to packages.models.src.user.user_dto can break packages.models.src.auth.auth_dto, while a change to packages.models.src.auth.auth_dto can't break packages.models.src.user.user_dto.
- Position
- Below the diagonal: packages.models.src.auth.auth_dto uses a module listed above it, which is the healthy direction.
23→4 packages.models.src.order.order_dto uses apps.web.src.pages.admin.Dashboard✕
- Connections
- 2 pairs of types, where a type in packages.models.src.order.order_dto uses a type in apps.web.src.pages.admin.Dashboard.
- The types involved
packages.models.src.order.order_dto.OrderDto→apps.web.src.pages.admin.Dashboard.OrderStatuspackages.models.src.order.order_dto.OrderStatusResponseDto→apps.web.src.pages.admin.Dashboard.OrderStatus
- Direction
- packages.models.src.order.order_dto uses apps.web.src.pages.admin.Dashboard, so a change to apps.web.src.pages.admin.Dashboard can break packages.models.src.order.order_dto, while a change to packages.models.src.order.order_dto can't break apps.web.src.pages.admin.Dashboard.
- Position
- Below the diagonal: packages.models.src.order.order_dto uses a module listed above it, which is the healthy direction.
24→13 packages.workflow-client.src.server uses packages.workflow-client.src.types✕
- Connections
- 3 pairs of types, where a type in packages.workflow-client.src.server uses a type in packages.workflow-client.src.types.
- The types involved
packages.workflow-client.src.server.response→packages.workflow-client.src.types.WorkflowEventpackages.workflow-client.src.server.temporal→packages.workflow-client.src.types.WorkflowEventpackages.workflow-client.src.server.temporal→packages.workflow-client.src.types.WorkflowExecutionStatus
- Direction
- packages.workflow-client.src.server uses packages.workflow-client.src.types, so a change to packages.workflow-client.src.types can break packages.workflow-client.src.server, while a change to packages.workflow-client.src.server can't break packages.workflow-client.src.types.
- Position
- Below the diagonal: packages.workflow-client.src.server uses a module listed above it, which is the healthy direction.
25→13 packages.workflow-client.src.session uses packages.workflow-client.src.types✕
- Connections
- 4 pairs of types, where a type in packages.workflow-client.src.session uses a type in packages.workflow-client.src.types.
- The types involved
packages.workflow-client.src.session.WorkflowSession→packages.workflow-client.src.types.WorkflowEventpackages.workflow-client.src.session.WorkflowSessionOptions→packages.workflow-client.src.types.WorkflowTransportpackages.workflow-client.src.session.WorkflowSessionSnapshot→packages.workflow-client.src.types.WorkflowExecutionStatuspackages.workflow-client.src.session.WorkflowSessionSnapshot→packages.workflow-client.src.types.WorkflowSessionStatus
- Direction
- packages.workflow-client.src.session uses packages.workflow-client.src.types, so a change to packages.workflow-client.src.types can break packages.workflow-client.src.session, while a change to packages.workflow-client.src.session can't break packages.workflow-client.src.types.
- Position
- Below the diagonal: packages.workflow-client.src.session uses a module listed above it, which is the healthy direction.
26→13 packages.workflow-client.src.transports uses packages.workflow-client.src.types✕
- Connections
- 7 pairs of types, where a type in packages.workflow-client.src.transports uses a type in packages.workflow-client.src.types.
- The types involved
packages.workflow-client.src.transports.fallback→packages.workflow-client.src.types.WorkflowEventpackages.workflow-client.src.transports.fallback→packages.workflow-client.src.types.WorkflowSubscribeOptionspackages.workflow-client.src.transports.fallback→packages.workflow-client.src.types.WorkflowTransportpackages.workflow-client.src.transports.http-stream→packages.workflow-client.src.types.WorkflowTransportpackages.workflow-client.src.transports.limited→packages.workflow-client.src.types.WorkflowTransportpackages.workflow-client.src.transports.polling→packages.workflow-client.src.types.WorkflowEventpackages.workflow-client.src.transports.polling→packages.workflow-client.src.types.WorkflowTransport
- Direction
- packages.workflow-client.src.transports uses packages.workflow-client.src.types, so a change to packages.workflow-client.src.types can break packages.workflow-client.src.transports, while a change to packages.workflow-client.src.transports can't break packages.workflow-client.src.types.
- Position
- Below the diagonal: packages.workflow-client.src.transports uses a module listed above it, which is the healthy direction.
27→8 apps.auth.src.app.app_controller uses packages.models.src.auth.login_dto✕
- Connections
- 2 pairs of types, where a type in apps.auth.src.app.app_controller uses a type in packages.models.src.auth.login_dto.
- The types involved
apps.auth.src.app.app_controller.AppController→packages.models.src.auth.login_dto.AuthLoginDtoapps.auth.src.app.app_controller.AppController→packages.models.src.auth.login_dto.AuthVerifyDto
- Direction
- apps.auth.src.app.app_controller uses packages.models.src.auth.login_dto, so a change to packages.models.src.auth.login_dto can break apps.auth.src.app.app_controller, while a change to apps.auth.src.app.app_controller can't break packages.models.src.auth.login_dto.
- Position
- Below the diagonal: apps.auth.src.app.app_controller uses a module listed above it, which is the healthy direction.
27→14 apps.auth.src.app.app_controller uses apps.auth.src.app.app_service✕
- Connections
- 1 pair of types, where a type in apps.auth.src.app.app_controller uses a type in apps.auth.src.app.app_service.
- The types involved
apps.auth.src.app.app_controller.AppController→apps.auth.src.app.app_service.AppService
- Direction
- apps.auth.src.app.app_controller uses apps.auth.src.app.app_service, so a change to apps.auth.src.app.app_service can break apps.auth.src.app.app_controller, while a change to apps.auth.src.app.app_controller can't break apps.auth.src.app.app_service.
- Position
- Below the diagonal: apps.auth.src.app.app_controller uses a module listed above it, which is the healthy direction.
28→6 apps.auth.src.app.user.user_service uses packages.core.src.lib.user.user_interface✕
- Connections
- 1 pair of types, where a type in apps.auth.src.app.user.user_service uses a type in packages.core.src.lib.user.user_interface.
- The types involved
apps.auth.src.app.user.user_service.UserService→packages.core.src.lib.user.user_interface.AuthUser
- Direction
- apps.auth.src.app.user.user_service uses packages.core.src.lib.user.user_interface, so a change to packages.core.src.lib.user.user_interface can break apps.auth.src.app.user.user_service, while a change to apps.auth.src.app.user.user_service can't break packages.core.src.lib.user.user_interface.
- Position
- Below the diagonal: apps.auth.src.app.user.user_service uses a module listed above it, which is the healthy direction.
28→11 apps.auth.src.app.user.user_service uses packages.models.src.user.update-user_dto✕
- Connections
- 1 pair of types, where a type in apps.auth.src.app.user.user_service uses a type in packages.models.src.user.update-user_dto.
- The types involved
apps.auth.src.app.user.user_service.UserService→packages.models.src.user.update-user_dto.UpdateUserDto
- Direction
- apps.auth.src.app.user.user_service uses packages.models.src.user.update-user_dto, so a change to packages.models.src.user.update-user_dto can break apps.auth.src.app.user.user_service, while a change to apps.auth.src.app.user.user_service can't break packages.models.src.user.update-user_dto.
- Position
- Below the diagonal: apps.auth.src.app.user.user_service uses a module listed above it, which is the healthy direction.
28→21 apps.auth.src.app.user.user_service uses packages.db.src.lib.user.user-repository_service✕
- Connections
- 1 pair of types, where a type in apps.auth.src.app.user.user_service uses a type in packages.db.src.lib.user.user-repository_service.
- The types involved
apps.auth.src.app.user.user_service.UserService→packages.db.src.lib.user.user-repository_service.UserRepositoryService
- Direction
- apps.auth.src.app.user.user_service uses packages.db.src.lib.user.user-repository_service, so a change to packages.db.src.lib.user.user-repository_service can break apps.auth.src.app.user.user_service, while a change to apps.auth.src.app.user.user_service can't break packages.db.src.lib.user.user-repository_service.
- Position
- Below the diagonal: apps.auth.src.app.user.user_service uses a module listed above it, which is the healthy direction.
29→1 apps.web.src.services uses apps.order.src.app.order.dto.admin-order-counts_dto✕
- Connections
- 1 pair of types, where a type in apps.web.src.services uses a type in apps.order.src.app.order.dto.admin-order-counts_dto.
- The types involved
apps.web.src.services.admin-orders→apps.order.src.app.order.dto.admin-order-counts_dto.AdminOrderCountsDto
- Direction
- apps.web.src.services uses apps.order.src.app.order.dto.admin-order-counts_dto, so a change to apps.order.src.app.order.dto.admin-order-counts_dto can break apps.web.src.services, while a change to apps.web.src.services can't break apps.order.src.app.order.dto.admin-order-counts_dto.
- Position
- Below the diagonal: apps.web.src.services uses a module listed above it, which is the healthy direction.
29→2 apps.web.src.services uses apps.order.src.app.order.dto.admin-order-list_dto✕
- Connections
- 2 pairs of types, where a type in apps.web.src.services uses a type in apps.order.src.app.order.dto.admin-order-list_dto.
- The types involved
apps.web.src.services.admin-orders→apps.order.src.app.order.dto.admin-order-list_dto.AdminOrderListQueryDtoapps.web.src.services.admin-orders→apps.order.src.app.order.dto.admin-order-list_dto.AdminOrderListResponseDto
- Direction
- apps.web.src.services uses apps.order.src.app.order.dto.admin-order-list_dto, so a change to apps.order.src.app.order.dto.admin-order-list_dto can break apps.web.src.services, while a change to apps.web.src.services can't break apps.order.src.app.order.dto.admin-order-list_dto.
- Position
- Below the diagonal: apps.web.src.services uses a module listed above it, which is the healthy direction.
29→3 apps.web.src.services uses apps.order.src.app.order.dto.admin-stats_dto✕
- Connections
- 1 pair of types, where a type in apps.web.src.services uses a type in apps.order.src.app.order.dto.admin-stats_dto.
- The types involved
apps.web.src.services.admin-orders→apps.order.src.app.order.dto.admin-stats_dto.AdminStatsDto
- Direction
- apps.web.src.services uses apps.order.src.app.order.dto.admin-stats_dto, so a change to apps.order.src.app.order.dto.admin-stats_dto can break apps.web.src.services, while a change to apps.web.src.services can't break apps.order.src.app.order.dto.admin-stats_dto.
- Position
- Below the diagonal: apps.web.src.services uses a module listed above it, which is the healthy direction.
29→16 apps.web.src.services uses apps.order.src.app.order.dto.admin-order-detail_dto✕
- Connections
- 1 pair of types, where a type in apps.web.src.services uses a type in apps.order.src.app.order.dto.admin-order-detail_dto.
- The types involved
apps.web.src.services.admin-orders→apps.order.src.app.order.dto.admin-order-detail_dto.AdminOrderDetailDto
- Direction
- apps.web.src.services uses apps.order.src.app.order.dto.admin-order-detail_dto, so a change to apps.order.src.app.order.dto.admin-order-detail_dto can break apps.web.src.services, while a change to apps.web.src.services can't break apps.order.src.app.order.dto.admin-order-detail_dto.
- Position
- Below the diagonal: apps.web.src.services uses a module listed above it, which is the healthy direction.
30→4 packages.db.src.lib.order.order-repository_service uses apps.web.src.pages.admin.Dashboard✕
- Connections
- 1 pair of types, where a type in packages.db.src.lib.order.order-repository_service uses a type in apps.web.src.pages.admin.Dashboard.
- The types involved
packages.db.src.lib.order.order-repository_service.OrderRepositoryService→apps.web.src.pages.admin.Dashboard.OrderStatus
- Direction
- packages.db.src.lib.order.order-repository_service uses apps.web.src.pages.admin.Dashboard, so a change to apps.web.src.pages.admin.Dashboard can break packages.db.src.lib.order.order-repository_service, while a change to packages.db.src.lib.order.order-repository_service can't break apps.web.src.pages.admin.Dashboard.
- Position
- Below the diagonal: packages.db.src.lib.order.order-repository_service uses a module listed above it, which is the healthy direction.
30→7 packages.db.src.lib.order.order-repository_service uses packages.db.src.lib.prisma_service✕
- Connections
- 1 pair of types, where a type in packages.db.src.lib.order.order-repository_service uses a type in packages.db.src.lib.prisma_service.
- The types involved
packages.db.src.lib.order.order-repository_service.OrderRepositoryService→packages.db.src.lib.prisma_service.PrismaService
- Direction
- packages.db.src.lib.order.order-repository_service uses packages.db.src.lib.prisma_service, so a change to packages.db.src.lib.prisma_service can break packages.db.src.lib.order.order-repository_service, while a change to packages.db.src.lib.order.order-repository_service can't break packages.db.src.lib.prisma_service.
- Position
- Below the diagonal: packages.db.src.lib.order.order-repository_service uses a module listed above it, which is the healthy direction.
30→9 packages.db.src.lib.order.order-repository_service uses packages.models.src.order.create-order_dto✕
- Connections
- 1 pair of types, where a type in packages.db.src.lib.order.order-repository_service uses a type in packages.models.src.order.create-order_dto.
- The types involved
packages.db.src.lib.order.order-repository_service.OrderRepositoryService→packages.models.src.order.create-order_dto.CreateOrderDto
- Direction
- packages.db.src.lib.order.order-repository_service uses packages.models.src.order.create-order_dto, so a change to packages.models.src.order.create-order_dto can break packages.db.src.lib.order.order-repository_service, while a change to packages.db.src.lib.order.order-repository_service can't break packages.models.src.order.create-order_dto.
- Position
- Below the diagonal: packages.db.src.lib.order.order-repository_service uses a module listed above it, which is the healthy direction.
30→23 packages.db.src.lib.order.order-repository_service uses packages.models.src.order.order_dto✕
- Connections
- 1 pair of types, where a type in packages.db.src.lib.order.order-repository_service uses a type in packages.models.src.order.order_dto.
- The types involved
packages.db.src.lib.order.order-repository_service.OrderRepositoryService→packages.models.src.order.order_dto.OrderDto
- Direction
- packages.db.src.lib.order.order-repository_service uses packages.models.src.order.order_dto, so a change to packages.models.src.order.order_dto can break packages.db.src.lib.order.order-repository_service, while a change to packages.db.src.lib.order.order-repository_service can't break packages.models.src.order.order_dto.
- Position
- Below the diagonal: packages.db.src.lib.order.order-repository_service uses a module listed above it, which is the healthy direction.
31→23 packages.models.src.order.order-summary_dto uses packages.models.src.order.order_dto✕
- Connections
- 1 pair of types, where a type in packages.models.src.order.order-summary_dto uses a type in packages.models.src.order.order_dto.
- The types involved
packages.models.src.order.order-summary_dto.OrderSummaryDto→packages.models.src.order.order_dto.OrderDto
- Direction
- packages.models.src.order.order-summary_dto uses packages.models.src.order.order_dto, so a change to packages.models.src.order.order_dto can break packages.models.src.order.order-summary_dto, while a change to packages.models.src.order.order-summary_dto can't break packages.models.src.order.order_dto.
- Position
- Below the diagonal: packages.models.src.order.order-summary_dto uses a module listed above it, which is the healthy direction.
32→13 packages.workflow-client.src.registry uses packages.workflow-client.src.types✕
- Connections
- 1 pair of types, where a type in packages.workflow-client.src.registry uses a type in packages.workflow-client.src.types.
- The types involved
packages.workflow-client.src.registry.WorkflowRegistryOptions→packages.workflow-client.src.types.WorkflowTransport
- Direction
- packages.workflow-client.src.registry uses packages.workflow-client.src.types, so a change to packages.workflow-client.src.types can break packages.workflow-client.src.registry, while a change to packages.workflow-client.src.registry can't break packages.workflow-client.src.types.
- Position
- Below the diagonal: packages.workflow-client.src.registry uses a module listed above it, which is the healthy direction.
32→25 packages.workflow-client.src.registry uses packages.workflow-client.src.session✕
- Connections
- 3 pairs of types, where a type in packages.workflow-client.src.registry uses a type in packages.workflow-client.src.session.
- The types involved
packages.workflow-client.src.registry.WorkflowRegistry→packages.workflow-client.src.session.WorkflowSessionpackages.workflow-client.src.registry.WorkflowRegistry→packages.workflow-client.src.session.WorkflowSessionSnapshotpackages.workflow-client.src.registry.WorkflowRegistryOptions→packages.workflow-client.src.session.WorkflowReconnectOptions
- Direction
- packages.workflow-client.src.registry uses packages.workflow-client.src.session, so a change to packages.workflow-client.src.session can break packages.workflow-client.src.registry, while a change to packages.workflow-client.src.registry can't break packages.workflow-client.src.session.
- Position
- Below the diagonal: packages.workflow-client.src.registry uses a module listed above it, which is the healthy direction.
33→28 apps.auth.src.app.activities.activities_service uses apps.auth.src.app.user.user_service✕
- Connections
- 1 pair of types, where a type in apps.auth.src.app.activities.activities_service uses a type in apps.auth.src.app.user.user_service.
- The types involved
apps.auth.src.app.activities.activities_service.ActivitiesService→apps.auth.src.app.user.user_service.UserService
- Direction
- apps.auth.src.app.activities.activities_service uses apps.auth.src.app.user.user_service, so a change to apps.auth.src.app.user.user_service can break apps.auth.src.app.activities.activities_service, while a change to apps.auth.src.app.activities.activities_service can't break apps.auth.src.app.user.user_service.
- Position
- Below the diagonal: apps.auth.src.app.activities.activities_service uses a module listed above it, which is the healthy direction.
34→6 apps.auth.src.app.user.user_controller uses packages.core.src.lib.user.user_interface✕
- Connections
- 1 pair of types, where a type in apps.auth.src.app.user.user_controller uses a type in packages.core.src.lib.user.user_interface.
- The types involved
apps.auth.src.app.user.user_controller.UserController→packages.core.src.lib.user.user_interface.AuthUser
- Direction
- apps.auth.src.app.user.user_controller uses packages.core.src.lib.user.user_interface, so a change to packages.core.src.lib.user.user_interface can break apps.auth.src.app.user.user_controller, while a change to apps.auth.src.app.user.user_controller can't break packages.core.src.lib.user.user_interface.
- Position
- Below the diagonal: apps.auth.src.app.user.user_controller uses a module listed above it, which is the healthy direction.
34→11 apps.auth.src.app.user.user_controller uses packages.models.src.user.update-user_dto✕
- Connections
- 1 pair of types, where a type in apps.auth.src.app.user.user_controller uses a type in packages.models.src.user.update-user_dto.
- The types involved
apps.auth.src.app.user.user_controller.UserController→packages.models.src.user.update-user_dto.UpdateUserDto
- Direction
- apps.auth.src.app.user.user_controller uses packages.models.src.user.update-user_dto, so a change to packages.models.src.user.update-user_dto can break apps.auth.src.app.user.user_controller, while a change to apps.auth.src.app.user.user_controller can't break packages.models.src.user.update-user_dto.
- Position
- Below the diagonal: apps.auth.src.app.user.user_controller uses a module listed above it, which is the healthy direction.
34→28 apps.auth.src.app.user.user_controller uses apps.auth.src.app.user.user_service✕
- Connections
- 1 pair of types, where a type in apps.auth.src.app.user.user_controller uses a type in apps.auth.src.app.user.user_service.
- The types involved
apps.auth.src.app.user.user_controller.UserController→apps.auth.src.app.user.user_service.UserService
- Direction
- apps.auth.src.app.user.user_controller uses apps.auth.src.app.user.user_service, so a change to apps.auth.src.app.user.user_service can break apps.auth.src.app.user.user_controller, while a change to apps.auth.src.app.user.user_controller can't break apps.auth.src.app.user.user_service.
- Position
- Below the diagonal: apps.auth.src.app.user.user_controller uses a module listed above it, which is the healthy direction.
35→1 apps.order.src.app.order.order_service uses apps.order.src.app.order.dto.admin-order-counts_dto✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.order.order_service uses a type in apps.order.src.app.order.dto.admin-order-counts_dto.
- The types involved
apps.order.src.app.order.order_service.OrderService→apps.order.src.app.order.dto.admin-order-counts_dto.AdminOrderCountsDto
- Direction
- apps.order.src.app.order.order_service uses apps.order.src.app.order.dto.admin-order-counts_dto, so a change to apps.order.src.app.order.dto.admin-order-counts_dto can break apps.order.src.app.order.order_service, while a change to apps.order.src.app.order.order_service can't break apps.order.src.app.order.dto.admin-order-counts_dto.
- Position
- Below the diagonal: apps.order.src.app.order.order_service uses a module listed above it, which is the healthy direction.
35→2 apps.order.src.app.order.order_service uses apps.order.src.app.order.dto.admin-order-list_dto✕
- Connections
- 2 pairs of types, where a type in apps.order.src.app.order.order_service uses a type in apps.order.src.app.order.dto.admin-order-list_dto.
- The types involved
apps.order.src.app.order.order_service.OrderService→apps.order.src.app.order.dto.admin-order-list_dto.AdminOrderListQueryDtoapps.order.src.app.order.order_service.OrderService→apps.order.src.app.order.dto.admin-order-list_dto.AdminOrderListResponseDto
- Direction
- apps.order.src.app.order.order_service uses apps.order.src.app.order.dto.admin-order-list_dto, so a change to apps.order.src.app.order.dto.admin-order-list_dto can break apps.order.src.app.order.order_service, while a change to apps.order.src.app.order.order_service can't break apps.order.src.app.order.dto.admin-order-list_dto.
- Position
- Below the diagonal: apps.order.src.app.order.order_service uses a module listed above it, which is the healthy direction.
35→3 apps.order.src.app.order.order_service uses apps.order.src.app.order.dto.admin-stats_dto✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.order.order_service uses a type in apps.order.src.app.order.dto.admin-stats_dto.
- The types involved
apps.order.src.app.order.order_service.OrderService→apps.order.src.app.order.dto.admin-stats_dto.AdminStatsDto
- Direction
- apps.order.src.app.order.order_service uses apps.order.src.app.order.dto.admin-stats_dto, so a change to apps.order.src.app.order.dto.admin-stats_dto can break apps.order.src.app.order.order_service, while a change to apps.order.src.app.order.order_service can't break apps.order.src.app.order.dto.admin-stats_dto.
- Position
- Below the diagonal: apps.order.src.app.order.order_service uses a module listed above it, which is the healthy direction.
35→4 apps.order.src.app.order.order_service uses apps.web.src.pages.admin.Dashboard✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.order.order_service uses a type in apps.web.src.pages.admin.Dashboard.
- The types involved
apps.order.src.app.order.order_service.OrderService→apps.web.src.pages.admin.Dashboard.OrderStatus
- Direction
- apps.order.src.app.order.order_service uses apps.web.src.pages.admin.Dashboard, so a change to apps.web.src.pages.admin.Dashboard can break apps.order.src.app.order.order_service, while a change to apps.order.src.app.order.order_service can't break apps.web.src.pages.admin.Dashboard.
- Position
- Below the diagonal: apps.order.src.app.order.order_service uses a module listed above it, which is the healthy direction.
35→7 apps.order.src.app.order.order_service uses packages.db.src.lib.prisma_service✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.order.order_service uses a type in packages.db.src.lib.prisma_service.
- The types involved
apps.order.src.app.order.order_service.OrderService→packages.db.src.lib.prisma_service.PrismaService
- Direction
- apps.order.src.app.order.order_service uses packages.db.src.lib.prisma_service, so a change to packages.db.src.lib.prisma_service can break apps.order.src.app.order.order_service, while a change to apps.order.src.app.order.order_service can't break packages.db.src.lib.prisma_service.
- Position
- Below the diagonal: apps.order.src.app.order.order_service uses a module listed above it, which is the healthy direction.
35→16 apps.order.src.app.order.order_service uses apps.order.src.app.order.dto.admin-order-detail_dto✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.order.order_service uses a type in apps.order.src.app.order.dto.admin-order-detail_dto.
- The types involved
apps.order.src.app.order.order_service.OrderService→apps.order.src.app.order.dto.admin-order-detail_dto.AdminOrderDetailDto
- Direction
- apps.order.src.app.order.order_service uses apps.order.src.app.order.dto.admin-order-detail_dto, so a change to apps.order.src.app.order.dto.admin-order-detail_dto can break apps.order.src.app.order.order_service, while a change to apps.order.src.app.order.order_service can't break apps.order.src.app.order.dto.admin-order-detail_dto.
- Position
- Below the diagonal: apps.order.src.app.order.order_service uses a module listed above it, which is the healthy direction.
35→19 apps.order.src.app.order.order_service uses packages.db.src.lib.payment.payment-repository_service✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.order.order_service uses a type in packages.db.src.lib.payment.payment-repository_service.
- The types involved
apps.order.src.app.order.order_service.OrderService→packages.db.src.lib.payment.payment-repository_service.PaymentRepositoryService
- Direction
- apps.order.src.app.order.order_service uses packages.db.src.lib.payment.payment-repository_service, so a change to packages.db.src.lib.payment.payment-repository_service can break apps.order.src.app.order.order_service, while a change to apps.order.src.app.order.order_service can't break packages.db.src.lib.payment.payment-repository_service.
- Position
- Below the diagonal: apps.order.src.app.order.order_service uses a module listed above it, which is the healthy direction.
35→30 apps.order.src.app.order.order_service uses packages.db.src.lib.order.order-repository_service✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.order.order_service uses a type in packages.db.src.lib.order.order-repository_service.
- The types involved
apps.order.src.app.order.order_service.OrderService→packages.db.src.lib.order.order-repository_service.OrderRepositoryService
- Direction
- apps.order.src.app.order.order_service uses packages.db.src.lib.order.order-repository_service, so a change to packages.db.src.lib.order.order-repository_service can break apps.order.src.app.order.order_service, while a change to apps.order.src.app.order.order_service can't break packages.db.src.lib.order.order-repository_service.
- Position
- Below the diagonal: apps.order.src.app.order.order_service uses a module listed above it, which is the healthy direction.
35→31 apps.order.src.app.order.order_service uses packages.models.src.order.order-summary_dto✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.order.order_service uses a type in packages.models.src.order.order-summary_dto.
- The types involved
apps.order.src.app.order.order_service.OrderService→packages.models.src.order.order-summary_dto.OrderSummaryDto
- Direction
- apps.order.src.app.order.order_service uses packages.models.src.order.order-summary_dto, so a change to packages.models.src.order.order-summary_dto can break apps.order.src.app.order.order_service, while a change to apps.order.src.app.order.order_service can't break packages.models.src.order.order-summary_dto.
- Position
- Below the diagonal: apps.order.src.app.order.order_service uses a module listed above it, which is the healthy direction.
36→25 packages.workflow-client.src.client uses packages.workflow-client.src.session✕
- Connections
- 2 pairs of types, where a type in packages.workflow-client.src.client uses a type in packages.workflow-client.src.session.
- The types involved
packages.workflow-client.src.client.WorkflowDefinition→packages.workflow-client.src.session.WorkflowReconnectOptionspackages.workflow-client.src.client.WorkflowDefinition→packages.workflow-client.src.session.WorkflowSessionSnapshot
- Direction
- packages.workflow-client.src.client uses packages.workflow-client.src.session, so a change to packages.workflow-client.src.session can break packages.workflow-client.src.client, while a change to packages.workflow-client.src.client can't break packages.workflow-client.src.session.
- Position
- Below the diagonal: packages.workflow-client.src.client uses a module listed above it, which is the healthy direction.
36→32 packages.workflow-client.src.client uses packages.workflow-client.src.registry✕
- Connections
- 1 pair of types, where a type in packages.workflow-client.src.client uses a type in packages.workflow-client.src.registry.
- The types involved
packages.workflow-client.src.client.WorkflowClientOptions→packages.workflow-client.src.registry.WorkflowStorage
- Direction
- packages.workflow-client.src.client uses packages.workflow-client.src.registry, so a change to packages.workflow-client.src.registry can break packages.workflow-client.src.client, while a change to packages.workflow-client.src.client can't break packages.workflow-client.src.registry.
- Position
- Below the diagonal: packages.workflow-client.src.client uses a module listed above it, which is the healthy direction.
37→6 apps.order.src.app.app_controller uses packages.core.src.lib.user.user_interface✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.app_controller uses a type in packages.core.src.lib.user.user_interface.
- The types involved
apps.order.src.app.app_controller.AppController→packages.core.src.lib.user.user_interface.AuthUser
- Direction
- apps.order.src.app.app_controller uses packages.core.src.lib.user.user_interface, so a change to packages.core.src.lib.user.user_interface can break apps.order.src.app.app_controller, while a change to apps.order.src.app.app_controller can't break packages.core.src.lib.user.user_interface.
- Position
- Below the diagonal: apps.order.src.app.app_controller uses a module listed above it, which is the healthy direction.
37→9 apps.order.src.app.app_controller uses packages.models.src.order.create-order_dto✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.app_controller uses a type in packages.models.src.order.create-order_dto.
- The types involved
apps.order.src.app.app_controller.AppController→packages.models.src.order.create-order_dto.CreateOrderDto
- Direction
- apps.order.src.app.app_controller uses packages.models.src.order.create-order_dto, so a change to packages.models.src.order.create-order_dto can break apps.order.src.app.app_controller, while a change to apps.order.src.app.app_controller can't break packages.models.src.order.create-order_dto.
- Position
- Below the diagonal: apps.order.src.app.app_controller uses a module listed above it, which is the healthy direction.
37→14 apps.order.src.app.app_controller uses apps.auth.src.app.app_service✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.app_controller uses a type in apps.auth.src.app.app_service.
- The types involved
apps.order.src.app.app_controller.AppController→apps.auth.src.app.app_service.AppService
- Direction
- apps.order.src.app.app_controller uses apps.auth.src.app.app_service, so a change to apps.auth.src.app.app_service can break apps.order.src.app.app_controller, while a change to apps.order.src.app.app_controller can't break apps.auth.src.app.app_service.
- Position
- Below the diagonal: apps.order.src.app.app_controller uses a module listed above it, which is the healthy direction.
37→35 apps.order.src.app.app_controller uses apps.order.src.app.order.order_service✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.app_controller uses a type in apps.order.src.app.order.order_service.
- The types involved
apps.order.src.app.app_controller.AppController→apps.order.src.app.order.order_service.OrderService
- Direction
- apps.order.src.app.app_controller uses apps.order.src.app.order.order_service, so a change to apps.order.src.app.order.order_service can break apps.order.src.app.app_controller, while a change to apps.order.src.app.app_controller can't break apps.order.src.app.order.order_service.
- Position
- Below the diagonal: apps.order.src.app.app_controller uses a module listed above it, which is the healthy direction.
38→1 apps.order.src.app.order.order-admin_controller uses apps.order.src.app.order.dto.admin-order-counts_dto✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.order.order-admin_controller uses a type in apps.order.src.app.order.dto.admin-order-counts_dto.
- The types involved
apps.order.src.app.order.order-admin_controller.OrderAdminController→apps.order.src.app.order.dto.admin-order-counts_dto.AdminOrderCountsDto
- Direction
- apps.order.src.app.order.order-admin_controller uses apps.order.src.app.order.dto.admin-order-counts_dto, so a change to apps.order.src.app.order.dto.admin-order-counts_dto can break apps.order.src.app.order.order-admin_controller, while a change to apps.order.src.app.order.order-admin_controller can't break apps.order.src.app.order.dto.admin-order-counts_dto.
- Position
- Below the diagonal: apps.order.src.app.order.order-admin_controller uses a module listed above it, which is the healthy direction.
38→2 apps.order.src.app.order.order-admin_controller uses apps.order.src.app.order.dto.admin-order-list_dto✕
- Connections
- 2 pairs of types, where a type in apps.order.src.app.order.order-admin_controller uses a type in apps.order.src.app.order.dto.admin-order-list_dto.
- The types involved
apps.order.src.app.order.order-admin_controller.OrderAdminController→apps.order.src.app.order.dto.admin-order-list_dto.AdminOrderListQueryDtoapps.order.src.app.order.order-admin_controller.OrderAdminController→apps.order.src.app.order.dto.admin-order-list_dto.AdminOrderListResponseDto
- Direction
- apps.order.src.app.order.order-admin_controller uses apps.order.src.app.order.dto.admin-order-list_dto, so a change to apps.order.src.app.order.dto.admin-order-list_dto can break apps.order.src.app.order.order-admin_controller, while a change to apps.order.src.app.order.order-admin_controller can't break apps.order.src.app.order.dto.admin-order-list_dto.
- Position
- Below the diagonal: apps.order.src.app.order.order-admin_controller uses a module listed above it, which is the healthy direction.
38→3 apps.order.src.app.order.order-admin_controller uses apps.order.src.app.order.dto.admin-stats_dto✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.order.order-admin_controller uses a type in apps.order.src.app.order.dto.admin-stats_dto.
- The types involved
apps.order.src.app.order.order-admin_controller.OrderAdminController→apps.order.src.app.order.dto.admin-stats_dto.AdminStatsDto
- Direction
- apps.order.src.app.order.order-admin_controller uses apps.order.src.app.order.dto.admin-stats_dto, so a change to apps.order.src.app.order.dto.admin-stats_dto can break apps.order.src.app.order.order-admin_controller, while a change to apps.order.src.app.order.order-admin_controller can't break apps.order.src.app.order.dto.admin-stats_dto.
- Position
- Below the diagonal: apps.order.src.app.order.order-admin_controller uses a module listed above it, which is the healthy direction.
38→16 apps.order.src.app.order.order-admin_controller uses apps.order.src.app.order.dto.admin-order-detail_dto✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.order.order-admin_controller uses a type in apps.order.src.app.order.dto.admin-order-detail_dto.
- The types involved
apps.order.src.app.order.order-admin_controller.OrderAdminController→apps.order.src.app.order.dto.admin-order-detail_dto.AdminOrderDetailDto
- Direction
- apps.order.src.app.order.order-admin_controller uses apps.order.src.app.order.dto.admin-order-detail_dto, so a change to apps.order.src.app.order.dto.admin-order-detail_dto can break apps.order.src.app.order.order-admin_controller, while a change to apps.order.src.app.order.order-admin_controller can't break apps.order.src.app.order.dto.admin-order-detail_dto.
- Position
- Below the diagonal: apps.order.src.app.order.order-admin_controller uses a module listed above it, which is the healthy direction.
38→17 apps.order.src.app.order.order-admin_controller uses apps.order.src.app.order.dto.update-order-status_dto✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.order.order-admin_controller uses a type in apps.order.src.app.order.dto.update-order-status_dto.
- The types involved
apps.order.src.app.order.order-admin_controller.OrderAdminController→apps.order.src.app.order.dto.update-order-status_dto.UpdateOrderStatusDto
- Direction
- apps.order.src.app.order.order-admin_controller uses apps.order.src.app.order.dto.update-order-status_dto, so a change to apps.order.src.app.order.dto.update-order-status_dto can break apps.order.src.app.order.order-admin_controller, while a change to apps.order.src.app.order.order-admin_controller can't break apps.order.src.app.order.dto.update-order-status_dto.
- Position
- Below the diagonal: apps.order.src.app.order.order-admin_controller uses a module listed above it, which is the healthy direction.
38→35 apps.order.src.app.order.order-admin_controller uses apps.order.src.app.order.order_service✕
- Connections
- 1 pair of types, where a type in apps.order.src.app.order.order-admin_controller uses a type in apps.order.src.app.order.order_service.
- The types involved
apps.order.src.app.order.order-admin_controller.OrderAdminController→apps.order.src.app.order.order_service.OrderService
- Direction
- apps.order.src.app.order.order-admin_controller uses apps.order.src.app.order.order_service, so a change to apps.order.src.app.order.order_service can break apps.order.src.app.order.order-admin_controller, while a change to apps.order.src.app.order.order-admin_controller can't break apps.order.src.app.order.order_service.
- Position
- Below the diagonal: apps.order.src.app.order.order-admin_controller uses a module listed above it, which is the healthy direction.
39→36 packages.workflow-client.src uses packages.workflow-client.src.client✕
- Connections
- 1 pair of types, where a type in packages.workflow-client.src uses a type in packages.workflow-client.src.client.
- The types involved
packages.workflow-client.src.client→packages.workflow-client.src.client.WorkflowDefinition
- Direction
- packages.workflow-client.src uses packages.workflow-client.src.client, so a change to packages.workflow-client.src.client can break packages.workflow-client.src, while a change to packages.workflow-client.src can't break packages.workflow-client.src.client.
- Position
- Below the diagonal: packages.workflow-client.src uses a module listed above it, which is the healthy direction.
40→36 packages.workflows.src.lib uses packages.workflow-client.src.client✕
- Connections
- 1 pair of types, where a type in packages.workflows.src.lib uses a type in packages.workflow-client.src.client.
- The types involved
packages.workflows.src.lib.workflow.utils→packages.workflow-client.src.client.WorkflowClient
- Direction
- packages.workflows.src.lib uses packages.workflow-client.src.client, so a change to packages.workflow-client.src.client can break packages.workflows.src.lib, while a change to packages.workflows.src.lib can't break packages.workflow-client.src.client.
- Position
- Below the diagonal: packages.workflows.src.lib 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 — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 76 | High / Critical |
| A05:2025 — Injection | 17 | High / Critical |
| A02:2025 — Security Misconfiguration | 11 | High / Critical |
| A07:2025 — Authentication Failures | 6 | High / Critical |
Roadmap
Top priorities: Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3); Resolve the 6 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (6); 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3). | +11.0 pts | Low | Secret Scanning |
| Resolve the 6 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (6). | +8.6 pts | Low | Dependency Hygiene |
| Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with order.service.spec.ts. | +4.6 pts | Low | Test Quality |
| 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. | +4.9 pts | Medium | Security & performance tooling |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +4.9 pts | Medium | DR & Backup |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +4.9 pts | Medium | Dependency Hygiene |
| Resolve the 1 Outdated (npm) finding(s) in Dependency Hygiene — start with REDACTED. | +1.4 pts | Low | Dependency Hygiene |
| Enforce accessibility in the toolchain you already use: enable Biome's a11y rule group in your biome.json `linter.rules` (it is off whenever `recommended` is false and the group is unlisted), then assert with @axe-core/playwright in tests, then gate axe/pa11y/Lighthouse in CI. | +1.5 pts | Medium | A11y enforcement |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 0.6 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.6 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.1 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| apps/order/src/app/order/order.service.ts | 6.0 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| turbo/generators/config.ts | 6.4 | Mixed | Cyclomatic Complexity: config.generator (cyclomatic 34) |
| REDACTED | 6.7 | Mixed | Dependency Hygiene: Deprecated: @oslojs/crypto |
| apps/web/src/pages/admin/Orders.tsx | 6.7 | Mixed | Cyclomatic Complexity: Orders.AdminOrdersPage (cyclomatic 64) |
| apps/order/src/workflows/order.workflow.ts | 6.7 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| apps/web/src/pages/MarketplacePage.tsx | 7.2 | Mixed | Cyclomatic Complexity: MarketplacePage.MarketplacePage (cyclomatic 22) |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| packages/cli/src/commands/generate.ts | 7.4 | Mixed | Cyclomatic Complexity: generate.generateService (cyclomatic 38) |
| packages/cli/src/commands/init.ts | 7.4 | Mixed | Cyclomatic Complexity: init.initCommand (cyclomatic 21) |
| apps/web/src/pages/ProductDetailPage.tsx | 7.4 | Mixed | Cyclomatic Complexity: ProductDetailPage.ProductDetailPage (cyclomatic 17) |
| apps/order/src/workflows/process-payment.workflow.ts | 7.8 | Mixed | Cyclomatic Complexity: process-payment.workflow.processPayment (cyclomatic 26) |
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 87 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 — 87 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, 405 of 449 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 apps/auth/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), 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. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI 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 apps/auth/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), 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 jest suite in apps/auth/ was NOT MEASURED: the dependency install for apps/auth/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), 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.
- 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 jest suite in apps/order/ was NOT MEASURED: the dependency install for apps/order/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), 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.
- 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 jest suite in apps/product/ was NOT MEASURED: the dependency install for apps/product/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), 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.
- 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 packages/payment/ was NOT MEASURED: the dependency install for packages/payment/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), 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.
- 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 packages/ui/ was NOT MEASURED: the dependency install for packages/ui/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), 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.
- 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 packages/workflow-client/ was NOT MEASURED: the dependency install for packages/workflow-client/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), 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-contributor repository — bus factor is not applicable (1 contributor(s) across 67 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `.agents/skills/temporal-playground/ui/src/types/index.ts`, `apps/web/react-router.config.ts`, `apps/web/src/routes.tsx`, `packages/core/.gitignore`, `packages/core/src/lib/order/workflow.utils.ts`, … (+8 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 14 — a file the compose project references is missing) — time="2026-11-09T10:04:53Z" level=warning msg="The \"POSTGRES_PASSWORD\" variable is not set. Defaulting to a blank string." env file .env not found: stat .env: no such file or directory; runtime evidence skipped.
- 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. 25 further occurrence(s) are not listed individually; the score already reflects all 65.
- R4 Test Coverage — 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. 69 further occurrence(s) are not listed individually; the score already reflects all 109.
- 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. 1 further occurrence(s) are not listed individually; the score already reflects all 41.
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.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality 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.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- 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.
- 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
11 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Orders.AdminOrdersPage at 64.
What to do
- Bring the 3 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with Orders.AdminOrdersPage (cyclomatic 64), generate.generateService (cyclomatic 38), config.generator (cyclomatic 34). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 7.6 to about 8.4/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
18 method(s) exceeded the cognitive complexity threshold of 15; the worst was Orders.AdminOrdersPage at 53.
What to do
- Bring the 4 bodies over 30 down to 30 or less in Cognitive Complexity — start with Orders.AdminOrdersPage (cognitive 53), generate.generateService (cognitive 51), OrderService.getOrderSummaryById (cognitive 34). — 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 4 together lifts Cognitive Complexity from 6.7 to about 7.5/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
20 god class(es) detected.
What to do
- Resolve the 16 FunctionTooLong finding(s) in God Classes — start with Orders.tsx, Dashboard.tsx, config.ts. — One of this dimension's main actionable groups (16 warning-level).
- Resolve the 3 FileTooLong finding(s) in God Classes — start with Orders.tsx, Dashboard.tsx, MarketplacePage.tsx. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with ProductDetailPage.tsx. — 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.
D5 · Coupling
14 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 5 module(s) off the main sequence, with abstractness counted on 13 of the 14 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 5 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 20 classes have LCOM4 above 3.
D9 · Test Distribution
185 test methods: 185 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 185 `it`/`test` case(s) across 28 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 2 zero-assertion, 1 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 185 tests.
What to do
- Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with order.service.spec.ts. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 No assertions finding(s) in Test Quality — start with Navigation.spec.tsx. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Fixed-sleep synchronisation finding(s) in Test Quality — start with transports.spec.ts. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D12 · Dependency Hygiene
23 outdated direct production npm dependency(ies) of 78 graded, 0 pinning defect(s), across 15 REDACTED (15 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 4 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 6 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Outdated (npm) finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Enforce Secret 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 681 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 681 package(s) this repository's committed lockfile installs for a consumer — its 78 production, optional and peer dependency(ies), across 15 product REDACTED manifest(s), and everything those install in turn. Its 194 `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 / UNLICENSED, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: packages/workflow-client/src/react/useWorkflow.ts (3×18=54); apps/order/src/workflows/process-payment.workflow.ts (2×26=52); apps/order/src/workflows/order.workflow.ts (3×15=45)
What to do
- Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with useWorkflow.ts, process-payment.workflow.ts, order.workflow.ts. — One of this dimension's main actionable groups (4 warning-level).
D17 · Explicit Debt
6 deducted task-comment markers across 21233 LoC (0.0/KLoC) → score 9.9. 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.
What to do
- Resolve the 6 TodoComment finding(s) in Explicit Debt — start with order.service.ts (4), order.workflow.ts, login.workflow.ts. — One of this dimension's main actionable groups (6 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 19 document(s) read across 18 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
2 domain type(s) cross context boundaries across 13 contexts; they are measured and withheld (not published, not scored). Contexts: auth, cli, core, db, email, models, order, payment, product, ui, web, workflow-client and 1 more.
D24 · Comment Value
16 of 305 judged comments only repeat the code they sit on (5.2 %). 4 comment(s) in another language or script were not judged.
What to do
- Resolve the 11 redundant comment finding(s) in Comment Value — start with order.service.ts (4), seed.ts (2), config.ts (2). — One of this dimension's main actionable groups (11 recommendation-level).
D26 · Project Cohesion
1 of 15 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
30 % of calls cross a namespace and 3 % go through an interface, but 61 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
2 finding(s): 0 critical, 2 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 2 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED. — 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)
17 finding(s): 0 critical, 3 high, 14 medium, 0 low. semgrep hit a parse error in 15 file(s) — `.agents/skills/temporal-playground/ui/src/types/index.ts` (line 1, line 2, line 3, …), `apps/web/react-router.config.ts` (line 10), `apps/web/src/routes.tsx` (line 52), `packages/core/.gitignore` (line 1, line 2, line 3, …), `packages/core/src/lib/order/workflow.utils.ts` (line 91), … (+10 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.
What to do
- 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).
- 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
72 finding(s): 2 critical, 43 high, 22 medium, 5 low.
What to do
- Resolve the 43 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (25), REDACTED (18). — One of this dimension's main actionable groups (43 issue-level).
- Resolve the 21 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (15), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (21 warning-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
D31 · IaC & Container Security
11 finding(s): 0 critical, 3 high, 8 medium, 0 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 8 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED (2). — One of this dimension's main actionable groups (8 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 78 of the 351 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/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).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
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 1 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
AC1 · Text alternatives
AC2 · Forms & labels
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×11) — .agents/skills/temporal-playground/ui/src/components/canvas/ActivityPicker.tsx:99, .agents/skills/temporal-playground/ui/src/components/canvas/NodeDetailPanel.tsx:312, .agents/skills/temporal-playground/ui/src/components/canvas/NodeDetailPanel.tsx:329, …
- This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×4) — .agents/skills/temporal-playground/ui/src/components/canvas/NodeDetailPanel.tsx:271, .agents/skills/temporal-playground/ui/src/components/canvas/ParamsEditor.tsx:275, .agents/skills/temporal-playground/ui/src/nodes/NodeField.tsx:34, …
- A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×2) — .agents/skills/temporal-playground/ui/src/components/canvas/ParamsEditor.tsx:285, apps/web/src/pages/MarketplacePage.tsx:607
- This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. — apps/web/src/pages/LoginPage.tsx:153
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×4) — apps/web/src/pages/OrderSummary.tsx:109, apps/web/src/pages/ShoppingCard.tsx:82, apps/web/src/pages/admin/Dashboard.tsx:500, …
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — packages/ui/src/lib/drawers/ShoppingCartContent.tsx:45
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×9) — .agents/skills/temporal-playground/ui/src/components/canvas/ActivityPicker.tsx:99, .agents/skills/temporal-playground/ui/src/components/canvas/NodeDetailPanel.tsx:329, .agents/skills/temporal-playground/ui/src/components/canvas/NodeDetailPanel.tsx:347, …
- <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×2) — .agents/skills/temporal-playground/ui/src/components/canvas/NodeDetailPanel.tsx:271, apps/web/src/pages/MarketplacePage.tsx:408
- <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×2) — .agents/skills/temporal-playground/ui/src/components/canvas/NodeDetailPanel.tsx:312, .agents/skills/temporal-playground/ui/src/components/chat/ChatInput.tsx:18
- <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×10) — apps/web/src/pages/ProductDetail.tsx:302, apps/web/src/pages/ProductDetail.tsx:443, apps/web/src/pages/ProductDetailPage.tsx:193, …
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — your Biome config enables no a11y rules and there's no axe/pa11y/Lighthouse in tests or CI. Start by turning on Biome's own a11y rule group to catch issues at author time. What was searched, so you can tell an absence from a miss: the 114 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — REDACTED:49
What to do
- Enforce accessibility in the toolchain you already use: enable Biome's a11y rule group in your biome.json `linter.rules` (it is off whenever `recommended` is false and the group is unlisted), then assert with @axe-core/playwright in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
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. — packages/core/src/lib/nest/bootstrap.ts:78
What to do
- Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, Azure Key Vault, GCP KMS / Secret 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
- Access here is not default-deny: this method of AppController carries no guard decorator, while its 6 sibling methods each carry one, the class carries none and no global guard (APP_GUARD, useGlobalGuards) covers it. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:196
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect. — apps/auth/src/app/app.service.ts:101
What to do
- Put every endpoint behind the guard its siblings carry — mount the router after (or with) the authentication middleware, or declare the guard and the rule it needs on the route — so the open surface is only what is public on purpose.
- Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
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.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add a README to the 12 of 17 project(s) that lack one — worth up to 1.4 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 10/11 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/cli`.
- `apps/web/src/entry.server.tsx` reports through `console.*` at line 95 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/src/entry.server.tsx:95
- `apps/web/src/routes/marketplace.tsx` reports through `console.*` at line 45 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/src/routes/marketplace.tsx:45
- `apps/web/src/routes/product.$id.tsx` reports through `console.*` at line 37 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/src/routes/product.$id.tsx:37
- `apps/web/src/routes/admin/orders.tsx` reports through `console.*` at line 52 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/web/src/routes/admin/orders.tsx:52
- `REDACTED` reports through `console.*` at line 167 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — REDACTED:167
- `packages/core/src/lib/workflows/state.ts` reports through `console.*` at line 54 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/src/lib/workflows/state.ts:54
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
- Add OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) so requests are traceable across the system, not just health-probable.
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 5452 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
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:46
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.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- The pipeline declares a deployment environment, but whether required reviewers / protection rules are attached to it lives in repository settings we cannot read — confirm the gate is enforced before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P6 · Release Hygiene
P8 · Schema migrations
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- 9 duplicated blocks under packages/models/src/ have copies in at least two of the sibling directories manufacturer, order, payment, product, role, user — 4 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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. — packages/models/src/manufacturer/manufacturer.dto.ts:15
- 7 duplicated blocks under apps/ have copies in at least two of the sibling directories auth, order, product — 5 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 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. — apps/auth/eslint.config.mjs:7
- 6 duplicated blocks under the repository root have copies in at least two of the sibling directories apps, packages, turbo — 4 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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. — apps/web/src/pages/ShoppingCard.tsx:61
- turbo/generators/config.ts:224 · turbo/generators/config.ts:563 — 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. — turbo/generators/config.ts:224
- apps/web/src/pages/ShoppingCard.tsx:61 · packages/ui/src/lib/drawers/ShoppingCartContent.tsx:74 — the two spans are one implementation copied and then locally edited — 452 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. — apps/web/src/pages/ShoppingCard.tsx:61
- apps/web/src/pages/admin/Dashboard.tsx:284 · apps/web/src/pages/admin/Orders.tsx:309 — 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. — apps/web/src/pages/admin/Dashboard.tsx:284
- apps/web/src/pages/admin/Dashboard.tsx:574 · apps/web/src/pages/admin/Dashboard.tsx:749 — the two spans are one implementation copied and then locally edited — 283 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. — apps/web/src/pages/admin/Dashboard.tsx:574
- apps/web/src/pages/admin/Dashboard.tsx:467 · apps/web/src/pages/admin/Dashboard.tsx:654 — the two spans are one implementation copied and then locally edited — 275 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. — apps/web/src/pages/admin/Dashboard.tsx:467
- turbo/generators/config.ts:76 · turbo/generators/config.ts:357 — 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. — turbo/generators/config.ts:76
- apps/web/src/services/admin-orders.ts:58 · apps/web/src/services/admin-orders.ts:106 · apps/web/src/services/admin-orders.ts:147 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — apps/web/src/services/admin-orders.ts:58
- apps/web/src/pages/MarketplaceHomepage.tsx:57 · apps/web/src/pages/MarketplacePage.tsx:182 — the two spans are one implementation copied and then locally edited — 174 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. — apps/web/src/pages/MarketplaceHomepage.tsx:57
- apps/web/src/pages/admin/Orders.tsx:575 · apps/web/src/pages/admin/Orders.tsx:667 — 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. — apps/web/src/pages/admin/Orders.tsx:575
- apps/web/src/pages/Order.tsx:213 · apps/web/src/pages/OrderSummary.tsx:162 — 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. — apps/web/src/pages/Order.tsx:213
- apps/auth/src/config/env.config.ts:1 · apps/order/src/config/env.config.ts:1 · apps/product/src/config/env.config.ts:1 — the 3 copies are spread across 3 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. — apps/auth/src/config/env.config.ts:1
- apps/web/src/pages/HomePage.tsx:274 · apps/web/src/pages/HomePage.tsx:306 — 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. — apps/web/src/pages/HomePage.tsx:274
- apps/web/src/pages/MarketplacePage.tsx:178 · apps/web/src/pages/ProductDetailPage.tsx:545 — the two spans are one implementation copied and then locally edited — 171 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. — apps/web/src/pages/MarketplacePage.tsx:178
- apps/web/src/pages/PrivacyPage.tsx:122 · apps/web/src/pages/TermsPage.tsx:128 — 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. — apps/web/src/pages/PrivacyPage.tsx:122
- apps/web/src/pages/admin/Orders.tsx:416 · apps/web/src/pages/admin/Orders.tsx:462 — 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. — apps/web/src/pages/admin/Orders.tsx:416
- packages/ui/src/lib/icons/Mic.tsx:8 · packages/ui/src/lib/icons/Search.tsx:8 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/ui/src/lib/icons/Mic.tsx:8
- packages/ui/src/lib/icons/Close.tsx:8 · packages/ui/src/lib/icons/Menu.tsx:8 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/ui/src/lib/icons/Close.tsx:8
- apps/auth/src/app/app.module.ts:18 · apps/order/src/app/app.module.ts:19 — 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. — apps/auth/src/app/app.module.ts:18
- apps/web/src/pages/MarketplaceHomepage.tsx:174 · apps/web/src/pages/MarketplaceHomepage.tsx:212 — 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. — apps/web/src/pages/MarketplaceHomepage.tsx:174
- apps/web/src/pages/admin/Dashboard.tsx:437 · apps/web/src/pages/admin/Dashboard.tsx:681 — 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. — apps/web/src/pages/admin/Dashboard.tsx:437
- packages/models/src/manufacturer/manufacturer.dto.ts:43 · packages/models/src/product/product.dto.ts:118 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/models/src/manufacturer/manufacturer.dto.ts:43
- packages/ui/src/lib/icons/Facebook.tsx:3 · packages/ui/src/lib/icons/GitHub.tsx:3 · packages/ui/src/lib/icons/Instagram.tsx:3 · packages/ui/src/lib/icons/Love.tsx:3 · +2 more site(s) not listed — the 6 copies are spread across 6 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/ui/src/lib/icons/Facebook.tsx:3
- apps/web/src/hooks/useAdminOrders.ts:34 · apps/web/src/hooks/useAdminOrders.ts:56 — 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. — apps/web/src/hooks/useAdminOrders.ts:34
- apps/web/src/pages/admin/Dashboard.tsx:252 · apps/web/src/pages/admin/Orders.tsx:271 — 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. — apps/web/src/pages/admin/Dashboard.tsx:252
- apps/web/src/pages/MarketplacePage.tsx:455 · apps/web/src/pages/MarketplacePage.tsx:472 — 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. — apps/web/src/pages/MarketplacePage.tsx:455
- packages/cli/src/commands/generate.ts:197 · packages/cli/src/commands/generate.ts:366 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/cli/src/commands/generate.ts:197
- packages/models/src/payment/payment.dto.ts:61 · packages/models/src/user/user.dto.ts:135 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/models/src/payment/payment.dto.ts:61
- packages/workflows/src/lib/client.service.ts:48 · packages/workflows/src/lib/worker.service.ts:98 — the two spans are one implementation copied and then locally edited — 65 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/workflows/src/lib/client.service.ts:48
- turbo/generators/config.ts:403 · turbo/generators/config.ts:719 — 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. — turbo/generators/config.ts:403
- apps/auth/src/config/env.config.ts:12 · apps/order/src/config/env.config.ts:12 — 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. — apps/auth/src/config/env.config.ts:12
- apps/web/src/pages/admin/Dashboard.tsx:396 · apps/web/src/pages/admin/Dashboard.tsx:517 — 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. — apps/web/src/pages/admin/Dashboard.tsx:396
- apps/web/src/routes/order/confirmation.tsx:1 · apps/web/src/routes/order/detail.tsx:1 · apps/web/src/routes/profile.tsx:1 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — apps/web/src/routes/order/confirmation.tsx:1
- packages/cli/src/utils/paths.ts:71 · turbo/generators/config.ts:698 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/cli/src/utils/paths.ts:71
- packages/models/src/user/user.dto.ts:97 · packages/models/src/user/user.dto.ts:119 — 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. — packages/models/src/user/user.dto.ts:97
- apps/web/src/pages/CheckoutPage.tsx:73 · apps/web/src/pages/CheckoutPage.tsx:92 — 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. — apps/web/src/pages/CheckoutPage.tsx:73
- apps/web/src/pages/MarketplaceHomepage.tsx:223 · apps/web/src/pages/MarketplaceHomepage.tsx:258 — 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. — apps/web/src/pages/MarketplaceHomepage.tsx:223
- packages/models/src/role/role.dto.ts:14 · packages/models/src/user/user.dto.ts:29 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/models/src/role/role.dto.ts:14
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- AdminOrdersPage has cyclomatic complexity 51 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 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. — apps/web/src/pages/admin/Orders.tsx:90
- generateService has cyclomatic complexity 28 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/cli/src/commands/generate.ts:87
- getOrderSummaryById has cyclomatic complexity 28 and cognitive complexity 34; 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. — apps/order/src/app/order/order.service.ts:193
- initCommand has cyclomatic complexity 18 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/cli/src/commands/init.ts:15
- parseSse has cyclomatic complexity 14 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/workflow-client/src/sse.ts:13
- recover has cyclomatic complexity 14 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/workflow-client/src/transports/fallback.ts:112
- ProductDetailPage has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/web/src/pages/ProductDetailPage.tsx:100
- workflowStreamEvents has cyclomatic complexity 13 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/workflow-client/src/server/temporal.ts:99
- CheckoutPage has cyclomatic complexity 13 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/web/src/pages/CheckoutPage.tsx:67
- infoCommand has cyclomatic complexity 12 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/cli/src/commands/info.ts:10
- (anonymous) has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/order/src/workflows/process-payment.workflow.ts:120
- handleWebhook has cyclomatic complexity 12 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/order/src/app/app.service.ts:213
- getAdminOrderDetail has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/order/src/app/order/order.service.ts:434
- useWorkflow has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/workflow-client/src/react/useWorkflow.ts:53
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
- apps/web/src/pages/admin/Orders.tsx has 1096 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/pages/admin/Orders.tsx:1
- apps/web/src/pages/admin/Dashboard.tsx has 806 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/pages/admin/Dashboard.tsx:1
- turbo/generators/config.ts has 716 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — turbo/generators/config.ts:1
- apps/web/src/pages/MarketplacePage.tsx has 593 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/pages/MarketplacePage.tsx:1
- apps/web/src/pages/ProductDetailPage.tsx has 558 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/pages/ProductDetailPage.tsx:1
- apps/order/src/app/order/order.service.ts has 514 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/order/src/app/order/order.service.ts:1
- apps/web/src/pages/ProductDetail.tsx has 472 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/pages/ProductDetail.tsx: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. (×40) — apps/web/src/pages/admin/Orders.tsx:1, apps/web/src/pages/admin/Dashboard.tsx:1, turbo/generators/config.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
R7 · Dead Code
- 2 file(s) (~32 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — apps/storybook
- 19 file(s) (~800 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: packages/db/prisma/seed.ts imports '../generated/prisma/client', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — packages/db
- 1 file(s) (~757 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — turbo/generators
- Unreachable from the 61 application, 30 tooling and 52 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (61 application, 30 tooling, 52 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 (×13) — apps/web/src/pages/ProductDetail.tsx, packages/workflow-client/src/react/types.test-d.tsx, apps/web/src/pages/ShoppingCard.tsx, …
- no import path from any entry point (61 application, 30 tooling, 52 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/models/src/role/create-role.dto.ts, packages/models/src/role/update-role.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 — packages/models/src/role/role.dto.ts
- Nothing ultimately consumes this binding: its only referrer is the re-export in apps/web/src/constants/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 apps/web/src/constants/index.ts in the same commit, or the barrel will import a name that no longer exists. (×4) — apps/web/src/constants/links.ts:1, apps/web/src/constants/links.ts:2, apps/web/src/constants/links.ts:3, …
- Nothing imports this binding — it is safe to review for removal. (×15) — apps/web/src/cookies/session.server.ts:17, apps/web/src/pages/MarketplaceHomepage.tsx:310, apps/web/src/pages/PrivacyPage.tsx:145, …
- Nothing ultimately consumes this binding: its only referrer is the re-export in apps/web/src/providers/auth/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 apps/web/src/providers/auth/index.ts in the same commit, or the barrel will import a name that no longer exists. (×2) — apps/web/src/providers/auth/hook.ts:13, apps/web/src/providers/auth/hook.ts:18
- No runtime consumer imports this binding — the only demand on it comes from a type-position import of its module, which asks for the module's type surface rather than for this name. If the value is genuinely unneeded, remove it; if a consumer needs only its TYPE, export that type (e.g. `export type X = typeof x`) and drop the value. A value export — a const, a function, a class — cannot itself be rewritten as `export type`. — packages/core/src/lib/order/providers.ts:6
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
- Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
- Declared in apps/auth/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- REDACTED → apps/auth/src/app/app.service.ts → apps/auth/src/workflows/index.ts → apps/auth/src/workflows/login.workflow.ts → apps/auth/src/main.ts → apps/auth/src/app/app.module.ts → REDACTED — REDACTED:18
- packages/email/src/lib/factory.ts → packages/email/src/lib/template.ts → packages/email/src/lib/factory.ts — packages/email/src/lib/factory.ts:14
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture
- MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. — packages/ui/src/hooks/useAvatarUrl.ts:7
What to do
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
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
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 2/3 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `action` holds an AbortSignal but calls `axios.post(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `axios.post(…, { signal })`. — apps/web/src/routes/login.tsx:20
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
- `verbose` at line 22 is called with an argument built by `JSON.stringify(data)` (line 23), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/db/src/lib/product/product-repository.service.ts:22
- `verbose` at line 42 is called with an argument built by `JSON.stringify(data)` (line 43), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/db/src/lib/product/product-repository.service.ts:42
- `verbose` at line 15 is called with an argument built by `JSON.stringify(createPaymentDto)` (line 16), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/db/src/lib/payment/payment-repository.service.ts:15
- `verbose` at line 14 is called with an argument built by `JSON.stringify(createOrderDto)` (line 15), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/db/src/lib/order/order-repository.service.ts:14
What to do
- Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is JavaScript's evaluation order, not a guess — then put the construction behind the level check the logger offers (`if (logger.isLevelEnabled('debug'))` for pino and winston, `isDebugEnabled()` for log4js, the repository's own debug flag where it has one), or hand the logger the object and a format string (`logger.debug({ payload }, 'raw request')`) so the serialising happens only when the line is written. Moving the call is not the fix: it is the join/projection/stringify in the argument that is paid, wherever the call sits.
X24 · Document value interpolated into markup unescaped
- `String.raw` window.ENV = ${JSON.stringify(ENV)}; `` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — apps/web/src/root.tsx:100
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
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. — packages/workflow-client/src/registry.ts:305
- `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — packages/workflow-client/src/session.ts:386
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `debug` at line 87 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/core/src/lib/nest/bootstrap.ts:87
- `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. — packages/core/src/lib/nest/bootstrap.ts:89
- `error` at line 100 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/core/src/lib/nest/bootstrap.ts:100
- `log` at line 11 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/core/src/lib/auth/auth.service.ts:11
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- 7/20 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
- ~4.5 `!` null assertions per 1k TypeScript source lines — 104 assertion(s) across the 23300 source line(s) of the 300 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: apps/order/src/app/order/dto/admin-order-detail.dto.ts (21), apps/order/src/app/order/dto/admin-order-list.dto.ts (12), packages/models/src/order/order.dto.ts (11). 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 `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 62% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 75% | Strong | Solid. |
| Maturity | 78% | Strong | Solid. |
| Readiness | 31% | Weak — gated by R8, P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 57% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 53% | Adequate | Acceptable, with room to improve. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 2 observation(s) recorded · Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 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 — 40 check(s) not relevant to this codebase
- AX1 Captive dependencies — Not applicable: NestJS makes a provider that injects a request-scoped one request-scoped itself (scope bubbles up the injection chain), and gives every consumer its own transient instance by contract.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 14 — a file the compose project references is missing) — time="2026-11-09T10:04:53Z" level=warning msg="The \"POSTGRES_PASSWORD\" variable is not set. Defaulting to a blank string." env file .env not found: stat .env: no such file or directory; 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-contributor 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 — N/A — too few peers to establish a naming convention (1667 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 13 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- 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: packages/core/src/lib/nest/bootstrap.ts:41 (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 REDACTED, 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 — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 76 finding(s)
- 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
- <input> without a programmatic label .agents/skills/temporal-playground/ui/src/components/canvas/ActivityPicker.tsx:99
- <input> without a programmatic label .agents/skills/temporal-playground/ui/src/components/canvas/NodeDetailPanel.tsx:329
- <input> without a programmatic label .agents/skills/temporal-playground/ui/src/components/canvas/NodeDetailPanel.tsx:347
- <input> without a programmatic label .agents/skills/temporal-playground/ui/src/components/canvas/ParamsEditor.tsx:105
- <input> without a programmatic label .agents/skills/temporal-playground/ui/src/components/canvas/ParamsEditor.tsx:121
- <input> without a programmatic label .agents/skills/temporal-playground/ui/src/components/canvas/ParamsEditor.tsx:275
- <input> without a programmatic label .agents/skills/temporal-playground/ui/src/components/canvas/ParamsEditor.tsx:311
- <input> without a programmatic label .agents/skills/temporal-playground/ui/src/components/canvas/ParamsEditor.tsx:327
- <input> without a programmatic label .agents/skills/temporal-playground/ui/src/nodes/NodeField.tsx:34
- <input> without a programmatic label .agents/skills/temporal-playground/ui/src/nodes/NodeField.tsx:49
- <input> without a programmatic label apps/web/src/pages/MarketplacePage.tsx:89
- <input> without a programmatic label apps/web/src/pages/MarketplacePage.tsx:100
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <textarea> without a programmatic label .agents/skills/temporal-playground/ui/src/components/canvas/NodeDetailPanel.tsx:312
- <textarea> without a programmatic label .agents/skills/temporal-playground/ui/src/components/chat/ChatInput.tsx:18
- <button> with no accessible text .agents/skills/temporal-playground/ui/src/components/canvas/ParamsEditor.tsx:285
- <button> with no accessible text apps/web/src/pages/MarketplacePage.tsx:607
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <select> without a programmatic label .agents/skills/temporal-playground/ui/src/components/canvas/NodeDetailPanel.tsx:271
- No assertions (empty test): should call createOrder method of OrderRepositoryService correctly apps/order/src/app/order/order.service.spec.ts:118
- REDACTED
- REDACTED
- REDACTED
- Import cycle (6 files) REDACTED:18
- Import cycle (2 files) packages/email/src/lib/factory.ts:14
Serious — 272 finding(s)
- No test reaches this file apps/web/src/pages/admin/Orders.tsx:1
- No test reaches this file apps/web/src/pages/admin/Dashboard.tsx:1
- No test reaches this file turbo/generators/config.ts:1
- No test reaches this file apps/web/src/pages/MarketplacePage.tsx:1
- No test reaches this file apps/web/src/pages/ProductDetailPage.tsx:1
- No test reaches this file apps/web/src/pages/ProductDetail.tsx:1
- No test reaches this file packages/cli/src/commands/generate.ts:1
- No test reaches this file REDACTED:1
- No test reaches this file apps/web/src/pages/HomePage.tsx:1
- No test reaches this file apps/web/src/pages/MarketplaceHomepage.tsx:1
- No test reaches this file packages/cli/src/commands/init.ts:1
- No test reaches this file apps/web/src/pages/Order.tsx:1
- No test reaches this file apps/web/src/pages/OrderSummary.tsx:1
- No test reaches this file apps/web/src/pages/OrderHistory.tsx:1
- No test reaches this file packages/workflow-client/src/react/types.test-d.tsx:1
- No test reaches this file apps/web/src/services/admin-orders.ts:1
- No test reaches this file packages/db/prisma/seed.ts:1
- No test reaches this file REDACTED:1
- No test reaches this file apps/web/src/pages/LoginPage.tsx:1
- No test reaches this file apps/web/src/hooks/useAdminOrders.ts:1
- No test reaches this file apps/web/src/pages/CheckoutPage.tsx:1
- No test reaches this file packages/ui/src/lib/layouts/Layout.tsx:1
- No test reaches this file apps/web/src/root.tsx:1
- No test reaches this file apps/web/src/pages/ShoppingCard.tsx:1
- No test reaches this file apps/web/src/pages/TermsPage.tsx:1
- Focus outline removed inline .agents/skills/temporal-playground/ui/src/components/canvas/ActivityPicker.tsx:99
- Focus outline removed inline .agents/skills/temporal-playground/ui/src/components/canvas/NodeDetailPanel.tsx:271
- Focus outline removed inline .agents/skills/temporal-playground/ui/src/components/canvas/NodeDetailPanel.tsx:312
- Focus outline removed inline .agents/skills/temporal-playground/ui/src/components/canvas/NodeDetailPanel.tsx:329
- Focus outline removed inline .agents/skills/temporal-playground/ui/src/components/canvas/NodeDetailPanel.tsx:347
- Focus outline removed inline .agents/skills/temporal-playground/ui/src/components/canvas/ParamsEditor.tsx:105
- Focus outline removed inline .agents/skills/temporal-playground/ui/src/components/canvas/ParamsEditor.tsx:121
- Focus outline removed inline .agents/skills/temporal-playground/ui/src/components/canvas/ParamsEditor.tsx:275
- Focus outline removed inline .agents/skills/temporal-playground/ui/src/components/canvas/ParamsEditor.tsx:311
- Focus outline removed inline .agents/skills/temporal-playground/ui/src/components/canvas/ParamsEditor.tsx:327
- Focus outline removed inline .agents/skills/temporal-playground/ui/src/components/chat/ChatInput.tsx:18
- Focus outline removed inline apps/web/src/pages/MarketplacePage.tsx:408
- Focus outline removed inline apps/web/src/pages/ProductDetail.tsx:302
- Focus outline removed inline apps/web/src/pages/ProductDetail.tsx:443
- Focus outline removed inline apps/web/src/pages/ProductDetailPage.tsx:193
- Focus outline removed inline apps/web/src/pages/ProductDetailPage.tsx:308
- Focus outline removed inline apps/web/src/pages/ProductDetailPage.tsx:340
- Focus outline removed inline apps/web/src/pages/ProductDetailPage.tsx:390
- Focus outline removed inline apps/web/src/pages/ProductDetailPage.tsx:404
- Focus outline removed inline apps/web/src/pages/ProductDetailPage.tsx:418
- Focus outline removed inline apps/web/src/pages/ProductDetailPage.tsx:431
- Focus outline removed inline apps/web/src/pages/ProductDetailPage.tsx:471
- Focus outline removed inline packages/ui/src/lib/inputs/search-bar/SearchBar.tsx:41
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FunctionTooLong: Orders.AdminOrdersPage apps/web/src/pages/admin/Orders.tsx:90
- FunctionTooLong: Dashboard.AdminDashboardPage apps/web/src/pages/admin/Dashboard.tsx:248
- FunctionTooLong: config.generator turbo/generators/config.ts:61
- FunctionTooLong: ProductDetailPage.ProductDetailPage apps/web/src/pages/ProductDetailPage.tsx:100
- FunctionTooLong: MarketplacePage.MarketplacePage apps/web/src/pages/MarketplacePage.tsx:211
- FunctionTooLong: Order.OrderPage apps/web/src/pages/Order.tsx:44
- FunctionTooLong: Header.Header packages/ui/src/lib/header/Header.tsx:30
- FunctionTooLong: OrderHistory.OrderHistory apps/web/src/pages/OrderHistory.tsx:34
- FunctionTooLong: OrderSummary.OrderSummary apps/web/src/pages/OrderSummary.tsx:44
- FunctionTooLong: generate.generateService packages/cli/src/commands/generate.ts:87
- FunctionTooLong: LoginPage.LoginPage apps/web/src/pages/LoginPage.tsx:31
- FunctionTooLong: ShoppingCartContent.ShoppingCartContent packages/ui/src/lib/drawers/ShoppingCartContent.tsx:30
- FunctionTooLong: CheckoutPage.CheckoutPage apps/web/src/pages/CheckoutPage.tsx:67
- FunctionTooLong: http-stream.createHttpStreamTransport packages/workflow-client/src/transports/http-stream.ts:63
- FunctionTooLong: ShoppingCard.ShoppingCart apps/web/src/pages/ShoppingCard.tsx:37
- FunctionTooLong: Profile.ProfileTab REDACTED:153
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Deprecated: eslint apps/auth/package.json:51
- Deprecated: eslint apps/order/package.json:58
- Deprecated: eslint apps/product/package.json:46
- Deprecated: @oslojs/crypto REDACTED:15
- Deprecated: crypto-js REDACTED:33
- Deprecated: @types/pino REDACTED:65
- TodoComment apps/order/src/workflows/order.workflow.ts:187
- TodoComment apps/order/src/app/order/order.service.ts:165
- TodoComment apps/order/src/app/order/order.service.ts:189
- TodoComment apps/order/src/app/order/order.service.ts:574
- TodoComment apps/order/src/app/order/order.service.ts:575
- TodoComment apps/auth/src/workflows/login.workflow.ts:108
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Off the main sequence: @projectx/email
- Off the main sequence: @proyecto26/temporal-workflows
- Off the main sequence: @projectx/ui
- Off the main sequence: @projectx/models
- Off the main sequence: @projectx/db
- Heading level jumps from h1 to h3 apps/web/src/pages/OrderSummary.tsx:109
- Heading level jumps from h1 to h3 apps/web/src/pages/ShoppingCard.tsx:82
- Heading level jumps from h1 to h3 apps/web/src/pages/admin/Dashboard.tsx:500
- Heading level jumps from h1 to h3 apps/web/src/pages/admin/Orders.tsx:514
- Hotspot: packages/workflow-client/src/react/useWorkflow.ts packages/workflow-client/src/react/useWorkflow.ts:53
- Hotspot: apps/order/src/workflows/process-payment.workflow.ts apps/order/src/workflows/process-payment.workflow.ts:66
- Hotspot: apps/order/src/workflows/order.workflow.ts apps/order/src/workflows/order.workflow.ts:53
- Hotspot: apps/web/src/routes/checkout.tsx apps/web/src/routes/checkout.tsx:35
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (22 lines × 2 locations) apps/web/src/pages/HomePage.tsx:274
- Duplicated block (22 lines × 2 locations) apps/web/src/pages/PrivacyPage.tsx:122
- Duplicated block (22 lines × 2 locations) apps/web/src/pages/admin/Orders.tsx:416
- Duplicated block (22 lines × 2 locations) packages/ui/src/lib/icons/Mic.tsx:8
- Duplicated block (19 lines × 2 locations) apps/auth/src/app/app.module.ts:18
- Duplicated block (19 lines × 2 locations) apps/web/src/pages/MarketplaceHomepage.tsx:174
- Duplicated block (19 lines × 2 locations) apps/web/src/pages/admin/Dashboard.tsx:437
- Duplicated block (19 lines × 2 locations) packages/models/src/manufacturer/manufacturer.dto.ts:43
- Duplicated block (16 lines × 2 locations) apps/web/src/pages/MarketplacePage.tsx:455
- Duplicated block (16 lines × 2 locations) packages/cli/src/commands/generate.ts:197
- Duplicated block (16 lines × 2 locations) packages/models/src/payment/payment.dto.ts:61
- Duplicated block (16 lines × 2 locations) turbo/generators/config.ts:403
- Duplicated block (15 lines × 2 locations) apps/auth/src/config/env.config.ts:12
- Duplicated block (15 lines × 2 locations) apps/web/src/pages/admin/Dashboard.tsx:396
- Duplicated block (15 lines × 2 locations) packages/cli/src/utils/paths.ts:71
- Duplicated block (15 lines × 2 locations) packages/models/src/user/user.dto.ts:97
- FileTooLong: admin/Orders.tsx apps/web/src/pages/admin/Orders.tsx
- FileTooLong: admin/Dashboard.tsx apps/web/src/pages/admin/Dashboard.tsx
- FileTooLong: pages/MarketplacePage.tsx apps/web/src/pages/MarketplacePage.tsx
- Duplicated block (14 lines × 2 locations) apps/web/src/pages/CheckoutPage.tsx:73
- Duplicated block (14 lines × 2 locations) apps/web/src/pages/MarketplaceHomepage.tsx:223
- Duplicated block (14 lines × 2 locations) packages/models/src/role/role.dto.ts:14
- Dead file (~12 LoC) apps/web/src/pages/checkout/Failure.tsx
- Dead file (~12 LoC) apps/web/src/pages/checkout/Pending.tsx
- Dead file (~12 LoC) apps/web/src/pages/checkout/Successful.tsx
- REDACTED
- REDACTED
- Workspace package's tests never run by CI apps/auth/package.json:16
- Workspace package's tests never run by CI apps/order/package.json:16
- Dead file (~0 LoC) packages/models/src/role/user-role.dto.ts
- Dead file (~0 LoC) packages/ui/src/lib/router.ts
- Unused dependency 'pino-pretty'
- Unused dependency 'pino-pretty'
- <OtpInput> field component without a label apps/web/src/pages/LoginPage.tsx:153
- Modal dialog does not manage focus packages/ui/src/lib/drawers/ShoppingCartContent.tsx:45
- Accessibility enforcement below the top rung REDACTED:49
- Orders.AdminOrdersPage (cyclomatic 64) apps/web/src/pages/admin/Orders.tsx:90
- generate.generateService (cyclomatic 38) packages/cli/src/commands/generate.ts:87
- config.generator (cyclomatic 34) turbo/generators/config.ts:61
- OrderService.getOrderSummaryById (cyclomatic 29) apps/order/src/app/order/order.service.ts:193
- process-payment.workflow.processPayment (cyclomatic 26) apps/order/src/workflows/process-payment.workflow.ts:66
- MarketplacePage.MarketplacePage (cyclomatic 22) apps/web/src/pages/MarketplacePage.tsx:211
- init.initCommand (cyclomatic 21) packages/cli/src/commands/init.ts:15
- checkout.Checkout (cyclomatic 19) apps/web/src/routes/checkout.tsx:35
- useWorkflow.useWorkflow (cyclomatic 18) packages/workflow-client/src/react/useWorkflow.ts:53
- ProductDetailPage.ProductDetailPage (cyclomatic 17) apps/web/src/pages/ProductDetailPage.tsx:100
- OrderService.getAdminOrderDetail (cyclomatic 16) apps/order/src/app/order/order.service.ts:434
- No assertions: handles loader data packages/ui/src/lib/navigation/Navigation.spec.tsx:48
- Fixed-sleep synchronisation: doesn't count a slow reader as an idle stream packages/workflow-client/src/transports/transports.spec.ts:492
- Orders.AdminOrdersPage (cognitive 53) apps/web/src/pages/admin/Orders.tsx:90
- generate.generateService (cognitive 51) packages/cli/src/commands/generate.ts:87
- OrderService.getOrderSummaryById (cognitive 34) apps/order/src/app/order/order.service.ts:193
- config.generator (cognitive 31) turbo/generators/config.ts:61
- process-payment.workflow.processPayment (cognitive 29) apps/order/src/workflows/process-payment.workflow.ts:66
- config.getNextAvailablePort (cognitive 28) turbo/generators/config.ts:6
- fallback.createFallbackTransport.recover (cognitive 27) packages/workflow-client/src/transports/fallback.ts:112
- sse.parseSse (cognitive 26) packages/workflow-client/src/sse.ts:13
- init.initCommand (cognitive 25) packages/cli/src/commands/init.ts:15
- WorkflowSession.#follow (cognitive 23) packages/workflow-client/src/session.ts:347
- order.workflow.createOrder (cognitive 21) apps/order/src/workflows/order.workflow.ts:53
- MarketplacePage.MarketplacePage (cognitive 21) apps/web/src/pages/MarketplacePage.tsx:211
- info.infoCommand (cognitive 20) packages/cli/src/commands/info.ts:10
- init.renameProject (cognitive 17) packages/cli/src/commands/init.ts:165
- WorkflowRegistry.hydrate (cognitive 17) packages/workflow-client/src/registry.ts:158
- LoginPage.LoginPage (cognitive 16) apps/web/src/pages/LoginPage.tsx:31
- useWorkflow.useWorkflow (cognitive 16) packages/workflow-client/src/react/useWorkflow.ts:53
- temporal.workflowStreamEvents (cognitive 16) packages/workflow-client/src/server/temporal.ts:99
- REDACTED
- REDACTED
- REDACTED
- ClassTooLong: ProductDetailPage apps/web/src/pages/ProductDetailPage.tsx:1
- REDACTED
- No DR/backup evidence
- Duplication concentrated across 6 sibling directories (9 clone groups) packages/models/src/manufacturer/manufacturer.dto.ts:15
- Duplication concentrated across 3 sibling directories (7 clone groups) apps/auth/eslint.config.mjs:7
- Duplication concentrated across 3 sibling directories (6 clone groups) apps/web/src/pages/ShoppingCard.tsx:61
- Duplicated block (81 lines × 2 locations) turbo/generators/config.ts:224
- Duplicated block with local edits (78 matched lines × 2 locations) apps/web/src/pages/ShoppingCard.tsx:61
- Duplicated block (75 lines × 2 locations) apps/web/src/pages/admin/Dashboard.tsx:284
- Duplicated block with local edits (62 matched lines × 2 locations) apps/web/src/pages/admin/Dashboard.tsx:574
- Duplicated block with local edits (56 matched lines × 2 locations) apps/web/src/pages/admin/Dashboard.tsx:467
- Duplicated block (47 lines × 2 locations) turbo/generators/config.ts:76
- Duplicated block (29 lines × 3 locations) apps/web/src/services/admin-orders.ts:58
- Duplicated block with local edits (28 matched lines × 2 locations) apps/web/src/pages/MarketplaceHomepage.tsx:57
- Duplicated block (26 lines × 2 locations) apps/web/src/pages/admin/Orders.tsx:575
- Duplicated block (24 lines × 2 locations) apps/web/src/pages/Order.tsx:213
- Duplicated block (22 lines × 3 locations) apps/auth/src/config/env.config.ts:1
- Duplicated block with local edits (22 matched lines × 2 locations) apps/web/src/pages/MarketplacePage.tsx:178
- Duplicated block (20 lines × 2 locations) packages/ui/src/lib/icons/Close.tsx:8
- Duplicated block (19 lines × 6 locations) packages/ui/src/lib/icons/Facebook.tsx:3
- Duplicated block (18 lines × 2 locations) apps/web/src/hooks/useAdminOrders.ts:34
- Duplicated block (17 lines × 2 locations) apps/web/src/pages/admin/Dashboard.tsx:252
- Duplicated block with local edits (16 matched lines × 2 locations) packages/workflows/src/lib/client.service.ts:48
- Duplicated block (15 lines × 3 locations) apps/web/src/routes/order/confirmation.tsx:1
- Complex function AdminOrdersPage (cyclomatic 51, cognitive 44) apps/web/src/pages/admin/Orders.tsx:90
- Complex function generateService (cyclomatic 28, cognitive 36) packages/cli/src/commands/generate.ts:87
- Complex function getOrderSummaryById (cyclomatic 28, cognitive 34) apps/order/src/app/order/order.service.ts:193
- Complex function initCommand (cyclomatic 18, cognitive 20) packages/cli/src/commands/init.ts:15
- Complex function parseSse (cyclomatic 14, cognitive 28) packages/workflow-client/src/sse.ts:13
- Complex function recover (cyclomatic 14, cognitive 27) packages/workflow-client/src/transports/fallback.ts:112
- Complex function ProductDetailPage (cyclomatic 14, cognitive 13) apps/web/src/pages/ProductDetailPage.tsx:100
- Complex function workflowStreamEvents (cyclomatic 13, cognitive 18) packages/workflow-client/src/server/temporal.ts:99
- Complex function CheckoutPage (cyclomatic 13, cognitive 14) apps/web/src/pages/CheckoutPage.tsx:67
- Complex function infoCommand (cyclomatic 12, cognitive 20) packages/cli/src/commands/info.ts:10
- Complex function (anonymous) (cyclomatic 12, cognitive 13) apps/order/src/workflows/process-payment.workflow.ts:120
- Complex function handleWebhook (cyclomatic 12, cognitive 12) apps/order/src/app/app.service.ts:213
- Complex function getAdminOrderDetail (cyclomatic 12, cognitive 11) apps/order/src/app/order/order.service.ts:434
- Complex function useWorkflow (cyclomatic 12, cognitive 11) packages/workflow-client/src/react/useWorkflow.ts:53
- apps/web/src/pages/admin/Orders.tsx: 1096 lines of code apps/web/src/pages/admin/Orders.tsx:1
- apps/web/src/pages/admin/Dashboard.tsx: 806 lines of code apps/web/src/pages/admin/Dashboard.tsx:1
- turbo/generators/config.ts: 716 lines of code turbo/generators/config.ts:1
- apps/web/src/pages/MarketplacePage.tsx: 593 lines of code apps/web/src/pages/MarketplacePage.tsx:1
- apps/web/src/pages/ProductDetailPage.tsx: 558 lines of code apps/web/src/pages/ProductDetailPage.tsx:1
- apps/order/src/app/order/order.service.ts: 514 lines of code apps/order/src/app/order/order.service.ts:1
- apps/web/src/pages/ProductDetail.tsx: 472 lines of code apps/web/src/pages/ProductDetail.tsx:1
- Dead file (~504 LoC) apps/web/src/pages/ProductDetail.tsx
- Dead file (~224 LoC) packages/workflow-client/src/react/types.test-d.tsx
- Dead file (~155 LoC) apps/web/src/pages/ShoppingCard.tsx
- Dead file (~50 LoC) packages/models/src/role/role.dto.ts
- Dead file (~19 LoC) apps/web/src/hooks/useProduct.ts
- Dead file (~17 LoC) apps/web/src/hooks/useCategories.ts
- Dead file (~9 LoC) packages/models/src/role/create-role.dto.ts
- Dead file (~7 LoC) packages/models/src/role/update-role.dto.ts
- Dead file (~4 LoC) packages/email/src/lib/common/utils.ts
- Unused dependency '@eslint/eslintrc'
- Weak hash algorithm packages/ui/src/hooks/useAvatarUrl.ts:7
- Async function without AbortSignal: action apps/web/src/routes/login.tsx:20
- Untrusted text written into markup unescaped apps/web/src/root.tsx:100
- Swallowed exception (empty catch) packages/workflow-client/src/registry.ts:305
- Swallowed exception (caught, then discarded) packages/workflow-client/src/session.ts:386
Minor — 78 finding(s)
- redundant comment apps/order/src/app/app.service.ts:247
- redundant comment apps/order/src/app/order/order.service.ts:296
- redundant comment apps/order/src/app/order/order.service.ts:423
- redundant comment apps/order/src/app/order/order.service.ts:539
- redundant comment apps/order/src/app/order/order.service.ts:568
- redundant comment apps/web/src/pages/admin/Orders.tsx:157
- redundant comment packages/cli/src/index.ts:48
- redundant comment packages/db/prisma/seed.ts:26
- redundant comment packages/db/prisma/seed.ts:37
- redundant comment turbo/generators/config.ts:46
- redundant comment turbo/generators/config.ts:62
- Unused export 'default' apps/web/src/pages/MarketplaceHomepage.tsx:310
- Unused export 'default' apps/web/src/pages/PrivacyPage.tsx:145
- Unused export 'default' apps/web/src/pages/ProductDetailPage.tsx:591
- Unused export 'default' REDACTED:418
- Unused export 'default' apps/web/src/pages/TermsPage.tsx:151
- Unused export 'default' packages/ui/src/lib/icons/Love.tsx:27
- Unused export 'default' packages/ui/src/lib/icons/Mic.tsx:31
- Console output used as the logging channel apps/web/src/entry.server.tsx:95
- Console output used as the logging channel apps/web/src/routes/marketplace.tsx:45
- Console output used as the logging channel apps/web/src/routes/product.$id.tsx:37
- Console output used as the logging channel apps/web/src/routes/admin/orders.tsx:52
- Console output used as the logging channel REDACTED:167
- Console output used as the logging channel packages/core/src/lib/workflows/state.ts:54
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Diagnostic log message is built whether or not it is wanted packages/db/src/lib/product/product-repository.service.ts:22
- Diagnostic log message is built whether or not it is wanted packages/db/src/lib/product/product-repository.service.ts:42
- Diagnostic log message is built whether or not it is wanted packages/db/src/lib/payment/payment-repository.service.ts:15
- Diagnostic log message is built whether or not it is wanted packages/db/src/lib/order/order-repository.service.ts:14
- Interpolated log message defeats structured logging packages/core/src/lib/nest/bootstrap.ts:87
- Interpolated log message defeats structured logging packages/core/src/lib/nest/bootstrap.ts:89
- Interpolated log message defeats structured logging packages/core/src/lib/nest/bootstrap.ts:100
- Interpolated log message defeats structured logging packages/core/src/lib/auth/auth.service.ts:11
- Deprecated: @ungap/structured-clone REDACTED:5306
- Deprecated: glob REDACTED:6927
- Deprecated: whatwg-encoding REDACTED:9973
- Duplicated predicate packages/workflow-client/src/server/actions.ts:101
- Duplicated predicate packages/workflow-client/src/server/response.ts:23
- Duplicated predicate apps/auth/src/config/temporal.config.ts:5
- Endpoints outside the guard REDACTED:196
- No named authorization policies apps/auth/src/app/app.service.ts:101
- Partial data-retention evidence
- Outdated (npm): stripe packages/payment/package.json:28
- No ADRs found
- Projects may be oversized for their cohesion
- Pass-through layer apps/order/src/app/activities/activities.service.ts:8
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- No SAST .github/workflows/ci.yml:4
- No dependency-update automation REDACTED:46
- Unused export 'GITHUB_URL' apps/web/src/constants/links.ts:1
- Unused export 'FACEBOOK_URL' apps/web/src/constants/links.ts:2
- Unused export 'INSTAGRAM_URL' apps/web/src/constants/links.ts:3
- Unused export 'NAVIGATION' apps/web/src/constants/navigation.ts:1
- Unused export 'getGlobalSession' apps/web/src/cookies/session.server.ts:17
- Unused export 'useAuthToken' apps/web/src/providers/auth/hook.ts:13
- Unused export 'useAuthUser' apps/web/src/providers/auth/hook.ts:18
- Unused export 'getAdminOrderDetailServer' apps/web/src/services/admin-orders.ts:172
- Unused export 'updateOrderStatusServer' apps/web/src/services/admin-orders.ts:188
- Unused export 'cancelAdminOrderServer' apps/web/src/services/admin-orders.ts:206
- Unused export 'camelCase' packages/cli/src/utils/case.ts:13
- Unused export 'upperSnakeCase' packages/cli/src/utils/case.ts:21
- Unused export 'getPackagesDir' packages/cli/src/utils/paths.ts:39
- Unused export 'getNextDebugPort' packages/cli/src/utils/paths.ts:123
- Unused export 'PaymentProvider' packages/core/src/lib/order/providers.ts:6
- Not all async functions that make a request accept an AbortSignal
- Strict null checking is not enabled everywhere the repository type-checks
- Null assertions (`!`) reduce the strict null checking score
- Silent fallback default in catch packages/workflow-client/src/registry.ts:287
Minor — 23 finding(s)
- Outdated (npm): @clack/prompts
- Outdated (npm): @nestjs/common
- Outdated (npm): @nestjs/config
- Outdated (npm): @nestjs/core
- Outdated (npm): @nestjs/jwt
- Outdated (npm): @nestjs/passport
- Outdated (npm): @nestjs/platform-express
- Outdated (npm): @nestjs/swagger
- Outdated (npm): @stripe/react-stripe-js
- Outdated (npm): @stripe/stripe-js
- Outdated (npm): @tanstack/react-query
- Outdated (npm): @tanstack/react-query-devtools
- Outdated (npm): chalk
- Outdated (npm): class-validator
- Outdated (npm): commander
- Outdated (npm): execa
- Outdated (npm): express-rate-limit
- Outdated (npm): framer-motion
- Outdated (npm): lucide-react
- Outdated (npm): mjml
- Outdated (npm): ora
- Outdated (npm): prisma
- doc comments repeat the names packages/core/src/lib/user/workflow.utils.ts:39
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-2641e41671e94c1d83572d8683455d4c/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2641e41671e94c1d83572d8683455d4c/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/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 . | 17 | 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 | 72 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 11 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 13 file(s) — `.agents/skills/temporal-playground/ui/src/types/index.ts`, `apps/web/react-router.config.ts`, `apps/web/src/routes.tsx`, `packages/core/.gitignore`, `packages/core/src/lib/order/workflow.utils.ts`, … (+8 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 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 |