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

Riaan007/farm-netwatch

https://github.com/Riaan007/farm-netwatch · scanned 2026-06-15 23:50 UTC (2 months, 3 weeks ago)

123 raw signals (0 security + 123 graph)

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

Complete repo analysis

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

JSON
Combined
61.1
/100
Security checks
61
0 findings
System graph
61
100.0% cov · 114 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 31 Medium 12 Low 67 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 114 Crowd 0 Layer: Software 5 Hardware 7 Frontend 1 Security 36 Cicd 2 Quality 13 Api 50
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 61.1/100 with 100.0% coverage. It contains 435 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 123 findings — concentrated in api (50), security (36), quality (18). Risk profile is high: 0 critical, 31 high, 16 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 110 of 114 actionable findings. 123 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 security auth conf 1.00 Flask mutation route `api_command` without `@login_required` — app/server.py:113
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app/server.py:113 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_config` without `@login_required` — app/server.py:90
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app/server.py:90 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_credentials` without `@login_required` — app/server.py:219
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app/server.py:219 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_device_meta` without `@login_required` — app/server.py:244
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app/server.py:244 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_devices_prune` without `@login_required` — app/server.py:230
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app/server.py:230 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_hikvision` without `@login_required` — app/server.py:263
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app/server.py:263 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_hub_connect` without `@login_required` — app/server.py:512
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app/server.py:512 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_hub_disconnect` without `@login_required` — app/server.py:528
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app/server.py:528 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_hub_wizard` without `@login_required` — hub/app/server.py:275
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
hub/app/server.py:275 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_kuma_repair` without `@login_required` — app/server.py:376
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app/server.py:376 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_kuma_sync_tags` without `@login_required` — app/server.py:356
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app/server.py:356 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_kuma_test` without `@login_required` — app/server.py:402
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app/server.py:402 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_kuma` without `@login_required` — app/server.py:306
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app/server.py:306 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_login` without `@login_required` — hub/app/server.py:83
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
hub/app/server.py:83 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_logout` without `@login_required` — hub/app/server.py:106
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
hub/app/server.py:106 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_photo` without `@login_required` — app/server.py:414
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app/server.py:414 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_setup` without `@login_required` — app/server.py:154
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app/server.py:154 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_site_command` without `@login_required` — hub/app/server.py:375
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
hub/app/server.py:375 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_site_poll` without `@login_required` — hub/app/server.py:431
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
hub/app/server.py:431 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_site_trigger` without `@login_required` — hub/app/server.py:393
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
hub/app/server.py:393 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_site_tunnel_close` without `@login_required` — hub/app/server.py:464
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
hub/app/server.py:464 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_site_tunnel` without `@login_required` — hub/app/server.py:441
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
hub/app/server.py:441 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_site` without `@login_required` — hub/app/server.py:214
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
hub/app/server.py:214 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_sites` without `@login_required` — hub/app/server.py:198
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
hub/app/server.py:198 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_test_ntfy` without `@login_required` — app/server.py:133
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app/server.py:133 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_trigger` without `@login_required` — app/server.py:100
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app/server.py:100 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_tunnel_close` without `@login_required` — app/server.py:557
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app/server.py:557 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_tunnel` without `@login_required` — app/server.py:541
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app/server.py:541 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_wizard` without `@login_required` — app/server.py:473
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
app/server.py:473 securityAuth flask unauth route
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in app/hikvision.py:40
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
app/hikvision.py:40 Tls verify false
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in app/identify.py:119
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
app/identify.py:119 Tls verify false
medium System graph quality Tests conf 1.00 CI is configured but no tests are detected
A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.
CI/CDConfig theaterRepo hardening
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: 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: hub/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 5 occurrences GitHub Action is tag-pinned rather than SHA-pinned
docker/setup-qemu-action@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 22, 25, 28, 36, 45
.github/workflows/build.yml:22, 25, 28, 36, 45 (5 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/build.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in app/static/index.html:435
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
app/static/index.html:435 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in app/static/setup.html:104
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
app/static/setup.html:104 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in hub/app/static/index.html:232
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
hub/app/static/index.html:232 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in hub/app/static/site.html:257
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
hub/app/static/site.html:257 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 Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 24 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 7 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `HUB_DATA`, `HUB_PROXY_RANGE`, `HUB_TCP_RANGE`, `NETWATCH_DATA`, `NETWATCH_INSTALL_URL`, `NETWATCH_PORT`, `WGEASY_URL`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, tests. 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 17 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: debian:bookworm-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:5 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: debian:bookworm-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
hub/Dockerfile:6 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-bookworm
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:25 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-bookworm
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
hub/Dockerfile:26 containersPinned dependencies
low System graph quality Integrity conf 1.00 5 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: hub/app/tunnels.py:conns, app/tunnels.py:conns 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.
5 occurrences
repo-level (5 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: hub/app/tunnels.py:start, hub/app/tunnels.py:start, app/tunnels.py:start, app/tunnels.py:start 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 sepa…
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: is_up
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/hubvpn.py:108
low System graph software Dead code conf 1.00 Possibly dead Python function: loop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scanner.py:702
low System graph software Dead code conf 1.00 Possibly dead Python function: loop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/listener.py:52
low System graph software Dead code conf 1.00 Possibly dead Python function: run_mdns
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/discovery.py:252
low System graph software Dead code conf 1.00 Possibly dead Python function: run_ssdp
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/discovery.py:249
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: ANY /
`hub/app/server.py` declares `ANY /` 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: ANY /api/auth-state
`hub/app/server.py` declares `ANY /api/auth-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: ANY /api/command
`app/server.py` declares `ANY /api/command` 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: ANY /api/config
`app/server.py` declares `ANY /api/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: ANY /api/devices
`app/server.py` declares `ANY /api/devices` 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: ANY /api/devices/<path:key>
`app/server.py` declares `ANY /api/devices/<path:key>` 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: ANY /api/devices/<path:key>/credentials
`app/server.py` declares `ANY /api/devices/<path:key>/credentials` 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: ANY /api/devices/<path:key>/health
`app/server.py` declares `ANY /api/devices/<path:key>/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: ANY /api/devices/<path:key>/hikvision
`app/server.py` declares `ANY /api/devices/<path:key>/hikvision` 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: ANY /api/devices/<path:key>/kuma
`app/server.py` declares `ANY /api/devices/<path:key>/kuma` 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: ANY /api/devices/<path:key>/photo
`app/server.py` declares `ANY /api/devices/<path:key>/photo` 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: ANY /api/devices/prune
`app/server.py` declares `ANY /api/devices/prune` 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: ANY /api/events
`app/server.py` declares `ANY /api/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: ANY /api/health
`hub/app/server.py` declares `ANY /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: ANY /api/history/<path:key>
`app/server.py` declares `ANY /api/history/<path:key>` 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: ANY /api/hub/connect
`app/server.py` declares `ANY /api/hub/connect` 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: ANY /api/hub/disconnect
`app/server.py` declares `ANY /api/hub/disconnect` 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: ANY /api/hub/overview
`hub/app/server.py` declares `ANY /api/hub/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: ANY /api/hub/sites
`hub/app/server.py` declares `ANY /api/hub/sites` 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: ANY /api/hub/sites/<site_id>
`hub/app/server.py` declares `ANY /api/hub/sites/<site_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: ANY /api/hub/sites/<site_id>/command
`hub/app/server.py` declares `ANY /api/hub/sites/<site_id>/command` 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: ANY /api/hub/sites/<site_id>/devices
`hub/app/server.py` declares `ANY /api/hub/sites/<site_id>/devices` 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: ANY /api/hub/sites/<site_id>/enroll
`hub/app/server.py` declares `ANY /api/hub/sites/<site_id>/enroll` 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: ANY /api/hub/sites/<site_id>/history/<path:key>
`hub/app/server.py` declares `ANY /api/hub/sites/<site_id>/history/<path:key>` 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: ANY /api/hub/sites/<site_id>/kuma
`hub/app/server.py` declares `ANY /api/hub/sites/<site_id>/kuma` 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: ANY /api/hub/sites/<site_id>/poll
`hub/app/server.py` declares `ANY /api/hub/sites/<site_id>/poll` 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: ANY /api/hub/sites/<site_id>/reachability
`hub/app/server.py` declares `ANY /api/hub/sites/<site_id>/reachability` 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: ANY /api/hub/sites/<site_id>/trigger
`hub/app/server.py` declares `ANY /api/hub/sites/<site_id>/trigger` 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: ANY /api/hub/sites/<site_id>/tunnel
`hub/app/server.py` declares `ANY /api/hub/sites/<site_id>/tunnel` 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: ANY /api/hub/sites/<site_id>/tunnel/<tid>
`hub/app/server.py` declares `ANY /api/hub/sites/<site_id>/tunnel/<tid>` 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: ANY /api/hub/sites/<site_id>/tunnels
`hub/app/server.py` declares `ANY /api/hub/sites/<site_id>/tunnels` 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: ANY /api/hub/status
`app/server.py` declares `ANY /api/hub/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: ANY /api/hub/wizard
`hub/app/server.py` declares `ANY /api/hub/wizard` 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: ANY /api/ip-history
`app/server.py` declares `ANY /api/ip-history` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/kuma/repair
`app/server.py` declares `ANY /api/kuma/repair` 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: ANY /api/kuma/sync-tags
`app/server.py` declares `ANY /api/kuma/sync-tags` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/kuma/test
`app/server.py` declares `ANY /api/kuma/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: ANY /api/login
`hub/app/server.py` declares `ANY /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: ANY /api/logout
`hub/app/server.py` declares `ANY /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: ANY /api/setup
`app/server.py` declares `ANY /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: ANY /api/status
`app/server.py` declares `ANY /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: ANY /api/test-ntfy
`app/server.py` declares `ANY /api/test-ntfy` 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: ANY /api/trigger
`app/server.py` declares `ANY /api/trigger` 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: ANY /api/tunnel
`app/server.py` declares `ANY /api/tunnel` 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: ANY /api/tunnel/<tid>
`app/server.py` declares `ANY /api/tunnel/<tid>` 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: ANY /api/wizard
`app/server.py` declares `ANY /api/wizard` 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: ANY /app.css
`hub/app/server.py` declares `ANY /app.css` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /login
`hub/app/server.py` declares `ANY /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: ANY /setup
`app/server.py` declares `ANY /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: ANY /site/<site_id>
`hub/app/server.py` declares `ANY /site/<site_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
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/809281bb-544c-4af7-b675-79383e80725c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/809281bb-544c-4af7-b675-79383e80725c/

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.