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

Scan timing: clone 3.73s · analysis 0.98s · 8.5 MB · GitHub API rate-limit (preflight)

TurboPack/SynEdit

https://github.com/TurboPack/SynEdit · scanned 2026-06-05 23:43 UTC (4 days, 5 hours ago) · 10 languages

179 raw signals (149 security + 30 graph) 40th percentile · Cpp · tiny (<2K LoC) System graph score 93 (lower by 46)

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

Complete repo analysis

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

JSON
Combined
72.6
/100
Security checks
52
4 findings
System graph
93
66.7% cov · 15 findings
Critical
1
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 55.0 0.15 8.25
security_score 55.0 0.25 13.75
testing_score 0.0 0.20 0.00
documentation_score 75.0 0.15 11.25
practices_score 40.0 0.15 6.00
code_quality 76.0 0.10 7.60
Overall 1.00 46.9
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 1 High 1 Medium 3 Low 9 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 4 System graph 15 Crowd 0 Layer: Quality 5 Security 2 Software 9 Api 1 Frontend 1 Cicd 1

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 1 finding
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/`.
1 matching finding on this repo
  • info Commented-code block (6 lines) in Demos/Folding/demo.py:160
View all commented-out code findings →
Config drift 1 finding
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.
1 matching finding on this repo
  • medium No CI/CD configuration found
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/d123de24-567a-4f21-a632-3344ebb98d76/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/d123de24-567a-4f21-a632-3344ebb98d76/

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.