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

simplelost-chao/nomi

https://github.com/simplelost-chao/nomi · scanned 2026-06-16 00:14 UTC (2 months, 2 weeks ago)

181 raw signals (0 security + 181 graph)

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

Complete repo analysis

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

JSON
Combined
58.0
/100
Security checks
58
0 findings
System graph
58
100.0% cov · 156 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 44 Medium 30 Low 78 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 156 Crowd 0 Layer: Software 10 Frontend 9 Hardware 5 Security 27 Cicd 1 Quality 29 Api 75
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 58.0/100 with 100.0% coverage. It contains 1322 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 181 findings — concentrated in api (75), quality (35), software (29). Risk profile is high: 0 critical, 44 high, 30 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 152 of 156 actionable findings. 181 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 /api/conversations/all (frontend/src/app/page.tsx:354)
`frontend/src/app/page.tsx:354` calls `DELETE /api/conversations/all` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/conversations/all` 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: DELETE /api/robots/${id} (frontend/src/lib/api.ts:61)
`frontend/src/lib/api.ts:61` calls `DELETE /api/robots/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/robots/<p>` 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: DELETE /api/robots/activity/all (frontend/src/app/page.tsx:365)
`frontend/src/app/page.tsx:365` calls `DELETE /api/robots/activity/all` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/robots/activity/all` 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/conversations/latest (desktop/src/renderer/api.ts:74)
`desktop/src/renderer/api.ts:74` calls `GET /api/conversations/latest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/conversations/latest` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/conversations/models (frontend/src/lib/api.ts:63)
`frontend/src/lib/api.ts:63` calls `GET /api/conversations/models` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/conversations/models` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/heartbeat/events?after=${lastSeq.current}&_t=${Date.now()} (frontend/src/app/group-chat/page.tsx:191)
`frontend/src/app/group-chat/page.tsx:191` calls `GET /api/heartbeat/events?after=${lastSeq.current}&_t=${Date.now()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/heartbeat/events` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/heartbeat/status (frontend/src/app/group-chat/page.tsx:144)
`frontend/src/app/group-chat/page.tsx:144` calls `GET /api/heartbeat/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/heartbeat/status` 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/robots (frontend/src/lib/api.ts:33)
`frontend/src/lib/api.ts:33` calls `GET /api/robots` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/robots` 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/robots/${id} (frontend/src/lib/api.ts:36)
`frontend/src/lib/api.ts:36` calls `GET /api/robots/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/robots/<p>` 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/robots/creation-status/${jobId} (frontend/src/app/page.tsx:56)
`frontend/src/app/page.tsx:56` calls `GET /api/robots/creation-status/${jobId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/robots/creation-status/<p>` If this points at an external API, prefix it with `https://`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/robots?desktop=true (desktop/src/renderer/api.ts:59)
`desktop/src/renderer/api.ts:59` calls `GET /api/robots?desktop=true` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/robots` 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: POST /api/conversations (desktop/src/renderer/api.ts:62)
`desktop/src/renderer/api.ts:62` calls `POST /api/conversations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/conversations` 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: POST /api/conversations (frontend/src/lib/api.ts:48)
`frontend/src/lib/api.ts:48` calls `POST /api/conversations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/conversations` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/heartbeat/busy?busy=${busy} (frontend/src/app/group-chat/page.tsx:165)
`frontend/src/app/group-chat/page.tsx:165` calls `POST /api/heartbeat/busy?busy=${busy}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/heartbeat/busy` 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/heartbeat/interval?seconds=${v} (frontend/src/app/group-chat/page.tsx:517)
`frontend/src/app/group-chat/page.tsx:517` calls `POST /api/heartbeat/interval?seconds=${v}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/heartbeat/interval` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/heartbeat/sleep (frontend/src/app/group-chat/page.tsx:390)
`frontend/src/app/group-chat/page.tsx:390` calls `POST /api/heartbeat/sleep` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/heartbeat/sleep` 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/heartbeat/wake (frontend/src/app/group-chat/page.tsx:394)
`frontend/src/app/group-chat/page.tsx:394` calls `POST /api/heartbeat/wake` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/heartbeat/wake` 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/heartbeat/wake (frontend/src/app/group-chat/page.tsx:410)
`frontend/src/app/group-chat/page.tsx:410` calls `POST /api/heartbeat/wake` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/heartbeat/wake` 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/objects/observe (frontend/src/lib/api.ts:39)
`frontend/src/lib/api.ts:39` calls `POST /api/objects/observe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/objects/observe` 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: POST /api/robots (frontend/src/lib/api.ts:16)
`frontend/src/lib/api.ts:16` calls `POST /api/robots` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/robots` 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/robots/from-image (frontend/src/app/page.tsx:112)
`frontend/src/app/page.tsx:112` calls `POST /api/robots/from-image` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/robots/from-image` 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/stt/transcribe (frontend/src/app/group-chat/page.tsx:351)
`frontend/src/app/group-chat/page.tsx:351` calls `POST /api/stt/transcribe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/stt/transcribe` 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 http://127.0.0.1:8100/api/stt/transcribe (desktop/src/renderer/components/VoiceButton.tsx:39)
`desktop/src/renderer/components/VoiceButton.tsx:39` calls `POST http://127.0.0.1:8100/api/stt/transcribe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:8100/api/stt/transcribe` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://nomi-api.zhuchao.life/api/agents/idle-chat (frontend/src/lib/api.ts:76)
`frontend/src/lib/api.ts:76` calls `POST https://nomi-api.zhuchao.life/api/agents/idle-chat` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/nomi-api.zhuchao.life/api/agents/idle-chat` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://nomi-api.zhuchao.life/api/robots/from-image (frontend/src/lib/api.ts:26)
`frontend/src/lib/api.ts:26` calls `POST https://nomi-api.zhuchao.life/api/robots/from-image` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/nomi-api.zhuchao.life/api/robots/from-image` If this points at an e…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI POST `activate_version` without auth dependency — backend/app/api/admin.py:464
`@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/app/api/admin.py:464 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `build_memories_for_existing` without auth dependency — backend/app/api/admin_web_creation.py:57
`@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/app/api/admin_web_creation.py:57 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `busy` without auth dependency — backend/app/api/heartbeat.py:51
`@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/app/api/heartbeat.py:51 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_character` without auth dependency — backend/app/api/admin.py:283
`@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/app/api/admin.py:283 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_from_web` without auth dependency — backend/app/api/admin_web_creation.py:29
`@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/app/api/admin_web_creation.py:29 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_robot_from_image` without auth dependency — backend/app/api/robots.py:40
`@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/app/api/robots.py:40 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `generate_images` without auth dependency — backend/app/api/admin.py:108
`@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/app/api/admin.py:108 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `remove_backgrounds` without auth dependency — backend/app/api/admin.py:184
`@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/app/api/admin.py:184 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `set_interval` without auth dependency — backend/app/api/heartbeat.py:58
`@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/app/api/heartbeat.py:58 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `set_tts_config` without auth dependency — backend/app/api/tts_genie.py:73
`@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/app/api/tts_genie.py:73 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `set_voice_lang` without auth dependency — backend/app/api/admin.py:91
`@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/app/api/admin.py:91 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `sleep` without auth dependency — backend/app/api/heartbeat.py:45
`@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/app/api/heartbeat.py:45 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `toggle_star` without auth dependency — backend/app/api/admin.py:502
`@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/app/api/admin.py:502 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `transcribe` without auth dependency — backend/app/api/stt.py:25
`@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/app/api/stt.py:25 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_action` without auth dependency — backend/app/api/heartbeat.py:114
`@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/app/api/heartbeat.py:114 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `upload_reference` without auth dependency — backend/app/api/admin.py:260
`@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/app/api/admin.py:260 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `upload_voice` without auth dependency — backend/app/api/admin.py:227
`@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/app/api/admin.py:227 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `wake` without auth dependency — backend/app/api/heartbeat.py:36
`@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/app/api/heartbeat.py:36 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'exec_used' in desktop/src/main/agent/app-sensor.ts:24
Found a known-risky pattern (exec_used). Review and replace if possible.
desktop/src/main/agent/app-sensor.ts:24 Exec used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — desktop/src/renderer/api.ts:6
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 — desktop/src/renderer/components/VoiceButton.tsx:39
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — desktop/src/renderer/public/live2dcubismcore.min.js:9
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/app/api/heartbeat/busy/route.ts:8
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/src/app/api/heartbeat/interval/route.ts:8
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/src/app/api/heartbeat/trigger/[robotId]/[action]/route.ts:10
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/src/app/api/objects/observe/route.ts:8
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/src/app/api/robots/[id]/activity/route.ts:12
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/src/app/api/robots/[id]/route.ts:10
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/src/app/api/robots/[id]/skills/route.ts:10
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/src/app/api/robots/creation-status/[jobId]/route.ts:11
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/app/api/robots/from-image/route.ts:8
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/src/app/api/stt/transcribe/route.ts:7
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/src/app/api/tts/regenerate/[robotId]/route.ts:10
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/src/app/page.tsx:354
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/src/lib/api.ts:4
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: backend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: frontend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in backend/app/admin_panel.html:409
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
backend/app/admin_panel.html:409 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in desktop/assets/characters/preview.html:199
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
desktop/assets/characters/preview.html:199 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in desktop/src/main/agent/app-sensor.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
desktop/src/main/agent/app-sensor.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in desktop/src/main/agent/screen-sensor.ts:77
Found a known-risky pattern (node_child_process). Review and replace if possible.
desktop/src/main/agent/screen-sensor.ts:77 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in desktop/src/main/backend.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
desktop/src/main/backend.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in desktop/src/main/index.ts:102
Found a known-risky pattern (node_child_process). Review and replace if possible.
desktop/src/main/index.ts:102 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in desktop/src/main/ipc.ts:52
Found a known-risky pattern (node_child_process). Review and replace if possible.
desktop/src/main/ipc.ts:52 Node child process
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/app/api/tts.py:515
`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 security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 137 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:22-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
frontend/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend/Dockerfile:1 containersPinned dependencies
low System graph quality Tests conf 1.00 Low test-to-source ratio
27 tests / 138 src (ratio 0.20).
low System graph quality Integrity conf 1.00 6 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/app/db/models_sqlite.py:process_bind_param, backend/app/db/models_sqlite.py:process_bind_param 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…
6 occurrences
repo-level (6 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 6 places
Functions with the same first-5-line body hash: backend/app/services/llm/openai.py:generate, backend/app/services/llm/anthropic.py:generate, backend/app/services/llm/deepseek.py:generate, backend/app/services/llm/claude_cli.py:generate This is *the* AI-coder failure mode (4× more duplication in vi…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph software Dead code conf 1.00 Possibly dead Python function: build_life_moments_prompt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/prompts/creation.py:348
low System graph software Dead code conf 1.00 Possibly dead Python function: build_moment_detail_prompt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/prompts/creation.py:351
low System graph software Dead code conf 1.00 Possibly dead Python function: build_moment_summary_prompt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/prompts/creation.py:354
low System graph software Dead code conf 1.00 Possibly dead Python function: create_robot_from_object
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/robot.py:23
low System graph software Dead code conf 1.00 Possibly dead Python function: do_run_migrations
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/alembic/env.py:27
low System graph software Dead code conf 1.00 10 occurrences Possibly dead Python function: downgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
10 files, 10 locations
backend/alembic/versions/39c38b95bc32_add_memory_strength_and_importance_to_.py:29
backend/alembic/versions/57fbf61d4fcf_add_relationships_snapshot_to_robots.py:28
backend/alembic/versions/5ee4eb5eea8e_add_memory_evolution_fields.py:33
backend/alembic/versions/66c72ef2d99a_add_batch_index_to_yearly_memories.py:28
backend/alembic/versions/9346fcfb1039_add_desktop_visible_to_robots.py:28
backend/alembic/versions/ae36e5831db0_add_asset_versions_table.py:41
backend/alembic/versions/b2c3d4e5f6a7_add_memory_layer.py:21
backend/alembic/versions/d82eedec33e0_add_activity_logs_table.py:37
low System graph software Dead code conf 1.00 Possibly dead Python function: process_bind_param
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/db/models_sqlite.py:45
low System graph software Dead code conf 1.00 Possibly dead Python function: process_result_value
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/db/models_sqlite.py:50
low System graph software Dead code conf 1.00 Possibly dead Python function: remove_listener
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/heartbeat.py:157
low System graph software Dead code conf 1.00 11 occurrences Possibly dead Python function: upgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
11 files, 11 locations
backend/alembic/versions/39c38b95bc32_add_memory_strength_and_importance_to_.py:21
backend/alembic/versions/57fbf61d4fcf_add_relationships_snapshot_to_robots.py:21
backend/alembic/versions/5ee4eb5eea8e_add_memory_evolution_fields.py:21
backend/alembic/versions/66c72ef2d99a_add_batch_index_to_yearly_memories.py:21
backend/alembic/versions/9346fcfb1039_add_desktop_visible_to_robots.py:21
backend/alembic/versions/a0e12534ebb0_add_energy_field.py:21
backend/alembic/versions/ae36e5831db0_add_asset_versions_table.py:21
backend/alembic/versions/b2c3d4e5f6a7_add_memory_layer.py:17
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 — desktop/src/main/agent/screen-sensor.ts:68
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — desktop/src/main/agent/sensor-manager.ts:59
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — desktop/src/main/backend.ts:36
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — desktop/src/main/index.ts:92
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 — desktop/src/main/ipc.ts:51
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 — desktop/src/renderer/api.ts:39
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — desktop/src/renderer/App.tsx:227
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/src/app/api/tts/speak/route.ts:14
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /activity/all
`backend/app/api/robots.py` declares `DELETE /activity/all` 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 /all
`backend/app/api/conversations.py` declares `DELETE /all` 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 /{robot_id}
`backend/app/api/robots.py` declares `DELETE /{robot_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 /
`backend/app/api/robots.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 /admin
`backend/app/main.py` declares `GET /admin` 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/app/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 /api/status
`backend/app/api/status.py` declares `GET /api/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 /characters
`backend/app/api/admin.py` declares `GET /characters` 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 /characters/create-from-web/status/{job_id}
`backend/app/api/admin_web_creation.py` declares `GET /characters/create-from-web/status/{job_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 document…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /characters/{char_id}/image/{state}
`backend/app/api/admin.py` declares `GET /characters/{char_id}/image/{state}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /characters/{char_id}/memories
`backend/app/api/admin.py` declares `GET /characters/{char_id}/memories` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /characters/{char_id}/versions
`backend/app/api/admin.py` declares `GET /characters/{char_id}/versions` 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 /characters/{char_id}/versions/{version_id}/file
`backend/app/api/admin.py` declares `GET /characters/{char_id}/versions/{version_id}/file` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /characters/{char_id}/voice-ref
`backend/app/api/admin.py` declares `GET /characters/{char_id}/voice-ref` 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 /creation-status/{job_id}
`backend/app/api/robots.py` declares `GET /creation-status/{job_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 /events
`backend/app/api/heartbeat.py` declares `GET /events` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /latest
`backend/app/api/conversations.py` declares `GET /latest` 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 /models
`backend/app/api/conversations.py` declares `GET /models` 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 /speak-qwen3
`backend/app/api/tts_qwen3.py` declares `GET /speak-qwen3` 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 /tools
`backend/app/api/admin.py` declares `GET /tools` 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 /{conversation_id}/messages
`backend/app/api/conversations.py` declares `GET /{conversation_id}/messages` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{robot_id}
`backend/app/api/robots.py` declares `GET /{robot_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 /{robot_id}/activity
`backend/app/api/robots.py` declares `GET /{robot_id}/activity` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{robot_id}/memories
`backend/app/api/robots.py` declares `GET /{robot_id}/memories` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{robot_id}/skills
`backend/app/api/robots.py` declares `GET /{robot_id}/skills` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /{robot_id}
`backend/app/api/robots.py` declares `PATCH /{robot_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /
`backend/app/api/conversations.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 /busy
`backend/app/api/heartbeat.py` declares `POST /busy` 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 /characters/create
`backend/app/api/admin.py` declares `POST /characters/create` 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 /characters/create-from-web
`backend/app/api/admin_web_creation.py` declares `POST /characters/create-from-web` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /characters/{char_id}/build-memories
`backend/app/api/admin_web_creation.py` declares `POST /characters/{char_id}/build-memories` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /characters/{char_id}/generate-images
`backend/app/api/admin.py` declares `POST /characters/{char_id}/generate-images` 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 /characters/{char_id}/remove-bg
`backend/app/api/admin.py` declares `POST /characters/{char_id}/remove-bg` 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 /characters/{char_id}/upload-reference
`backend/app/api/admin.py` declares `POST /characters/{char_id}/upload-reference` 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 /characters/{char_id}/upload-voice
`backend/app/api/admin.py` declares `POST /characters/{char_id}/upload-voice` 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 /characters/{char_id}/versions/{version_id}/activate
`backend/app/api/admin.py` declares `POST /characters/{char_id}/versions/{version_id}/activate` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /characters/{char_id}/versions/{version_id}/star
`backend/app/api/admin.py` declares `POST /characters/{char_id}/versions/{version_id}/star` 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: POST /characters/{char_id}/voice-lang
`backend/app/api/admin.py` declares `POST /characters/{char_id}/voice-lang` 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 /from-image
`backend/app/api/robots.py` declares `POST /from-image` 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 /idle-chat
`backend/app/api/agents.py` declares `POST /idle-chat` 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 /interval
`backend/app/api/heartbeat.py` declares `POST /interval` 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 /observe
`backend/app/api/objects.py` declares `POST /observe` 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 /react
`backend/app/api/agents.py` declares `POST /react` 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 /search
`backend/app/api/agents.py` declares `POST /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 /sleep
`backend/app/api/heartbeat.py` declares `POST /sleep` 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 /transcribe
`backend/app/api/stt.py` declares `POST /transcribe` 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 /trigger/{robot_id}/{action}
`backend/app/api/heartbeat.py` declares `POST /trigger/{robot_id}/{action}` 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 /wake
`backend/app/api/heartbeat.py` declares `POST /wake` 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 /{conversation_id}/message
`backend/app/api/conversations.py` declares `POST /{conversation_id}/message` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /tools/{tool_name}
`backend/app/api/admin.py` declares `PUT /tools/{tool_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
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/d6626a3a-59b5-4e23-897b-820acfd9b790/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/d6626a3a-59b5-4e23-897b-820acfd9b790/

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.