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

Scan timing: clone 19.65s · analysis 31.07s · 23.7 MB · GitHub API rate-limit (preflight)

ginoleeswan/hero

https://github.com/ginoleeswan/hero · scanned 2026-06-05 22:33 UTC (4 days, 8 hours ago) · 10 languages

189 raw signals (93 security + 96 graph) 34th percentile · Typescript · medium (20-100K LoC) System graph score 73 (lower by 8)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 8 hours ago · v2 · 104 actionable findings from 2 signal sources. 37 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 59.4 0.25 14.85
testing_score 53.0 0.20 10.60
documentation_score 60.7 0.15 9.11
practices_score 76.0 0.15 11.40
code_quality 65.3 0.10 6.53
Overall 1.00 65.2
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Commented-out code 2 findings
What it is: Lines of source that were intentionally disabled but never deleted.
Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.
How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.
Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.
2 matching findings on this repo
  • info Commented-code block (9 lines) in app/(tabs)/explore.web.tsx:34
  • info Commented-code block (5 lines) in src/lib/api.ts:214
View all commented-out code findings →
Config drift 4 findings
What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.
Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.
How AI causes it: AI writes new config from memory rather than reading the existing source.
Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.
4 matching findings on this repo
  • low File has no detected symbols: metro.config.js
  • low File has no detected symbols: babel.config.js
  • low File has no detected symbols: app.config.ts
  • low File has no detected symbols: react-native.config.js
View all config drift findings →
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/d65872d5-1283-4b43-95c8-2d8d80982c15/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d65872d5-1283-4b43-95c8-2d8d80982c15/

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.