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.

All bands Strong Adequate 158 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
mikefarah/yq 1 adequate · 3 strong Go 66,439 lines 16,017 2026-10-25 strong
linkerd/linkerd2 2 adequate · 3 strong Go 285,803 lines 11,521 2026-10-28 strong
envoyproxy/gateway 1 adequate · 4 strong Go 1,439,869 lines 3,126 2026-11-08 strong
influxdata/telegraf 2 adequate · 3 strong Go 731,313 lines 17,880 2026-10-23 strong
victoriametrics/victoriametrics 1 adequate · 4 strong Go 509,859 lines 17,898 2026-10-23 strong
wtfutil/wtf 4 strong Go 47,870 lines 17,129 2026-10-23 strong
pion/webrtc 4 strong Go 81,527 lines 16,851 2026-10-23 strong
prest/prest 1 adequate · 4 strong Go 73,876 lines 4,630 2026-11-03 strong
mosn/mosn 1 adequate · 4 strong Go 266,382 lines 4,507 2026-11-03 strong
crunchydata/postgres-operator 2 adequate · 3 strong Go 124,157 lines 4,456 2026-11-03 strong
openflagr/flagr 2 adequate · 3 strong Go 70,879 lines 2,611 2026-11-08 strong
altinity/clickhouse-operator 2 adequate · 3 strong Go 533,997 lines 2,578 2026-11-08 strong
oauth2-proxy/oauth2-proxy 2 adequate · 3 strong Go 105,439 lines 15,241 2026-10-23 strong
wal-g/wal-g 2 adequate · 3 strong Go 161,733 lines 4,326 2026-11-03 strong
kopia/kopia 1 adequate · 3 strong Go 173,900 lines 14,410 2026-10-23 strong
dnscontrol/dnscontrol 1 adequate · 3 strong Go 271,662 lines 3,993 2026-11-03 strong
tinode/chat 2 adequate · 3 strong Go 79,424 lines 13,530 2026-10-23 strong
ory/oathkeeper 2 adequate · 3 strong Go 90,646 lines 3,608 2026-11-03 strong
argoproj/argo-rollouts 2 adequate · 3 strong Go 270,335 lines 3,616 2026-11-03 strong
encoredev/encore 2 adequate · 3 strong Go 346,649 lines 12,523 2026-10-23 strong
owncast/owncast 1 adequate · 4 strong Go 192,134 lines 11,624 2026-10-23 strong
storj/storj 2 adequate · 3 strong Go 834,667 lines 3,284 2026-11-03 strong
vouch/vouch-proxy 1 adequate · 4 strong Go 9,985 lines 3,281 2026-11-03 strong
dtm-labs/dtm 2 adequate · 3 strong Go 21,491 lines 10,923 2026-10-23 strong
crossplane/crossplane 1 adequate · 4 strong Go 177,826 lines 12,189 2026-10-22 strong
kedacore/keda 1 adequate · 4 strong Go 217,273 lines 10,657 2026-10-23 strong
kube-vip/kube-vip 2 adequate · 3 strong Go 60,601 lines 2,996 2026-11-03 strong
root-gg/plik 2 adequate · 3 strong Go 92,728 lines 1,839 2026-11-07 strong
fwdcloudsec/granted 1 adequate · 3 strong Go 16,642 lines 1,810 2026-11-07 strong
lf-edge/ekuiper 2 adequate · 3 strong Go 305,770 lines 1,747 2026-11-08 strong

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.