Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.
Sign up free Scan another repo

tako0614/takosumi

https://github.com/tako0614/takosumi · scanned 2026-06-16 00:29 UTC (2 months, 2 weeks ago)

468 raw signals (0 security + 468 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 440 actionable findings from 1 signal source. 28 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
56.5
/100
Security checks
57
0 findings
System graph
57
100.0% cov · 440 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 184 Medium 52 Low 85 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 440 Crowd 0 Layer: Software 3 Frontend 27 Network 3 Hardware 3 Security 7 Quality 216 Api 181
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 56.5/100 with 100.0% coverage. It contains 5669 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 468 findings — concentrated in quality (239), api (181), frontend (27). Risk profile is high: 0 critical, 184 high, 75 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 319 of 440 actionable findings. 468 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: DELETE /internal/v1/dependencies/${dependencyId} (core/api/deploy_control_model_routes_test.ts:356)
`core/api/deploy_control_model_routes_test.ts:356` calls `DELETE /internal/v1/dependencies/${dependencyId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/dependencies/<p>` If this points at an …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /internal/v1/installations/${installationId} (core/api/deploy_control_public_routes_e2e_test.ts:705)
`core/api/deploy_control_public_routes_e2e_test.ts:705` calls `DELETE /internal/v1/installations/${installationId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>` If this poin…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /health (core/api/request_correlation_test.ts:124)
`core/api/request_correlation_test.ts:124` calls `GET /health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/health` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/compatibility-reports/${checkedBody.report.id} (core/api/deploy_control_source_routes_test.ts:231)
`core/api/deploy_control_source_routes_test.ts:231` calls `GET /internal/v1/compatibility-reports/${checkedBody.report.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/compatibility-reports/<…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/compatibility-reports/${report.id} (core/api/deploy_control_source_routes_test.ts:324)
`core/api/deploy_control_source_routes_test.ts:324` calls `GET /internal/v1/compatibility-reports/${report.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/compatibility-reports/<p>` If this …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/connections (core/api/deploy_control_connection_routes_test.ts:505)
`core/api/deploy_control_connection_routes_test.ts:505` calls `GET /internal/v1/connections` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/connections` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/connections (core/api/deploy_control_connection_routes_test.ts:516)
`core/api/deploy_control_connection_routes_test.ts:516` calls `GET /internal/v1/connections` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/connections` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/connections/cloudflare/oauth/callback?code=code_cf&state=state_cf (core/api/deploy_control_connection_routes_test.ts:373)
`core/api/deploy_control_connection_routes_test.ts:373` calls `GET /internal/v1/connections/cloudflare/oauth/callback?code=code_cf&state=state_cf` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/connections/gcp/oauth/callback (core/api/deploy_control_connection_routes_test.ts:410)
`core/api/deploy_control_connection_routes_test.ts:410` calls `GET /internal/v1/connections/gcp/oauth/callback` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/connections/gcp/oauth/callback` If …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/connections?spaceId=${SPACE_ID} (core/api/deploy_control_connection_routes_test.ts:479)
`core/api/deploy_control_connection_routes_test.ts:479` calls `GET /internal/v1/connections?spaceId=${SPACE_ID}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/connections` If this points at an …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/connections?spaceId=${SPACE_ID}&limit=-1 (core/api/deploy_control_pagination_routes_test.ts:161)
`core/api/deploy_control_pagination_routes_test.ts:161` calls `GET /internal/v1/connections?spaceId=${SPACE_ID}&limit=-1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/connections` If this poin…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/connections?spaceId=${SPACE_ID}&limit=3 (core/api/deploy_control_pagination_routes_test.ts:144)
`core/api/deploy_control_pagination_routes_test.ts:144` calls `GET /internal/v1/connections?spaceId=${SPACE_ID}&limit=3` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/connections` If this point…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/deployments/deploy_missing0001 (core/api/deploy_control_public_routes_e2e_test.ts:483)
`core/api/deploy_control_public_routes_e2e_test.ts:483` calls `GET /internal/v1/deployments/deploy_missing0001` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/deployments/deploy_missing0001` If …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/install-configs?spaceId=${SPACE_ID}&cursor=not-a-cursor!! (core/api/deploy_control_pagination_routes_test.ts:260)
`core/api/deploy_control_pagination_routes_test.ts:260` calls `GET /internal/v1/install-configs?spaceId=${SPACE_ID}&cursor=not-a-cursor!!` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/install-…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/install-configs?spaceId=${spaceId} (core/api/deploy_control_model_routes_test.ts:218)
`core/api/deploy_control_model_routes_test.ts:218` calls `GET /internal/v1/install-configs?spaceId=${spaceId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/install-configs` If this points at a…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/installations/${consumer}/dependencies (core/api/deploy_control_model_routes_test.ts:363)
`core/api/deploy_control_model_routes_test.ts:363` calls `GET /internal/v1/installations/${consumer}/dependencies` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>/dependencies` …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/installations/${installationId} (core/api/deploy_control_model_routes_test.ts:202)
`core/api/deploy_control_model_routes_test.ts:202` calls `GET /internal/v1/installations/${installationId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>` If this points at an…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/installations/${installationId} (core/api/deploy_control_public_routes_e2e_test.ts:447)
`core/api/deploy_control_public_routes_e2e_test.ts:447` calls `GET /internal/v1/installations/${installationId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>` If this points …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/installations/${installationId} (core/api/deploy_control_public_routes_e2e_test.ts:497)
`core/api/deploy_control_public_routes_e2e_test.ts:497` calls `GET /internal/v1/installations/${installationId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>` If this points …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/installations/${installationId}/deployment-outputs (core/api/deploy_control_public_routes_e2e_test.ts:365)
`core/api/deploy_control_public_routes_e2e_test.ts:365` calls `GET /internal/v1/installations/${installationId}/deployment-outputs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/installations/${installationId}/deployments (core/api/deploy_control_public_routes_e2e_test.ts:453)
`core/api/deploy_control_public_routes_e2e_test.ts:453` calls `GET /internal/v1/installations/${installationId}/deployments` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>/depl…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/operator-connection-defaults (core/api/deploy_control_connection_routes_test.ts:567)
`core/api/deploy_control_connection_routes_test.ts:567` calls `GET /internal/v1/operator-connection-defaults` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/operator-connection-defaults` If this…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/output-shares?spaceId=space_denied01 (core/api/deploy_control_internal_routes_test.ts:366)
`core/api/deploy_control_internal_routes_test.ts:366` calls `GET /internal/v1/output-shares?spaceId=space_denied01` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/output-shares` If this points a…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/plan-runs/${runId} (core/api/deploy_control_public_routes_e2e_test.ts:41)
`core/api/deploy_control_public_routes_e2e_test.ts:41` calls `GET /internal/v1/plan-runs/${runId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/plan-runs/<p>` If this points at an external API…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/providers (core/api/deploy_control_public_routes_e2e_test.ts:133)
`core/api/deploy_control_public_routes_e2e_test.ts:133` calls `GET /internal/v1/providers` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/providers` If this points at an external API, prefix it …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/run-groups/${group.runGroup.id} (core/api/run_group_routes_test.ts:326)
`core/api/run_group_routes_test.ts:326` calls `GET /internal/v1/run-groups/${group.runGroup.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/run-groups/<p>` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/runner-profiles (core/api/deploy_control_internal_routes_test.ts:251)
`core/api/deploy_control_internal_routes_test.ts:251` calls `GET /internal/v1/runner-profiles` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/runner-profiles` If this points at an external API, …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/runs/${body.backup.createdByRunId} (core/api/deploy_control_backup_routes_test.ts:107)
`core/api/deploy_control_backup_routes_test.ts:107` calls `GET /internal/v1/runs/${body.backup.createdByRunId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/runs/<p>` If this points at an exte…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/runs/${body.backup.createdByRunId} (core/api/deploy_control_backup_routes_test.ts:131)
`core/api/deploy_control_backup_routes_test.ts:131` calls `GET /internal/v1/runs/${body.backup.createdByRunId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/runs/<p>` If this points at an exte…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/runs/${compatibilityRunId}/events (core/api/deploy_control_source_routes_test.ts:255)
`core/api/deploy_control_source_routes_test.ts:255` calls `GET /internal/v1/runs/${compatibilityRunId}/events` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/runs/<p>/events` If this points at a…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/runs/${compatibilityRunId}/logs (core/api/deploy_control_source_routes_test.ts:249)
`core/api/deploy_control_source_routes_test.ts:249` calls `GET /internal/v1/runs/${compatibilityRunId}/logs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/runs/<p>/logs` If this points at an ex…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/runs/${driftRun.id} (core/api/deploy_control_public_routes_e2e_test.ts:772)
`core/api/deploy_control_public_routes_e2e_test.ts:772` calls `GET /internal/v1/runs/${driftRun.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/runs/<p>` If this points at an external API, p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/runs/${payload.id} (core/api/deploy_control_public_routes_e2e_test.ts:715)
`core/api/deploy_control_public_routes_e2e_test.ts:715` calls `GET /internal/v1/runs/${payload.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/runs/<p>` If this points at an external API, pr…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/runs/${planRun.id} (core/api/deploy_control_public_routes_e2e_test.ts:333)
`core/api/deploy_control_public_routes_e2e_test.ts:333` calls `GET /internal/v1/runs/${planRun.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/runs/<p>` If this points at an external API, pr…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/runs/${planRun.id}/events (core/api/deploy_control_public_routes_e2e_test.ts:401)
`core/api/deploy_control_public_routes_e2e_test.ts:401` calls `GET /internal/v1/runs/${planRun.id}/events` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/runs/<p>/events` If this points at an ex…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/runs/${planRun.id}/logs (core/api/deploy_control_public_routes_e2e_test.ts:391)
`core/api/deploy_control_public_routes_e2e_test.ts:391` calls `GET /internal/v1/runs/${planRun.id}/logs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/runs/<p>/logs` If this points at an extern…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/runs/plan_missing00000001/logs (core/api/deploy_control_public_routes_e2e_test.ts:414)
`core/api/deploy_control_public_routes_e2e_test.ts:414` calls `GET /internal/v1/runs/plan_missing00000001/logs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/runs/plan_missing00000001/logs` If …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/runtime-handlers (core/runtime-agent/server_test.ts:135)
`core/runtime-agent/server_test.ts:135` calls `GET /internal/v1/runtime-handlers` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/runtime-handlers` If this points at an external API, prefix it wi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/runtime-handlers (core/runtime-agent/server_test.ts:138)
`core/runtime-agent/server_test.ts:138` calls `GET /internal/v1/runtime-handlers` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/runtime-handlers` If this points at an external API, prefix it wi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/sources (core/api/deploy_control_source_routes_test.ts:433)
`core/api/deploy_control_source_routes_test.ts:433` calls `GET /internal/v1/sources` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources` If this points at an external API, prefix it with `ht…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/sources/${sourceId} (core/api/deploy_control_source_routes_test.ts:141)
`core/api/deploy_control_source_routes_test.ts:141` calls `GET /internal/v1/sources/${sourceId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources/<p>` If this points at an external API, pr…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/sources/${sourceId}/snapshots (core/api/deploy_control_source_routes_test.ts:155)
`core/api/deploy_control_source_routes_test.ts:155` calls `GET /internal/v1/sources/${sourceId}/snapshots` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources/<p>/snapshots` If this points at…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/sources/not-a-source/snapshots (core/api/deploy_control_source_routes_test.ts:425)
`core/api/deploy_control_source_routes_test.ts:425` calls `GET /internal/v1/sources/not-a-source/snapshots` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources/not-a-source/snapshots` If this…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/sources?spaceId=space_1 (core/api/deploy_control_source_routes_test.ts:136)
`core/api/deploy_control_source_routes_test.ts:136` calls `GET /internal/v1/sources?spaceId=space_1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources` If this points at an external API, pr…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/spaces (core/api/deploy_control_model_routes_test.ts:431)
`core/api/deploy_control_model_routes_test.ts:431` calls `GET /internal/v1/spaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces` If this points at an external API, prefix it with `https…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/spaces (core/api/deploy_control_model_routes_test.ts:98)
`core/api/deploy_control_model_routes_test.ts:98` calls `GET /internal/v1/spaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/spaces/${SPACE_ID}/activity (core/api/deploy_control_connection_routes_test.ts:185)
`core/api/deploy_control_connection_routes_test.ts:185` calls `GET /internal/v1/spaces/${SPACE_ID}/activity` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/<p>/activity` If this points at…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/spaces/${SPACE_ID}/activity (core/api/deploy_control_connection_routes_test.ts:711)
`core/api/deploy_control_connection_routes_test.ts:711` calls `GET /internal/v1/spaces/${SPACE_ID}/activity` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/<p>/activity` If this points at…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/spaces/${SPACE_ID}/installations (core/api/deploy_control_pagination_routes_test.ts:180)
`core/api/deploy_control_pagination_routes_test.ts:180` calls `GET /internal/v1/spaces/${SPACE_ID}/installations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/<p>/installations` If this…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/spaces/${spaceId} (core/api/deploy_control_model_routes_test.ts:92)
`core/api/deploy_control_model_routes_test.ts:92` calls `GET /internal/v1/spaces/${spaceId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/<p>` If this points at an external API, prefix …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/spaces/${spaceId}/activity${query} (core/api/activity_routes_test.ts:178)
`core/api/activity_routes_test.ts:178` calls `GET /internal/v1/spaces/${spaceId}/activity${query}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/<p>/activity/<p>` If this points at an ex…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/spaces/${spaceId}/installations (core/api/deploy_control_model_routes_test.ts:146)
`core/api/deploy_control_model_routes_test.ts:146` calls `GET /internal/v1/spaces/${spaceId}/installations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/<p>/installations` If this point…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/spaces/space_12345678/billing (core/api/billing_routes_test.ts:109)
`core/api/billing_routes_test.ts:109` calls `GET /internal/v1/spaces/space_12345678/billing` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_12345678/billing` If this points at an ex…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/spaces/space_12345678/credit-reservations (core/api/billing_routes_test.ts:182)
`core/api/billing_routes_test.ts:182` calls `GET /internal/v1/spaces/space_12345678/credit-reservations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_12345678/credit-reservations`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/spaces/space_12345678/usage (core/api/billing_routes_test.ts:165)
`core/api/billing_routes_test.ts:165` calls `GET /internal/v1/spaces/space_12345678/usage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_12345678/usage` If this points at an extern…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/spaces/space_87654321/billing (core/api/billing_routes_test.ts:342)
`core/api/billing_routes_test.ts:342` calls `GET /internal/v1/spaces/space_87654321/billing` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_87654321/billing` If this points at an ex…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/spaces/space_aaaaaaaa/backups (core/api/deploy_control_backup_routes_test.ts:178)
`core/api/deploy_control_backup_routes_test.ts:178` calls `GET /internal/v1/spaces/space_aaaaaaaa/backups` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_aaaaaaaa/backups` If this p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /internal/v1/spaces/space_bbbbbbbb/backups (core/api/deploy_control_backup_routes_test.ts:191)
`core/api/deploy_control_backup_routes_test.ts:191` calls `GET /internal/v1/spaces/space_bbbbbbbb/backups` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_bbbbbbbb/backups` If this p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /items/one (core/api/request_correlation_test.ts:31)
`core/api/request_correlation_test.ts:31` calls `GET /items/one` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/items/one` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /items/one (core/api/request_correlation_test.ts:81)
`core/api/request_correlation_test.ts:81` calls `GET /items/one` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/items/one` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /missing (core/api/request_correlation_test.ts:152)
`core/api/request_correlation_test.ts:152` calls `GET /missing` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/missing` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /ok (core/api/request_correlation_test.ts:151)
`core/api/request_correlation_test.ts:151` calls `GET /ok` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/ok` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/account/session/me (dashboard/src/views/account/lib/session.ts:8)
`dashboard/src/views/account/lib/session.ts:8` calls `GET /v1/account/session/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/account/session/me` If this points at an external API, prefix it with `https://` so th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://cloudflare-dns.com/dns-query?name=${encodeURIComponent( host, )}&type=${type} (runner/entrypoint.ts:2470)
`runner/entrypoint.ts:2470` calls `GET https://cloudflare-dns.com/dns-query?name=${encodeURIComponent( host, )}&type=${type}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/cloudflare-dns.co…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /internal/v1/installations/${installationId} (core/api/deploy_control_public_routes_e2e_test.ts:670)
`core/api/deploy_control_public_routes_e2e_test.ts:670` calls `PATCH /internal/v1/installations/${installationId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>` If this point…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /internal/v1/installations/${installationId} (core/api/deploy_control_public_routes_e2e_test.ts:678)
`core/api/deploy_control_public_routes_e2e_test.ts:678` calls `PATCH /internal/v1/installations/${installationId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>` If this point…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /internal/v1/installations/${installationId} (core/api/deploy_control_public_routes_e2e_test.ts:691)
`core/api/deploy_control_public_routes_e2e_test.ts:691` calls `PATCH /internal/v1/installations/${installationId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>` If this point…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /internal/v1/sources/${source.id} (core/api/deploy_control_source_routes_test.ts:412)
`core/api/deploy_control_source_routes_test.ts:412` calls `PATCH /internal/v1/sources/${source.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources/<p>` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /internal/v1/spaces/${spaceId} (core/api/deploy_control_public_routes_e2e_test.ts:502)
`core/api/deploy_control_public_routes_e2e_test.ts:502` calls `PATCH /internal/v1/spaces/${spaceId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/<p>` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /internal/v1/spaces/${spaceId} (core/api/deploy_control_public_routes_e2e_test.ts:511)
`core/api/deploy_control_public_routes_e2e_test.ts:511` calls `PATCH /internal/v1/spaces/${spaceId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/<p>` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/retired-provider-env-set-compat/cpp_foreign0001/verify (core/api/deploy_control_internal_routes_test.ts:188)
`core/api/deploy_control_internal_routes_test.ts:188` calls `POST /api/retired-provider-env-set-compat/cpp_foreign0001/verify` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/retired-provider-env-set-compat/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/apply-runs (core/api/deploy_control_public_routes_e2e_test.ts:346)
`core/api/deploy_control_public_routes_e2e_test.ts:346` calls `POST /internal/v1/apply-runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/apply-runs` If this points at an external API, prefix …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/apply-runs (core/api/deploy_control_public_routes_e2e_test.ts:434)
`core/api/deploy_control_public_routes_e2e_test.ts:434` calls `POST /internal/v1/apply-runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/apply-runs` If this points at an external API, prefix …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/apply-runs (core/api/deploy_control_public_routes_e2e_test.ts:742)
`core/api/deploy_control_public_routes_e2e_test.ts:742` calls `POST /internal/v1/apply-runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/apply-runs` If this points at an external API, prefix …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/apply-runs (core/api/deploy_control_public_routes_e2e_test.ts:781)
`core/api/deploy_control_public_routes_e2e_test.ts:781` calls `POST /internal/v1/apply-runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/apply-runs` If this points at an external API, prefix …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/apply-runs (core/api/run_group_routes_test.ts:190)
`core/api/run_group_routes_test.ts:190` calls `POST /internal/v1/apply-runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/apply-runs` If this points at an external API, prefix it with `https:/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/connections/${connection.id}/revoke (core/api/deploy_control_connection_routes_test.ts:697)
`core/api/deploy_control_connection_routes_test.ts:697` calls `POST /internal/v1/connections/${connection.id}/revoke` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/connections/<p>/revoke` If th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/connections/${connection.id}/test (core/api/deploy_control_connection_routes_test.ts:622)
`core/api/deploy_control_connection_routes_test.ts:622` calls `POST /internal/v1/connections/${connection.id}/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/connections/<p>/test` If this p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/connections/${connection.id}/test (core/api/deploy_control_connection_routes_test.ts:671)
`core/api/deploy_control_connection_routes_test.ts:671` calls `POST /internal/v1/connections/${connection.id}/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/connections/<p>/test` If this p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/connections/cloudflare/oauth/start (core/api/deploy_control_connection_routes_test.ts:358)
`core/api/deploy_control_connection_routes_test.ts:358` calls `POST /internal/v1/connections/cloudflare/oauth/start` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/connections/cloudflare/oauth/s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/connections/not-a-conn-id/test (core/api/deploy_control_connection_routes_test.ts:733)
`core/api/deploy_control_connection_routes_test.ts:733` calls `POST /internal/v1/connections/not-a-conn-id/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/connections/not-a-conn-id/test` If…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/connections/provider-env-set (core/api/deploy_control_public_routes_e2e_test.ts:159)
`core/api/deploy_control_public_routes_e2e_test.ts:159` calls `POST /internal/v1/connections/provider-env-set` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/connections/provider-env-set` If thi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/connections/provider-env-set (core/api/deploy_control_public_routes_e2e_test.ts:83)
`core/api/deploy_control_public_routes_e2e_test.ts:83` calls `POST /internal/v1/connections/provider-env-set` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/connections/provider-env-set` If this…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/deploy (core/api/deploy_control_deploy_routes_test.ts:87)
`core/api/deploy_control_deploy_routes_test.ts:87` calls `POST /internal/v1/deploy` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/deploy` If this points at an external API, prefix it with `http…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/deploy (core/api/deploy_control_deploy_routes_test.ts:98)
`core/api/deploy_control_deploy_routes_test.ts:98` calls `POST /internal/v1/deploy` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/deploy` If this points at an external API, prefix it with `http…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/deployments/${deploymentId}/rollback-plan (core/api/deploy_control_public_routes_e2e_test.ts:471)
`core/api/deploy_control_public_routes_e2e_test.ts:471` calls `POST /internal/v1/deployments/${deploymentId}/rollback-plan` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/deployments/<p>/rollbac…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/deployments/deploy_missing0001/rollback-plan (core/api/deploy_control_public_routes_e2e_test.ts:487)
`core/api/deploy_control_public_routes_e2e_test.ts:487` calls `POST /internal/v1/deployments/deploy_missing0001/rollback-plan` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/deployments/deploy_m…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/installations/${consumer}/dependencies (core/api/deploy_control_model_routes_test.ts:305)
`core/api/deploy_control_model_routes_test.ts:305` calls `POST /internal/v1/installations/${consumer}/dependencies` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>/dependencies`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/installations/${consumer}/dependencies (core/api/deploy_control_model_routes_test.ts:327)
`core/api/deploy_control_model_routes_test.ts:327` calls `POST /internal/v1/installations/${consumer}/dependencies` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>/dependencies`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/installations/${consumer}/dependencies (core/api/deploy_control_model_routes_test.ts:410)
`core/api/deploy_control_model_routes_test.ts:410` calls `POST /internal/v1/installations/${consumer}/dependencies` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>/dependencies`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/installations/${consumer}/dependencies (core/api/run_group_routes_test.ts:247)
`core/api/run_group_routes_test.ts:247` calls `POST /internal/v1/installations/${consumer}/dependencies` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>/dependencies` If this po…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/installations/${installationId}/drift-check (core/api/deploy_control_public_routes_e2e_test.ts:761)
`core/api/deploy_control_public_routes_e2e_test.ts:761` calls `POST /internal/v1/installations/${installationId}/drift-check` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>/dri…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/installations/${installationId}/plan (core/api/activity_routes_test.ts:192)
`core/api/activity_routes_test.ts:192` calls `POST /internal/v1/installations/${installationId}/plan` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>/plan` If this points at an …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/installations/${installationId}/plan (core/api/deploy_control_model_routes_test.ts:253)
`core/api/deploy_control_model_routes_test.ts:253` calls `POST /internal/v1/installations/${installationId}/plan` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>/plan` If this p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/installations/${installationId}/plan (core/api/deploy_control_public_routes_e2e_test.ts:318)
`core/api/deploy_control_public_routes_e2e_test.ts:318` calls `POST /internal/v1/installations/${installationId}/plan` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>/plan` If t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/installations/${installationId}/plan (core/api/deploy_control_public_routes_e2e_test.ts:384)
`core/api/deploy_control_public_routes_e2e_test.ts:384` calls `POST /internal/v1/installations/${installationId}/plan` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>/plan` If t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/installations/${installationId}/plan (core/api/deploy_control_public_routes_e2e_test.ts:424)
`core/api/deploy_control_public_routes_e2e_test.ts:424` calls `POST /internal/v1/installations/${installationId}/plan` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>/plan` If t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/installations/${installationId}/plan (core/api/deploy_control_public_routes_e2e_test.ts:727)
`core/api/deploy_control_public_routes_e2e_test.ts:727` calls `POST /internal/v1/installations/${installationId}/plan` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>/plan` If t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/installations/${installationId}/plan (core/api/run_group_routes_test.ts:179)
`core/api/run_group_routes_test.ts:179` calls `POST /internal/v1/installations/${installationId}/plan` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/<p>/plan` If this points at an…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/installations/inst_aaaaaaaa/backups (core/api/deploy_control_backup_routes_test.ts:119)
`core/api/deploy_control_backup_routes_test.ts:119` calls `POST /internal/v1/installations/inst_aaaaaaaa/backups` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/inst_aaaaaaaa/backu…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/installations/inst_aaaaaaaa/backups (core/api/deploy_control_backup_routes_test.ts:217)
`core/api/deploy_control_backup_routes_test.ts:217` calls `POST /internal/v1/installations/inst_aaaaaaaa/backups` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/inst_aaaaaaaa/backu…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/installations/inst_bbbbbbbb/backups (core/api/deploy_control_backup_routes_test.ts:151)
`core/api/deploy_control_backup_routes_test.ts:151` calls `POST /internal/v1/installations/inst_bbbbbbbb/backups` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/inst_bbbbbbbb/backu…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/installations/not-an-installation/backups (core/api/deploy_control_backup_routes_test.ts:160)
`core/api/deploy_control_backup_routes_test.ts:160` calls `POST /internal/v1/installations/not-an-installation/backups` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/installations/not-an-instal…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/lifecycle/verify (core/runtime-agent/server_test.ts:155)
`core/runtime-agent/server_test.ts:155` calls `POST /internal/v1/lifecycle/verify` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/lifecycle/verify` If this points at an external API, prefix it w…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/lifecycle/verify (core/runtime-agent/server_test.ts:175)
`core/runtime-agent/server_test.ts:175` calls `POST /internal/v1/lifecycle/verify` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/lifecycle/verify` If this points at an external API, prefix it w…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/lifecycle/verify (core/runtime-agent/server_test.ts:218)
`core/runtime-agent/server_test.ts:218` calls `POST /internal/v1/lifecycle/verify` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/lifecycle/verify` If this points at an external API, prefix it w…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/lifecycle/verify (core/runtime-agent/server_test.ts:256)
`core/runtime-agent/server_test.ts:256` calls `POST /internal/v1/lifecycle/verify` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/lifecycle/verify` If this points at an external API, prefix it w…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/lifecycle/verify (core/runtime-agent/server_test.ts:295)
`core/runtime-agent/server_test.ts:295` calls `POST /internal/v1/lifecycle/verify` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/lifecycle/verify` If this points at an external API, prefix it w…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/output-shares (core/api/deploy_control_internal_routes_test.ts:327)
`core/api/deploy_control_internal_routes_test.ts:327` calls `POST /internal/v1/output-shares` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/output-shares` If this points at an external API, pre…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/output-shares (core/api/deploy_control_internal_routes_test.ts:346)
`core/api/deploy_control_internal_routes_test.ts:346` calls `POST /internal/v1/output-shares` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/output-shares` If this points at an external API, pre…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/output-shares (core/api/deploy_control_public_routes_e2e_test.ts:569)
`core/api/deploy_control_public_routes_e2e_test.ts:569` calls `POST /internal/v1/output-shares` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/output-shares` If this points at an external API, p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/output-shares (core/api/deploy_control_public_routes_e2e_test.ts:628)
`core/api/deploy_control_public_routes_e2e_test.ts:628` calls `POST /internal/v1/output-shares` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/output-shares` If this points at an external API, p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/output-shares (core/api/deploy_control_public_routes_e2e_test.ts:646)
`core/api/deploy_control_public_routes_e2e_test.ts:646` calls `POST /internal/v1/output-shares` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/output-shares` If this points at an external API, p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/output-shares/${created.id}/approve (core/api/deploy_control_public_routes_e2e_test.ts:586)
`core/api/deploy_control_public_routes_e2e_test.ts:586` calls `POST /internal/v1/output-shares/${created.id}/approve` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/output-shares/<p>/approve` If…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/output-shares/${created.id}/revoke (core/api/deploy_control_public_routes_e2e_test.ts:615)
`core/api/deploy_control_public_routes_e2e_test.ts:615` calls `POST /internal/v1/output-shares/${created.id}/revoke` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/output-shares/<p>/revoke` If t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/output-shares/oshare_missing00001/revoke (core/api/deploy_control_public_routes_e2e_test.ts:661)
`core/api/deploy_control_public_routes_e2e_test.ts:661` calls `POST /internal/v1/output-shares/oshare_missing00001/revoke` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/output-shares/oshare_mis…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/plan-runs (core/api/deploy_control_internal_routes_test.ts:130)
`core/api/deploy_control_internal_routes_test.ts:130` calls `POST /internal/v1/plan-runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/plan-runs` If this points at an external API, prefix it w…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/plan-runs (core/api/deploy_control_internal_routes_test.ts:146)
`core/api/deploy_control_internal_routes_test.ts:146` calls `POST /internal/v1/plan-runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/plan-runs` If this points at an external API, prefix it w…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/plan-runs (core/api/deploy_control_internal_routes_test.ts:213)
`core/api/deploy_control_internal_routes_test.ts:213` calls `POST /internal/v1/plan-runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/plan-runs` If this points at an external API, prefix it w…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/run-groups/${group.runGroup.id}/approve (core/api/run_group_routes_test.ts:338)
`core/api/run_group_routes_test.ts:338` calls `POST /internal/v1/run-groups/${group.runGroup.id}/approve` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/run-groups/<p>/approve` If this points at…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/runs/${compatibilityRunId}/approve (core/api/deploy_control_source_routes_test.ts:261)
`core/api/deploy_control_source_routes_test.ts:261` calls `POST /internal/v1/runs/${compatibilityRunId}/approve` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/runs/<p>/approve` If this points a…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/runs/${planRun.id}/approve (core/api/deploy_control_public_routes_e2e_test.ts:340)
`core/api/deploy_control_public_routes_e2e_test.ts:340` calls `POST /internal/v1/runs/${planRun.id}/approve` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/runs/<p>/approve` If this points at an…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/runs/${planRun.id}/approve (core/api/deploy_control_public_routes_e2e_test.ts:430)
`core/api/deploy_control_public_routes_e2e_test.ts:430` calls `POST /internal/v1/runs/${planRun.id}/approve` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/runs/<p>/approve` If this points at an…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/runs/${planRun.id}/approve (core/api/deploy_control_public_routes_e2e_test.ts:736)
`core/api/deploy_control_public_routes_e2e_test.ts:736` calls `POST /internal/v1/runs/${planRun.id}/approve` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/runs/<p>/approve` If this points at an…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/sources (core/api/activity_routes_test.ts:98)
`core/api/activity_routes_test.ts:98` calls `POST /internal/v1/sources` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/sources (core/api/deploy_control_model_routes_test.ts:45)
`core/api/deploy_control_model_routes_test.ts:45` calls `POST /internal/v1/sources` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources` If this points at an external API, prefix it with `htt…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/sources (core/api/deploy_control_public_routes_e2e_test.ts:231)
`core/api/deploy_control_public_routes_e2e_test.ts:231` calls `POST /internal/v1/sources` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources` If this points at an external API, prefix it wit…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/sources (core/api/deploy_control_source_routes_test.ts:106)
`core/api/deploy_control_source_routes_test.ts:106` calls `POST /internal/v1/sources` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/sources (core/api/deploy_control_source_routes_test.ts:121)
`core/api/deploy_control_source_routes_test.ts:121` calls `POST /internal/v1/sources` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/sources (core/api/deploy_control_source_routes_test.ts:164)
`core/api/deploy_control_source_routes_test.ts:164` calls `POST /internal/v1/sources` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/sources (core/api/deploy_control_source_routes_test.ts:356)
`core/api/deploy_control_source_routes_test.ts:356` calls `POST /internal/v1/sources` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/sources (core/api/deploy_control_source_routes_test.ts:402)
`core/api/deploy_control_source_routes_test.ts:402` calls `POST /internal/v1/sources` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/sources (core/api/deploy_control_source_routes_test.ts:62)
`core/api/deploy_control_source_routes_test.ts:62` calls `POST /internal/v1/sources` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources` If this points at an external API, prefix it with `ht…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/sources (core/api/deploy_control_source_routes_test.ts:76)
`core/api/deploy_control_source_routes_test.ts:76` calls `POST /internal/v1/sources` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources` If this points at an external API, prefix it with `ht…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/sources (core/api/deploy_control_source_routes_test.ts:92)
`core/api/deploy_control_source_routes_test.ts:92` calls `POST /internal/v1/sources` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources` If this points at an external API, prefix it with `ht…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/sources (core/api/run_group_routes_test.ts:91)
`core/api/run_group_routes_test.ts:91` calls `POST /internal/v1/sources` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/sources/${source.id}/compatibility-check (core/api/deploy_control_source_routes_test.ts:190)
`core/api/deploy_control_source_routes_test.ts:190` calls `POST /internal/v1/sources/${source.id}/compatibility-check` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources/<p>/compatibility-ch…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/sources/${source.id}/compatibility-check (core/api/deploy_control_source_routes_test.ts:382)
`core/api/deploy_control_source_routes_test.ts:382` calls `POST /internal/v1/sources/${source.id}/compatibility-check` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources/<p>/compatibility-ch…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/sources/${sourceId}/sync (core/api/deploy_control_source_routes_test.ts:148)
`core/api/deploy_control_source_routes_test.ts:148` calls `POST /internal/v1/sources/${sourceId}/sync` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/sources/<p>/sync` If this points at an exter…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces (core/api/activity_routes_test.ts:77)
`core/api/activity_routes_test.ts:77` calls `POST /internal/v1/spaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces` If this points at an external API, prefix it with `https://` so the …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces (core/api/deploy_control_internal_routes_test.ts:66)
`core/api/deploy_control_internal_routes_test.ts:66` calls `POST /internal/v1/spaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces` If this points at an external API, prefix it with `ht…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces (core/api/deploy_control_internal_routes_test.ts:86)
`core/api/deploy_control_internal_routes_test.ts:86` calls `POST /internal/v1/spaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces` If this points at an external API, prefix it with `ht…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces (core/api/deploy_control_model_routes_test.ts:108)
`core/api/deploy_control_model_routes_test.ts:108` calls `POST /internal/v1/spaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces` If this points at an external API, prefix it with `http…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces (core/api/deploy_control_model_routes_test.ts:27)
`core/api/deploy_control_model_routes_test.ts:27` calls `POST /internal/v1/spaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces` If this points at an external API, prefix it with `https…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces (core/api/deploy_control_public_routes_e2e_test.ts:120)
`core/api/deploy_control_public_routes_e2e_test.ts:120` calls `POST /internal/v1/spaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces` If this points at an external API, prefix it with …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces (core/api/deploy_control_public_routes_e2e_test.ts:218)
`core/api/deploy_control_public_routes_e2e_test.ts:218` calls `POST /internal/v1/spaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces` If this points at an external API, prefix it with …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces (core/api/deploy_control_public_routes_e2e_test.ts:67)
`core/api/deploy_control_public_routes_e2e_test.ts:67` calls `POST /internal/v1/spaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces` If this points at an external API, prefix it with `…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces (core/api/run_group_routes_test.ts:217)
`core/api/run_group_routes_test.ts:217` calls `POST /internal/v1/spaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/${spaceId}/drift-check (core/api/run_group_routes_test.ts:282)
`core/api/run_group_routes_test.ts:282` calls `POST /internal/v1/spaces/${spaceId}/drift-check` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/<p>/drift-check` If this points at an extern…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/${spaceId}/installations (core/api/activity_routes_test.ts:125)
`core/api/activity_routes_test.ts:125` calls `POST /internal/v1/spaces/${spaceId}/installations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/<p>/installations` If this points at an ext…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/${spaceId}/installations (core/api/deploy_control_model_routes_test.ts:128)
`core/api/deploy_control_model_routes_test.ts:128` calls `POST /internal/v1/spaces/${spaceId}/installations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/<p>/installations` If this poin…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/${spaceId}/installations (core/api/deploy_control_model_routes_test.ts:156)
`core/api/deploy_control_model_routes_test.ts:156` calls `POST /internal/v1/spaces/${spaceId}/installations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/<p>/installations` If this poin…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/${spaceId}/installations (core/api/deploy_control_model_routes_test.ts:169)
`core/api/deploy_control_model_routes_test.ts:169` calls `POST /internal/v1/spaces/${spaceId}/installations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/<p>/installations` If this poin…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/${spaceId}/installations (core/api/deploy_control_model_routes_test.ts:189)
`core/api/deploy_control_model_routes_test.ts:189` calls `POST /internal/v1/spaces/${spaceId}/installations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/<p>/installations` If this poin…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/${spaceId}/installations (core/api/deploy_control_model_routes_test.ts:240)
`core/api/deploy_control_model_routes_test.ts:240` calls `POST /internal/v1/spaces/${spaceId}/installations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/<p>/installations` If this poin…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/${spaceId}/installations (core/api/deploy_control_model_routes_test.ts:270)
`core/api/deploy_control_model_routes_test.ts:270` calls `POST /internal/v1/spaces/${spaceId}/installations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/<p>/installations` If this poin…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/${spaceId}/installations (core/api/deploy_control_public_routes_e2e_test.ts:262)
`core/api/deploy_control_public_routes_e2e_test.ts:262` calls `POST /internal/v1/spaces/${spaceId}/installations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/<p>/installations` If this…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/${spaceId}/installations (core/api/run_group_routes_test.ts:127)
`core/api/run_group_routes_test.ts:127` calls `POST /internal/v1/spaces/${spaceId}/installations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/<p>/installations` If this points at an ex…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/${spaceId}/plan-update (core/api/run_group_routes_test.ts:273)
`core/api/run_group_routes_test.ts:273` calls `POST /internal/v1/spaces/${spaceId}/plan-update` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/<p>/plan-update` If this points at an extern…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/${spaceId}/plan-update (core/api/run_group_routes_test.ts:310)
`core/api/run_group_routes_test.ts:310` calls `POST /internal/v1/spaces/${spaceId}/plan-update` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/<p>/plan-update` If this points at an extern…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/not-a-space/backups (core/api/deploy_control_backup_routes_test.ts:81)
`core/api/deploy_control_backup_routes_test.ts:81` calls `POST /internal/v1/spaces/not-a-space/backups` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/not-a-space/backups` If this points …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/not-a-space/drift-check (core/api/run_group_routes_test.ts:372)
`core/api/run_group_routes_test.ts:372` calls `POST /internal/v1/spaces/not-a-space/drift-check` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/not-a-space/drift-check` If this points at …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/not-a-space/plan-update (core/api/run_group_routes_test.ts:366)
`core/api/run_group_routes_test.ts:366` calls `POST /internal/v1/spaces/not-a-space/plan-update` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/not-a-space/plan-update` If this points at …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/space_12345678/credits/top-up (core/api/billing_routes_test.ts:204)
`core/api/billing_routes_test.ts:204` calls `POST /internal/v1/spaces/space_12345678/credits/top-up` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_12345678/credits/top-up` If this …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/space_12345678/credits/top-up (core/api/billing_routes_test.ts:223)
`core/api/billing_routes_test.ts:223` calls `POST /internal/v1/spaces/space_12345678/credits/top-up` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_12345678/credits/top-up` If this …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/space_12345678/subscription/change (core/api/billing_routes_test.ts:287)
`core/api/billing_routes_test.ts:287` calls `POST /internal/v1/spaces/space_12345678/subscription/change` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_12345678/subscription/change…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/space_12345678/subscription/change (core/api/billing_routes_test.ts:325)
`core/api/billing_routes_test.ts:325` calls `POST /internal/v1/spaces/space_12345678/subscription/change` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_12345678/subscription/change…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/space_99999999/credits/top-up (core/api/billing_routes_test.ts:270)
`core/api/billing_routes_test.ts:270` calls `POST /internal/v1/spaces/space_99999999/credits/top-up` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_99999999/credits/top-up` If this …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/space_aaaaaaaa/backups (core/api/deploy_control_backup_routes_test.ts:169)
`core/api/deploy_control_backup_routes_test.ts:169` calls `POST /internal/v1/spaces/space_aaaaaaaa/backups` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_aaaaaaaa/backups` If this …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/space_aaaaaaaa/backups (core/api/deploy_control_backup_routes_test.ts:173)
`core/api/deploy_control_backup_routes_test.ts:173` calls `POST /internal/v1/spaces/space_aaaaaaaa/backups` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_aaaaaaaa/backups` If this …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/space_aaaaaaaa/backups (core/api/deploy_control_backup_routes_test.ts:212)
`core/api/deploy_control_backup_routes_test.ts:212` calls `POST /internal/v1/spaces/space_aaaaaaaa/backups` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_aaaaaaaa/backups` If this …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/space_aaaaaaaa/backups (core/api/deploy_control_backup_routes_test.ts:233)
`core/api/deploy_control_backup_routes_test.ts:233` calls `POST /internal/v1/spaces/space_aaaaaaaa/backups` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_aaaaaaaa/backups` If this …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/space_aaaaaaaa/backups (core/api/deploy_control_backup_routes_test.ts:63)
`core/api/deploy_control_backup_routes_test.ts:63` calls `POST /internal/v1/spaces/space_aaaaaaaa/backups` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_aaaaaaaa/backups` If this p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/space_aaaaaaaa/backups (core/api/deploy_control_backup_routes_test.ts:90)
`core/api/deploy_control_backup_routes_test.ts:90` calls `POST /internal/v1/spaces/space_aaaaaaaa/backups` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_aaaaaaaa/backups` If this p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/space_aaaaaaaa/uploads (core/api/deploy_control_deploy_routes_test.ts:47)
`core/api/deploy_control_deploy_routes_test.ts:47` calls `POST /internal/v1/spaces/space_aaaaaaaa/uploads` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_aaaaaaaa/uploads` If this p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/space_aaaaaaaa/uploads (core/api/deploy_control_deploy_routes_test.ts:56)
`core/api/deploy_control_deploy_routes_test.ts:56` calls `POST /internal/v1/spaces/space_aaaaaaaa/uploads` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_aaaaaaaa/uploads` If this p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/space_bbbbbbbb/backups (core/api/deploy_control_backup_routes_test.ts:72)
`core/api/deploy_control_backup_routes_test.ts:72` calls `POST /internal/v1/spaces/space_bbbbbbbb/backups` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_bbbbbbbb/backups` If this p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /internal/v1/spaces/space_bbbbbbbb/uploads (core/api/deploy_control_deploy_routes_test.ts:77)
`core/api/deploy_control_deploy_routes_test.ts:77` calls `POST /internal/v1/spaces/space_bbbbbbbb/uploads` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/spaces/space_bbbbbbbb/uploads` If this p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /internal/v1/operator-connection-defaults (core/api/deploy_control_connection_routes_test.ts:539)
`core/api/deploy_control_connection_routes_test.ts:539` calls `PUT /internal/v1/operator-connection-defaults` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/operator-connection-defaults` If this…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /internal/v1/operator-connection-defaults (core/api/deploy_control_connection_routes_test.ts:550)
`core/api/deploy_control_connection_routes_test.ts:550` calls `PUT /internal/v1/operator-connection-defaults` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/operator-connection-defaults` If this…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /internal/v1/operator-connection-defaults (core/api/deploy_control_connection_routes_test.ts:583)
`core/api/deploy_control_connection_routes_test.ts:583` calls `PUT /internal/v1/operator-connection-defaults` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/internal/v1/operator-connection-defaults` If this…
Dangling fetchHelper:request
high System graph security security conf 1.00 Insecure pattern 'exec_used' in accounts/cli/src/cli-accounts-db.ts:577
Found a known-risky pattern (exec_used). Review and replace if possible.
accounts/cli/src/cli-accounts-db.ts:577 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in accounts/service/src/d1-store.ts:51
Found a known-risky pattern (exec_used). Review and replace if possible.
accounts/service/src/d1-store.ts:51 Exec used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — accounts/cli/src/cli-accounts-api.ts:25
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — accounts/cli/src/cli-connections-commands.ts:260
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — accounts/cli/src/cli-deploy-commands.ts:198
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — accounts/cli/src/cli-serve-runtime.ts:805
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — contract/internal-rpc.ts:315
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — contract/reference/host-blocklist.ts:9
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — core/adapters/vault/mod.ts:331
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — core/api/deploy_control_connection_routes_test.ts:603
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — core/runtime-agent/artifact_fetcher.ts:16
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — core/runtime-agent/artifact_fetcher_test.ts:39
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — core/shared/runtime/workers.ts:13
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — dashboard/src/lib/control-api.ts:67
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — dashboard/src/views/account/lib/http.ts:60
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — dashboard/src/views/account/lib/session.ts:8
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — deploy/accounts-cloudflare/src/handler.ts:37
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — deploy/accounts-cloudflare/src/worker_test.ts:28
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — deploy/local-substrate/route-registrar/mod.ts:81
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — deploy/node-postgres/src/composed-app.ts:188
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — deploy/node-postgres/src/composed-app_test.ts:102
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — deploy/node-postgres/src/server.ts:213
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — deploy/platform/source_webhook_test.ts:219
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — deploy/platform/worker.ts:96
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — opentofu-modules/module-files.ts:269
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — providers/aws/connection.ts:73
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — providers/cloudflare/hosting/cf_proxy_worker.ts:152
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — providers/cloudflare/hosting/wfp_dispatch_worker.ts:9
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — providers/cloudflare/hosting/wfp_dispatch_worker_test.ts:19
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — runner/entrypoint.ts:2263
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/smoke-cloudflare.ts:76
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — worker/src/bindings.ts:176
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — worker/src/container_runner.ts:268
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — worker/src/deploy_control_seam.ts:69
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — worker/src/durable/OpenTofuRunnerObject_test.ts:63
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — worker/src/handler.ts:30
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — worker/src/index_test.ts:55
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — worker/src/runner_source_archive_relay_test.ts:71
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — worker/src/runner_source_archive_restore_test.ts:60
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — worker/src/runner_state_r2_test.ts:94
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — worker/src/worker_service.ts:146
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: runner/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 24 occurrences Frontend route `/sign-in/callback` has no Link/navigate to it — dashboard/src/index.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
24 occurrences
repo-level (24 hits)
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in accounts/cli/src/cli-accounts-db.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
accounts/cli/src/cli-accounts-db.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in accounts/cli/src/cli-deploy-commands.ts:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
accounts/cli/src/cli-deploy-commands.ts:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in accounts/service/src/export-archive.ts:21
Found a known-risky pattern (node_child_process). Review and replace if possible.
accounts/service/src/export-archive.ts:21 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 96 placeholder/mock markers across 36 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph network Security conf 1.00 Privileged port 1000 in use
Port 1000 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
deploy/node-postgres/Dockerfile Ports
medium System graph network Security conf 1.00 Privileged port 127 in use
Port 127 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
deploy/local-substrate/scripts/prove-no-public-leak.sh Ports
medium System graph network Security conf 1.00 Privileged port 256 in use
Port 256 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
deploy/local-substrate/scripts/tenant-isolation.sh Ports
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
low System graph quality Integrity conf 1.00 32 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CADDY_ADMIN_URL`, `CLOUDFLARE_PROVIDER_VERSION`, `DYNAMIC_HOST_SUFFIX`, `GATEWAY_ROUTE_PROJECTION_FILE`, `LANG`, `LC_ALL`, `LC_MESSAGES`, `LOCAL_SUBSTRATE_TEST_BED` + 24 more. Add them (with a placeholder/comment) to .env.example so onboarding doe…
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 134 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 6 occurrences Docker base image is tag-pinned but not digest-pinned: oven/bun:1
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
3 files, 6 locations
deploy/node-postgres/Dockerfile:6, 23, 29 (3 hits)
Dockerfile:5, 19 (2 hits)
runner/Dockerfile:1
containersPinned dependencies
low System graph quality Agent instructions conf 1.00 Multiple root agent instruction files without precedence
The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies.
Governance
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: deploy/local-substrate/scripts/stripe-webhook-replay.py:http_error_302, deploy/local-substrate/scripts/passkey-e2e.py:http_error_302 This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Co…
duplicatesduplication
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: accounts/cli/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
accounts/cli/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: accounts/platform-services/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
accounts/platform-services/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: accounts/service/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
accounts/service/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: deploy/node-postgres/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
deploy/node-postgres/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: docs/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
docs/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `accounts_v1` in accounts/cli/src/cli-accounts-db.ts:626
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `accounts_v1` in accounts/service/migrations_test.ts:15
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `accounts_v1` in accounts/service/src/postgres-store_test.ts:42
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `accounts_v1` in accounts/service/src/postgres/accounts.ts:26
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `accounts_v1` in accounts/service/src/postgres/billing.ts:33
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `accounts_v1` in accounts/service/src/postgres/passkeys.ts:24
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `accounts_v1` in accounts/service/src/postgres/refresh-chain.ts:31
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `accounts_v1` in accounts/service/src/postgres/sessions.ts:15
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `accounts_v1` in accounts/service/src/postgres/tokens.ts:32
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `accounts_v1` in accounts/service/src/store.ts:714
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `acct_legacy` in accounts/service/src/d1-store_test.ts:517
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `bkp_old` in core/domains/backups/mod_test.ts:437
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `cr_old` in core/adapters/storage/drizzle/schema/schema_mirror_test.ts:497
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `dep_old` in accounts/service/src/mod_test.ts:4886
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `dep_old` in core/domains/deploy-control/store_model_test.ts:1071
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `inst_unused` in core/domains/deploy-control/apply_create_once_test.ts:192
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `installation_v1` in accounts/service/src/postgres/installations.ts:38
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `installation_v1` in accounts/service/src/postgres/internal.ts:636
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `installation_v1` in accounts/service/src/postgres/launch-tokens.ts:25
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `installation_v1` in accounts/service/src/postgres/oidc.ts:16
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `obs_old` in core/domains/runtime/stores_test.ts:42
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `secret_blobs_legacy` in worker/src/d1_opentofu_store.ts:3109
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `secret_v1` in core/domains/resources/service_test.ts:446
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `secret_version_v1` in core/adapters/secret-store/memory_test.ts:25
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `snap_old` in core/domains/deploy-control/installation_run_test.ts:965
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `whsec_local_substrate_fixture_v1` in deploy/local-substrate/scripts/stripe-webhook-replay.py:12
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: b64url_decode
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
deploy/local-substrate/scripts/passkey-e2e.py:67
low System graph software Dead code conf 1.00 Possibly dead Python function: http_error_302
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
deploy/local-substrate/scripts/stripe-webhook-replay.py:62
low System graph software Dead code conf 1.00 Possibly dead Python function: http_error_302
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
deploy/local-substrate/scripts/passkey-e2e.py:100
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — cli/commands/completions.ts:27
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — cli/commands/init.ts:31
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — cli/commands/migrate.ts:150
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — cli/commands/server.ts:94
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — cli/commands/version.ts:8
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — core/adapters/vault/mod.ts:117
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — core/api/artifact_routes_test.ts:129
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — core/api/request_correlation.ts:162
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — core/domains/audit-replication/external_log.ts:178
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — core/runtime-agent/server.ts:387
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — core/scripts/db-migrate-down.ts:124
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — core/scripts/db-migrate.ts:72
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — core/shared/log.ts:187
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — deploy/local-substrate/oauth-mock/main.ts:71
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — deploy/local-substrate/route-registrar/mod.ts:161
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — deploy/local-substrate/wrappers/agent.ts:41
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — deploy/local-substrate/wrappers/cloud.ts:50
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — deploy/node-postgres/src/server.ts:152
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — deploy/node-postgres/src/static-assets_test.ts:15
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/check-platform-bindings.ts:24
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/prove-live-opentofu-plan-apply.ts:260
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/prove-opentofu-output-snapshot.ts:613
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/smoke-cloudflare.ts:120
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/validate-production-hardening-evidence.ts:618
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/verify-production-hardening-gates.ts:420
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak

Showing first 300 of 319. Refine filters or use the findings page for deep search.

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/708250e8-1e57-4154-bf4b-484172453413/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/708250e8-1e57-4154-bf4b-484172453413/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.