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
17 of your 72 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 39.74s for a 79.2 MB repo slow.
  • Repobility's analysis ran in 3.5s after the clone landed.

charlesvestal/schwung

https://github.com/charlesvestal/schwung · scanned 2026-06-05 20:40 UTC (4 days, 13 hours ago) · 10 languages

153 raw signals (69 security + 84 graph) 11/13 scanners ran 62nd percentile · C · large (100-500K LoC) System graph score 84 (lower by 16)

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

Complete repo analysis

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

JSON
Combined
80.5
/100
Security checks
77
32 findings
System graph
84
88.9% cov · 40 findings
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 65.0 0.15 9.75
security_score 100.0 0.25 25.00
testing_score 31.0 0.20 6.20
documentation_score 70.0 0.15 10.50
practices_score 75.0 0.15 11.25
code_quality 46.0 0.10 4.60
Overall 1.00 67.3
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
Severity: Critical 0 High 6 Medium 11 Low 33 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 32 System graph 40 Crowd 0 Layer: Quality 31 Cicd 6 Software 6 Security 6 Api 1 Frontend 19 Hardware 3

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 (5 lines) in scripts/generate_font.py:1014
View all commented-out code 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/3e1c4285-0bca-4ba4-9c2b-65cfa56d6ae4/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/3e1c4285-0bca-4ba4-9c2b-65cfa56d6ae4/

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.