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

u-root/u-root

https://github.com/u-root/u-root · scanned 2026-06-05 17:20 UTC (4 days, 22 hours ago) · 10 languages

219 raw signals (67 security + 152 graph) 11/13 scanners ran 94th percentile · Go · medium (20-100K LoC) System graph score 61 (higher by 20)

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

Complete repo analysis

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

JSON
Combined
75.1
/100
Security checks
89
21 findings
System graph
61
88.9% cov · 50 findings
Critical
2
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 100.0 0.25 25.00
testing_score 80.0 0.20 16.00
documentation_score 61.0 0.15 9.15
practices_score 72.0 0.15 10.80
code_quality 80.0 0.10 8.00
Overall 1.00 81.7
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 2 High 5 Medium 22 Low 27 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 21 System graph 50 Crowd 0 Layer: Quality 19 Security 11 Software 15 Cicd 5 Api 1 Frontend 2 Network 4 Hardware 14

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in cmds/exp/ssh/utils_plan9.go
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 cmds/exp/ssh/utils_plan9.go:54; move to env var / secrets manager.
cmds/exp/ssh/utils_plan9.go:54
#2
Insecure pattern 'eval_used' in pkg/forth/forth.go:207
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
pkg/forth/forth.go:207
#3
GitHub Action tracks a moving branch
GapSeverity.HIGH Layer.CICD score 0.375
Why: high severity
.github/workflows/cifuzz.yml:9
#4
GitHub Action tracks a moving branch
GapSeverity.HIGH Layer.CICD score 0.375
Why: high severity
.github/workflows/cifuzz.yml:15
#5
Privileged port 256 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in .vmtest.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
.vmtest.yaml
#6
Privileged port 550 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in .vmtest.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
.vmtest.yaml
#7
No auth library detected
GapSeverity.MEDIUM Layer.SECURITY score 0.338
Why: medium severity
#8
Insecure pattern 'weak_hash' in pkg/tss/tss.go:80
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
pkg/tss/tss.go:80
#9
Insecure pattern 'weak_hash' in pkg/boot/fit/vfit.go:35
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
pkg/boot/fit/vfit.go:35
#10
Insecure pattern 'weak_hash' in pkg/netcat/const.go:26
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
pkg/netcat/const.go:26

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/2fcec4ea-77dc-4b3f-ba33-9dc1ecd00739/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/2fcec4ea-77dc-4b3f-ba33-9dc1ecd00739/

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.