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

smithersai/smithers

https://github.com/smithersai/smithers · scanned 2026-06-16 00:17 UTC (2 months, 2 weeks ago)

434 raw signals (0 security + 434 graph)

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

Complete repo analysis

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

JSON
Combined
43.2
/100
Security checks
43
0 findings
System graph
43
100.0% cov · 431 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 115 Medium 78 Low 124 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 431 Crowd 0 Layer: Frontend 56 Hardware 2 Security 45 Cicd 2 Quality 211 Api 115
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 43.2/100 with 100.0% coverage. It contains 10415 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 434 findings — concentrated in quality (211), api (115), frontend (56). Risk profile is high: 0 critical, 115 high, 81 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 315 of 431 actionable findings. 434 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: GET /__smithers_studio/api${path} (apps/smithers-studio-2/src/workflows/workflowsApi.ts:41)
`apps/smithers-studio-2/src/workflows/workflowsApi.ts:41` calls `GET /__smithers_studio/api${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/__smithers_studio/api/<p>` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /__smithers_studio/api${path} (apps/smithers-studio-2/src/workspace/chatApi.ts:47)
`apps/smithers-studio-2/src/workspace/chatApi.ts:47` calls `GET /__smithers_studio/api${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/__smithers_studio/api/<p>` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /__smithers_studio/api${path} (apps/smithers-studio-2/src/workspaceApi.ts:570)
`apps/smithers-studio-2/src/workspaceApi.ts:570` calls `GET /__smithers_studio/api${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/__smithers_studio/api/<p>` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/repos/fixture/widgets/issues (apps/smithers/tests/e2e/plueBridge.spec.ts:43)
`apps/smithers/tests/e2e/plueBridge.spec.ts:43` calls `GET /api/repos/fixture/widgets/issues` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/repos/fixture/widgets/issues` If this points at an external API, prefix it…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/repos/fixture/widgets/issues (apps/smithers/tests/e2e/splitConfig.spec.ts:63)
`apps/smithers/tests/e2e/splitConfig.spec.ts:63` calls `GET /api/repos/fixture/widgets/issues` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/repos/fixture/widgets/issues` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/user (apps/smithers/tests/e2e/plueBridge.spec.ts:22)
`apps/smithers/tests/e2e/plueBridge.spec.ts:22` calls `GET /api/user` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/user` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/user (apps/smithers/tests/e2e/splitConfig.spec.ts:17)
`apps/smithers/tests/e2e/splitConfig.spec.ts:17` calls `GET /api/user` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/user` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/user/keys (apps/smithers/tests/e2e/splitConfig.spec.ts:34)
`apps/smithers/tests/e2e/splitConfig.spec.ts:34` calls `GET /api/user/keys` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/user/keys` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/user/repos (apps/smithers/tests/e2e/plueBridge.spec.ts:29)
`apps/smithers/tests/e2e/plueBridge.spec.ts:29` calls `GET /api/user/repos` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/user/repos` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/user/repos (apps/smithers/tests/e2e/splitConfig.spec.ts:48)
`apps/smithers/tests/e2e/splitConfig.spec.ts:48` calls `GET /api/user/repos` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/user/repos` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /sync/health (apps/smithers/src/pair/PairCoding.tsx:153)
`apps/smithers/src/pair/PairCoding.tsx:153` calls `GET /sync/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/sync/health` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /sync/v1/shape?${params} (apps/smithers/src/pair/PairCoding.tsx:87)
`apps/smithers/src/pair/PairCoding.tsx:87` calls `GET /sync/v1/shape?${params}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/sync/v1/shape` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/approval/list (packages/server/tests/server.test.js:549)
`packages/server/tests/server.test.js:549` calls `GET /v1/approval/list` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/approval/list` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/approval/list (packages/server/tests/server.test.js:611)
`packages/server/tests/server.test.js:611` calls `GET /v1/approval/list` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/approval/list` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/runs (packages/server/tests/server.test.js:500)
`packages/server/tests/server.test.js:500` calls `GET /v1/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` 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/runs (packages/server/tests/server.test.js:508)
`packages/server/tests/server.test.js:508` calls `GET /v1/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` 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/runs/${runId} (packages/server/tests/server.test.js:74)
`packages/server/tests/server.test.js:74` calls `GET /v1/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: `/runs/<p>` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/runs/${startData.runId} (packages/server/tests/server.test.js:269)
`packages/server/tests/server.test.js:269` calls `GET /v1/runs/${startData.runId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs/<p>` 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: GET /v1/runs/${startData.runId}/frames (packages/server/tests/server.test.js:361)
`packages/server/tests/server.test.js:361` calls `GET /v1/runs/${startData.runId}/frames` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs/<p>/frames` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/runs/${startData.runId}/frames?limit=10&afterFrameNo=0 (packages/server/tests/server.test.js:380)
`packages/server/tests/server.test.js:380` calls `GET /v1/runs/${startData.runId}/frames?limit=10&afterFrameNo=0` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs/<p>/frames` If this points at an externa…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/runs/non-existent-run-id (packages/server/tests/server.test.js:278)
`packages/server/tests/server.test.js:278` calls `GET /v1/runs/non-existent-run-id` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs/non-existent-run-id` If this points at an external API, prefix it with…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/runs/non-existent-run-id/frames (packages/server/tests/server.test.js:367)
`packages/server/tests/server.test.js:367` calls `GET /v1/runs/non-existent-run-id/frames` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs/non-existent-run-id/frames` If this points at an external API, …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/runs?limit=10 (packages/server/tests/server.test.js:536)
`packages/server/tests/server.test.js:536` calls `GET /v1/runs?limit=10` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/runs?limit=10&status=running (packages/server/tests/server.test.js:517)
`packages/server/tests/server.test.js:517` calls `GET /v1/runs?limit=10&status=running` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` 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: GET /v1/unknown-route (packages/server/tests/serve.test.js:635)
`packages/server/tests/serve.test.js:635` calls `GET /v1/unknown-route` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/unknown-route` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/unknown-route (packages/server/tests/server.test.js:634)
`packages/server/tests/server.test.js:634` calls `GET /v1/unknown-route` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/unknown-route` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/console (packages/server/tests/gateway-ui.test.jsx:132)
`packages/server/tests/gateway-ui.test.jsx:132` calls `GET http://127.0.0.1:${port}/console` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/console` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/console (packages/server/tests/gateway-ui.test.jsx:166)
`packages/server/tests/gateway-ui.test.jsx:166` calls `GET http://127.0.0.1:${port}/console` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/console` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/console (packages/server/tests/gateway-ui.test.jsx:169)
`packages/server/tests/gateway-ui.test.jsx:169` calls `GET http://127.0.0.1:${port}/console` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/console` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/console (packages/server/tests/gateway-ui.test.jsx:187)
`packages/server/tests/gateway-ui.test.jsx:187` calls `GET http://127.0.0.1:${port}/console` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/console` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/console (packages/server/tests/gateway-ui.test.jsx:79)
`packages/server/tests/gateway-ui.test.jsx:79` calls `GET http://127.0.0.1:${port}/console` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/console` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/console (packages/server/tests/gateway-ui.test.jsx:99)
`packages/server/tests/gateway-ui.test.jsx:99` calls `GET http://127.0.0.1:${port}/console` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/console` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/console/__smithers_ui/client.js (packages/server/tests/gateway-ui.test.jsx:107)
`packages/server/tests/gateway-ui.test.jsx:107` calls `GET http://127.0.0.1:${port}/console/__smithers_ui/client.js` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/console/__smithers_ui/client.j…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/console/__smithers_ui/client.js (packages/server/tests/gateway-ui.test.jsx:140)
`packages/server/tests/gateway-ui.test.jsx:140` calls `GET http://127.0.0.1:${port}/console/__smithers_ui/client.js` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/console/__smithers_ui/client.j…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/console/__smithers_ui/client.js (packages/server/tests/gateway-ui.test.jsx:175)
`packages/server/tests/gateway-ui.test.jsx:175` calls `GET http://127.0.0.1:${port}/console/__smithers_ui/client.js` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/console/__smithers_ui/client.j…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/console/__smithers_ui/client.js (packages/server/tests/gateway-ui.test.jsx:88)
`packages/server/tests/gateway-ui.test.jsx:88` calls `GET http://127.0.0.1:${port}/console/__smithers_ui/client.js` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/console/__smithers_ui/client.js…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/metrics (packages/server/tests/gateway-webhooks.test.jsx:152)
`packages/server/tests/gateway-webhooks.test.jsx:152` calls `GET http://127.0.0.1:${port}/metrics` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/metrics` If this points at an external API, pref…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/workflows/deploy (packages/server/tests/gateway-ui.test.jsx:206)
`packages/server/tests/gateway-ui.test.jsx:206` calls `GET http://127.0.0.1:${port}/workflows/deploy` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/workflows/deploy` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}${path} (packages/server/tests/serve.test.js:65)
`packages/server/tests/serve.test.js:65` calls `GET http://localhost:${port}${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/<p>` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}${path} (packages/server/tests/server.test.js:31)
`packages/server/tests/server.test.js:31` calls `GET http://localhost:${port}${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/<p>` If this points at an external API, prefix it with `https…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/events (packages/server/tests/serve.test.js:408)
`packages/server/tests/serve.test.js:408` calls `GET http://localhost:${port}/events` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/events` If this points at an external API, prefix it with `ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/events (packages/server/tests/serve.test.js:433)
`packages/server/tests/serve.test.js:433` calls `GET http://localhost:${port}/events` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/events` If this points at an external API, prefix it with `ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/events?afterSeq=999999 (packages/server/tests/serve.test.js:468)
`packages/server/tests/serve.test.js:468` calls `GET http://localhost:${port}/events?afterSeq=999999` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/events` If this points at an external API, pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/metrics (packages/server/tests/serve.test.js:516)
`packages/server/tests/serve.test.js:516` calls `GET http://localhost:${port}/metrics` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/metrics` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/metrics (packages/server/tests/serve.test.js:544)
`packages/server/tests/serve.test.js:544` calls `GET http://localhost:${port}/metrics` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/metrics` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/metrics (packages/server/tests/serve.test.js:568)
`packages/server/tests/serve.test.js:568` calls `GET http://localhost:${port}/metrics` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/metrics` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/metrics (packages/server/tests/serve.test.js:589)
`packages/server/tests/serve.test.js:589` calls `GET http://localhost:${port}/metrics` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/metrics` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/metrics (packages/server/tests/serve.test.js:607)
`packages/server/tests/serve.test.js:607` calls `GET http://localhost:${port}/metrics` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/metrics` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/metrics (packages/server/tests/serve.test.js:618)
`packages/server/tests/serve.test.js:618` calls `GET http://localhost:${port}/metrics` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/metrics` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/v1/runs/${startData.runId}/events (packages/server/tests/server.test.js:476)
`packages/server/tests/server.test.js:476` calls `GET http://localhost:${port}/v1/runs/${startData.runId}/events` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/v1/runs/<p>/events` If this point…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/v1/runs/non-existent-run-id/events (packages/server/tests/server.test.js:491)
`packages/server/tests/server.test.js:491` calls `GET http://localhost:${port}/v1/runs/non-existent-run-id/events` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/v1/runs/non-existent-run-id/even…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/repos/${REPO}/releases/latest (scripts/fetch-jj-binaries.mjs:36)
`scripts/fetch-jj-binaries.mjs:36` calls `GET https://api.github.com/repos/${REPO}/releases/latest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/repos/<p>/releases/latest` If this points at a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.openai.com/v1/models (packages/agents/src/diagnostics/getDiagnosticStrategy.js:206)
`packages/agents/src/diagnostics/getDiagnosticStrategy.js:206` calls `GET https://api.openai.com/v1/models` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.openai.com/v1/models` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.openai.com/v1/models (packages/agents/src/diagnostics/getDiagnosticStrategy.js:258)
`packages/agents/src/diagnostics/getDiagnosticStrategy.js:258` calls `GET https://api.openai.com/v1/models` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.openai.com/v1/models` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://generativelanguage.googleapis.com/v1beta/models (packages/agents/src/diagnostics/getDiagnosticStrategy.js:335)
`packages/agents/src/diagnostics/getDiagnosticStrategy.js:335` calls `GET https://generativelanguage.googleapis.com/v1beta/models` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/generativelanguage.googleapis.…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://generativelanguage.googleapis.com/v1beta/models (packages/agents/src/diagnostics/getDiagnosticStrategy.js:400)
`packages/agents/src/diagnostics/getDiagnosticStrategy.js:400` calls `GET https://generativelanguage.googleapis.com/v1beta/models` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/generativelanguage.googleapis.…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /__smithers_studio/api/chat/message (apps/smithers-studio-2/src/workspace/chatApi.ts:91)
`apps/smithers-studio-2/src/workspace/chatApi.ts:91` calls `POST /__smithers_studio/api/chat/message` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/__smithers_studio/api/chat/message` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /approve/task1 (packages/server/tests/serve.test.js:340)
`packages/server/tests/serve.test.js:340` calls `POST /approve/task1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/approve/task1` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /approve/task1 (packages/server/tests/serve.test.js:584)
`packages/server/tests/serve.test.js:584` calls `POST /approve/task1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/approve/task1` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /deny/task1 (packages/server/tests/serve.test.js:362)
`packages/server/tests/serve.test.js:362` calls `POST /deny/task1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/deny/task1` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /deny/task1 (packages/server/tests/serve.test.js:602)
`packages/server/tests/serve.test.js:602` calls `POST /deny/task1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/deny/task1` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /sync${path} (apps/smithers/src/pair/PairCoding.tsx:40)
`apps/smithers/src/pair/PairCoding.tsx:40` calls `POST /sync${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/sync/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/runs (packages/server/tests/server.test.js:181)
`packages/server/tests/server.test.js:181` calls `POST /v1/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` 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: POST /v1/runs (packages/server/tests/server.test.js:194)
`packages/server/tests/server.test.js:194` calls `POST /v1/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` 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: POST /v1/runs (packages/server/tests/server.test.js:203)
`packages/server/tests/server.test.js:203` calls `POST /v1/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` 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: POST /v1/runs (packages/server/tests/server.test.js:215)
`packages/server/tests/server.test.js:215` calls `POST /v1/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` 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: POST /v1/runs (packages/server/tests/server.test.js:224)
`packages/server/tests/server.test.js:224` calls `POST /v1/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` 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: POST /v1/runs (packages/server/tests/server.test.js:250)
`packages/server/tests/server.test.js:250` calls `POST /v1/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` 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: POST /v1/runs (packages/server/tests/server.test.js:263)
`packages/server/tests/server.test.js:263` calls `POST /v1/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` 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: POST /v1/runs (packages/server/tests/server.test.js:288)
`packages/server/tests/server.test.js:288` calls `POST /v1/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` 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: POST /v1/runs (packages/server/tests/server.test.js:299)
`packages/server/tests/server.test.js:299` calls `POST /v1/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` 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: POST /v1/runs (packages/server/tests/server.test.js:313)
`packages/server/tests/server.test.js:313` calls `POST /v1/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` 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: POST /v1/runs (packages/server/tests/server.test.js:338)
`packages/server/tests/server.test.js:338` calls `POST /v1/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` 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: POST /v1/runs (packages/server/tests/server.test.js:356)
`packages/server/tests/server.test.js:356` calls `POST /v1/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` 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: POST /v1/runs (packages/server/tests/server.test.js:375)
`packages/server/tests/server.test.js:375` calls `POST /v1/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` 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: POST /v1/runs (packages/server/tests/server.test.js:390)
`packages/server/tests/server.test.js:390` calls `POST /v1/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` 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: POST /v1/runs (packages/server/tests/server.test.js:429)
`packages/server/tests/server.test.js:429` calls `POST /v1/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` 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: POST /v1/runs (packages/server/tests/server.test.js:468)
`packages/server/tests/server.test.js:468` calls `POST /v1/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` 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: POST /v1/runs (packages/server/tests/server.test.js:649)
`packages/server/tests/server.test.js:649` calls `POST /v1/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs` 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: POST /v1/runs/${startData.runId}/cancel (packages/server/tests/server.test.js:318)
`packages/server/tests/server.test.js:318` calls `POST /v1/runs/${startData.runId}/cancel` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs/<p>/cancel` If this points at an external API, prefix it with `…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/runs/${startData.runId}/nodes/task1/approve (packages/server/tests/server.test.js:395)
`packages/server/tests/server.test.js:395` calls `POST /v1/runs/${startData.runId}/nodes/task1/approve` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs/<p>/nodes/task1/approve` If this points at an exte…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/runs/${startData.runId}/nodes/task1/deny (packages/server/tests/server.test.js:434)
`packages/server/tests/server.test.js:434` calls `POST /v1/runs/${startData.runId}/nodes/task1/deny` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs/<p>/nodes/task1/deny` If this points at an external A…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/runs/${startData.runId}/resume (packages/server/tests/server.test.js:343)
`packages/server/tests/server.test.js:343` calls `POST /v1/runs/${startData.runId}/resume` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs/<p>/resume` If this points at an external API, prefix it with `…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/runs/non-existent-run-id/cancel (packages/server/tests/server.test.js:326)
`packages/server/tests/server.test.js:326` calls `POST /v1/runs/non-existent-run-id/cancel` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs/non-existent-run-id/cancel` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/runs/non-existent-run-id/nodes/some-node/approve (packages/server/tests/server.test.js:404)
`packages/server/tests/server.test.js:404` calls `POST /v1/runs/non-existent-run-id/nodes/some-node/approve` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs/non-existent-run-id/nodes/some-node/approve` …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/runs/non-existent-run-id/nodes/some-node/approve (packages/server/tests/server.test.js:415)
`packages/server/tests/server.test.js:415` calls `POST /v1/runs/non-existent-run-id/nodes/some-node/approve` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs/non-existent-run-id/nodes/some-node/approve` …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/runs/non-existent-run-id/nodes/some-node/deny (packages/server/tests/server.test.js:443)
`packages/server/tests/server.test.js:443` calls `POST /v1/runs/non-existent-run-id/nodes/some-node/deny` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs/non-existent-run-id/nodes/some-node/deny` If thi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/runs/non-existent-run-id/nodes/some-node/deny (packages/server/tests/server.test.js:454)
`packages/server/tests/server.test.js:454` calls `POST /v1/runs/non-existent-run-id/nodes/some-node/deny` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/runs/non-existent-run-id/nodes/some-node/deny` If thi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/rpc (packages/server/tests/gateway-http-boundaries.test.js:159)
`packages/server/tests/gateway-http-boundaries.test.js:159` calls `POST http://127.0.0.1:${port}/rpc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/rpc` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/rpc (packages/server/tests/gateway-http-boundaries.test.js:196)
`packages/server/tests/gateway-http-boundaries.test.js:196` calls `POST http://127.0.0.1:${port}/rpc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/rpc` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/rpc (packages/server/tests/gateway-http-boundaries.test.js:210)
`packages/server/tests/gateway-http-boundaries.test.js:210` calls `POST http://127.0.0.1:${port}/rpc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/rpc` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/rpc (packages/server/tests/gateway-http-boundaries.test.js:265)
`packages/server/tests/gateway-http-boundaries.test.js:265` calls `POST http://127.0.0.1:${port}/rpc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/rpc` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/rpc (packages/server/tests/gateway-http-boundaries.test.js:281)
`packages/server/tests/gateway-http-boundaries.test.js:281` calls `POST http://127.0.0.1:${port}/rpc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/rpc` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/rpc (packages/server/tests/gateway-http-boundaries.test.js:294)
`packages/server/tests/gateway-http-boundaries.test.js:294` calls `POST http://127.0.0.1:${port}/rpc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/rpc` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/rpc (packages/server/tests/gateway-http-boundaries.test.js:308)
`packages/server/tests/gateway-http-boundaries.test.js:308` calls `POST http://127.0.0.1:${port}/rpc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/rpc` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/rpc (packages/server/tests/gateway-http-boundaries.test.js:324)
`packages/server/tests/gateway-http-boundaries.test.js:324` calls `POST http://127.0.0.1:${port}/rpc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/rpc` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/rpc (packages/server/tests/gateway-http-boundaries.test.js:394)
`packages/server/tests/gateway-http-boundaries.test.js:394` calls `POST http://127.0.0.1:${port}/rpc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/rpc` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/rpc (packages/server/tests/gateway-http-boundaries.test.js:410)
`packages/server/tests/gateway-http-boundaries.test.js:410` calls `POST http://127.0.0.1:${port}/rpc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/rpc` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/rpc (packages/server/tests/gateway.test.jsx:369)
`packages/server/tests/gateway.test.jsx:369` calls `POST http://127.0.0.1:${port}/rpc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/rpc` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/rpc (packages/server/tests/gateway.test.jsx:389)
`packages/server/tests/gateway.test.jsx:389` calls `POST http://127.0.0.1:${port}/rpc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/rpc` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/rpc/${method} (e2e/faults/case25-approval-scope-denial.test.ts:127)
`e2e/faults/case25-approval-scope-denial.test.ts:127` calls `POST http://127.0.0.1:${port}/v1/rpc/${method}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/rpc/<p>` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/rpc/${method} (packages/server/tests/gateway-ui.test.jsx:43)
`packages/server/tests/gateway-ui.test.jsx:43` calls `POST http://127.0.0.1:${port}/v1/rpc/${method}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/rpc/<p>` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/rpc/${method} (packages/server/tests/gateway-v1-contract.test.jsx:95)
`packages/server/tests/gateway-v1-contract.test.jsx:95` calls `POST http://127.0.0.1:${port}/v1/rpc/${method}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/rpc/<p>` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/rpc/listRuns (apps/cli/tests/gateway-command.test.js:87)
`apps/cli/tests/gateway-command.test.js:87` calls `POST http://127.0.0.1:${port}/v1/rpc/listRuns` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/rpc/listruns` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/webhooks/${workflowKey} (e2e/faults/case17-webhook-bad-signature.test.ts:299)
`e2e/faults/case17-webhook-bad-signature.test.ts:299` calls `POST http://127.0.0.1:${port}/webhooks/${workflowKey}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/webhooks/<p>` If this points at…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/webhooks/${workflowKey} (packages/server/tests/gateway-webhooks.test.jsx:45)
`packages/server/tests/gateway-webhooks.test.jsx:45` calls `POST http://127.0.0.1:${port}/webhooks/${workflowKey}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/webhooks/<p>` If this points at …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/webhooks/github (packages/server/tests/gateway-webhooks.test.jsx:135)
`packages/server/tests/gateway-webhooks.test.jsx:135` calls `POST http://127.0.0.1:${port}/webhooks/github` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/webhooks/github` If this points at an e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${port}/v1/runs (packages/server/tests/server.test.js:236)
`packages/server/tests/server.test.js:236` calls `POST http://localhost:${port}/v1/runs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/v1/runs` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages/count_tokens (packages/agents/src/diagnostics/getDiagnosticStrategy.js:108)
`packages/agents/src/diagnostics/getDiagnosticStrategy.js:108` calls `POST https://api.anthropic.com/v1/messages/count_tokens` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages/coun…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.freestyle.sh/v1/vms/${vm}/exec-await (apps/smithers/src/pair/pairSyncDO.ts:171)
`apps/smithers/src/pair/pairSyncDO.ts:171` calls `POST https://api.freestyle.sh/v1/vms/${vm}/exec-await` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.freestyle.sh/v1/vms/<p>/exec-await` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/notifications (apps/smithers/tests/e2e/plueBridge.spec.ts:55)
`apps/smithers/tests/e2e/plueBridge.spec.ts:55` calls `PUT /api/notifications` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/notifications` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'exec_used' in apps/review/src/server/d1.ts:35
Found a known-risky pattern (exec_used). Review and replace if possible.
apps/review/src/server/d1.ts:35 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/control-plane/src/index.d.ts:4
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/control-plane/src/index.d.ts:4 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/errors/src/smithersErrorDefinitions.js:315
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/errors/src/smithersErrorDefinitions.js:315 Exec used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in packages/graph/src/dom/extract.js:26
Found a known-risky pattern (new_function_used). Review and replace if possible.
packages/graph/src/dom/extract.js:26 New function used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/cli/src/index.js:1945
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 — apps/cli/src/watch.js:83
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 — apps/review/src/server/worker.ts:54
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 — apps/smithers-studio-2/electrobun/studioRpc.ts:21
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 — apps/smithers-studio-2/server/createWorkspaceApiServer.test.ts:158
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 — apps/smithers-studio-2/src/runs/useRunsData.ts:86
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 — apps/smithers/public/sw.js: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 — apps/smithers/src/auth/authClient.ts:238
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 — apps/smithers/src/env.ts:65
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 — apps/smithers/src/gateway/gatewayClient.test.ts:104
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 — apps/smithers/src/gateway/gatewayClient.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 — apps/smithers/src/jjhub/platformFetch.ts:17
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 — apps/smithers/src/observability/workerMetrics.test.ts:43
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 — apps/smithers/src/pair/pairSyncDO.ts:171
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 — apps/smithers/src/worker.realkey.test.ts:40
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 — apps/smithers/src/worker.test.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 — apps/smithers/src/worker.ts:376
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 — apps/smithers/src/workerPlue.test.ts:74
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 — benchmarks/claw-eval-live/gateway/src/server.ts:86
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 — benchmarks/swe-bench-pro/scripts/fetch-dataset.js:21
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 — e2e/faults/case17-webhook-bad-signature.test.ts:299
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 — e2e/faults/case25-approval-scope-denial.test.ts:127
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 — examples/swe-evo/dataset/load.ts:38
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 — packages/gateway-client/src/sync/SyncCache.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 — packages/openapi/src/loadSpecEffect.js:26
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 — packages/openapi/src/tool-factory/_helpers.js:126
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 — packages/server/src/gateway.js:1494
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/e2e-real/worker.ts:64
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/fetch-jj-binaries.mjs:36
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: examples/kubernetes/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/pr-review.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in apps/smithers/src/pair/pairSyncDO.ts:82
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
apps/smithers/src/pair/pairSyncDO.ts:82 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/server/src/gatewayUi/defaultOperatorUi.js:1258
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/server/src/gatewayUi/defaultOperatorUi.js:1258 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in poc/run-chronicle.html:413
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
poc/run-chronicle.html:413 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/src/agent-commands/runAgentAdd.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/src/agent-commands/runAgentAdd.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/src/agent-detection.js:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/src/agent-detection.js:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/src/hijack.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/src/hijack.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/src/index.js:28
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/src/index.js:28 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/src/restore.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/src/restore.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/src/resume-detached.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/src/resume-detached.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/src/scheduler.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/src/scheduler.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/cli/src/workflow-pack.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/cli/src/workflow-pack.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/review/action/src/runAction.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/review/action/src/runAction.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/review/action/src/runReview.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/review/action/src/runReview.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/review/src/cli/main.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/review/src/cli/main.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/review/src/github/runGh.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/review/src/github/runGh.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/smithers-studio-2/server/runs/launchWorkflowRun.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/smithers-studio-2/server/runs/launchWorkflowRun.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/smithers-studio-2/server/workspaceBackend.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/smithers-studio-2/server/workspaceBackend.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in benchmarks/swe-bench-pro/scripts/setup.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
benchmarks/swe-bench-pro/scripts/setup.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in benchmarks/swe-bench-pro/src/extractPatch.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
benchmarks/swe-bench-pro/src/extractPatch.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in benchmarks/swe-bench-pro/src/prepareCheckout.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
benchmarks/swe-bench-pro/src/prepareCheckout.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in benchmarks/swe-bench-pro/src/runViaGateway.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
benchmarks/swe-bench-pro/src/runViaGateway.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in benchmarks/swe-bench-pro/src/runWorkflowForInstance.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
benchmarks/swe-bench-pro/src/runWorkflowForInstance.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in benchmarks/swe-bench-pro/src/scorePatch.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
benchmarks/swe-bench-pro/src/scorePatch.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/agents/src/BaseCliAgent/runRpcCommandEffect.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/agents/src/BaseCliAgent/runRpcCommandEffect.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/agents/src/diagnostics/getDiagnosticStrategy.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/agents/src/diagnostics/getDiagnosticStrategy.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/driver/src/child-process.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/driver/src/child-process.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/engine/src/effect/diff-bundle.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/engine/src/effect/diff-bundle.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/engine/src/engine.js:43
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/engine/src/engine.js:43 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/server/src/gatewayRoutes/getNodeDiff.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/server/src/gatewayRoutes/getNodeDiff.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/smithers/src/tools/utils.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/smithers/src/tools/utils.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/usage/src/readClaudeCredentials.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/usage/src/readClaudeCredentials.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/vcs/src/vcsToolingStatus.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/vcs/src/vcsToolingStatus.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/bump.mjs:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/bump.mjs:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-docs.mjs:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-docs.mjs:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-llms.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-llms.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/e2e-real/capture-gifs.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/e2e-real/capture-gifs.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/fetch-jj-binaries.mjs:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/fetch-jj-binaries.mjs:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/publish.mjs:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/publish.mjs:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/sandbox.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/sandbox.ts:2 Node child process
medium System graph cicd CI/CD security conf 1.00 4 occurrences Install-time lifecycle script performs network/shell-sensitive actions
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
4 files, 4 locations
packages/jj-darwin-arm64/package.json
packages/jj-darwin-x64/package.json
packages/jj-linux-arm64/package.json
packages/jj-linux-x64/package.json
CI/CD securitySupply chainNpm
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — benchmarks/roadmapbench/harness/audit_run.py:115
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 167 placeholder/mock markers across 85 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 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 Debug conf 1.00 Debug logging residue appears in source files
Found 264 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 Docker base image is tag-pinned but not digest-pinned: oven/bun:1.3
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
examples/kubernetes/Dockerfile:1 containersPinned dependencies
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/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.
apps/cli/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/observability/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.
apps/observability/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/review/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.
apps/review/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/smithers-demo/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.
apps/smithers-demo/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/smithers-studio-2/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.
apps/smithers-studio-2/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/smithers-tui-demo/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.
apps/smithers-tui-demo/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/smithers/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.
apps/smithers/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: e2e/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.
e2e/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: examples/dstack/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.
examples/dstack/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: examples/kubernetes/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.
examples/kubernetes/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/accounts/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.
packages/accounts/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/agents/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.
packages/agents/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/components/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.
packages/components/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/control-plane/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.
packages/control-plane/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/db/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.
packages/db/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/devtools/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.
packages/devtools/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/driver/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.
packages/driver/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/engine/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.
packages/engine/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/errors/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.
packages/errors/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/gateway-client/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.
packages/gateway-client/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/gateway-react/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.
packages/gateway-react/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/gateway/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.
packages/gateway/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/graph/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.
packages/graph/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/memory/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.
packages/memory/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/openapi/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.
packages/openapi/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/pi-plugin/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.
packages/pi-plugin/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/protocol/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.
packages/protocol/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/react-reconciler/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.
packages/react-reconciler/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/sandbox/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.
packages/sandbox/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/scheduler/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.
packages/scheduler/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/scorers/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.
packages/scorers/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/server/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.
packages/server/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/smithers/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.
packages/smithers/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/time-travel/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.
packages/time-travel/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/tool-context/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.
packages/tool-context/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/usage/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.
packages/usage/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/vcs/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.
packages/vcs/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_smithers_cp_secret_refs_legacy` in packages/control-plane/src/index.js:184
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 `current_working_copy` in apps/smithers-studio-2/server/workspaceBackend.ts:2392
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 `lnOld` in apps/smithers/src/diff/authRefactorDiff.ts: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 quality Integrity conf 1.00 Old/deprecated-named symbol `lnOld` in apps/smithers/src/diff/Diff.ts:7
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 `lnOld` in apps/smithers/src/diff/diffDomain.test.ts:27
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 `lnOld` in apps/smithers/src/diff/DiffHunks.tsx:43
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 `lnOld` in apps/smithers/src/diff/diffPaginateDomain.test.ts:117
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 `org_legacy` in packages/control-plane/tests/control-plane.test.js:316
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 `out_unused` in packages/time-travel/tests/rewindRollback.test.ts:21
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 `parse_log_pytest_v2` in examples/swe-evo/harness/parsers.py:8
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 `runLegacy` in packages/engine/tests/engine-legacy-mode.test.jsx: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 `runWorkflowBodyLegacy` in packages/engine/src/engine.js:4623
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 `sessions_v1` in apps/smithers/src/approvals/approvals.ts:146
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 `V_old` in benchmarks/roadmapbench/harness/audit_run.py: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 `withoutOld` in apps/smithers-studio-2/src/issues/IssuesPanel.tsx:95
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 `withoutOld` in apps/smithers-studio-2/src/landings/LandingsPanel.tsx:204
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 `working_copy` in packages/engine/tests/workspace-watcher.test.js:60
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 frontend Frontend quality conf 1.00 React Flow <Controls> without dark theming — apps/smithers-demo/src/App.tsx:223
`<Controls>` ships with white buttons. Override `.react-flow__controls` and `.react-flow__controls-button` in your stylesheet or pass a styled wrapper. Why: P1 in CHECKLIST.md — vendor defaults bleed light through. Rule id: fq.controls.no-bg
Fq controls no bg
low System graph frontend Frontend quality conf 1.00 React Flow <Controls> without dark theming — apps/smithers/src/askme/WorkflowGraph.tsx:57
`<Controls>` ships with white buttons. Override `.react-flow__controls` and `.react-flow__controls-button` in your stylesheet or pass a styled wrapper. Why: P1 in CHECKLIST.md — vendor defaults bleed light through. Rule id: fq.controls.no-bg
Fq controls no bg
low System graph frontend Frontend quality conf 1.00 React Flow edge with `label=` but no project-wide edge-label CSS override — packages/accounts/src/parseAccountsFile.js:86
React Flow edge labels render with a white rectangle behind the text by default, which scatters bright boxes across a dark canvas. Either drop the label, or override `.react-flow__edge-textbg` and `.react-flow__edge-text` in your stylesheet. Why: P-H in CHECKLIST.md — vendor edge labels bleed whit…
Fq edge label no bg
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 — apps/cli/src/index.js:2236
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 — apps/cli/src/workflow-pack.js:1722
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 — apps/cli/tests/_capture-workflow-ui-screenshots.test.js:116
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 — apps/cli/tests/workflow-ui-all.e2e.test.js:165
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 — apps/review/action/src/runAction.ts:32
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 — apps/review/action/src/runGate.ts:25
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 — apps/review/alchemy.run.ts:73
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 — apps/review/src/cli/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 — apps/smithers-studio-2/scripts/dev.ts:59
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 — apps/smithers-studio-2/scripts/pty-server.ts:595
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 — apps/smithers-studio-2/tests/e2e/pty-server.spec.ts:40
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 — apps/smithers/alchemy.run.ts:81
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 — apps/smithers/scripts/capture/capture.ts:533
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 — apps/smithers/scripts/capture/generateSlideshow.ts:402
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 — apps/smithers/tests/fixtures/authFixture.ts:64
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 — apps/smithers/tests/fixtures/cerebrasUpstream.ts:62
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 — apps/smithers/tests/fixtures/fakePlueHost.ts:452
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 — apps/smithers/tests/fixtures/plueFixture.ts:137
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 — apps/smithers/tests/fixtures/workerHost.ts:40
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 — benchmarks/claw-eval-live/gateway/src/server.ts:118
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 — benchmarks/swe-bench-pro/scripts/cli.js:69
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 — benchmarks/swe-bench-pro/scripts/fetch-dataset.js:23
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 — benchmarks/swe-bench-pro/scripts/gateway-server.js: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 — benchmarks/swe-bench-pro/scripts/setup.js: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 — benchmarks/swe-bench-pro/src/runBenchmark.js:33
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 — benchmarks/swe-bench-pro/src/runInstance.js:56
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 — benchmarks/swe-bench-pro/src/runViaGateway.js:163
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 — e2e/faults/case28-soak-live-stream-rss.test.ts:282
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 — examples/bun-port-smithers/components/porting-rules.ts:66
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 — examples/kubernetes/scripts/build.js:11
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 — examples/kubernetes/scripts/deploy.js:14
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 — examples/kubernetes/scripts/teardown.js:2
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 — examples/swe-evo/dataset/load.ts:83
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 — examples/swe-evo/run.ts:262
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 — examples/swe-evo/verify-gold.ts:82
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 — packages/agents/tests/opencode-e2e.test.js:45
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 — packages/agents/tests/vibe-agent-e2e.test.js:46
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 — packages/devtools/src/DevToolsRunStore.js: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 — packages/react-reconciler/src/devtools/SmithersDevTools.js:238
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/e2e-real/build-slideshow.ts:349
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/e2e-real/capture-gifs.ts:97
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/e2e-real/worker.ts:73
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/generate-llms.ts:239
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/normalize-bunx.ts:136
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/normalize-placeholders.ts:133
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/optimize-llms-full.ts:404
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/sandbox.ts:18
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 api Wiring conf 1.00 Unused endpoint: GET /events
`packages/server/src/serve.js` declares `GET /events` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /approve/:nodeId
`packages/server/src/serve.js` declares `POST /approve/:nodeId` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint

Showing first 300 of 315. 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/6b75b606-f295-4593-a3ca-00d9d9e20417/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/6b75b606-f295-4593-a3ca-00d9d9e20417/

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.