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

Scan timing: clone 2.27s · analysis 2.72s · 2.5 MB · GitHub API rate-limit (preflight)

avelino/awesome-go

https://github.com/avelino/awesome-go · scanned 2026-06-05 04:37 UTC (9 hours, 23 minutes ago) · 10 languages

74 findings (64 legacy + 10 scanner) 14th percentile · Go · small (2-20K LoC) Scanner says 96 (lower by 21)

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

Complete repo analysis

Last scanned 9 hours, 23 minutes ago · v2 · 69 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
86.1
/100
Repobility
77
64 legacy
9-layer
96
55.6% cov · 5 gaps
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 100.0 0.15 15.00
security_score 55.0 0.25 13.75
testing_score 80.0 0.20 16.00
documentation_score 82.0 0.15 12.30
practices_score 72.0 0.15 10.80
code_quality 69.4 0.10 6.94
Overall 1.00 74.8
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 64 Medium 1 Low 2 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 64 9-layer 5 Crowd 0 Layer: Quality 1 Software 63 Api 1 Frontend 1 Cicd 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.

Fragile runtime 1 finding
What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.
Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.
How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.
Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).
1 matching finding on this repo
  • low Duplicated implementation block across source files .github/scripts/check-quality/main.go:188
View all fragile runtime 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/8a9786a9-f820-4353-a30d-bf4f5c088a14/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/8a9786a9-f820-4353-a30d-bf4f5c088a14/

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.