Go repositories reading strong
Every public repository surveyed, browsable and searchable. Including the unflattering ones — a tool that only published good results would be a badge vending machine, not a diligence instrument.
| Repository | Language | Size | Stars | Read | Band |
|---|---|---|---|---|---|
| navidrome/navidrome 2 adequate · 3 strong | Go | 322,101 lines | 23,847 | 2026-10-25 | |
| getanteon/anteon 2 adequate · 3 strong | Go | 25,709 lines | 8,514 | 2026-11-03 | |
| wukongim/wukongim 2 adequate · 3 strong | Go | 1,940,751 lines | 4,986 | 2026-11-08 | |
| cockroachdb/cockroach 2 adequate · 3 strong | Go | 2,370,315 lines | 32,606 | 2026-10-22 | |
| grafana/k6 5 strong | Go | 275,771 lines | 32,010 | 2026-10-22 | |
| werf/werf 2 adequate · 3 strong | Go | 202,006 lines | 4,738 | 2026-11-08 | |
| open-telemetry/opentelemetry-collector 4 strong | Go | 330,563 lines | 7,728 | 2026-11-03 | |
| gitleaks/gitleaks 2 adequate · 3 strong | Go | 27,496 lines | 30,233 | 2026-10-22 | |
| kubeedge/kubeedge 2 adequate · 3 strong | Go | 317,215 lines | 7,621 | 2026-11-03 | |
| evcc-io/evcc 2 adequate · 3 strong | Go | 445,388 lines | 7,506 | 2026-11-03 | |
| nats-io/nats-server 2 adequate · 3 strong | Go | 475,473 lines | 20,797 | 2026-10-25 | |
| gopasspw/gopass 2 adequate · 3 strong | Go | 109,465 lines | 7,307 | 2026-11-03 | |
| trufflesecurity/trufflehog 2 adequate · 3 strong | Go | 525,605 lines | 28,647 | 2026-10-22 | |
| uber-go/zap 4 strong | Go | 26,094 lines | 24,677 | 2026-10-23 | |
| komari-monitor/komari 2 adequate · 3 strong | Go | 83,108 lines | 6,882 | 2026-11-03 | |
| thanos-io/thanos 1 adequate · 4 strong | Go | 287,337 lines | 14,258 | 2026-10-28 | |
| opencost/opencost 2 adequate · 3 strong | Go | 262,294 lines | 6,801 | 2026-11-03 | |
| jaegertracing/jaeger 2 adequate · 3 strong | Go | 293,274 lines | 23,332 | 2026-10-23 | |
| ccfos/nightingale 2 adequate · 3 strong | Go | 605,725 lines | 13,401 | 2026-10-28 | |
| kubernetes/kube-state-metrics 1 adequate · 4 strong | Go | 50,382 lines | 6,234 | 2026-11-03 | |
| kiali/kiali 2 adequate · 3 strong | Go | 505,142 lines | 3,647 | 2026-11-08 | |
| montferret/ferret 1 adequate · 3 strong | Go | 295,995 lines | 6,021 | 2026-11-03 | |
| hashicorp/nomad 2 adequate · 3 strong | Go | 855,891 lines | 16,986 | 2026-10-25 | |
| gofr-dev/gofr 1 adequate · 4 strong | Go | 273,089 lines | 20,841 | 2026-10-23 | |
| easegress-io/easegress 2 adequate · 3 strong | Go | 137,875 lines | 5,873 | 2026-11-03 | |
| bluenviron/mediamtx 2 adequate · 3 strong | Go | 111,343 lines | 20,495 | 2026-10-23 | |
| go-task/task 4 strong | Go | 63,386 lines | 16,196 | 2026-10-25 | |
| apache/casbin 1 adequate · 3 strong | Go | 80,755 lines | 20,467 | 2026-10-23 | |
| gotify/server 2 adequate · 3 strong | Go | 29,734 lines | 15,991 | 2026-10-25 | |
| superstreamlabs/memphis 1 adequate · 4 strong | Go | 356,809 lines | 3,444 | 2026-11-08 |
What a band means. A band sums up one reading of one commit: strong, adequate or significant findings. Here it counts the project's code, process, product, security and operations. A report reads more than that, so its band can differ from its row.
How listing works. Every public repository surveyed is listed — assessing public work is commentary on public work, and a library that hid the small ones would be quietly editorialising about which code counts. Private repositories are never listed. Anyone who proves control of a repo can attach a response to a finding, request a re-run, or delist it. Delisting is immediate and no-questions. An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev. There is no org-level score. Repositories are listed one by one, and sorting by band orders them by their own readings. Takedown: one email, 48 hours.