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.
87 of your 162 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 10.78s · analysis 7.72s · 29.6 MB · GitHub API rate-limit (preflight)

leon-ai/leon

https://github.com/leon-ai/leon · scanned 2026-06-05 18:35 UTC (4 days, 18 hours ago) · 10 languages

495 raw signals (155 security + 340 graph) 11/13 scanners ran 48th percentile · Typescript · large (100-500K LoC) System graph score 80 (lower by 5)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 18 hours ago · v2 · 201 actionable findings from 2 signal sources. 124 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 100.0 0.25 25.00
testing_score 35.0 0.20 7.00
documentation_score 75.0 0.15 11.25
practices_score 77.0 0.15 11.55
code_quality 70.0 0.10 7.00
Overall 1.00 74.5
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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

#1
Insecure pattern 'eval_used' in tcp_server/src/lib/tts/api.py:70
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
tcp_server/src/lib/tts/api.py:70
#2
Insecure pattern 'exec_used' in server/src/declarations.d.ts:18
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
server/src/declarations.d.ts:18
#3
Dangling fetch: GET /${this.gitBranch}/package.json (server/src/updater.ts:21)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#4
Dangling fetch: POST /on-post-install (server/src/telemetry.ts:53)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#5
Dangling fetch: POST /on-start (server/src/telemetry.ts:104)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#6
Dangling fetch: POST /on-start (server/src/telemetry.ts:118)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#7
Dangling fetch: POST /on-utterance (server/src/telemetry.ts:156)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#8
Dangling fetch: POST /on-utterance (server/src/telemetry.ts:174)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#9
Dangling fetch: POST /on-error (server/src/telemetry.ts:199)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#10
Dangling fetch: POST /on-event (server/src/telemetry.ts:245)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.

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/672a583a-861d-47a6-880c-08e510bfe10f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/672a583a-861d-47a6-880c-08e510bfe10f/

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.