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.

thomasb6/FundusTracker

https://github.com/thomasb6/FundusTracker · scanned 2026-06-16 00:35 UTC (2 months, 2 weeks ago)

26 raw signals (0 security + 26 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 23 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 5 Low 16 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 23 Crowd 0 Layer: Software 7 Frontend 2 Hardware 3 Security 2 Quality 9

Exclude dismissed / FP Exclude test files

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

No auth library detected

GapSeverity.MEDIUM Layer.SECURITY score 0.338

Why: medium severity

Insecure pattern 'direct_innerhtml_assignment' in assets/shortcuts_help.js:39

GapSeverity.MEDIUM Layer.SECURITY score 0.248

Why: medium severity · OWASP-class risk

assets/shortcuts_help.js:39

Dockerfile runs as root: Dockerfile

GapSeverity.MEDIUM Layer.HARDWARE score 0.225

Why: medium severity

Critical user flow still appears backed by mock or placeholder data

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity

Network/subprocess call without timeout or try/except — main.py:469

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity · crashes are likely without this

Fix: Add a `timeout=N` argument and wrap in `try/except` in main.py:469 to prevent hung calls.

Stray `console.log` in TS/JS — assets/keyboard_shortcuts.js:19

GapSeverity.LOW Layer.FRONTEND score 0.170

Why: low severity · fix is short / mechanical

Fix: Delete or guard the `console.log` in assets/keyboard_shortcuts.js:19.

Possibly dead Python function: count_access_requests

GapSeverity.LOW Layer.SOFTWARE score 0.140

Why: low severity · clean removal is a safe PR

Fix: If genuinely unused, remove the function in auth.py:191; if framework-registered, add a docstring.

auth.py:191

Possibly dead Python function: load_global_patient_data

GapSeverity.LOW Layer.SOFTWARE score 0.140

Why: low severity · clean removal is a safe PR

Fix: If genuinely unused, remove the function in auth.py:229; if framework-registered, add a docstring.

auth.py:229

Possibly dead Python function: save_global_patient_data

GapSeverity.LOW Layer.SOFTWARE score 0.140

Why: low severity · clean removal is a safe PR

Fix: If genuinely unused, remove the function in auth.py:237; if framework-registered, add a docstring.

auth.py:237

#10

Possibly dead Python function: list_dossiers_for_patient

GapSeverity.LOW Layer.SOFTWARE score 0.140

Why: low severity · clean removal is a safe PR

Fix: If genuinely unused, remove the function in auth.py:464; if framework-registered, add a docstring.

auth.py:464

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/0f3607ef-68d6-4440-a1d5-43801236916a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0f3607ef-68d6-4440-a1d5-43801236916a/

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.