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

bensalmon91-cpu/PoolAI

https://github.com/bensalmon91-cpu/PoolAI · scanned 2026-06-17 01:39 UTC (1 month, 2 weeks ago)

156 raw signals (0 security + 156 graph)

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

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -23.7 (diff) · 135 actionable findings from 1 signal source. 21 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

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

Showing 125 of 135 actionable findings. 156 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 Agent instructions conf 1.00 Agent instruction/config may expose a secret: pi-software/CLAUDE.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
pi-software/CLAUDE.md:62 SecretsClaude instruction
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: pi-software/PoolDash_v6/CLAUDE.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
pi-software/PoolDash_v6/CLAUDE.md:41 SecretsClaude instruction
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/portal/pools (web-portal/js/portal.js:184)
`web-portal/js/portal.js:184` calls `GET /api/portal/pools` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/portal/pools` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/accounts (web-portal/js/admin.js:221)
`web-portal/js/admin.js:221` calls `POST /api/admin/accounts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/accounts` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/pools (web-portal/js/admin.js:292)
`web-portal/js/admin.js:292` calls `POST /api/admin/pools` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/pools` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/users (web-portal/js/admin.js:327)
`web-portal/js/admin.js:327` calls `POST /api/admin/users` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph security auth conf 1.00 Flask mutation route `api_initiate` without `@login_required` — brain/launcher.py:685
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
brain/launcher.py:685 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_push` without `@login_required` — brain/launcher.py:657
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
brain/launcher.py:657 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `api_settings` without `@login_required` — brain/launcher.py:646
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
brain/launcher.py:646 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `apply_changes` without `@login_required` — brain/technician_web.py:303
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
brain/technician_web.py:303 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `finish_session` without `@login_required` — brain/technician_web.py:281
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
brain/technician_web.py:281 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `respond` without `@login_required` — brain/technician_web.py:270
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
brain/technician_web.py:270 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `sms_webhook` without `@login_required` — brain/technician_sms.py:225
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
brain/technician_sms.py:225 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `start_session` without `@login_required` — brain/technician_web.py:261
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
brain/technician_web.py:261 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `whatsapp_webhook` without `@login_required` — brain/technician_sms.py:240
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
brain/technician_sms.py:240 securityAuth flask unauth route
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in pi-software/PoolDash_v6/pooldash_app/static/js/plotly-basic-2.27.0.min.js:8
Found a known-risky pattern (new_function_used). Review and replace if possible.
pi-software/PoolDash_v6/pooldash_app/static/js/plotly-basic-2.27.0.min.js:8 New function used
high System graph security security conf 1.00 Insecure pattern 'python_os_system' in pi-software/PoolDash_v6/scripts/device_upload.py:69
Found a known-risky pattern (python_os_system). Review and replace if possible.
pi-software/PoolDash_v6/scripts/device_upload.py:69 Python os system
high System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in pi-software/PoolDash_v6/scripts/button_handler.py:83
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
pi-software/PoolDash_v6/scripts/button_handler.py:83 Subprocess shell true
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — pi-software/PoolDash_v6/pooldash_app/static/sw.js:53
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 — web-portal/js/admin.js:22
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 — web-portal/js/portal.js:85
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: brain/CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
brain/CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: pi-software/.claude/settings.local.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
pi-software/.claude/settings.local.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: pi-software/PoolDash_v6/CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
pi-software/PoolDash_v6/CLAUDE.md VerificationClaude instruction
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. 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 security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in brain/launcher.py:565
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
brain/launcher.py:565 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pi-software/PoolDash_v6/pooldash_app/blueprints/charts.py:426
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pi-software/PoolDash_v6/pooldash_app/blueprints/charts.py:426 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py:1173
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py:1173 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pi-software/PoolDash_v6/pooldash_app/blueprints/proxy.py:60
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pi-software/PoolDash_v6/pooldash_app/blueprints/proxy.py:60 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pi-software/PoolDash_v6/pooldash_app/static/js/plotly-basic-2.27.0.min.js:8
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pi-software/PoolDash_v6/pooldash_app/static/js/plotly-basic-2.27.0.min.js:8 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in web-portal/js/admin.js:31
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
web-portal/js/admin.js:31 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in web-portal/js/app.js:86
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
web-portal/js/app.js:86 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in web-portal/js/portal.js:18
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
web-portal/js/portal.js:18 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in web-portal/poolai_deploy/assets/js/pwa.js:90
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
web-portal/poolai_deploy/assets/js/pwa.js:90 Direct innerhtml assignment
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py:2929
`subprocess.Popen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — pi-software/PoolDash_v6/scripts/publish_update.py:56
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — pi-software/PoolDash_v6/scripts/update_check.py:626
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 70 placeholder/mock markers across 27 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 1000 in use
Port 1000 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
pi-software/PoolDash_v6/deploy/pre_configure.sh Ports
medium System graph network Security conf 1.00 Privileged port 502 in use
Port 502 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
pi-software/PoolDash_v6/scripts/post_install.sh Ports
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
11 test file(s) for 126 source file(s) (ratio 0.09). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 33 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `BACKOFF_ENABLED`, `DB_PORT`, `DEVICE_IDS`, `FAILURE_ALERT_THRESHOLD`, `HEALTH_LOG_INTERVAL`, `LOG_LEVEL`, `MAINT_DB_PATH`, `MODBUS_PROFILE` + 25 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 717 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 quality Integrity conf 1.00 20 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: ai-assistant/pi/ai_sync.py:get_db_path, ai-assistant/pi/ai_sync.py:get_db 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.
20 occurrences
repo-level (20 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 quality Integrity conf 1.00 Old/deprecated-named symbol `app_backup` in pi-software/PoolDash_v6/scripts/update_check.py:447
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `old_backup` in pi-software/PoolDash_v6/tools/config_backup.py:84
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `ssh_authorized_keys_backup` in pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py:1962
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: add_alarm_note
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
pi-software/PoolDash_v6/pooldash_app/db/alarm_log.py:102
low System graph software Dead code conf 1.00 Possibly dead Python function: bit_names_from_value
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
pi-software/PoolDash_v6/tools/modbus_logger.py:1048
low System graph software Dead code conf 1.00 Possibly dead Python function: button_callback
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
pi-software/PoolDash_v6/scripts/button_handler.py:172
low System graph software Dead code conf 1.00 Possibly dead Python function: check_database_health
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
pi-software/PoolDash_v6/pooldash_app/db/connection.py:144
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_deploy
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
web-portal/deploy.py:438
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_list
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
web-portal/deploy.py:425
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_verify
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
web-portal/deploy.py:466
low System graph software Dead code conf 1.00 Possibly dead Python function: delete_lsi_reading
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
pi-software/PoolDash_v6/pooldash_app/db/lsi_history.py:196
low System graph software Dead code conf 1.00 Possibly dead Python function: detect_protocol
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
pi-software/PoolDash_v6/tools/modbus_logger.py:257
low System graph software Dead code conf 1.00 Possibly dead Python function: ensure_maintenance_table_in_pool_db
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
pi-software/PoolDash_v6/pooldash_app/db/maintenance.py:49
low System graph software Dead code conf 1.00 Possibly dead Python function: init_database
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
pi-software/PoolDash_v6/pooldash_app/db/connection.py:26
low System graph software Dead code conf 1.00 Possibly dead Python function: log_alarm
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
pi-software/PoolDash_v6/pooldash_app/db/alarm_log.py:57
low System graph software Dead code conf 1.00 Possibly dead Python function: process_ai_response
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
ai-assistant/pi/ai_sync.py:153
low System graph software Dead code conf 1.00 Possibly dead Python function: save_insight
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
brain/llm_analyzer.py:82
low System graph software Dead code conf 1.00 Possibly dead Python function: scan_port
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
pi-software/PoolDash_v6/pooldash_app/utils/net.py:324
low System graph software Dead code conf 1.00 Possibly dead Python function: set_db_path
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
ai-assistant/pi/ai_sync.py:39
low System graph software Dead code conf 1.00 Possibly dead Python function: update_equipment
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
brain/investigator.py:218
low System graph software Dead code conf 1.00 Possibly dead Python function: update_optimal_parameters
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
brain/investigator.py:224
low System graph frontend Frontend quality conf 1.00 React Flow edge with `label=` but no project-wide edge-label CSS override — pi-software/PoolDash_v6/pooldash_app/static/js/plotly-basic-2.27.0.min.js:8
React Flow edge labels render with a white rectangle behind the text by default, which scatters bright boxes across a dark canvas. Either drop the label, or override `.react-flow__edge-textbg` and `.react-flow__edge-text` in your stylesheet. Why: P-H in CHECKLIST.md — vendor edge labels bleed whit…
Fq edge label no bg
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — mobile-app/src/services/auth.ts:67
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 — mobile-app/src/stores/authStore.ts:146
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 — mobile-app/src/stores/deviceStore.ts:145
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 — web-portal/poolai_deploy/assets/js/pwa.js:32
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 — web-portal/poolai_deploy/service-worker.js:42
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: ANY /
`ai-assistant/pi/blueprints/ai_assistant.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 /<pool>/<metric>
`pi-software/PoolDash_v6/pooldash_app/blueprints/charts.py` declares `ANY /<pool>/<metric>` 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: ANY /<pool>/lsi
`pi-software/PoolDash_v6/pooldash_app/blueprints/charts.py` declares `ANY /<pool>/lsi` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /<pool>/trends
`pi-software/PoolDash_v6/pooldash_app/blueprints/charts.py` declares `ANY /<pool>/trends` 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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/<pool>/<metric>/data
`pi-software/PoolDash_v6/pooldash_app/blueprints/charts.py` declares `ANY /api/<pool>/<metric>/data` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/<pool>/trends/data
`pi-software/PoolDash_v6/pooldash_app/blueprints/charts.py` declares `ANY /api/<pool>/trends/data` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or document…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/answer
`ai-assistant/pi/blueprints/ai_assistant.py` declares `ANY /api/answer` 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/ask-me
`ai-assistant/pi/blueprints/ai_assistant.py` declares `ANY /api/ask-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: ANY /api/health
`pi-software/PoolDash_v6/pooldash_app/blueprints/health.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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/ping
`pi-software/PoolDash_v6/pooldash_app/blueprints/health.py` declares `ANY /api/ping` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/questions
`ai-assistant/pi/blueprints/ai_assistant.py` declares `ANY /api/questions` 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/stats
`ai-assistant/pi/blueprints/ai_assistant.py` declares `ANY /api/stats` 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/suggestion/<int:suggestion_id>/action
`ai-assistant/pi/blueprints/ai_assistant.py` declares `ANY /api/suggestion/<int:suggestion_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 docu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/suggestion/<int:suggestion_id>/read
`ai-assistant/pi/blueprints/ai_assistant.py` declares `ANY /api/suggestion/<int:suggestion_id>/read` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/suggestions
`ai-assistant/pi/blueprints/ai_assistant.py` declares `ANY /api/suggestions` 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 /canonical.html
`pi-software/PoolDash_v6/pooldash_app/__init__.py` declares `ANY /canonical.html` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /connect
`pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py` declares `ANY /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 consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /connectivitycheck.gstatic.com
`pi-software/PoolDash_v6/pooldash_app/__init__.py` declares `ANY /connectivitycheck.gstatic.com` 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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /gen_204
`pi-software/PoolDash_v6/pooldash_app/__init__.py` declares `ANY /gen_204` 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 /generate_204
`pi-software/PoolDash_v6/pooldash_app/__init__.py` declares `ANY /generate_204` 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 /hotspot-detect.html
`pi-software/PoolDash_v6/pooldash_app/__init__.py` declares `ANY /hotspot-detect.html` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /ip_proxy
`pi-software/PoolDash_v6/pooldash_app/blueprints/ip_view.py` declares `ANY /ip_proxy` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /ip_view
`pi-software/PoolDash_v6/pooldash_app/blueprints/ip_view.py` declares `ANY /ip_view` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /library/test/success.html
`pi-software/PoolDash_v6/pooldash_app/__init__.py` declares `ANY /library/test/success.html` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /ncsi.txt
`pi-software/PoolDash_v6/pooldash_app/__init__.py` declares `ANY /ncsi.txt` 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 /pool/<pool>
`pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py` declares `ANY /pool/<pool>` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /pool/<pool>/lsi/autofill
`pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py` declares `ANY /pool/<pool>/lsi/autofill` 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 docum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /pool/<pool>/lsi/history
`pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py` declares `ANY /pool/<pool>/lsi/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 docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /pool/<pool>/maintenance
`pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py` declares `ANY /pool/<pool>/maintenance` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /pool/<pool>/maintenance/logs
`pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py` declares `ANY /pool/<pool>/maintenance/logs` 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 d…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /qr
`pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py` declares `ANY /qr` 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 /qr/page
`pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py` declares `ANY /qr/page` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /settings
`pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py` declares `ANY /settings` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /settings/ethernet
`pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py` declares `ANY /settings/ethernet` 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: ANY /settings/network/diagnostics
`pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py` declares `ANY /settings/network/diagnostics` 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 d…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /settings/network/reset
`pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py` declares `ANY /settings/network/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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /settings/reboot
`pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py` declares `ANY /settings/reboot` 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: ANY /settings/wifi
`pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py` declares `ANY /settings/wifi` 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: ANY /settings/wifi/disconnect
`pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py` declares `ANY /settings/wifi/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 docum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /settings/wifi/ip
`pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py` declares `ANY /settings/wifi/ip` 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 w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /settings/wifi/scan
`pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py` declares `ANY /settings/wifi/scan` 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: ANY /success.txt
`pi-software/PoolDash_v6/pooldash_app/__init__.py` declares `ANY /success.txt` 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 /<pool>
`pi-software/PoolDash_v6/pooldash_app/blueprints/alarms.py` declares `GET /<pool>` 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: GET /<pool>/export
`pi-software/PoolDash_v6/pooldash_app/blueprints/alarms.py` declares `GET /<pool>/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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /<pool>/history
`pi-software/PoolDash_v6/pooldash_app/blueprints/alarms.py` declares `GET /<pool>/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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/<pool>
`pi-software/PoolDash_v6/pooldash_app/blueprints/alarms.py` declares `GET /api/<pool>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/<pool>/controller-states
`pi-software/PoolDash_v6/pooldash_app/blueprints/alarms.py` declares `GET /api/<pool>/controller-states` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or do…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/<pool>/states
`pi-software/PoolDash_v6/pooldash_app/blueprints/alarms.py` declares `GET /api/<pool>/states` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /<pool>/sync
`pi-software/PoolDash_v6/pooldash_app/blueprints/alarms.py` declares `POST /<pool>/sync` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /acknowledge/<int:alarm_id>
`pi-software/PoolDash_v6/pooldash_app/blueprints/alarms.py` declares `POST /acknowledge/<int:alarm_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 doc…
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: pi-software/PoolDash_v6/pooldash_app/blueprints/main_ui.py (4929 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: pi-software/PoolDash_v6/tools/modbus_logger.py (2073 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/379a4f5a-baa9-44ec-a53a-6f471a19aad7/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/379a4f5a-baa9-44ec-a53a-6f471a19aad7/

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.