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

theshadow27/mcp-cli

https://github.com/theshadow27/mcp-cli · scanned 2026-06-16 00:34 UTC (2 months, 2 weeks ago)

338 raw signals (0 security + 338 graph)

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

Complete repo analysis

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

JSON
Combined
48.2
/100
Security checks
48
0 findings
System graph
48
100.0% cov · 323 findings
Critical
6
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 6 High 74 Medium 86 Low 102 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 323 Crowd 0 Layer: Frontend 69 Security 42 Cicd 3 Quality 142 Api 67
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 48.2/100 with 100.0% coverage. It contains 5402 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 338 findings — concentrated in quality (142), frontend (69), api (67). Risk profile is high: 18 critical, 74 high, 86 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 251 of 323 actionable findings. 338 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.

critical System graph security Secrets conf 1.00 Possible secret in packages/core/src/telemetry.ts
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
packages/core/src/telemetry.ts:16
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/diary/20260312.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/diary/20260312.md:78 SecretsClaude instruction
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/memory/feedback_phase_repair_to_qa.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/memory/feedback_phase_repair_to_qa.md:10 SecretsClaude instruction
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/memory/feedback_quota_status_staleness.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/memory/feedback_quota_status_staleness.md:14 SecretsClaude instruction
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost${path} (packages/daemon/src/ipc-server.spec.ts:120)
`packages/daemon/src/ipc-server.spec.ts:120` calls `GET http://localhost${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>` If this points at an external API, prefix it with `https://` so th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events (packages/daemon/src/ipc-server.spec.ts:2287)
`packages/daemon/src/ipc-server.spec.ts:2287` calls `GET http://localhost/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/events` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events (packages/daemon/src/ipc-server.spec.ts:2342)
`packages/daemon/src/ipc-server.spec.ts:2342` calls `GET http://localhost/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/events` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events (packages/daemon/src/ipc-server.spec.ts:2387)
`packages/daemon/src/ipc-server.spec.ts:2387` calls `GET http://localhost/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/events` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events (packages/daemon/src/ipc-server.spec.ts:2587)
`packages/daemon/src/ipc-server.spec.ts:2587` calls `GET http://localhost/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/events` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events (packages/daemon/src/ipc-server.spec.ts:2831)
`packages/daemon/src/ipc-server.spec.ts:2831` calls `GET http://localhost/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/events` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events (packages/daemon/src/ipc-server.spec.ts:2881)
`packages/daemon/src/ipc-server.spec.ts:2881` calls `GET http://localhost/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/events` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events (packages/daemon/src/ipc-server.spec.ts:2900)
`packages/daemon/src/ipc-server.spec.ts:2900` calls `GET http://localhost/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/events` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events (packages/daemon/src/ipc-server.spec.ts:3502)
`packages/daemon/src/ipc-server.spec.ts:3502` calls `GET http://localhost/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/events` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events (packages/daemon/src/ipc-server.spec.ts:3518)
`packages/daemon/src/ipc-server.spec.ts:3518` calls `GET http://localhost/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/events` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events (packages/daemon/src/ipc-server.spec.ts:3564)
`packages/daemon/src/ipc-server.spec.ts:3564` calls `GET http://localhost/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/events` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events (packages/daemon/src/ipc-server.spec.ts:3611)
`packages/daemon/src/ipc-server.spec.ts:3611` calls `GET http://localhost/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/events` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events (packages/daemon/src/ipc-server.spec.ts:3653)
`packages/daemon/src/ipc-server.spec.ts:3653` calls `GET http://localhost/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/events` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events (packages/daemon/src/ipc-server.spec.ts:3677)
`packages/daemon/src/ipc-server.spec.ts:3677` calls `GET http://localhost/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/events` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events (packages/daemon/src/ipc-server.spec.ts:3736)
`packages/daemon/src/ipc-server.spec.ts:3736` calls `GET http://localhost/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/events` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events (packages/daemon/src/ipc-server.spec.ts:3862)
`packages/daemon/src/ipc-server.spec.ts:3862` calls `GET http://localhost/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/events` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events (packages/daemon/src/ipc-server.spec.ts:4101)
`packages/daemon/src/ipc-server.spec.ts:4101` calls `GET http://localhost/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/events` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events (packages/daemon/src/ipc-server.spec.ts:4128)
`packages/daemon/src/ipc-server.spec.ts:4128` calls `GET http://localhost/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/events` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events (test/session-result-sse.integration.spec.ts:51)
`test/session-result-sse.integration.spec.ts:51` calls `GET http://localhost/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/events` 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/events?phase=review (packages/daemon/src/ipc-server.spec.ts:3046)
`packages/daemon/src/ipc-server.spec.ts:3046` calls `GET http://localhost/events?phase=review` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` 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/events?pr=${encodeURIComponent(bad)} (packages/daemon/src/ipc-server.spec.ts:2300)
`packages/daemon/src/ipc-server.spec.ts:2300` calls `GET http://localhost/events?pr=${encodeURIComponent(bad)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?pr=${encodeURIComponent(bad)} (packages/daemon/src/ipc-server.spec.ts:3488)
`packages/daemon/src/ipc-server.spec.ts:3488` calls `GET http://localhost/events?pr=${encodeURIComponent(bad)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?responseTail=other-session (packages/daemon/src/ipc-server.spec.ts:2455)
`packages/daemon/src/ipc-server.spec.ts:2455` calls `GET http://localhost/events?responseTail=other-session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external API, …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?responseTail=other-session (packages/daemon/src/ipc-server.spec.ts:3932)
`packages/daemon/src/ipc-server.spec.ts:3932` calls `GET http://localhost/events?responseTail=other-session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external API, …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?responseTail=s1 (packages/daemon/src/ipc-server.spec.ts:2422)
`packages/daemon/src/ipc-server.spec.ts:2422` calls `GET http://localhost/events?responseTail=s1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?responseTail=s1 (packages/daemon/src/ipc-server.spec.ts:3897)
`packages/daemon/src/ipc-server.spec.ts:3897` calls `GET http://localhost/events?responseTail=s1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?since=${cursor} (packages/daemon/src/ipc-server.spec.ts:2328)
`packages/daemon/src/ipc-server.spec.ts:2328` calls `GET http://localhost/events?since=${cursor}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?since=${encodeURIComponent(bad)} (packages/daemon/src/ipc-server.spec.ts:2313)
`packages/daemon/src/ipc-server.spec.ts:2313` calls `GET http://localhost/events?since=${encodeURIComponent(bad)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?since=0 (packages/daemon/src/ipc-server.spec.ts:2538)
`packages/daemon/src/ipc-server.spec.ts:2538` calls `GET http://localhost/events?since=0` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?since=0 (packages/daemon/src/ipc-server.spec.ts:3183)
`packages/daemon/src/ipc-server.spec.ts:3183` calls `GET http://localhost/events?since=0` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?since=0 (packages/daemon/src/ipc-server.spec.ts:3330)
`packages/daemon/src/ipc-server.spec.ts:3330` calls `GET http://localhost/events?since=0` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?since=0 (packages/daemon/src/ipc-server.spec.ts:3458)
`packages/daemon/src/ipc-server.spec.ts:3458` calls `GET http://localhost/events?since=0` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?since=0 (packages/daemon/src/ipc-server.spec.ts:3979)
`packages/daemon/src/ipc-server.spec.ts:3979` calls `GET http://localhost/events?since=0` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?since=0&responseTail=other-session (packages/daemon/src/ipc-server.spec.ts:3267)
`packages/daemon/src/ipc-server.spec.ts:3267` calls `GET http://localhost/events?since=0&responseTail=other-session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?since=0&responseTail=other-session (packages/daemon/src/ipc-server.spec.ts:4063)
`packages/daemon/src/ipc-server.spec.ts:4063` calls `GET http://localhost/events?since=0&responseTail=other-session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?since=0&responseTail=s1 (packages/daemon/src/ipc-server.spec.ts:3225)
`packages/daemon/src/ipc-server.spec.ts:3225` calls `GET http://localhost/events?since=0&responseTail=s1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external API, pre…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?since=0&responseTail=s1 (packages/daemon/src/ipc-server.spec.ts:4021)
`packages/daemon/src/ipc-server.spec.ts:4021` calls `GET http://localhost/events?since=0&responseTail=s1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external API, pre…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?since=0&subscribe=work_item (packages/daemon/src/ipc-server.spec.ts:3141)
`packages/daemon/src/ipc-server.spec.ts:3141` calls `GET http://localhost/events?since=0&subscribe=work_item` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external API,…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?since=2 (packages/daemon/src/ipc-server.spec.ts:2693)
`packages/daemon/src/ipc-server.spec.ts:2693` calls `GET http://localhost/events?since=2` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?since=2 (packages/daemon/src/ipc-server.spec.ts:2763)
`packages/daemon/src/ipc-server.spec.ts:2763` calls `GET http://localhost/events?since=2` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?subscribe=mail&responseTail=s1 (packages/daemon/src/ipc-server.spec.ts:2644)
`packages/daemon/src/ipc-server.spec.ts:2644` calls `GET http://localhost/events?subscribe=mail&responseTail=s1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?subscribe=session (packages/daemon/src/ipc-server.spec.ts:3817)
`packages/daemon/src/ipc-server.spec.ts:3817` calls `GET http://localhost/events?subscribe=session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external API, prefix it…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?subscribe=work_item (packages/daemon/src/ipc-server.spec.ts:2490)
`packages/daemon/src/ipc-server.spec.ts:2490` calls `GET http://localhost/events?subscribe=work_item` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?subscribe=work_item&pr=42 (packages/daemon/src/ipc-server.spec.ts:3093)
`packages/daemon/src/ipc-server.spec.ts:3093` calls `GET http://localhost/events?subscribe=work_item&pr=42` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external API, p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/events?type=pr.* (packages/daemon/src/ipc-server.spec.ts:2929)
`packages/daemon/src/ipc-server.spec.ts:2929` calls `GET http://localhost/events?type=pr.*` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/events` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/logs (packages/daemon/src/ipc-server.spec.ts:444)
`packages/daemon/src/ipc-server.spec.ts:444` calls `GET http://localhost/logs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/logs` If this points at an external API, prefix it with `https://` so the…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/logs?daemon=true (packages/daemon/src/ipc-server.spec.ts:4178)
`packages/daemon/src/ipc-server.spec.ts:4178` calls `GET http://localhost/logs?daemon=true` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/logs` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/logs?daemon=true&lines=0 (packages/daemon/src/ipc-server.spec.ts:2018)
`packages/daemon/src/ipc-server.spec.ts:2018` calls `GET http://localhost/logs?daemon=true&lines=0` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/logs` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/logs?daemon=true&lines=10 (packages/daemon/src/ipc-server.spec.ts:2039)
`packages/daemon/src/ipc-server.spec.ts:2039` calls `GET http://localhost/logs?daemon=true&lines=10` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/logs` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/logs?server=myserver&lines=5 (packages/daemon/src/ipc-server.spec.ts:2077)
`packages/daemon/src/ipc-server.spec.ts:2077` calls `GET http://localhost/logs?server=myserver&lines=5` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/logs` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/metrics (packages/daemon/src/ipc-server.spec.ts:1296)
`packages/daemon/src/ipc-server.spec.ts:1296` calls `GET http://localhost/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/metrics` 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:${assignedPort}/ (scripts/rules/fixtures/no-hardcoded-test-port__clean.fixture.ts:26)
`scripts/rules/fixtures/no-hardcoded-test-port__clean.fixture.ts:26` calls `GET http://localhost:${assignedPort}/` 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>` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/callback?code=again (packages/daemon/src/auth/callback-server.spec.ts:129)
`packages/daemon/src/auth/callback-server.spec.ts:129` calls `GET http://localhost:${port}/callback?code=again` 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>/callback` If this points at an exte…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/invalid (packages/daemon/src/claude-session/ws-server.spec.ts:959)
`packages/daemon/src/claude-session/ws-server.spec.ts:959` calls `GET http://localhost:${port}/invalid` 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>/invalid` If this points at an external API,…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${port}/session/nonexistent (packages/daemon/src/claude-session/ws-server.spec.ts:950)
`packages/daemon/src/claude-session/ws-server.spec.ts:950` calls `GET http://localhost:${port}/session/nonexistent` 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>/session/nonexistent` If this po…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${server.port}/ (scripts/bun-segfault-repro/worker.ts:28)
`scripts/bun-segfault-repro/worker.ts:28` calls `GET http://localhost:${server.port}/` 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>` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost/rpc (packages/daemon/src/alias-state.spec.ts:88)
`packages/daemon/src/alias-state.spec.ts:88` calls `POST http://localhost/rpc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/rpc` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost/rpc (packages/daemon/src/ipc-server.spec.ts:211)
`packages/daemon/src/ipc-server.spec.ts:211` calls `POST http://localhost/rpc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/rpc` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost/rpc (packages/daemon/src/ipc-server.spec.ts:4257)
`packages/daemon/src/ipc-server.spec.ts:4257` calls `POST http://localhost/rpc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/rpc` If this points at an external API, prefix it with `https://` so the…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost/rpc (packages/daemon/src/ipc-server.spec.ts:4270)
`packages/daemon/src/ipc-server.spec.ts:4270` calls `POST http://localhost/rpc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/rpc` If this points at an external API, prefix it with `https://` so the…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost/rpc (packages/daemon/src/ipc-server.spec.ts:4313)
`packages/daemon/src/ipc-server.spec.ts:4313` calls `POST http://localhost/rpc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/rpc` If this points at an external API, prefix it with `https://` so the…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost/rpc (packages/daemon/src/ipc-server.spec.ts:859)
`packages/daemon/src/ipc-server.spec.ts:859` calls `POST http://localhost/rpc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/rpc` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost/rpc (packages/daemon/src/ipc-server.ts:71)
`packages/daemon/src/ipc-server.ts:71` calls `POST http://localhost/rpc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/rpc` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost/rpc (test/harness.ts:275)
`test/harness.ts:275` calls `POST http://localhost/rpc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost/rpc` 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 https://api.openai.com/v1/embeddings (.claude/skills/estimate/embed.ts:51)
`.claude/skills/estimate/embed.ts:51` calls `POST https://api.openai.com/v1/embeddings` 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/embeddings` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/core/src/branch-guard.ts:39
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/core/src/branch-guard.ts:39 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/core/src/git.ts:30
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/core/src/git.ts:30 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/daemon/src/github/graphql-client.ts:244
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/daemon/src/github/graphql-client.ts:244 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/daemon/src/index.ts:150
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/daemon/src/index.ts:150 Exec used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in packages/daemon/src/site/browser/playwright.ts:424
Found a known-risky pattern (new_function_used). Review and replace if possible.
packages/daemon/src/site/browser/playwright.ts:424 New function used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — .claude/skills/estimate/embed.ts:51
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/clone/src/engine/__tests__/mock-provider.spec.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 — packages/clone/src/engine/__tests__/mock-provider.ts:129
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/clone/src/engine/clone.ts:29
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/clone/src/engine/pull.ts:285
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/clone/src/providers/asana.spec.ts:481
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/clone/src/providers/asana.ts:220
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/clone/src/providers/confluence.spec.ts:335
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/clone/src/providers/confluence.ts:224
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/clone/src/providers/github-issues.spec.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 — packages/clone/src/providers/github-issues.ts:163
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/clone/src/providers/jira.spec.ts:266
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/clone/src/providers/jira.ts:182
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/clone/src/providers/provider.ts:97
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/command/src/commands/upgrade.ts:148
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/command/src/commands/vfs.ts:347
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/command/src/registry/client.ts:5
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/core/src/gh-client.ts:4
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/core/src/ipc-client.ts:166
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/daemon/src/alias-state.spec.ts:88
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/daemon/src/auth/callback-server.spec.ts:24
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/daemon/src/auth/callback-server.ts:55
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/daemon/src/claude-session/ws-server.spec.ts:950
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/daemon/src/ipc-server.spec.ts:120
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/daemon/src/ipc-server.ts:194
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/daemon/src/open-event-stream.spec.ts:234
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/opencode/src/opencode-client.ts:4
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/opencode/src/opencode-sse.spec.ts:76
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/opencode-spike.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 — test/event-filter.integration.spec.ts:99
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 — test/harness.ts:275
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 — test/http-401-server.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 — test/monitor-alias.integration.spec.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 — test/session-result-sse.integration.spec.ts:51
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 authority lacks a verifier contract: .claude/commands/mine-rules.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/commands/mine-rules.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/memory/feedback_meta_issue_planning_guard.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/memory/feedback_meta_issue_planning_guard.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/memory/feedback_no_rebase_sprint_branch.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/memory/feedback_no_rebase_sprint_branch.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/memory/feedback_phase_repair_to_qa.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/memory/feedback_phase_repair_to_qa.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/memory/feedback_schedulewakeup_orchestration.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/memory/feedback_schedulewakeup_orchestration.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/memory/feedback_sprint_bulk_and_cascade.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/memory/feedback_sprint_bulk_and_cascade.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/memory/project_sprint_operator.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/memory/project_sprint_operator.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/memory/project_sprites_remote_orchestration.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/memory/project_sprites_remote_orchestration.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/memory/user_cache_ttl.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/memory/user_cache_ttl.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/diary/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/diary/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/estimate/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/estimate/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/sprint-lessons/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/sprint-lessons/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/sprint/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/sprint/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/why/references/plan.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/why/references/plan.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/why/references/why-workflow.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/why/references/why-workflow.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/why/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/why/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/sprints/sprint-24.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/sprints/sprint-24.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: packages/daemon/src/mock-session/CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
packages/daemon/src/mock-session/CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: skill/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
skill/SKILL.md VerificationSkill file
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 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/release.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in .claude/skills/estimate/backfill.ts:22
Found a known-risky pattern (node_child_process). Review and replace if possible.
.claude/skills/estimate/backfill.ts:22 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in .claude/skills/estimate/triage.ts:21
Found a known-risky pattern (node_child_process). Review and replace if possible.
.claude/skills/estimate/triage.ts:21 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in .claude/skills/sprint-lessons/extract-sprint-sessions.ts:28
Found a known-risky pattern (node_child_process). Review and replace if possible.
.claude/skills/sprint-lessons/extract-sprint-sessions.ts:28 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in agent-grid/src/isolation.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
agent-grid/src/isolation.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in docs/claude-patch/triage.ts:23
Found a known-risky pattern (node_child_process). Review and replace if possible.
docs/claude-patch/triage.ts:23 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/clone/src/engine/clone.ts:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/clone/src/engine/clone.ts:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/clone/src/engine/pull.ts:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/clone/src/engine/pull.ts:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/command/src/commands/alias.ts:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/command/src/commands/alias.ts:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/core/src/claude-patch/patcher.ts:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/core/src/claude-patch/patcher.ts:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/daemon/src/port-holder.ts:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/daemon/src/port-holder.ts:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/daemon/src/tls/self-signed.ts:18
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/daemon/src/tls/self-signed.ts:18 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/_runner/ci-steps.ts:26
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/_runner/ci-steps.ts:26 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/_runner/runner.ts:25
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/_runner/runner.ts:25 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/_runner/verdict-cache.ts:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/_runner/verdict-cache.ts:11 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/agent-grid-detect.ts:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/agent-grid-detect.ts:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/coverage-diff.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/coverage-diff.ts:1 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 107 placeholder/mock markers across 35 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
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
89 test file(s) for 895 source file(s) (ratio 0.10). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Maintenance conf 1.00 75 TODO/FIXME markers
High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 356 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 cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/upload-artifact@v7 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 4 locations
.github/workflows/ci.yml:113, 154, 201 (3 hits)
.github/workflows/macos-matrix.yml:67
CI/CD securitySupply chainGithub actions
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: agent-grid/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.
agent-grid/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/acp/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/acp/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/clone/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/clone/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/codex/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/codex/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/command/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/command/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/control/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/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/core/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/core/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/daemon/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/daemon/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/opencode/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/opencode/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `closeOld` in packages/daemon/src/server-pool.spec.ts:1475
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 `feedback_old` in packages/command/src/commands/memory.spec.ts:136
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 cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
package.json CI/CD securitySupply chainNpm
low System graph frontend Frontend quality conf 1.00 React Flow edge with `label=` but no project-wide edge-label CSS override — packages/core/src/gh-client.ts:728
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 — .claude/skills/diary/extract-sessions.ts:227
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 — .claude/skills/estimate/backfill.ts:423
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 — .claude/skills/estimate/embed.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 — .claude/skills/estimate/score.ts:473
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 — .claude/skills/estimate/triage.ts:68
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 — .claude/skills/estimate/validate-triage.ts:149
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 — .claude/skills/estimate/validate.ts:531
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 — .claude/skills/find-session/scripts/extract-messages.ts:91
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 — .claude/skills/find-session/scripts/recent-sessions.ts:42
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 — .claude/skills/find-session/scripts/search-sessions.ts:176
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 — .claude/skills/flaky-tests/mine-flaky-tests.ts:207
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 — .claude/skills/rule-author/scripts/extract-pr.ts:140
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 — .claude/skills/sprint-lessons/extract-sprint-sessions.ts:392
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 — docs/claude-patch/slice.ts:36
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 — docs/claude-patch/triage.ts:203
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/command/src/alias-runner.ts:85
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/command/src/commands/agent-grid.ts:314
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/command/src/commands/agent.ts:1626
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/command/src/commands/alias.spec.ts:177
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/command/src/commands/alias.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 — packages/command/src/commands/auth.ts: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 — packages/command/src/commands/automation.ts:30
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/command/src/commands/claude.ts:580
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/command/src/commands/completions.ts:145
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/command/src/commands/dump.ts:138
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/command/src/commands/export.ts:117
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/command/src/commands/gc.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 — packages/command/src/commands/get.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 — packages/command/src/commands/import.ts:398
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/command/src/commands/memory.ts:327
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/command/src/commands/note.ts:75
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/command/src/commands/phase.ts:112
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/command/src/commands/pr.ts:257
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/command/src/commands/registry-cmd.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 — packages/command/src/commands/serve-kill.ts: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 — packages/command/src/commands/site.ts:22
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/command/src/commands/spans.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 — packages/command/src/commands/sprint-stats.ts:411
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/command/src/commands/telemetry.ts:22
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/command/src/commands/track.ts:264
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/command/src/commands/tty.ts:79
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/command/src/commands/upgrade.ts:48
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/command/src/commands/version.ts: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 — packages/command/src/commands/vfs.ts:199
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/command/src/commands/worktree-commands.ts:124
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/command/src/main.ts:130
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/command/src/output.ts:53
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/core/src/alias-bundle.spec.ts:55
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/daemon/src/alias-executor.spec.ts:255
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/daemon/src/automation-dispatcher.ts:416
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/daemon/src/handlers/alias.spec.ts:129
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/daemon/src/index.ts:939
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/acp-spike.ts:768
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/build.ts:22
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/check-coverage.ts:272
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/install-agent.ts:84
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/release.ts:179
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/rules/fixtures/args-bounds__flagged.fixture.ts:38
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/rules/fixtures/args-bounds__safe.fixture.ts:16
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/rules/fixtures/args-bounds__suppressed.fixture.ts:17
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/rules/fixtures/named-timeouts__clean.fixture.ts:39
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/rules/fixtures/no-manual-arg-parsing__clean.fixture.ts: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 — scripts/rules/fixtures/no-manual-arg-parsing__flagged.fixture.ts:19
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/rules/fixtures/no-manual-arg-parsing__suppressed.fixture.ts:15
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/rules/fixtures/no-raw-path-handling__clean.fixture.ts:48
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/rules/fixtures/test-empty-catch__flagged.fixture.ts:24
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/test-failures.ts: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 — scripts/test-timing.ts:216
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 /session
`packages/opencode/src/opencode-client.ts` declares `GET /session` 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 /session
`packages/opencode/src/opencode-client.ts` declares `POST /session` 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: packages/command/src/commands/agent.spec.ts (2492 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/command/src/commands/agent.ts (1969 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/command/src/commands/claude.spec.ts (5750 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/command/src/commands/claude.ts (2283 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/command/src/commands/phase.spec.ts (3710 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/command/src/commands/phase.ts (2120 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/daemon/src/claude-server.spec.ts (1895 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/daemon/src/claude-session/ws-server.spec.ts (5442 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/daemon/src/claude-session/ws-server.ts (2967 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/daemon/src/db/state.spec.ts (2425 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/daemon/src/db/state.ts (1976 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/daemon/src/index.ts (1444 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/daemon/src/ipc-server.spec.ts (4440 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/daemon/src/server-pool.spec.ts (1836 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/daemon/src/work-items-server.spec.ts (1534 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/67e53a5f-fde4-4448-baab-939f4b580a01/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/67e53a5f-fde4-4448-baab-939f4b580a01/

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.