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

Scan timing: clone 6.97s · analysis 16.7s · 10.2 MB · GitHub API rate-limit (preflight)

spkenv/spk

https://github.com/spkenv/spk · scanned 2026-06-05 23:52 UTC (4 days, 4 hours ago) · 10 languages

222 raw signals (130 security + 92 graph) 8th percentile · Rust · large (100-500K LoC) System graph score 84 (lower by 31)

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

Complete repo analysis

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

JSON
Combined
68.4
/100
Security checks
53
54 findings
System graph
84
88.9% cov · 28 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 60.0 0.15 9.00
security_score 47.1 0.25 11.78
testing_score 12.0 0.20 2.40
documentation_score 89.0 0.15 13.35
practices_score 75.0 0.15 11.25
code_quality 49.6 0.10 4.96
Overall 1.00 52.7
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 1 High 24 Medium 7 Low 29 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 54 System graph 28 Crowd 0 Layer: Cicd 5 Quality 36 Security 5 Software 30 Frontend 3 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 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 (11 lines) in website/static/js/jquery.sticky.js:1
  • info Commented-code block (5 lines) in examples/cmake/package.py:29
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/994cdc6d-c00a-437d-97ae-0a0df1f7ac9e/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/994cdc6d-c00a-437d-97ae-0a0df1f7ac9e/

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.