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
206 of your 346 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 34.86s for a 113.8 MB repo slow.
  • Repobility's analysis ran in 21.97s after the clone landed.

davila7/claude-code-templates

https://github.com/davila7/claude-code-templates.git · scanned 2026-06-09 04:40 UTC (18 hours, 31 minutes ago) · 10 languages

11449 raw signals (306 security + 11143 graph) 11/13 scanners ran 71st percentile · Python · large (100-500K LoC) System graph score 50 (higher by 33)

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

Complete repo analysis

Last scanned 18 hours, 30 minutes ago · v12 · 526 actionable findings from 2 signal sources. 234 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
65.1
/100
Security checks
81
121 findings
System graph
50
100.0% cov · 405 findings
Critical
8
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 75.0 0.20 15.00
documentation_score 100.0 0.15 15.00
practices_score 81.0 0.15 12.15
code_quality 59.0 0.10 5.90
Overall 1.00 82.1
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: layer: api × excluding tests × Reset all
Severity: Critical 8 High 85 Medium 107 Low 241 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 121 System graph 405 Crowd 0 Layer: Quality 204 Security 54 Software 81 Cicd 6 Frontend 93 Network 10 Hardware 1 Api 77
Scan summary Quality grade A- (82/100). Dimensions: security 100, maintainability 60. 306 findings (55 security). 229,013 lines analyzed.

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

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/live-task/control (dashboard/src/components/live-task/LiveTaskPanel.tsx:38)
`dashboard/src/components/live-task/LiveTaskPanel.tsx:38` calls `GET /api/live-task/control` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/live-task/control` If this points at an external API, prefix it with `https…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/live-task/cycles?limit=20 (dashboard/src/components/live-task/LiveTaskPanel.tsx:30)
`dashboard/src/components/live-task/LiveTaskPanel.tsx:30` calls `GET /api/live-task/cycles?limit=20` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/live-task/cycles` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/live-task/tools?cycle_id=${cycleId} (dashboard/src/components/live-task/LiveTaskPanel.tsx:46)
`dashboard/src/components/live-task/LiveTaskPanel.tsx:46` calls `GET /api/live-task/tools?cycle_id=${cycleId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/live-task/tools` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /claude-jobs.json (dashboard/src/components/JobsPreview.tsx:74)
`dashboard/src/components/JobsPreview.tsx:74` calls `GET /claude-jobs.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/claude-jobs.json` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /claude-jobs.json (dashboard/src/components/JobsView.tsx:96)
`dashboard/src/components/JobsView.tsx:96` calls `GET /claude-jobs.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/claude-jobs.json` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trending-data.json (dashboard/src/components/TrendingView.tsx:59)
`dashboard/src/components/TrendingView.tsx:59` calls `GET /trending-data.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trending-data.json` 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 https://aitmpl.com/api/agents.json (cli-tool/src/index.js:1464)
`cli-tool/src/index.js:1464` calls `GET https://aitmpl.com/api/agents.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/aitmpl.com/api/agents.json` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://aitmpl.com/components.json (api/discord/interactions.js:24)
`api/discord/interactions.js:24` calls `GET https://aitmpl.com/components.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/aitmpl.com/components.json` If this points at an external API, prefix it with `ht…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/repos/${GITHUB_CONFIG.owner}/${GITHUB_CONFIG.repo}/contents/cli-tool/components/${type}/${file.name} (docs/js/script.js:1256)
`docs/js/script.js:1256` calls `GET https://api.github.com/repos/${GITHUB_CONFIG.owner}/${GITHUB_CONFIG.repo}/contents/cli-tool/components/${type}/${file.name}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/repos/davila7/claude-code-templates/contents/cli-tool/components/agents (cli-tool/src/index.js:1479)
`cli-tool/src/index.js:1479` calls `GET https://api.github.com/repos/davila7/claude-code-templates/contents/cli-tool/components/agents` 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/davi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/repos/davila7/claude-code-templates/contents/cli-tool/components/agents (cli-tool/src/sdk/global-agent-manager.js:546)
`cli-tool/src/sdk/global-agent-manager.js:546` calls `GET https://api.github.com/repos/davila7/claude-code-templates/contents/cli-tool/components/agents` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.git…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/repos/davila7/claude-code-templates/contents/cli-tool/components/agents (cli-tool/src/sdk/global-agent-manager.js:581)
`cli-tool/src/sdk/global-agent-manager.js:581` calls `GET https://api.github.com/repos/davila7/claude-code-templates/contents/cli-tool/components/agents` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.git…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/repos/davila7/claude-code-templates/contents/cli-tool/components/agents/${item.name} (cli-tool/src/index.js:1523)
`cli-tool/src/index.js:1523` calls `GET https://api.github.com/repos/davila7/claude-code-templates/contents/cli-tool/components/agents/${item.name}` 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.c…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/repos/davila7/claude-code-templates/contents/cli-tool/components/agents/${item.name} (cli-tool/src/sdk/global-agent-manager.js:595)
`cli-tool/src/sdk/global-agent-manager.js:595` calls `GET https://api.github.com/repos/davila7/claude-code-templates/contents/cli-tool/components/agents/${item.name}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://code.claude.com/docs (cloudflare-workers/docs-monitor/index.js:15)
`cloudflare-workers/docs-monitor/index.js:15` calls `GET https://code.claude.com/docs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/code.claude.com/docs` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://raw.githubusercontent.com/davila7/claude-code-templates/main/cli-tool/components/.claude-plugin/marketplace.json (docs/js/component-page.js:514)
`docs/js/component-page.js:514` calls `GET https://raw.githubusercontent.com/davila7/claude-code-templates/main/cli-tool/components/.claude-plugin/marketplace.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://registry.npmjs.org/${NPM_PACKAGE}/latest (api/claude-code-check.js:13)
`api/claude-code-check.js:13` calls `GET https://registry.npmjs.org/${NPM_PACKAGE}/latest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/registry.npmjs.org/<p>/latest` If this points at an external API, pref…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET https://registry.npmjs.org/${NPM_PACKAGE}/latest (api/claude-code-monitor/check-version.js:13)
`api/claude-code-monitor/check-version.js:13` calls `GET https://registry.npmjs.org/${NPM_PACKAGE}/latest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/registry.npmjs.org/<p>/latest` If this points at an ex…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET https://registry.npmjs.org/${NPM_PACKAGE}/latest (api/claude-code-monitor/webhook.js:24)
`api/claude-code-monitor/webhook.js:24` calls `GET https://registry.npmjs.org/${NPM_PACKAGE}/latest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/registry.npmjs.org/<p>/latest` If this points at an external…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET https://registry.npmjs.org/${NPM_PACKAGE}/latest (dashboard/src/pages/api/claude-code-check.ts:10)
`dashboard/src/pages/api/claude-code-check.ts:10` calls `GET https://registry.npmjs.org/${NPM_PACKAGE}/latest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/registry.npmjs.org/<p>/latest` If this points at a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://www.aitmpl.com/components.json (dashboard/src/pages/api/discord/interactions.ts:29)
`dashboard/src/pages/api/discord/interactions.ts:29` calls `GET https://www.aitmpl.com/components.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.aitmpl.com/components.json` If this points at an exte…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/collections/share (dashboard/src/components/MyComponentsView.tsx:598)
`dashboard/src/components/MyComponentsView.tsx:598` calls `POST /api/collections/share` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/collections/share` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/live-task/control (dashboard/src/components/live-task/LiveTaskPanel.tsx:112)
`dashboard/src/components/live-task/LiveTaskPanel.tsx:112` calls `POST /api/live-task/control` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/live-task/control` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://github.com/login/oauth/access_token (dashboard/src/pages/api/github/token.ts:24)
`dashboard/src/pages/api/github/token.ts:24` calls `POST https://github.com/login/oauth/access_token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/github.com/login/oauth/access_token` If this points at an e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://www.aitmpl.com/api/track-command-usage (cli-tool/src/tracking-service.js:262)
`cli-tool/src/tracking-service.js:262` calls `POST https://www.aitmpl.com/api/track-command-usage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.aitmpl.com/api/track-command-usage` If this points at an e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://www.aitmpl.com/api/track-download-supabase (cli-tool/src/tracking-service.js:132)
`cli-tool/src/tracking-service.js:132` calls `POST https://www.aitmpl.com/api/track-download-supabase` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.aitmpl.com/api/track-download-supabase` If this points…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://www.aitmpl.com/api/track-installation-outcome (cli-tool/src/tracking-service.js:338)
`cli-tool/src/tracking-service.js:338` calls `POST https://www.aitmpl.com/api/track-installation-outcome` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.aitmpl.com/api/track-installation-outcome` If this …
Dangling fetchFetch
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/users/{user_id}
`cli-tool/components/skills/development/api-design-principles/assets/rest-api-template.py` declares `DELETE /api/users/{user_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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`scripts/dev-server.js` 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 /2025
`cli-tool/src/analytics.js` declares `GET /2025` 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/2025
`cli-tool/src/analytics.js` declares `GET /api/2025` 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/activity
`cli-tool/src/analytics.js` declares `GET /api/activity` 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/agents
`cli-tool/src/analytics.js` declares `GET /api/agents` 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/conversation-state
`cli-tool/src/analytics.js` declares `GET /api/conversation-state` 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/conversation-states
`cli-tool/src/chats-mobile.js` declares `GET /api/conversation-states` 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/conversation/:sessionId
`cli-tool/src/claude-api-proxy.js` declares `GET /api/conversation/:sessionId` 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/conversations
`cli-tool/src/analytics.js` declares `GET /api/conversations` 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/conversations/:id/analytics
`cli-tool/src/chats-mobile.js` declares `GET /api/conversations/:id/analytics` 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/conversations/:id/messages
`cli-tool/src/analytics.js` declares `GET /api/conversations/:id/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: GET /api/data
`cli-tool/src/analytics.js` declares `GET /api/data` 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/directories
`cli-tool/src/chats-mobile.js` declares `GET /api/directories` 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/fast-update
`cli-tool/src/analytics.js` declares `GET /api/fast-update` 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/permissions
`cli-tool/src/plugin-dashboard.js` declares `GET /api/permissions` 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/realtime
`cli-tool/src/analytics.js` declares `GET /api/realtime` 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/refresh
`cli-tool/src/analytics.js` declares `GET /api/refresh` 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/session/:id
`cli-tool/src/analytics.js` declares `GET /api/session/: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 /api/session/data
`cli-tool/src/analytics.js` declares `GET /api/session/data` 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/sessions/:id/teammates/:agentId
`cli-tool/src/teams-dashboard.js` declares `GET /api/sessions/:id/teammates/:agentId` 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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/sessions/:id/timeline
`cli-tool/src/teams-dashboard.js` declares `GET /api/sessions/:id/timeline` 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/skills
`cli-tool/src/skill-dashboard.js` declares `GET /api/skills` 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/skills/:name
`cli-tool/src/skill-dashboard.js` declares `GET /api/skills/:name` 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/skills/:name/file/*
`cli-tool/src/skill-dashboard.js` declares `GET /api/skills/:name/file/*` 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/system/health
`cli-tool/src/analytics.js` declares `GET /api/system/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/system/metrics
`cli-tool/src/analytics.js` declares `GET /api/system/metrics` 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/task/:taskId
`cli-tool/src/sandbox-server.js` declares `GET /api/task/:taskId` 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/tasks
`cli-tool/src/sandbox-server.js` declares `GET /api/tasks` 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/users
`cli-tool/components/skills/development/api-design-principles/assets/rest-api-template.py` declares `GET /api/users` 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 re…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/users/{user_id}
`cli-tool/components/skills/development/api-design-principles/assets/rest-api-template.py` declares `GET /api/users/{user_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 — c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/version
`cli-tool/src/analytics.js` 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 /blog/*
`scripts/dev-server.js` declares `GET /blog/*` 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 /component/:type/:name
`scripts/dev-server.js` declares `GET /component/:type/:name` 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 /todos
`cli-tool/components/skills/ai-research/loki-mode/examples/todo-app-generated/backend/src/routes/todos.ts` declares `GET /todos` 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 —…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/users/{user_id}
`cli-tool/components/skills/development/api-design-principles/assets/rest-api-template.py` declares `PATCH /api/users/{user_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 —…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/conversations/:id/download
`cli-tool/src/chats-mobile.js` declares `POST /api/conversations/:id/download` 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/conversations/:id/search
`cli-tool/src/chats-mobile.js` declares `POST /api/conversations/:id/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 /api/execute
`cli-tool/src/sandbox-server.js` declares `POST /api/execute` 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/install-agent
`cli-tool/src/sandbox-server.js` declares `POST /api/install-agent` 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/search
`cli-tool/src/chats-mobile.js` declares `POST /api/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 /api/send-message
`cli-tool/src/claude-api-proxy.js` declares `POST /api/send-message` 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/users
`cli-tool/components/skills/development/api-design-principles/assets/rest-api-template.py` declares `POST /api/users` 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 r…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /todos
`cli-tool/components/skills/ai-research/loki-mode/examples/todo-app-generated/backend/src/routes/todos.ts` declares `POST /todos` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api
`cli-tool/components/skills/ai-research/loki-mode/examples/todo-app-generated/backend/src/index.ts` declares `USE /api` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /assets
`cli-tool/src/sandbox-server.js` declares `USE /assets` 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: USE /components
`cli-tool/src/chats-mobile.js` declares `USE /components` 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: USE /css
`cli-tool/src/sandbox-server.js` declares `USE /css` 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: USE /js
`cli-tool/src/sandbox-server.js` declares `USE /js` 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: USE /services
`cli-tool/src/chats-mobile.js` declares `USE /services` 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
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/a656f031-2648-4f24-9993-6b291c9bf048/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/a656f031-2648-4f24-9993-6b291c9bf048/

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.