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
26 of your 75 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

smithersai/smithers

https://github.com/smithersai/smithers · scanned 2026-06-06 00:35 UTC (4 days, 1 hour ago) · 10 languages

703 raw signals (73 security + 630 graph) 11/13 scanners ran 78th percentile · Javascript · medium (20-100K LoC) System graph score 68 (higher by 11)

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

Complete repo analysis

Last scanned 4 days, 1 hour ago · v2 · 340 actionable findings from 2 signal sources. 48 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
73.6
/100
Security checks
79
25 findings
System graph
68
100.0% cov · 315 findings
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 85.0 0.20 17.00
documentation_score 69.0 0.15 10.35
practices_score 60.0 0.15 9.00
code_quality 80.0 0.10 8.00
Overall 1.00 78.3
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 102 Medium 24 Low 116 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 25 System graph 315 Crowd 0 Layer: Quality 135 Security 4 Cicd 2 Software 55 Frontend 41 Hardware 2 Api 101
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 Ranks in the 89th percentile among large-sized repos. Strongest dependencies (85), security (75); weakest testing (50), structure (51). 14 findings. Most common pattern: cpp-new-without-delete.

Showing 242 of 340 actionable findings. 388 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 Security checks software dependencies conf 0.90 ✓ Repobility [MINED122] package.json dep `smithers-orchestrator` pulled from URL/Git: `dependencies.smithers-orchestrator` = `file:../../packages/smithers` bypasses the npm registry. No integrity hash, no version locking, no registry-side scanning. If the URL or git host is compromised, every `npm install` pulls the new payload.
Publish the dependency to npm (or your private registry) and reference it by `^x.y.z`. If that's not possible, lock by commit SHA: `git+https://...#<full-sha>` AND verify the SHA in CI.
examples/dstack/package.json:1
high Security checks software dependencies conf 0.90 ✓ Repobility [MINED122] package.json dep `smithers-orchestrator` pulled from URL/Git: `dependencies.smithers-orchestrator` = `file:../../packages/smithers` bypasses the npm registry. No integrity hash, no version locking, no registry-side scanning. If the URL or git host is compromised, every `npm install` pulls the new payload.
Publish the dependency to npm (or your private registry) and reference it by `^x.y.z`. If that's not possible, lock by commit SHA: `git+https://...#<full-sha>` AND verify the SHA in CI.
examples/kubernetes/package.json:1
medium Security checks cicd CI/CD security conf 0.90 ✓ Repobility 7 occurrences GitHub Action is tag-pinned rather than SHA-pinned
[MINED115] Action `pnpm/action-setup` pinned to mutable ref `@v6.0.8`: `uses: pnpm/[email protected]` resolves at workflow-run time. Tags and branches can be re-pushed by the action owner; that made the tj-actions/changed-files compromise (2025) instantly affect ~23K repos. Pin to a 40-char commi…
3 files, 7 locations
.github/workflows/ci.yml:15, 42, 52 (3 hits)
.github/workflows/faults-nightly.yml:17, 27 (2 hits)
.github/workflows/faults.yml:16, 26 (2 hits)
CI/CD securitySupply chainGitHub Actions
low Security checks cicd CI/CD security conf 0.90 ✓ Repobility 8 occurrences GitHub Action is tag-pinned rather than SHA-pinned
[MINED115] Action `actions/checkout` pinned to mutable ref `@v6.0.2`: `uses: actions/[email protected]` resolves at workflow-run time. Tags and branches can be re-pushed by the action owner; that made the tj-actions/changed-files compromise (2025) instantly affect ~23K repos. Pin to a 40-char commit …
3 files, 8 locations
.github/workflows/ci.yml:14, 20, 41, 47 (4 hits)
.github/workflows/faults-nightly.yml:16, 22 (2 hits)
.github/workflows/faults.yml:15, 21 (2 hits)
CI/CD securitySupply chainGitHub Actions
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 /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.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 /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}/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 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
medium Security checks quality Practices conf 1.00 [CFG006] Missing .gitignore: No .gitignore file. Risk of committing secrets and build artifacts.
Add a .gitignore appropriate for your language/framework.
high Security checks quality Quality conf 0.74 Codex auth.json is read or copied without visible secret-file hardening
Use the platform credential store where possible. If auth files must be touched, enforce 0600 permissions, avoid backups in the repo/workspace, redact logs, and document rotation if the file is exposed.
apps/cli/src/agent-detection.js:26
medium Security checks quality Quality conf 0.73 Codex session log reader may expose prompts or tool-call content
Parse only usage metadata by default. Redact prompts, tool arguments, file paths, and message content before storage, telemetry, export, screenshots, or support bundles.
apps/cli/src/index.js:503
medium Security checks quality Quality conf 0.70 Public web app has no Content Security Policy
Add a Content-Security-Policy header through the web framework or hosting config. For static apps, add a CSP meta tag that restricts default-src, script-src, connect-src, img-src, and frame-ancestors.
index.html
medium Security checks quality Quality conf 0.78 Public web service has no security.txt
Add /.well-known/security.txt with Contact, Expires, Canonical, Preferred-Languages, and Policy fields. Keep the contact endpoint monitored.
.well-known/security.txt
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/cli/src/index.js:5194
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/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/worker.realkey.test.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 — 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:159
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:61
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/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:1426
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 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 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
low Security checks quality Quality conf 0.60 30 occurrences Duplicated implementation block across source files
Duplicate implementation blocks are maintenance debt. Keep them visible, but they are not a high-severity defect unless the duplicated logic is security-sensitive or drifting.
12 files, 30 locations
.smithers/ui/review.tsx:22, 66, 176, 182, 186 (5 hits)
.smithers/ui/ship-pipeline.tsx:20, 53, 459, 463 (4 hits)
.smithers/ui/improve-test-coverage.tsx:12, 194, 201 (3 hits)
.smithers/ui/open-code-review.tsx:64, 308, 309 (3 hits)
.smithers/ui/research-plan-implement.tsx:244, 245, 537 (3 hits)
.smithers/ui/research.tsx:185, 191, 195 (3 hits)
.smithers/ui/implement.tsx:260, 267 (2 hits)
.smithers/ui/ralph.tsx:132, 138 (2 hits)
duplicationquality
low Security checks quality Quality conf 0.50 Public web app has no humans.txt
Add humans.txt with team ownership, contact URL, key documentation links, and the last-updated date.
humans.txt
low Security checks quality Quality conf 0.72 Public web app has no sitemap
Add sitemap.xml, a sitemap index, or a framework-native sitemap route and reference it from robots.txt.
sitemap.xml
low Security checks quality Quality conf 0.74 robots.txt does not advertise a sitemap
Add `Sitemap: https://your-domain.example/sitemap.xml` to robots.txt.
packages/usage/README.md
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 software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/AgentAvailability.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/AggregateNodeDetailParams.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/AskOptions.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/ChatAttemptMeta.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/ChatAttemptRow.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/ChatOutputEvent.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/DiscoveredWorkflow.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/EnrichedNodeDetail.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/EventCategory.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/FindDbWaitOptions.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/FormatEventLineOptions.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/HijackCandidate.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/HijackLaunchSpec.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/index.d.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/InitWorkflowPackOptions.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/InitWorkflowPackResult.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/NativeHijackEngine.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/NodeDetailAttempt.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/NodeDetailTokenUsage.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/ParsedNodeOutputEvent.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/RenderNodeDetailOptions.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/RunAutoResumeSkipReason.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/RunDiffCommandResult.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/RunOutputCommandResult.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/RunRewindCommandInput.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/RunRewindCommandResult.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/RunTreeCommandInput.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/RunTreeCommandResult.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/SmithersEventType.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/SupervisorPollSummary.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/TreeRenderOptions.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/WatchLoopResult.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/WatchRenderContext.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/WhyBlocker.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/WhyBlockerKind.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/WorkflowCta.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/src/WorkflowSourceType.ts
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/tests/cli-flag-validation.test.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/tests/cli-format.test.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/tests/cli-help.test.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/tests/cli-workflows-validate.test.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/tests/errorMessage-coverage.test.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/tests/eval-suite.test.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/tests/event-categories.test.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/tests/semantic-mcp.test.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: apps/cli/tests/token-store.test.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: benchmarks/swe-bench-pro/scripts/gateway-server.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: benchmarks/swe-bench-pro/src/config.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: benchmarks/swe-bench-pro/src/swebpScorer.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: preload.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
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:2391
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:4345
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 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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/cli/src/index.js:2060
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:1717
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/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:43
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/workerHost.ts:37
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:93
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:147
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:224
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/generate-llms.ts:234
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:155
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:394
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
low System graph api Wiring conf 1.00 Unused endpoint: POST /deny/:nodeId
`packages/server/src/serve.js` declares `POST /deny/: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
low System graph api Wiring conf 1.00 Unused endpoint: PUT /
`apps/smithers/public/sw.js` declares `PUT /` 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 quality Complexity conf 1.00 Very large file: apps/cli/src/index.js (5809 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/cli/src/workflow-pack.js (3865 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/smithers-studio-2/server/workspaceBackend.ts (4720 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/components/src/index.d.ts (1602 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/db/src/adapter.js (2530 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/db/src/index.d.ts (5209 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/engine/src/engine.js (7301 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/engine/src/index.d.ts (1685 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/server/src/gateway.js (4219 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/server/src/index.js (1247 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/3ea87ef2-a1fd-4fb0-9ab4-17a616e1e4c3/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/3ea87ef2-a1fd-4fb0-9ab4-17a616e1e4c3/

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.