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

yazelin/ching-tech-os

https://github.com/yazelin/ching-tech-os · scanned 2026-06-16 01:05 UTC (2 months, 1 week ago)

282 raw signals (0 security + 282 graph)

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

Complete repo analysis

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

JSON
Combined
54.7
/100
Security checks
55
0 findings
System graph
55
100.0% cov · 262 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 84 Medium 65 Low 109 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 262 Crowd 0 Layer: Software 26 Frontend 12 Hardware 1 Security 35 Cicd 2 Quality 56 Api 130
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 54.7/100 with 100.0% coverage. It contains 6744 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 282 findings — concentrated in api (130), quality (73), security (35). Risk profile is high: 0 critical, 84 high, 65 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 251 of 262 actionable findings. 282 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: DELETE /ai/chats/${chatId} (frontend/js/api-client.js:100)
`frontend/js/api-client.js:100` calls `DELETE /ai/chats/${chatId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/ai/chats/<p>` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/bot-settings/${platform} (frontend/js/settings.js:1270)
`frontend/js/settings.js:1270` calls `DELETE /api/admin/bot-settings/${platform}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/bot-settings/<p>` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/users/${user.id} (frontend/js/settings.js:847)
`frontend/js/settings.js:847` calls `DELETE /api/admin/users/${user.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users/<p>` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/ai/agents/${agentId} (frontend/js/agent-settings.js:163)
`frontend/js/agent-settings.js:163` calls `DELETE /api/ai/agents/${agentId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ai/agents/<p>` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/ai/prompts/${promptId} (frontend/js/prompt-editor.js:130)
`frontend/js/prompt-editor.js:130` calls `DELETE /api/ai/prompts/${promptId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ai/prompts/<p>` 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: DELETE /api/bot/files/${fileId} (frontend/js/linebot.js:1260)
`frontend/js/linebot.js:1260` calls `DELETE /api/bot/files/${fileId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/bot/files/<p>` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/bot/groups/${groupId} (frontend/js/linebot.js:1292)
`frontend/js/linebot.js:1292` calls `DELETE /api/bot/groups/${groupId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/bot/groups/<p>` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/nas/file (frontend/js/file-manager.js:1800)
`frontend/js/file-manager.js:1800` calls `DELETE /api/nas/file` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/nas/file` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/scheduler/tasks/${id} (frontend/js/task-scheduler.js:82)
`frontend/js/task-scheduler.js:82` calls `DELETE /api/scheduler/tasks/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/scheduler/tasks/<p>` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/skills/${encodeURIComponent(skillName)} (frontend/js/agent-settings.js:1210)
`frontend/js/agent-settings.js:1210` calls `DELETE /api/skills/${encodeURIComponent(skillName)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/skills/<p>` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/voice/settings (frontend/js/voice-app.js:107)
`frontend/js/voice-app.js:107` calls `DELETE /api/voice/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/voice/settings` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ai/chats (frontend/js/api-client.js:66)
`frontend/js/api-client.js:66` calls `GET /ai/chats` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/ai/chats` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /ai/chats/${chatId} (frontend/js/api-client.js:91)
`frontend/js/api-client.js:91` calls `GET /ai/chats/${chatId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/ai/chats/<p>` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /ai/prompts (frontend/js/api-client.js:123)
`frontend/js/api-client.js:123` calls `GET /ai/prompts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/ai/prompts` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/bot-settings/${platform} (frontend/js/settings.js:1035)
`frontend/js/settings.js:1035` calls `GET /api/admin/bot-settings/${platform}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/bot-settings/<p>` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/default-permissions (frontend/js/settings.js:876)
`frontend/js/settings.js:876` calls `GET /api/admin/default-permissions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/default-permissions` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/users (frontend/js/settings.js:277)
`frontend/js/settings.js:277` calls `GET /api/admin/users` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/ai/agents (frontend/js/agent-settings.js:83)
`frontend/js/agent-settings.js:83` calls `GET /api/ai/agents` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ai/agents` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/ai/agents (frontend/js/ai-assistant.js:95)
`frontend/js/ai-assistant.js:95` calls `GET /api/ai/agents` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ai/agents` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/ai/agents (frontend/js/ai-log.js:68)
`frontend/js/ai-log.js:68` calls `GET /api/ai/agents` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ai/agents` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/ai/agents (frontend/js/task-scheduler.js:38)
`frontend/js/task-scheduler.js:38` calls `GET /api/ai/agents` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ai/agents` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/ai/agents/${agentId} (frontend/js/agent-settings.js:118)
`frontend/js/agent-settings.js:118` calls `GET /api/ai/agents/${agentId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ai/agents/<p>` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/ai/logs/${logId} (frontend/js/ai-log.js:135)
`frontend/js/ai-log.js:135` calls `GET /api/ai/logs/${logId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ai/logs/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/ai/logs/stats?${params.toString()} (frontend/js/ai-log.js:119)
`frontend/js/ai-log.js:119` calls `GET /api/ai/logs/stats?${params.toString()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ai/logs/stats` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/ai/logs?${params.toString()} (frontend/js/ai-log.js:95)
`frontend/js/ai-log.js:95` calls `GET /api/ai/logs?${params.toString()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ai/logs` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/ai/prompts (frontend/js/agent-settings.js:100)
`frontend/js/agent-settings.js:100` calls `GET /api/ai/prompts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ai/prompts` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/ai/prompts/${promptId} (frontend/js/prompt-editor.js:85)
`frontend/js/prompt-editor.js:85` calls `GET /api/ai/prompts/${promptId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ai/prompts/<p>` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/bot${endpoint} (frontend/js/memory-manager.js:48)
`frontend/js/memory-manager.js:48` calls `GET /api/bot${endpoint}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/bot/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/config/apps (frontend/js/desktop.js:143)
`frontend/js/desktop.js:143` calls `GET /api/config/apps` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/config/apps` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/messages/unread-count (frontend/js/socket-client.js:117)
`frontend/js/socket-client.js:117` calls `GET /api/messages/unread-count` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/messages/unread-count` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/nas/browse?path=${encodeURIComponent(path)} (frontend/js/file-manager.js:717)
`frontend/js/file-manager.js:717` calls `GET /api/nas/browse?path=${encodeURIComponent(path)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/nas/browse` 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/nas/connections (frontend/js/file-manager.js:158)
`frontend/js/file-manager.js:158` calls `GET /api/nas/connections` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/nas/connections` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/nas/download?path=${encodeURIComponent(filePath)} (frontend/js/file-manager.js:1614)
`frontend/js/file-manager.js:1614` calls `GET /api/nas/download?path=${encodeURIComponent(filePath)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/nas/download` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/nas/search?path=${encodeURIComponent(currentPath)}&query=${encodeURIComponent(searchQuery)}&max_depth=5&max_results=100 (frontend/js/file-manager.js:790)
`frontend/js/file-manager.js:790` calls `GET /api/nas/search?path=${encodeURIComponent(currentPath)}&query=${encodeURIComponent(searchQuery)}&max_depth=5&max_results=100` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/nas/shares (frontend/js/file-manager.js:699)
`frontend/js/file-manager.js:699` calls `GET /api/nas/shares` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/nas/shares` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/scheduler/tasks (frontend/js/task-scheduler.js:25)
`frontend/js/task-scheduler.js:25` calls `GET /api/scheduler/tasks` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/scheduler/tasks` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/share${endpoint} (frontend/js/share-manager.js:74)
`frontend/js/share-manager.js:74` calls `GET /api/share${endpoint}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/share/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/skills (frontend/js/agent-settings.js:825)
`frontend/js/agent-settings.js:825` calls `GET /api/skills` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/skills` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/skills (frontend/js/task-scheduler.js:48)
`frontend/js/task-scheduler.js:48` calls `GET /api/skills` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/skills` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/skills/${encodeURIComponent(skillName)} (frontend/js/agent-settings.js:1090)
`frontend/js/agent-settings.js:1090` calls `GET /api/skills/${encodeURIComponent(skillName)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/skills/<p>` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/skills/${encodeURIComponent(skillName)} (frontend/js/agent-settings.js:947)
`frontend/js/agent-settings.js:947` calls `GET /api/skills/${encodeURIComponent(skillName)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/skills/<p>` If this points at an external API, prefix it with `https://` so…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/skills/${encodeURIComponent(skillName)}/files/${encodeURIComponent(filePath)} (frontend/js/agent-settings.js:1373)
`frontend/js/agent-settings.js:1373` calls `GET /api/skills/${encodeURIComponent(skillName)}/files/${encodeURIComponent(filePath)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/skills/<p>/files/<p>` If this points…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/skills/hub/sources (frontend/js/agent-settings.js:846)
`frontend/js/agent-settings.js:846` calls `GET /api/skills/hub/sources` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/skills/hub/sources` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/user/me (frontend/js/header.js:80)
`frontend/js/header.js:80` calls `GET /api/user/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/user/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/user/me (frontend/js/permissions.js:21)
`frontend/js/permissions.js:21` calls `GET /api/user/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/user/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/user/me (frontend/js/user-profile.js:269)
`frontend/js/user-profile.js:269` calls `GET /api/user/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/user/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/voice/scopes (frontend/js/voice-app.js:60)
`frontend/js/voice-app.js:60` calls `GET /api/voice/scopes` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/voice/scopes` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/voice/settings?${params} (frontend/js/voice-app.js:72)
`frontend/js/voice-app.js:72` calls `GET /api/voice/settings?${params}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/voice/settings` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/voice/voices${params} (frontend/js/voice-app.js:43)
`frontend/js/voice-app.js:43` calls `GET /api/voice/voices${params}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/voice/voices/<p>` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /projects?limit=100 (frontend/js/linebot.js:449)
`frontend/js/linebot.js:449` calls `GET /projects?limit=100` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /ai/chats/${chatId} (frontend/js/api-client.js:112)
`frontend/js/api-client.js:112` calls `PATCH /ai/chats/${chatId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/ai/chats/<p>` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/admin/users/${user.id} (frontend/js/settings.js:669)
`frontend/js/settings.js:669` calls `PATCH /api/admin/users/${user.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users/<p>` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/admin/users/${user.id}/permissions (frontend/js/settings.js:969)
`frontend/js/settings.js:969` calls `PATCH /api/admin/users/${user.id}/permissions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users/<p>/permissions` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/admin/users/${user.id}/status (frontend/js/settings.js:766)
`frontend/js/settings.js:766` calls `PATCH /api/admin/users/${user.id}/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users/<p>/status` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/nas/rename (frontend/js/file-manager.js:1749)
`frontend/js/file-manager.js:1749` calls `PATCH /api/nas/rename` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/nas/rename` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/scheduler/tasks/${id}/toggle (frontend/js/task-scheduler.js:90)
`frontend/js/task-scheduler.js:90` calls `PATCH /api/scheduler/tasks/${id}/toggle` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/scheduler/tasks/<p>/toggle` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/user/me (frontend/js/user-profile.js:289)
`frontend/js/user-profile.js:289` calls `PATCH /api/user/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/user/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /ai/chats (frontend/js/api-client.js:75)
`frontend/js/api-client.js:75` calls `POST /ai/chats` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/ai/chats` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/bot-settings/${platform}/test (frontend/js/settings.js:1247)
`frontend/js/settings.js:1247` calls `POST /api/admin/bot-settings/${platform}/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/bot-settings/<p>/test` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/users (frontend/js/settings.js:609)
`frontend/js/settings.js:609` calls `POST /api/admin/users` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/users/${user.id}/clear-password (frontend/js/settings.js:807)
`frontend/js/settings.js:807` calls `POST /api/admin/users/${user.id}/clear-password` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users/<p>/clear-password` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/users/${user.id}/reset-password (frontend/js/settings.js:723)
`frontend/js/settings.js:723` calls `POST /api/admin/users/${user.id}/reset-password` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users/<p>/reset-password` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/ai/test (frontend/js/agent-settings.js:185)
`frontend/js/agent-settings.js:185` calls `POST /api/ai/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ai/test` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/change-password (frontend/js/user-profile.js:230)
`frontend/js/user-profile.js:230` calls `POST /api/auth/change-password` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/change-password` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/nas/connect (frontend/js/file-manager.js:297)
`frontend/js/file-manager.js:297` calls `POST /api/nas/connect` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/nas/connect` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/nas/mkdir (frontend/js/file-manager.js:1704)
`frontend/js/file-manager.js:1704` calls `POST /api/nas/mkdir` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/nas/mkdir` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/nas/upload (frontend/js/file-manager.js:1663)
`frontend/js/file-manager.js:1663` calls `POST /api/nas/upload` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/nas/upload` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/scheduler/tasks (frontend/js/task-scheduler.js:56)
`frontend/js/task-scheduler.js:56` calls `POST /api/scheduler/tasks` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/scheduler/tasks` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/scheduler/tasks/${id}/run (frontend/js/task-scheduler.js:100)
`frontend/js/task-scheduler.js:100` calls `POST /api/scheduler/tasks/${id}/run` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/scheduler/tasks/<p>/run` If this points at an external API, prefix it with `https://` so…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/share (frontend/js/share-dialog.js:150)
`frontend/js/share-dialog.js:150` calls `POST /api/share` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/share` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/skills/hub/inspect (frontend/js/agent-settings.js:1556)
`frontend/js/agent-settings.js:1556` calls `POST /api/skills/hub/inspect` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/skills/hub/inspect` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/skills/hub/install (frontend/js/agent-settings.js:1329)
`frontend/js/agent-settings.js:1329` calls `POST /api/skills/hub/install` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/skills/hub/install` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/skills/hub/search (frontend/js/agent-settings.js:1266)
`frontend/js/agent-settings.js:1266` calls `POST /api/skills/hub/search` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/skills/hub/search` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/skills/reload (frontend/js/agent-settings.js:1073)
`frontend/js/agent-settings.js:1073` calls `POST /api/skills/reload` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/skills/reload` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/voice/preview (frontend/js/voice-app.js:126)
`frontend/js/voice-app.js:126` calls `POST /api/voice/preview` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/voice/preview` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/bot-settings/${platform} (frontend/js/settings.js:1184)
`frontend/js/settings.js:1184` calls `PUT /api/admin/bot-settings/${platform}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/bot-settings/<p>` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/bot-settings/${platform} (frontend/js/settings.js:1215)
`frontend/js/settings.js:1215` calls `PUT /api/admin/bot-settings/${platform}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/bot-settings/<p>` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/scheduler/tasks/${id} (frontend/js/task-scheduler.js:69)
`frontend/js/task-scheduler.js:69` calls `PUT /api/scheduler/tasks/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/scheduler/tasks/<p>` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/skills/${encodeURIComponent(skillName)} (frontend/js/agent-settings.js:1173)
`frontend/js/agent-settings.js:1173` calls `PUT /api/skills/${encodeURIComponent(skillName)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/skills/<p>` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/voice/settings (frontend/js/voice-app.js:86)
`frontend/js/voice-app.js:86` calls `PUT /api/voice/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/voice/settings` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI PATCH `rename_item` without auth dependency — backend/src/ching_tech_os/api/nas.py:636
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/src/ching_tech_os/api/nas.py:636 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_directory` without auth dependency — backend/src/ching_tech_os/api/nas.py:692
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/src/ching_tech_os/api/nas.py:692 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `telegram_webhook` without auth dependency — backend/src/ching_tech_os/api/telegram_router.py:39
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/src/ching_tech_os/api/telegram_router.py:39 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_proactive_push` without auth dependency — backend/src/ching_tech_os/api/internal_push.py:122
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/src/ching_tech_os/api/internal_push.py:122 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — extends/nvr/skills/nvr-viewer/frontend/nvr-app.js:30
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 — frontend/js/agent-settings.js:1266
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 — frontend/js/ai-log.js:95
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 — frontend/js/file-manager.js:717
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 — frontend/js/linebot.js:65
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/js/message-center.js: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 — frontend/js/pdf-viewer.js:266
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/js/public.js:46
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 — frontend/js/share-dialog.js:150
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 — frontend/js/task-scheduler.js:90
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 — frontend/js/user-profile.js:230
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/nanobanana/diagram.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/nanobanana/diagram.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/nanobanana/edit.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/nanobanana/edit.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/nanobanana/generate.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/nanobanana/generate.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/nanobanana/icon.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/nanobanana/icon.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/nanobanana/pattern.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/nanobanana/pattern.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/nanobanana/restore.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/nanobanana/restore.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/nanobanana/story.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/nanobanana/story.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/opsx/apply.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/opsx/apply.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/opsx/archive.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/opsx/archive.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/opsx/sync.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/opsx/sync.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/ctos-architecture/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/ctos-architecture/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/ctos-kb/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/ctos-kb/SKILL.md VerificationClaude instruction
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 security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in extends/nvr/skills/nvr-viewer/frontend/nvr-app.js:47
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
extends/nvr/skills/nvr-viewer/frontend/nvr-app.js:47 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/index.html:255
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/index.html:255 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/agent-settings.js:532
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/agent-settings.js:532 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/ai-assistant.js:273
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/ai-assistant.js:273 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/ai-log.js:290
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/ai-log.js:290 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/command-palette.js:39
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/command-palette.js:39 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/external-app.js:116
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/external-app.js:116 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/file-manager.js:190
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/file-manager.js:190 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/header.js:119
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/header.js:119 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/image-viewer.js:167
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/image-viewer.js:167 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/knowledge-base.js:330
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/knowledge-base.js:330 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/linebot.js:128
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/linebot.js:128 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/login.js:348
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/login.js:348 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/memory-manager.js:171
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/memory-manager.js:171 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/message-center.js:126
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/message-center.js:126 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/notification.js:60
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/notification.js:60 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/onboarding.js:120
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/onboarding.js:120 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/prompt-editor.js:276
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/prompt-editor.js:276 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/public.js:202
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/public.js:202 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/share-dialog.js:191
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/share-dialog.js:191 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/share-manager.js:187
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/share-manager.js:187 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/task-scheduler.js:131
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/task-scheduler.js:131 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/taskbar.js:39
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/taskbar.js:39 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/terminal.js:184
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/terminal.js:184 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/ui-helpers.js:56
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/ui-helpers.js:56 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/user-profile.js:53
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/user-profile.js:53 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/voice-app.js:190
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/voice-app.js:190 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/js/window.js:144
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/js/window.js:144 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/login.html:110
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/login.html:110 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/main.js:19
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/main.js:19 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in frontend/js/login.js:256
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
frontend/js/login.js:256 Insert adjacent html
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/src/ching_tech_os/services/knowledge.py:300
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/src/ching_tech_os/skills/media-transcription/scripts/transcribe.py:297
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 58 placeholder/mock markers across 15 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Integrity conf 1.00 32 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AGENT_ALLOWED_LIBRARY_PATHS`, `AGENT_ALLOWED_SHARED_SOURCES`, `ANTHROPIC_API_KEY`, `BOT_SECRET_KEY`, `BRAVE_SEARCH_API_KEY`, `CHING_TECH_WORKING_DIR`, `CTOS_AGENT_ID`, `CTOS_CONFIG` + 24 more. Add them (with a placeholder/comment) to .env.example …
config drift
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 362 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/setup-python@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 4 locations
.github/workflows/backend-tests.yml:28, 53 (2 hits)
.github/workflows/lighthouse.yml:21, 67 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 17 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: cli/src/ctos_cli/main.py:cmd_erp_boms, cli/src/ctos_cli/main.py:cmd_erp_bom 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 separate.
17 occurrences
repo-level (17 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: extends/voice/voice_tts.py:list_voices, extends/voice/voice_tts.py:list_voices, extends/voice/voice_tts.py:list_voices, extends/voice/voice_tts.py:list_voices This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: extends/voice/voice_tts.py:synthesize_audio, extends/voice/voice_tts.py:synthesize_audio, extends/voice/voice_tts.py:synthesize_audio, extends/voice/voice_tts.py:synthesize_audio This is *the* AI-coder failure mode (4× more duplication in vibe-coded …
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `file_legacy` in backend/tests/test_linebot_ai_context_prompt.py:34
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 `from_legacy` in backend/src/ching_tech_os/services/path_manager.py:332
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 `is_tool_deprecated` in backend/src/ching_tech_os/services/mcp/server.py:148
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 `is_tool_deprecated` in backend/src/ching_tech_os/services/permissions.py:33
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 `is_tool_deprecated` in backend/tests/test_mcp_media_server_tools.py:156
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 `test_new_formats_not_legacy` in backend/tests/test_linebot_utils.py:122
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: cleanup_old_files
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
extends/voice/voice_tts.py:639
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_app
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/scaffold.py:296
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_erp_bom
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
cli/src/ctos_cli/main.py:612
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_erp_boms
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
cli/src/ctos_cli/main.py:592
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_erp_find
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
cli/src/ctos_cli/main.py:532
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_erp_item
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
cli/src/ctos_cli/main.py:546
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_erp_stock
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
cli/src/ctos_cli/main.py:565
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_extends
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/scaffold.py:449
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_files_get
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
cli/src/ctos_cli/main.py:520
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_files_ls
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
cli/src/ctos_cli/main.py:508
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_kb_add
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
cli/src/ctos_cli/main.py:347
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_kb_attachments
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
cli/src/ctos_cli/main.py:422
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_kb_get
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
cli/src/ctos_cli/main.py:264
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_kb_search
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
cli/src/ctos_cli/main.py:289
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_kb_update
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
cli/src/ctos_cli/main.py:383
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_lib_get
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
cli/src/ctos_cli/main.py:489
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_lib_ls
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
cli/src/ctos_cli/main.py:482
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_login
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
cli/src/ctos_cli/main.py:123
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_logout
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
cli/src/ctos_cli/main.py:176
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_skill
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/scaffold.py:537
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_token_list
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
cli/src/ctos_cli/main.py:210
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_token_revoke
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
cli/src/ctos_cli/main.py:231
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_validate
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/scaffold.py:687
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_whoami
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
cli/src/ctos_cli/main.py:189
low System graph software Dead code conf 1.00 Possibly dead Python function: transcribe_file
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
extends/voice/groq_stt.py:31
low System graph software Dead code conf 1.00 Possibly dead Python function: transcribe_file_with_segments
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
extends/voice/groq_stt.py:102
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 — frontend/js/config.js:72
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 — frontend/js/desktop.js:198
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 — frontend/js/external-app.js:223
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 — frontend/js/file-opener.js:115
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 — frontend/js/knowledge-base.js:90
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 — frontend/js/linebot.js:572
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 — frontend/js/socket-client.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 — frontend/js/taskbar.js:211
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 — frontend/tests/path-utils.test.js:28
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 — frontend/tests/ui-helpers.test.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 — frontend/tests/window-ux.test.js:43
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph quality Integrity conf 1.00 Stub function `downgrade` (body is just `pass`/`return`) — backend/migrations/versions/015_update_jfmskin_agents.py:118
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph quality Integrity conf 1.00 Stub function `downgrade` (body is just `pass`/`return`) — backend/migrations/versions/023_fix_queue_status_prompt.py:56
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph quality Integrity conf 1.00 Stub function `ensure_default_linebot_agents` (body is just `pass`/`return`) — backend/src/ching_tech_os/main.py:24
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /chats/{chat_id}
`backend/src/ching_tech_os/api/ai_router.py` declares `DELETE /chats/{chat_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: DELETE /{kb_id}
`backend/src/ching_tech_os/api/knowledge.py` declares `DELETE /{kb_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: DELETE /{kb_id}/attachments/{attachment_idx}
`backend/src/ching_tech_os/api/knowledge.py` declares `DELETE /{kb_id}/attachments/{attachment_idx}` 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 docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /{name}
`backend/src/ching_tech_os/api/skills.py` declares `DELETE /{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: DELETE /{platform}
`backend/src/ching_tech_os/api/bot_settings.py` declares `DELETE /{platform}` 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 /
`backend/src/ching_tech_os/main.py` 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/health
`backend/src/ching_tech_os/main.py` 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 /assets/{path:path}
`backend/src/ching_tech_os/api/knowledge.py` declares `GET /assets/{path:path}` 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 /attachments/{path:path}
`backend/src/ching_tech_os/api/knowledge.py` declares `GET /attachments/{path:path}` 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 /chats
`backend/src/ching_tech_os/api/ai_router.py` declares `GET /chats` 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 /chats/{chat_id}
`backend/src/ching_tech_os/api/ai_router.py` declares `GET /chats/{chat_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 /hub/sources
`backend/src/ching_tech_os/api/skills.py` declares `GET /hub/sources` 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 /index.html
`backend/src/ching_tech_os/main.py` declares `GET /index.html` 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 /items
`scripts/scaffold.py` declares `GET /items` 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 /login.html
`backend/src/ching_tech_os/main.py` declares `GET /login.html` 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 /public.html
`backend/src/ching_tech_os/main.py` declares `GET /public.html` 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 /recording-status
`extends/nvr/api/nvr_status.py` declares `GET /recording-status` 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 /s/{token}
`backend/src/ching_tech_os/main.py` declares `GET /s/{token}` 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 /snapshot/{channel}
`extends/nvr/api/nvr_snapshot.py` declares `GET /snapshot/{channel}` 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 /tags
`backend/src/ching_tech_os/api/knowledge.py` declares `GET /tags` 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 /tts/{file_id}.m4a
`extends/voice/tts_router.py` declares `GET /tts/{file_id}.m4a` 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 /tts/{file_id}.mp3
`extends/voice/tts_router.py` declares `GET /tts/{file_id}.mp3` 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 /{kb_id}
`backend/src/ching_tech_os/api/knowledge.py` declares `GET /{kb_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 /{kb_id}/history
`backend/src/ching_tech_os/api/knowledge.py` declares `GET /{kb_id}/history` 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 /{kb_id}/version/{commit}
`backend/src/ching_tech_os/api/knowledge.py` declares `GET /{kb_id}/version/{commit}` 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 /{name}
`backend/src/ching_tech_os/api/skills.py` declares `GET /{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 /{name}/files/{file_path:path}
`backend/src/ching_tech_os/api/skills.py` declares `GET /{name}/files/{file_path:path}` 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: GET /{name}/frontend/{file_path:path}
`backend/src/ching_tech_os/api/skills.py` declares `GET /{name}/frontend/{file_path:path}` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{name}/meta
`backend/src/ching_tech_os/api/skills.py` declares `GET /{name}/meta` 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 /{name}/references/{ref_path:path}
`backend/src/ching_tech_os/api/skills.py` declares `GET /{name}/references/{ref_path:path}` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{platform}
`backend/src/ching_tech_os/api/bot_settings.py` declares `GET /{platform}` 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 /chats/{chat_id}
`backend/src/ching_tech_os/api/ai_router.py` declares `PATCH /chats/{chat_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: PATCH /{kb_id}/attachments/{attachment_idx}
`backend/src/ching_tech_os/api/knowledge.py` declares `PATCH /{kb_id}/attachments/{attachment_idx}` 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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /
`backend/src/ching_tech_os/api/knowledge.py` declares `POST /` 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 /chats
`backend/src/ching_tech_os/api/ai_router.py` declares `POST /chats` 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 /hub/inspect
`backend/src/ching_tech_os/api/skills.py` declares `POST /hub/inspect` 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 /hub/install
`backend/src/ching_tech_os/api/skills.py` declares `POST /hub/install` 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 /hub/search
`backend/src/ching_tech_os/api/skills.py` declares `POST /hub/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 /login
`backend/src/ching_tech_os/api/auth.py` declares `POST /login` 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 /logout
`backend/src/ching_tech_os/api/auth.py` declares `POST /logout` 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 /proactive-push
`backend/src/ching_tech_os/api/internal_push.py` declares `POST /proactive-push` 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 /rebuild-index
`backend/src/ching_tech_os/api/knowledge.py` declares `POST /rebuild-index` 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 /reload
`backend/src/ching_tech_os/api/skills.py` declares `POST /reload` 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 /webhook
`backend/src/ching_tech_os/api/telegram_router.py` declares `POST /webhook` 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 /{kb_id}/attachments
`backend/src/ching_tech_os/api/knowledge.py` declares `POST /{kb_id}/attachments` 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 /{name}/scripts/{script}/run
`backend/src/ching_tech_os/api/skills.py` declares `POST /{name}/scripts/{script}/run` 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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{platform}/test
`backend/src/ching_tech_os/api/bot_settings.py` declares `POST /{platform}/test` 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: PUT /{kb_id}
`backend/src/ching_tech_os/api/knowledge.py` declares `PUT /{kb_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: PUT /{name}
`backend/src/ching_tech_os/api/skills.py` declares `PUT /{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: PUT /{platform}
`backend/src/ching_tech_os/api/bot_settings.py` declares `PUT /{platform}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: backend/src/ching_tech_os/services/linebot_ai.py (1871 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/src/ching_tech_os/skills/research-skill/scripts/start-research.py (1556 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/js/agent-settings.js (1776 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/js/file-manager.js (1901 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/js/linebot.js (1442 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/dfb8981c-0aaa-4359-b74f-ea1e19747641/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/dfb8981c-0aaa-4359-b74f-ea1e19747641/

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.