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

the-vibe-dev/guardiannode

https://github.com/the-vibe-dev/guardiannode · scanned 2026-06-16 00:33 UTC (2 months, 2 weeks ago)

129 raw signals (0 security + 129 graph)

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

Complete repo analysis

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

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

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

critical System graph security Secrets conf 1.00 Possible secret in backend/app/static/assets/index-BwTxGcoF.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
backend/app/static/assets/index-BwTxGcoF.js:67
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /devices/${device_id} (dashboard/src/api.ts:45)
`dashboard/src/api.ts:45` calls `DELETE /devices/${device_id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/devices/<p>` 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: GET /alerts/${id} (dashboard/src/api.ts:52)
`dashboard/src/api.ts:52` calls `GET /alerts/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/alerts/<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 /auth/me (dashboard/src/api.ts:31)
`dashboard/src/api.ts:31` calls `GET /auth/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/me` 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 /dashboard/overview (dashboard/src/api.ts:37)
`dashboard/src/api.ts:37` calls `GET /dashboard/overview` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/overview` 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 /devices (dashboard/src/api.ts:38)
`dashboard/src/api.ts:38` calls `GET /devices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/devices` 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 /models/status (dashboard/src/api.ts:57)
`dashboard/src/api.ts:57` calls `GET /models/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/models/status` 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 /policies/${profile_id}/effective (dashboard/src/api.ts:104)
`dashboard/src/api.ts:104` calls `GET /policies/${profile_id}/effective` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/policies/<p>/effective` If this points at an external API, prefix it with `https://` s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /profiles (dashboard/src/api.ts:59)
`dashboard/src/api.ts:59` calls `GET /profiles` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/profiles` 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 /profiles/policy/meta (dashboard/src/api.ts:85)
`dashboard/src/api.ts:85` calls `GET /profiles/policy/meta` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/profiles/policy/meta` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /settings/notifications (dashboard/src/api.ts:86)
`dashboard/src/api.ts:86` calls `GET /settings/notifications` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/settings/notifications` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /settings/retention (dashboard/src/api.ts:91)
`dashboard/src/api.ts:91` calls `GET /settings/retention` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/settings/retention` 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 /setup/status (dashboard/src/api.ts:24)
`dashboard/src/api.ts:24` calls `GET /setup/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/setup/status` 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 /storage (dashboard/src/api.ts:96)
`dashboard/src/api.ts:96` calls `GET /storage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/storage` 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 /devices/${device_id}/profile (dashboard/src/api.ts:47)
`dashboard/src/api.ts:47` calls `PATCH /devices/${device_id}/profile` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/devices/<p>/profile` If this points at an external API, prefix it with `https://` so the …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /policies/${profile_id}/effective (dashboard/src/api.ts:106)
`dashboard/src/api.ts:106` calls `PATCH /policies/${profile_id}/effective` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/policies/<p>/effective` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /profiles/${profile_id} (dashboard/src/api.ts:81)
`dashboard/src/api.ts:81` calls `PATCH /profiles/${profile_id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/profiles/<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: PATCH /settings/notifications (dashboard/src/api.ts:88)
`dashboard/src/api.ts:88` calls `PATCH /settings/notifications` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/settings/notifications` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /settings/retention (dashboard/src/api.ts:93)
`dashboard/src/api.ts:93` calls `PATCH /settings/retention` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/settings/retention` 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 /alerts/${id}/feedback (dashboard/src/api.ts:56)
`dashboard/src/api.ts:56` calls `POST /alerts/${id}/feedback` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/alerts/<p>/feedback` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /alerts/${id}/review (dashboard/src/api.ts:54)
`dashboard/src/api.ts:54` calls `POST /alerts/${id}/review` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/alerts/<p>/review` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /auth/login (dashboard/src/api.ts:29)
`dashboard/src/api.ts:29` calls `POST /auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/login` 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 /auth/logout (dashboard/src/api.ts:30)
`dashboard/src/api.ts:30` calls `POST /auth/logout` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/logout` 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 /auth/recovery-reset (dashboard/src/api.ts:33)
`dashboard/src/api.ts:33` calls `POST /auth/recovery-reset` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/recovery-reset` 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: POST /auth/setup (dashboard/src/api.ts:27)
`dashboard/src/api.ts:27` calls `POST /auth/setup` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/setup` 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 /devices/${device_id}/pause (dashboard/src/api.ts:41)
`dashboard/src/api.ts:41` calls `POST /devices/${device_id}/pause` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/devices/<p>/pause` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /devices/${device_id}/resume (dashboard/src/api.ts:43)
`dashboard/src/api.ts:43` calls `POST /devices/${device_id}/resume` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/devices/<p>/resume` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /devices/pair/start (dashboard/src/api.ts:39)
`dashboard/src/api.ts:39` calls `POST /devices/pair/start` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/devices/pair/start` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /models/test (dashboard/src/api.ts:58)
`dashboard/src/api.ts:58` calls `POST /models/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/models/test` 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 /profiles (dashboard/src/api.ts:66)
`dashboard/src/api.ts:66` calls `POST /profiles` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/profiles` 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 /settings/notifications/test (dashboard/src/api.ts:90)
`dashboard/src/api.ts:90` calls `POST /settings/notifications/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/settings/notifications/test` If this points at an external API, prefix it with `https://` s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /settings/retention/run-cleanup (dashboard/src/api.ts:95)
`dashboard/src/api.ts:95` calls `POST /settings/retention/run-cleanup` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/settings/retention/run-cleanup` If this points at an external API, prefix it with `https…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /setup/recovery (dashboard/src/api.ts:25)
`dashboard/src/api.ts:25` calls `POST /setup/recovery` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/setup/recovery` 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 /storage/export (dashboard/src/api.ts:97)
`dashboard/src/api.ts:97` calls `POST /storage/export` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/storage/export` 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 /storage/wipe (dashboard/src/api.ts:99)
`dashboard/src/api.ts:99` calls `POST /storage/wipe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/storage/wipe` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph security auth conf 1.00 FastAPI POST `create_child_request` without auth dependency — backend/app/api/child_requests.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/app/api/child_requests.py:39 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `get_recovery_code` without auth dependency — backend/app/api/setup.py:32
`@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/setup.py:32 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `heartbeat` without auth dependency — backend/app/api/devices.py:222
`@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/devices.py:222 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_screenshot` without auth dependency — backend/app/api/events.py:153
`@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/events.py:153 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest` without auth dependency — backend/app/api/events.py:48
`@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/events.py:48 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `pair_complete` without auth dependency — backend/app/api/devices.py:135
`@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/devices.py:135 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `recovery_reset` without auth dependency — backend/app/api/auth.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/auth.py:91 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `setup` without auth dependency — backend/app/api/auth.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/app/api/auth.py:122 securityAuth fastapi unauth mutation
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — backend/app/static/assets/index-BwTxGcoF.js:33
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — backend/app/static/assets/index-BwTxGcoF.js:1
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 Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
softprops/action-gh-release@v2 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 173, 197
.github/workflows/release-installers.yml:173, 197 (2 hits)
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/deploy-docs.yml CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/release-installers.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in backend/app/static/assets/index-BwTxGcoF.js:37
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
backend/app/static/assets/index-BwTxGcoF.js:37 Direct innerhtml assignment
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 quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 19 placeholder/mock markers across 7 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph network Security conf 1.00 Privileged port 465 in use
Port 465 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
dashboard/src/pages/Settings.tsx Ports
medium System graph network Security conf 1.00 Privileged port 587 in use
Port 587 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
dashboard/src/pages/Settings.tsx Ports
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 cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
actions/deploy-pages@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/deploy-docs.yml:41 CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/app/api/devices.py:resume_device, backend/app/api/devices.py:revoke_device 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.
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: agent-windows/src/ocr_engine.py:recognize, agent-windows/src/ocr_engine.py:recognize, agent-windows/src/ocr_engine.py:recognize, agent-windows/src/ocr_engine.py:recognize This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — …
duplicatesduplication
low System graph software Dead code conf 1.00 Possibly dead Python function: add_service
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent-windows/src/pairing_client.py:39
low System graph software Dead code conf 1.00 Possibly dead Python function: current_device
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/api/deps.py:30
low System graph software Dead code conf 1.00 Possibly dead Python function: current_user
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/api/deps.py:20
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_with_image_path
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/ollama_client.py:114
low System graph software Dead code conf 1.00 Possibly dead Python function: health
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent-windows/src/backend_client.py:16
low System graph software Dead code conf 1.00 Possibly dead Python function: list_models
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/ollama_client.py:52
low System graph software Dead code conf 1.00 Possibly dead Python function: make_engine
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent-windows/src/ocr_engine.py:81
low System graph software Dead code conf 1.00 Possibly dead Python function: pull
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/ollama_client.py:134
low System graph software Dead code conf 1.00 Possibly dead Python function: recognize
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent-windows/src/ocr_engine.py:60
low System graph software Dead code conf 1.00 Possibly dead Python function: remove_service
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent-windows/src/pairing_client.py:54
low System graph software Dead code conf 1.00 Possibly dead Python function: run_once
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/workers/cleanup_worker.py:29
low System graph software Dead code conf 1.00 Possibly dead Python function: run_once
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/workers/offline_monitor.py:135
low System graph software Dead code conf 1.00 Possibly dead Python function: send_event
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent-windows/src/backend_client.py:22
low System graph software Dead code conf 1.00 Possibly dead Python function: update_service
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent-windows/src/pairing_client.py:57
low System graph software Dead code conf 1.00 Possibly dead Python function: write_credentials
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent-windows/src/parent_auth.py:25
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 api Wiring conf 1.00 Unused endpoint: DELETE /api/{device_id}
`backend/app/api/devices.py` declares `DELETE /api/{device_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 /api/{profile_id}
`backend/app/api/profiles.py` declares `DELETE /api/{profile_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/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
`backend/app/api/storage.py` declares `GET /api` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/capture-config
`backend/app/api/devices.py` declares `GET /api/capture-config` 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/me
`backend/app/api/auth.py` declares `GET /api/me` 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/overview
`backend/app/api/dashboard.py` declares `GET /api/overview` 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/policy/meta
`backend/app/api/profiles.py` declares `GET /api/policy/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 /api/status
`backend/app/api/setup.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 /api/{alert_id}
`backend/app/api/alerts.py` declares `GET /api/{alert_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/{event_id}/screenshot
`backend/app/api/events.py` declares `GET /api/{event_id}/screenshot` 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/{event_id}/text
`backend/app/api/events.py` declares `GET /api/{event_id}/text` 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/{profile_id}/effective
`backend/app/api/policies.py` declares `GET /api/{profile_id}/effective` 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 /notifications
`backend/app/api/settings.py` declares `GET /notifications` 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 /retention
`backend/app/api/settings.py` declares `GET /retention` 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 /{full_path:path}
`backend/app/main.py` declares `GET /{full_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: PATCH /api/{device_id}/profile
`backend/app/api/devices.py` declares `PATCH /api/{device_id}/profile` 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 /api/{policy_id}
`backend/app/api/policies.py` declares `PATCH /api/{policy_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 /api/{profile_id}
`backend/app/api/profiles.py` declares `PATCH /api/{profile_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 /api/{profile_id}/effective
`backend/app/api/policies.py` declares `PATCH /api/{profile_id}/effective` 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 /notifications
`backend/app/api/settings.py` declares `PATCH /notifications` 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 /retention
`backend/app/api/settings.py` declares `PATCH /retention` 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/child_requests.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 /api
`backend/app/api/events.py` declares `POST /api` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/export
`backend/app/api/storage.py` declares `POST /api/export` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/heartbeat
`backend/app/api/devices.py` declares `POST /api/heartbeat` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/login
`backend/app/api/auth.py` declares `POST /api/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 /api/logout
`backend/app/api/auth.py` declares `POST /api/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 /api/pair/complete
`backend/app/api/devices.py` declares `POST /api/pair/complete` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/pair/start
`backend/app/api/devices.py` declares `POST /api/pair/start` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/recovery
`backend/app/api/setup.py` declares `POST /api/recovery` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/recovery-reset
`backend/app/api/auth.py` declares `POST /api/recovery-reset` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/screenshot
`backend/app/api/events.py` declares `POST /api/screenshot` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/setup
`backend/app/api/auth.py` declares `POST /api/setup` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/test
`backend/app/api/models.py` declares `POST /api/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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/wipe
`backend/app/api/storage.py` declares `POST /api/wipe` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/{alert_id}/action
`backend/app/api/alerts.py` declares `POST /api/{alert_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 /api/{alert_id}/feedback
`backend/app/api/alerts.py` declares `POST /api/{alert_id}/feedback` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/{alert_id}/review
`backend/app/api/alerts.py` declares `POST /api/{alert_id}/review` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/{device_id}/pause
`backend/app/api/devices.py` declares `POST /api/{device_id}/pause` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/{device_id}/resume
`backend/app/api/devices.py` declares `POST /api/{device_id}/resume` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/{risk_id}/feedback
`backend/app/api/risks.py` declares `POST /api/{risk_id}/feedback` 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 /notifications/test
`backend/app/api/settings.py` declares `POST /notifications/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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /retention/run-cleanup
`backend/app/api/settings.py` declares `POST /retention/run-cleanup` 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 /{request_id}/review
`backend/app/api/child_requests.py` declares `POST /{request_id}/review` 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/bfbcd6f7-c2d8-40ee-9595-c9ce1ae54e6e/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/bfbcd6f7-c2d8-40ee-9595-c9ce1ae54e6e/

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.