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

thedotmack/claude-mem

https://github.com/thedotmack/claude-mem · scanned 2026-06-16 00:34 UTC (2 months, 2 weeks ago)

426 raw signals (0 security + 426 graph)

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

Complete repo analysis

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

JSON
Combined
36.3
/100
Security checks
36
0 findings
System graph
36
100.0% cov · 416 findings
Critical
1
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 1 High 95 Medium 77 Low 139 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 416 Crowd 0 Layer: Software 1 Frontend 65 Hardware 4 Security 52 Cicd 3 Quality 148 Api 143
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 36.3/100 with 100.0% coverage. It contains 4294 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 426 findings — concentrated in quality (148), api (143), frontend (65). Risk profile is high: 1 critical, 95 high, 82 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 312 of 416 actionable findings. 426 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 docker/e2e/server-beta-e2e.mjs
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
docker/e2e/server-beta-e2e.mjs:152
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${address.port}/api/health (tests/server/server-beta-service.test.ts:49)
`tests/server/server-beta-service.test.ts:49` calls `GET http://127.0.0.1:${address.port}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${address.port}/v1/info (tests/server/server-beta-service.test.ts:53)
`tests/server/server-beta-service.test.ts:53` calls `GET http://127.0.0.1:${address.port}/v1/info` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/info` If this points at an external API, pref…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${e}/api/readiness (plugin/scripts/worker-cli.js:12)
`plugin/scripts/worker-cli.js:12` calls `GET http://127.0.0.1:${e}/api/readiness` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/readiness` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}${endpointPath} (src/services/infrastructure/HealthMonitor.ts:13)
`src/services/infrastructure/HealthMonitor.ts:13` calls `GET http://127.0.0.1:${port}${endpointPath}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/<p>` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}${path} (tests/compat/sessions-observations-adapter.test.ts:166)
`tests/compat/sessions-observations-adapter.test.ts:166` calls `GET http://127.0.0.1:${port}${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/<p>` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}${path} (tests/server/runtime/jobs-list-and-operator-routes.test.ts:153)
`tests/server/runtime/jobs-list-and-operator-routes.test.ts:153` calls `GET http://127.0.0.1:${port}${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/<p>` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}${path} (tests/server/runtime/server-session-routes.test.ts:134)
`tests/server/runtime/server-session-routes.test.ts:134` calls `GET http://127.0.0.1:${port}${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/<p>` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}${path} (tests/server/runtime/team-project-jobs-routes.test.ts:174)
`tests/server/runtime/team-project-jobs-routes.test.ts:174` calls `GET http://127.0.0.1:${port}${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/<p>` If this points at an external API, pre…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/ (tests/server/server-runtime-smoke.test.ts:124)
`tests/server/server-runtime-smoke.test.ts:124` calls `GET http://127.0.0.1:${port}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>` 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://127.0.0.1:${port}/ (tests/server/server-viewer-routes.test.ts:69)
`tests/server/server-viewer-routes.test.ts:69` calls `GET http://127.0.0.1:${port}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>` 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://127.0.0.1:${port}/api/health (src/services/infrastructure/HealthMonitor.ts:26)
`src/services/infrastructure/HealthMonitor.ts:26` calls `GET http://127.0.0.1:${port}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external API, pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/health (tests/server/server-security-headers.test.ts:42)
`tests/server/server-security-headers.test.ts:42` calls `GET http://127.0.0.1:${port}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external API, pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/health (tests/server/server-security-headers.test.ts:57)
`tests/server/server-security-headers.test.ts:57` calls `GET http://127.0.0.1:${port}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external API, pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/health (tests/worker-spawn.test.ts:23)
`tests/worker-spawn.test.ts:23` calls `GET http://127.0.0.1:${port}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/readiness (src/services/integrations/WindsurfHooksInstaller.ts:296)
`src/services/integrations/WindsurfHooksInstaller.ts:296` calls `GET http://127.0.0.1:${port}/api/readiness` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/readiness` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/stats (scripts/bug-report/collector.ts:122)
`scripts/bug-report/collector.ts:122` calls `GET http://127.0.0.1:${port}/api/stats` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/stats` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/echo (tests/server/middleware/request-id.test.ts:17)
`tests/server/middleware/request-id.test.ts:17` calls `GET http://127.0.0.1:${port}/echo` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/echo` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/echo (tests/server/middleware/request-id.test.ts:36)
`tests/server/middleware/request-id.test.ts:36` calls `GET http://127.0.0.1:${port}/echo` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/echo` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/echo (tests/server/middleware/request-id.test.ts:55)
`tests/server/middleware/request-id.test.ts:55` calls `GET http://127.0.0.1:${port}/echo` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/echo` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/health (scripts/bug-report/collector.ts:111)
`scripts/bug-report/collector.ts:111` calls `GET http://127.0.0.1:${port}/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/health` 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://127.0.0.1:${port}/v1/info (tests/server/server-runtime-smoke.test.ts:88)
`tests/server/server-runtime-smoke.test.ts:88` calls `GET http://127.0.0.1:${port}/v1/info` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/info` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/v1/info (tests/server/server-viewer-routes.test.ts:61)
`tests/server/server-viewer-routes.test.ts:61` calls `GET http://127.0.0.1:${port}/v1/info` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/info` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/v1/jobs/${encodeURIComponent(jobId!)} (tests/server/runtime/server-mcp-routes.test.ts:225)
`tests/server/runtime/server-mcp-routes.test.ts:225` calls `GET http://127.0.0.1:${port}/v1/jobs/${encodeURIComponent(jobId!)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/jobs/<p>` If thi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/v1/projects (tests/server/server-runtime-smoke.test.ts:115)
`tests/server/server-runtime-smoke.test.ts:115` calls `GET http://127.0.0.1:${port}/v1/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/projects` If this points at an external API, pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/v1/projects (tests/server/server-runtime-smoke.test.ts:96)
`tests/server/server-runtime-smoke.test.ts:96` calls `GET http://127.0.0.1:${port}/v1/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/projects` If this points at an external API, pre…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/v1/projects (tests/server/v1-routes.test.ts:216)
`tests/server/v1-routes.test.ts:216` calls `GET http://127.0.0.1:${port}/v1/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/projects` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/v1/projects (tests/server/v1-routes.test.ts:259)
`tests/server/v1-routes.test.ts:259` calls `GET http://127.0.0.1:${port}/v1/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/projects` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/v1/teams/${teamAId}/jobs (tests/server/runtime/team-project-jobs-routes.test.ts:243)
`tests/server/runtime/team-project-jobs-routes.test.ts:243` calls `GET http://127.0.0.1:${port}/v1/teams/${teamAId}/jobs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/teams/<p>/jobs` If thi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/health (tests/integration/hook-execution-e2e.test.ts:139)
`tests/integration/hook-execution-e2e.test.ts:139` calls `GET http://127.0.0.1:${testPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/health (tests/integration/hook-execution-e2e.test.ts:170)
`tests/integration/hook-execution-e2e.test.ts:170` calls `GET http://127.0.0.1:${testPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/health (tests/integration/hook-execution-e2e.test.ts:176)
`tests/integration/hook-execution-e2e.test.ts:176` calls `GET http://127.0.0.1:${testPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/health (tests/integration/hook-execution-e2e.test.ts:74)
`tests/integration/hook-execution-e2e.test.ts:74` calls `GET http://127.0.0.1:${testPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/health (tests/integration/worker-api-endpoints.test.ts:101)
`tests/integration/worker-api-endpoints.test.ts:101` calls `GET http://127.0.0.1:${testPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/health (tests/integration/worker-api-endpoints.test.ts:229)
`tests/integration/worker-api-endpoints.test.ts:229` calls `GET http://127.0.0.1:${testPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/health (tests/integration/worker-api-endpoints.test.ts:274)
`tests/integration/worker-api-endpoints.test.ts:274` calls `GET http://127.0.0.1:${testPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/health (tests/integration/worker-api-endpoints.test.ts:280)
`tests/integration/worker-api-endpoints.test.ts:280` calls `GET http://127.0.0.1:${testPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/health (tests/integration/worker-api-endpoints.test.ts:300)
`tests/integration/worker-api-endpoints.test.ts:300` calls `GET http://127.0.0.1:${testPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/health (tests/integration/worker-api-endpoints.test.ts:75)
`tests/integration/worker-api-endpoints.test.ts:75` calls `GET http://127.0.0.1:${testPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/health (tests/server/server.test.ts:256)
`tests/server/server.test.ts:256` calls `GET http://127.0.0.1:${testPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/health (tests/server/server.test.ts:270)
`tests/server/server.test.ts:270` calls `GET http://127.0.0.1:${testPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/health (tests/server/server.test.ts:293)
`tests/server/server.test.ts:293` calls `GET http://127.0.0.1:${testPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/health (tests/server/server.test.ts:299)
`tests/server/server.test.ts:299` calls `GET http://127.0.0.1:${testPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/health (tests/server/server.test.ts:310)
`tests/server/server.test.ts:310` calls `GET http://127.0.0.1:${testPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/health (tests/server/server.test.ts:337)
`tests/server/server.test.ts:337` calls `GET http://127.0.0.1:${testPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/nonexistent (tests/integration/hook-execution-e2e.test.ts:188)
`tests/integration/hook-execution-e2e.test.ts:188` calls `GET http://127.0.0.1:${testPort}/api/nonexistent` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/nonexistent` If this points at an e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/nonexistent (tests/server/server.test.ts:411)
`tests/server/server.test.ts:411` calls `GET http://127.0.0.1:${testPort}/api/nonexistent` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/nonexistent` If this points at an external API, pref…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/readiness (tests/integration/hook-execution-e2e.test.ts:109)
`tests/integration/hook-execution-e2e.test.ts:109` calls `GET http://127.0.0.1:${testPort}/api/readiness` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/readiness` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/readiness (tests/integration/hook-execution-e2e.test.ts:89)
`tests/integration/hook-execution-e2e.test.ts:89` calls `GET http://127.0.0.1:${testPort}/api/readiness` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/readiness` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/readiness (tests/integration/worker-api-endpoints.test.ts:115)
`tests/integration/worker-api-endpoints.test.ts:115` calls `GET http://127.0.0.1:${testPort}/api/readiness` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/readiness` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/readiness (tests/integration/worker-api-endpoints.test.ts:136)
`tests/integration/worker-api-endpoints.test.ts:136` calls `GET http://127.0.0.1:${testPort}/api/readiness` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/readiness` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/readiness (tests/integration/worker-api-endpoints.test.ts:251)
`tests/integration/worker-api-endpoints.test.ts:251` calls `GET http://127.0.0.1:${testPort}/api/readiness` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/readiness` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/readiness (tests/integration/worker-api-endpoints.test.ts:256)
`tests/integration/worker-api-endpoints.test.ts:256` calls `GET http://127.0.0.1:${testPort}/api/readiness` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/readiness` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/readiness (tests/server/server.test.ts:353)
`tests/server/server.test.ts:353` calls `GET http://127.0.0.1:${testPort}/api/readiness` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/readiness` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/readiness (tests/server/server.test.ts:376)
`tests/server/server.test.ts:376` calls `GET http://127.0.0.1:${testPort}/api/readiness` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/readiness` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/search/nonexistent/nested (tests/integration/worker-api-endpoints.test.ts:192)
`tests/integration/worker-api-endpoints.test.ts:192` calls `GET http://127.0.0.1:${testPort}/api/search/nonexistent/nested` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/search/nonexistent/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/unknown-endpoint (tests/integration/worker-api-endpoints.test.ts:167)
`tests/integration/worker-api-endpoints.test.ts:167` calls `GET http://127.0.0.1:${testPort}/api/unknown-endpoint` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/unknown-endpoint` If this po…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/version (tests/integration/hook-execution-e2e.test.ts:121)
`tests/integration/hook-execution-e2e.test.ts:121` calls `GET http://127.0.0.1:${testPort}/api/version` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/version` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/version (tests/integration/worker-api-endpoints.test.ts:150)
`tests/integration/worker-api-endpoints.test.ts:150` calls `GET http://127.0.0.1:${testPort}/api/version` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/version` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${testPort}/api/version (tests/server/server.test.ts:393)
`tests/server/server.test.ts:393` calls `GET http://127.0.0.1:${testPort}/api/version` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/version` If this points at an external API, prefix it wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${t}${e} (plugin/scripts/mcp-server.cjs:82)
`plugin/scripts/mcp-server.cjs:82` calls `GET http://127.0.0.1:${t}${e}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/<p>` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${t}${e} (plugin/scripts/transcript-watcher.cjs:16)
`plugin/scripts/transcript-watcher.cjs:16` calls `GET http://127.0.0.1:${t}${e}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/<p>` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${t}/api/health (plugin/scripts/mcp-server.cjs:82)
`plugin/scripts/mcp-server.cjs:82` calls `GET http://127.0.0.1:${t}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${t}/api/health (plugin/scripts/worker-cli.js:5)
`plugin/scripts/worker-cli.js:5` calls `GET http://127.0.0.1:${t}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` 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://127.0.0.1:${workerPort}/api/health (src/npx-cli/commands/doctor.ts:87)
`src/npx-cli/commands/doctor.ts:87` calls `GET http://127.0.0.1:${workerPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${workerPort}/api/health (src/npx-cli/commands/install.ts:1755)
`src/npx-cli/commands/install.ts:1755` calls `GET http://127.0.0.1:${workerPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${workerPort}/api/readiness (src/services/integrations/OpenCodeInstaller.ts:198)
`src/services/integrations/OpenCodeInstaller.ts:198` calls `GET http://127.0.0.1:${workerPort}/api/readiness` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/readiness` If this points at an e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/repos/${e}/${t} (plugin/ui/viewer-bundle.js:11)
`plugin/ui/viewer-bundle.js:11` calls `GET https://api.github.com/repos/${e}/${t}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/repos/<p>/<p>` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/repos/${username}/${repo} (src/ui/viewer/hooks/useGitHubStars.ts:23)
`src/ui/viewer/hooks/useGitHubStars.ts:23` calls `GET https://api.github.com/repos/${username}/${repo}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/repos/<p>/<p>` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: OPTIONS http://127.0.0.1:${testPort}/api/health (tests/integration/worker-api-endpoints.test.ts:202)
`tests/integration/worker-api-endpoints.test.ts:202` calls `OPTIONS http://127.0.0.1:${testPort}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: OPTIONS http://127.0.0.1:${testPort}/api/settings (tests/worker/middleware/cors-restriction.test.ts:113)
`tests/worker/middleware/cors-restriction.test.ts:113` calls `OPTIONS http://127.0.0.1:${testPort}/api/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/settings` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: OPTIONS http://127.0.0.1:${testPort}/api/settings (tests/worker/middleware/cors-restriction.test.ts:127)
`tests/worker/middleware/cors-restriction.test.ts:127` calls `OPTIONS http://127.0.0.1:${testPort}/api/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/settings` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: OPTIONS http://127.0.0.1:${testPort}/api/settings (tests/worker/middleware/cors-restriction.test.ts:142)
`tests/worker/middleware/cors-restriction.test.ts:142` calls `OPTIONS http://127.0.0.1:${testPort}/api/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/settings` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: OPTIONS http://127.0.0.1:${testPort}/api/settings (tests/worker/middleware/cors-restriction.test.ts:157)
`tests/worker/middleware/cors-restriction.test.ts:157` calls `OPTIONS http://127.0.0.1:${testPort}/api/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/settings` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: OPTIONS http://127.0.0.1:${testPort}/api/settings (tests/worker/middleware/cors-restriction.test.ts:172)
`tests/worker/middleware/cors-restriction.test.ts:172` calls `OPTIONS http://127.0.0.1:${testPort}/api/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/settings` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: OPTIONS http://127.0.0.1:${testPort}/api/settings (tests/worker/middleware/cors-restriction.test.ts:85)
`tests/worker/middleware/cors-restriction.test.ts:85` calls `OPTIONS http://127.0.0.1:${testPort}/api/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/settings` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: OPTIONS http://127.0.0.1:${testPort}/api/settings (tests/worker/middleware/cors-restriction.test.ts:99)
`tests/worker/middleware/cors-restriction.test.ts:99` calls `OPTIONS http://127.0.0.1:${testPort}/api/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/settings` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH http://127.0.0.1:${port}/v1/memories/${memory.id} (tests/server/v1-routes.test.ts:328)
`tests/server/v1-routes.test.ts:328` calls `PATCH http://127.0.0.1:${port}/v1/memories/${memory.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/memories/<p>` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}${path} (tests/server/v1-routes.test.ts:346)
`tests/server/v1-routes.test.ts:346` calls `POST http://127.0.0.1:${port}${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/<p>` If this points at an external API, prefix it with `https://`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/sessions/observations (tests/compat/sessions-observations-adapter.test.ts:350)
`tests/compat/sessions-observations-adapter.test.ts:350` calls `POST http://127.0.0.1:${port}/api/sessions/observations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/sessions/observations`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/events (tests/server/server-beta-service.test.ts:102)
`tests/server/server-beta-service.test.ts:102` calls `POST http://127.0.0.1:${port}/v1/events` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/events` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/events/batch (tests/server/server-beta-service.test.ts:227)
`tests/server/server-beta-service.test.ts:227` calls `POST http://127.0.0.1:${port}/v1/events/batch` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/events/batch` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/events/batch (tests/server/v1-routes.test.ts:283)
`tests/server/v1-routes.test.ts:283` calls `POST http://127.0.0.1:${port}/v1/events/batch` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/events/batch` If this points at an external API, pref…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/events?generate=false (tests/server/server-beta-service.test.ts:164)
`tests/server/server-beta-service.test.ts:164` calls `POST http://127.0.0.1:${port}/v1/events?generate=false` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/events` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/projects (tests/server/server-runtime-smoke.test.ts:106)
`tests/server/server-runtime-smoke.test.ts:106` calls `POST http://127.0.0.1:${port}/v1/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/projects` If this points at an external API, p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/projects (tests/server/v1-routes.test.ts:188)
`tests/server/v1-routes.test.ts:188` calls `POST http://127.0.0.1:${port}/v1/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/projects` If this points at an external API, prefix it wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/projects (tests/server/v1-routes.test.ts:208)
`tests/server/v1-routes.test.ts:208` calls `POST http://127.0.0.1:${port}/v1/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/projects` If this points at an external API, prefix it wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/v1/projects (tests/server/v1-routes.test.ts:232)
`tests/server/v1-routes.test.ts:232` calls `POST http://127.0.0.1:${port}/v1/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/v1/projects` If this points at an external API, prefix it wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${testPort}/api/auth/session (tests/server/server.test.ts:83)
`tests/server/server.test.ts:83` calls `POST http://127.0.0.1:${testPort}/api/auth/session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/auth/session` If this points at an external API, pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${testPort}/api/nonexistent (tests/integration/worker-api-endpoints.test.ts:216)
`tests/integration/worker-api-endpoints.test.ts:216` calls `POST http://127.0.0.1:${testPort}/api/nonexistent` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/nonexistent` If this points at a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${testPort}/api/test-json (tests/integration/hook-execution-e2e.test.ts:200)
`tests/integration/hook-execution-e2e.test.ts:200` calls `POST http://127.0.0.1:${testPort}/api/test-json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/test-json` If this points at an exte…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${testPort}/api/unknown-endpoint (tests/integration/worker-api-endpoints.test.ts:179)
`tests/integration/worker-api-endpoints.test.ts:179` calls `POST http://127.0.0.1:${testPort}/api/unknown-endpoint` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/unknown-endpoint` If this p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${t}/api/admin/shutdown (plugin/scripts/worker-cli.js:5)
`plugin/scripts/worker-cli.js:5` calls `POST http://127.0.0.1:${t}/api/admin/shutdown` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/admin/shutdown` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.telegram.org/bot${botToken}/sendMessage (openclaw/src/index.ts:468)
`openclaw/src/index.ts:468` calls `POST https://api.telegram.org/bot${botToken}/sendMessage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.telegram.org/bot/<p>/sendmessage` If this points at an external …
Dangling fetchFetch
high System graph hardware Supply chain conf 1.00 Dockerfile pipes a remote installer into a shell
Executing downloaded code during image build gives the remote endpoint build-time code execution. Prefer pinned packages or verify downloaded installers by checksum/signature.
docker/claude-mem/Dockerfile:21 containersRemote installer
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in plugin/scripts/mcp-server.cjs:6
Found a known-risky pattern (new_function_used). Review and replace if possible.
plugin/scripts/mcp-server.cjs:6 New function used
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — plugin/ui/viewer-bundle.js:9
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/ui/viewer/components/TerminalPreview.tsx:134
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — plugin/scripts/mcp-server.cjs:82
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 — plugin/scripts/transcript-watcher.cjs:14
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 — plugin/ui/viewer-bundle.js:11
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/discord-release-notify.js:84
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/import-memories.ts:39
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/servers/mcp-server.ts:516
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 — src/services/integrations/OpenCodeInstaller.ts:198
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/services/integrations/TelegramNotifier.ts:50
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 — src/services/integrations/WindsurfHooksInstaller.ts:296
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 — src/services/telemetry/cli-telemetry.ts:60
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/services/worker/GeminiProvider.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 — src/services/worker/OpenRouterProvider.ts:52
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 — src/shared/worker-utils.ts:63
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/ui/viewer/utils/api.ts:2
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/anti-pattern-czar.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/anti-pattern-czar.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: plugin/.mcp.json
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.
plugin/.mcp.json VerificationMcp config
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: plugin/skills/how-it-works/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.
plugin/skills/how-it-works/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: plugin/skills/pathfinder/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.
plugin/skills/pathfinder/SKILL.md VerificationSkill file
medium System graph security Agent instructions conf 1.00 Agent instruction contains unpinned remote install: .claude/plans/animated-installer.md
Remote install commands in agent instructions are a supply-chain risk, especially when an agent can execute shell commands.
.claude/plans/animated-installer.md:5 Supply chainClaude instruction
medium System graph security Agent instructions conf 1.00 Agent instruction contains unpinned remote install: openclaw/SKILL.md
Remote install commands in agent instructions are a supply-chain risk, especially when an agent can execute shell commands.
openclaw/SKILL.md:10 Supply chainSkill 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 hardware Security conf 1.00 Dockerfile runs as root: docker/claude-mem/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 6 occurrences GitHub Action is tag-pinned rather than SHA-pinned
oven-sh/setup-bun@v2 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
4 files, 6 locations
.github/workflows/ci.yml:21, 61, 104 (3 hits)
.github/workflows/claude.yml:35
.github/workflows/deploy-install-scripts.yml:23
.github/workflows/npm-publish.yml:18
CI/CD securitySupply chainGithub actions
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/claude.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in plugin/ui/viewer-bundle.js:9
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
plugin/ui/viewer-bundle.js:9 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/ui/viewer/components/TerminalPreview.tsx:134
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/ui/viewer/components/TerminalPreview.tsx:134 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in plugin/ui/viewer-bundle.js:8
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
plugin/ui/viewer-bundle.js:8 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in plugin/.mcp.json:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
plugin/.mcp.json:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in plugin/scripts/bun-runner.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
plugin/scripts/bun-runner.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in plugin/scripts/context-generator.cjs:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
plugin/scripts/context-generator.cjs:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in plugin/scripts/mcp-server.cjs:82
Found a known-risky pattern (node_child_process). Review and replace if possible.
plugin/scripts/mcp-server.cjs:82 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in plugin/scripts/transcript-watcher.cjs:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
plugin/scripts/transcript-watcher.cjs:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in plugin/scripts/version-check.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
plugin/scripts/version-check.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in plugin/scripts/worker-wrapper.cjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
plugin/scripts/worker-wrapper.cjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in plugin/skills/standup/standup.mjs:45
Found a known-risky pattern (node_child_process). Review and replace if possible.
plugin/skills/standup/standup.mjs:45 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/bug-report/cli.ts:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/bug-report/cli.ts:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/bug-report/collector.ts:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/bug-report/collector.ts:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/build-worker-binary.js:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/build-worker-binary.js:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/cwd-remap.ts:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/cwd-remap.ts:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/discord-release-notify.js:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/discord-release-notify.js:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/gen-plugin-lockfile.cjs:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/gen-plugin-lockfile.cjs:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/generate-changelog.js:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/generate-changelog.js:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/publish.js:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/publish.js:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/regenerate-claude-md.ts:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/regenerate-claude-md.ts:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/smoke-clean-room.cjs:36
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/smoke-clean-room.cjs:36 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/strip-comments.ts:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/strip-comments.ts:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/sync-marketplace.cjs:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/sync-marketplace.cjs:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/claude-md-commands.ts:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/claude-md-commands.ts:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/npx-cli/commands/doctor.ts:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/npx-cli/commands/doctor.ts:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/npx-cli/commands/ide-detection.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/npx-cli/commands/ide-detection.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/npx-cli/commands/install.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/npx-cli/commands/install.ts:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/npx-cli/install/npm-install-helper.ts:17
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/npx-cli/install/npm-install-helper.ts:17 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/npx-cli/install/setup-runtime.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/npx-cli/install/setup-runtime.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/npx-cli/utils/bun-resolver.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/npx-cli/utils/bun-resolver.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/sdk/commit-verification.ts:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/sdk/commit-verification.ts:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/server/runtime/ServerBetaService.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/server/runtime/ServerBetaService.ts:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/services/infrastructure/ProcessManager.ts:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/services/infrastructure/ProcessManager.ts:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/services/infrastructure/WorktreeAdoption.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/services/infrastructure/WorktreeAdoption.ts:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/services/integrations/CodexCliInstaller.ts:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/services/integrations/CodexCliInstaller.ts:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/services/integrations/CursorHooksInstaller.ts:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/services/integrations/CursorHooksInstaller.ts:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/services/smart-file-read/parser.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/services/smart-file-read/parser.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/services/sqlite/SchemaRepair.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/services/sqlite/SchemaRepair.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/services/sync/ChromaMcpManager.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/services/sync/ChromaMcpManager.ts:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/services/worker-service.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/services/worker-service.ts:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/services/worker/BranchManager.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/services/worker/BranchManager.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/shared/find-claude-executable.ts:25
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/shared/find-claude-executable.ts:25 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/shared/oauth-token.ts:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/shared/oauth-token.ts:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/shared/paths.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/shared/paths.ts:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/shared/spawn.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/shared/spawn.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/supervisor/process-registry.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/supervisor/process-registry.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/supervisor/shutdown.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/supervisor/shutdown.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/utils/project-name.ts:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/utils/project-name.ts:3 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 33 placeholder/mock markers across 16 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 921 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
docker/claude-mem/Dockerfile:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 6 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 6 locations
.github/workflows/convert-feature-requests.yml:28, 89, 107 (3 hits)
.github/workflows/summary.yml:17, 21 (2 hits)
.github/workflows/claude.yml:29
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: evals/swebench/summarize.py:render_summary_markdown, evals/swebench/summarize.py:resolve_rate This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separ…
duplicatesduplication
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: openclaw/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.
openclaw/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: 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.
package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `file_v2` in tests/utils/logger-format-tool.test.ts:354
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 `idx_memory_sources_legacy` in src/storage/sqlite/schema.ts:199
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 `name_v2` in tests/cursor-hooks-json-utils.test.ts:128
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 `name_v2` in tests/cursor-mcp-config.test.ts:212
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 `nLegacy` in src/services/integrations/CodexCliInstaller.ts:450
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 `nOld` in tests/utils/claude-md-utils.test.ts:82
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 `project_v2` in tests/cursor-registry.test.ts:97
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 `project_v2` in tests/integration/chroma-vector-sync.test.ts:215
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 `skippedTooOld` in src/shared/find-claude-executable.ts:358
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 `unstable_legacy` in plugin/ui/viewer-bundle.js:8
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: run_one_instance
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
evals/swebench/run-batch.py:235
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 — docs/context/agent-sdk-v2-examples.ts:25
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — install/public/installer.js:3
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 — openclaw/test-sse-consumer.js:59
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — plugin/scripts/statusline-counts.js: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 — plugin/scripts/version-check.js:148
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 — plugin/scripts/worker-cli.js:4
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 — plugin/ui/viewer-bundle.js:14
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — ragtime/ragtime.ts:61
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/anti-pattern-test/detect-error-handling-antipatterns.ts:454
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/bug-report/cli.ts:54
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-hooks.js: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 — scripts/build-viewer.js:13
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-worker-binary.js:11
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/check-pending-queue.ts:98
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-postinstall-allowlist.js:97
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/cleanup-duplicates.ts:46
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/clear-pending-queue.ts:18
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/cwd-remap.ts:62
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/discord-release-notify.js:108
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/export-memories.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 — scripts/fix-corrupted-timestamps.ts:49
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/generate-changelog.js:82
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/import-memories.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/investigate-timestamps.ts:21
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/pr-babysit-status.ts:396
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/publish.js: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/regenerate-claude-md.ts:262
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/strip-comments.ts:44
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/sync-plugin-manifests.js:98
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/translate-readme/cli.ts:21
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/translate-readme/examples.ts:11
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/translate-readme/index.ts:276
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/validate-timestamp-logic.ts:21
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/verify-timestamp-fix.ts:35
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 — src/integrations/opencode-plugin/index.ts:188
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 — src/npx-cli/commands/doctor.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 — src/npx-cli/commands/install.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 — src/npx-cli/commands/runtime.ts:226
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 — src/npx-cli/commands/server-jobs.ts:166
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 — src/npx-cli/commands/server.ts:167
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 — src/npx-cli/commands/telemetry.ts:120
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/npx-cli/index.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 — src/server/runtime/ServerBetaService.ts:335
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 — src/services/integrations/CodexCliInstaller.ts:132
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 — src/services/integrations/CursorHooksInstaller.ts:168
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 — src/services/integrations/GeminiCliHooksInstaller.ts:159
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 — src/services/integrations/McpIntegrations.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 — src/services/integrations/OpenClawInstaller.ts:204
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 — src/services/integrations/OpenCodeInstaller.ts:82
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/services/integrations/WindsurfHooksInstaller.ts:192
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 — src/services/transcripts/cli.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 — src/services/worker-service.ts:888
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 — src/shared/hook-io.ts:114
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 — src/ui/viewer/hooks/useSSE.ts:31
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/infrastructure/version-consistency.test.ts:56
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/infrastructure/worker-json-status.test.ts:171
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 — tests/install-non-tty.test.ts:62
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/integration/chroma-vector-sync.test.ts:73
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/log-level-audit.test.ts:238
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/logger-usage-standards.test.ts:184
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 — tests/services/sqlite/schema-repair.test.ts:56
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/worker-spawn.test.ts:118
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: ALL /api/auth/*splat
`plugin/scripts/worker-service.cjs` declares `ALL /api/auth/*splat` 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: DELETE
`plugin/scripts/server-beta-service.cjs` declares `DELETE ` 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: GET /
`plugin/scripts/server-beta-service.cjs` declares `GET /` 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: GET /api/admin/doctor
`plugin/scripts/server-beta-service.cjs` declares `GET /api/admin/doctor` 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: GET /api/health
`plugin/scripts/server-beta-service.cjs` declares `GET /api/health` 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: GET /api/instructions
`plugin/scripts/server-beta-service.cjs` declares `GET /api/instructions` 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: GET /api/version
`plugin/scripts/server-beta-service.cjs` declares `GET /api/version` 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: GET /v1/audit
`plugin/scripts/worker-service.cjs` declares `GET /v1/audit` 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: GET /v1/events/:id
`plugin/scripts/server-beta-service.cjs` declares `GET /v1/events/:id` 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: GET /v1/events/:id/observations
`plugin/scripts/server-beta-service.cjs` declares `GET /v1/events/:id/observations` 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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /v1/info
`plugin/scripts/server-beta-service.cjs` declares `GET /v1/info` 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: GET /v1/jobs
`plugin/scripts/server-beta-service.cjs` declares `GET /v1/jobs` 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: GET /v1/jobs/:id
`plugin/scripts/server-beta-service.cjs` declares `GET /v1/jobs/:id` 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: GET /v1/memories/:id
`plugin/scripts/worker-service.cjs` declares `GET /v1/memories/:id` 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: GET /v1/projects
`plugin/scripts/worker-service.cjs` declares `GET /v1/projects` 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: GET /v1/projects/:id
`plugin/scripts/worker-service.cjs` declares `GET /v1/projects/:id` 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: GET /v1/projects/:projectId/jobs
`plugin/scripts/server-beta-service.cjs` declares `GET /v1/projects/:projectId/jobs` 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 consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /v1/sessions/:id
`plugin/scripts/server-beta-service.cjs` declares `GET /v1/sessions/:id` 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: GET /v1/teams/:teamId/jobs
`plugin/scripts/server-beta-service.cjs` declares `GET /v1/teams/:teamId/jobs` 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: PATCH /v1/memories/:id
`plugin/scripts/worker-service.cjs` declares `PATCH /v1/memories/:id` 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 /api/admin/restart
`plugin/scripts/server-beta-service.cjs` declares `POST /api/admin/restart` 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 /api/admin/shutdown
`plugin/scripts/server-beta-service.cjs` declares `POST /api/admin/shutdown` 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 /api/sessions/observations
`plugin/scripts/server-beta-service.cjs` declares `POST /api/sessions/observations` 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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/sessions/summarize
`plugin/scripts/server-beta-service.cjs` declares `POST /api/sessions/summarize` 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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /v1/agents?beta=true
`plugin/scripts/worker-service.cjs` declares `POST /v1/agents?beta=true` 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 /v1/complete
`plugin/scripts/worker-service.cjs` declares `POST /v1/complete` 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 /v1/context
`plugin/scripts/server-beta-service.cjs` declares `POST /v1/context` 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 /v1/environments?beta=true
`plugin/scripts/worker-service.cjs` declares `POST /v1/environments?beta=true` 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 /v1/events
`plugin/scripts/server-beta-service.cjs` declares `POST /v1/events` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /v1/events/batch
`plugin/scripts/server-beta-service.cjs` declares `POST /v1/events/batch` 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 /v1/files?beta=true
`plugin/scripts/worker-service.cjs` declares `POST /v1/files?beta=true` 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 /v1/jobs/:id/cancel
`plugin/scripts/server-beta-service.cjs` declares `POST /v1/jobs/:id/cancel` 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 /v1/jobs/:id/retry
`plugin/scripts/server-beta-service.cjs` declares `POST /v1/jobs/:id/retry` 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 /v1/memories
`plugin/scripts/server-beta-service.cjs` declares `POST /v1/memories` 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 /v1/memory_stores?beta=true
`plugin/scripts/worker-service.cjs` declares `POST /v1/memory_stores?beta=true` 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 /v1/messages
`plugin/scripts/worker-service.cjs` declares `POST /v1/messages` 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 /v1/messages/batches
`plugin/scripts/worker-service.cjs` declares `POST /v1/messages/batches` 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 /v1/messages/batches?beta=true
`plugin/scripts/worker-service.cjs` declares `POST /v1/messages/batches?beta=true` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /v1/messages/count_tokens
`plugin/scripts/worker-service.cjs` declares `POST /v1/messages/count_tokens` 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 /v1/messages/count_tokens?beta=true
`plugin/scripts/worker-service.cjs` declares `POST /v1/messages/count_tokens?beta=true` 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 con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /v1/messages?beta=true
`plugin/scripts/worker-service.cjs` declares `POST /v1/messages?beta=true` 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 /v1/projects
`plugin/scripts/worker-service.cjs` declares `POST /v1/projects` 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 /v1/search
`plugin/scripts/server-beta-service.cjs` declares `POST /v1/search` 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 /v1/sessions/:id/end
`plugin/scripts/server-beta-service.cjs` declares `POST /v1/sessions/:id/end` 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 /v1/sessions/start
`plugin/scripts/server-beta-service.cjs` declares `POST /v1/sessions/start` 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 /v1/sessions?beta=true
`plugin/scripts/worker-service.cjs` declares `POST /v1/sessions?beta=true` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint

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

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

This page is publicly accessible at: https://repobility.com/scan/15461b0a-dfc3-48c2-a521-11e925bdc000/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/15461b0a-dfc3-48c2-a521-11e925bdc000/

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.