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.

Scan timing: clone 1.49s · analysis 1.92s · 1.5 MB · GitHub API rate-limit (preflight)

mateiszakwork-cloud/hiro

https://github.com/mateiszakwork-cloud/hiro.git · scanned 2026-05-25 15:37 UTC (1 week, 3 days ago) · 10 languages

193 findings (39 legacy + 154 scanner) 20th percentile · Typescript · small (2-20K LoC) Scanner says 77 (lower by 20)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 3 days ago · v2 · 116 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 100.0 0.15 15.00
security_score 62.2 0.25 15.55
testing_score 30.0 0.20 6.00
documentation_score 38.7 0.15 5.81
practices_score 44.0 0.15 6.60
code_quality 77.4 0.10 7.74
Overall 1.00 56.7
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
Possible secret in src/pages/Login.tsx
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in src/pages/Login.tsx:52; move to env var / secrets manager.
src/pages/Login.tsx:52
#2
Possible secret in src/pages/Register.tsx
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in src/pages/Register.tsx:55; move to env var / secrets manager.
src/pages/Register.tsx:55
#3
Possible secret in src/pages/Register.tsx
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in src/pages/Register.tsx:56; move to env var / secrets manager.
src/pages/Register.tsx:56
#4
Possible secret in src/pages/Register.tsx
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in src/pages/Register.tsx:57; move to env var / secrets manager.
src/pages/Register.tsx:57
#5
Possible secret in src/pages/Register.tsx
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in src/pages/Register.tsx:58; move to env var / secrets manager.
src/pages/Register.tsx:58
#6
.env file present in repo: .env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#7
`dangerouslySetInnerHTML` used in a React component — src/components/ui/chart.tsx:70
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#8
No auth library detected
GapSeverity.MEDIUM Layer.SECURITY score 0.338
Why: medium severity
#9
Insecure pattern 'dangerous_innerhtml' in src/components/ui/chart.tsx:70
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
src/components/ui/chart.tsx:70
#10
ORM models found but no DB engine detected
GapSeverity.MEDIUM Layer.DATA score 0.225
Why: medium severity

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/ecbe478e-97ee-4d3d-90ff-98c1aca2692b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ecbe478e-97ee-4d3d-90ff-98c1aca2692b/

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.