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

Scan timing: clone 27.44s · analysis 17.79s · 28.9 MB · GitHub API rate-limit (preflight)

moby/moby

https://github.com/moby/moby · scanned 2026-06-05 08:19 UTC (5 days, 20 hours ago) · 10 languages

389 raw signals (185 security + 204 graph) 11/13 scanners ran 88th percentile · Go · large (100-500K LoC) System graph score 75 (higher by 15)

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

Complete repo analysis

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

JSON
Combined
83.2
/100
Security checks
92
48 findings
System graph
75
100.0% cov · 90 findings
Critical
3
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 85.0 0.15 12.75
practices_score 100.0 0.15 15.00
code_quality 80.0 0.10 8.00
Overall 1.00 89.5
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 3 High 12 Medium 59 Low 42 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 48 System graph 90 Crowd 0 Layer: Cicd 18 Quality 40 Security 32 Software 7 Api 1 Network 4 Hardware 35 Frontend 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.

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
  • high [SEC088] Go: TLS InsecureSkipVerify=true: tls.Config{InsecureSkipVerify:true} d… pkg/plugins/plugins.go:117
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/fb0932ce-efa0-403b-a495-6413b4e72fc7/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/fb0932ce-efa0-403b-a495-6413b4e72fc7/

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.