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
etcd-io/etcd 1 adequate · 4 strong Go 251,842 lines 52,320 2026-10-25 strong
hashicorp/terraform 1 adequate · 3 strong Go 776,373 lines 49,738 2026-10-25 strong
pinchtab/pinchtab 1 adequate · 4 strong Go 414,881 lines 10,437 2026-11-08 strong
velero-io/velero 2 adequate · 3 strong Go 533,084 lines 10,352 2026-11-08 strong
cli/cli 4 strong Go 329,468 lines 46,408 2026-10-25 strong
reviewdog/reviewdog 1 adequate · 4 strong Go 28,961 lines 9,716 2026-11-07 strong
spf13/cobra 4 strong Go 19,916 lines 44,668 2026-10-25 strong
cadence-workflow/cadence 1 adequate · 4 strong Go 1,094,390 lines 9,511 2026-11-08 strong
crowdsecurity/crowdsec 1 adequate · 4 strong Go 238,531 lines 15,441 2026-11-03 strong
goharbor/harbor 2 adequate · 3 strong Go 430,617 lines 29,629 2026-10-28 strong
gofiber/fiber 2 adequate · 3 strong Go 203,724 lines 40,186 2026-10-25 strong
orchestratorinc/agent-orchestrator 2 adequate · 3 strong Go 1,330,654 lines 14,044 2026-11-03 strong
photoprism/photoprism 1 adequate · 4 strong Go 669,951 lines 40,238 2026-10-25 strong
kyverno/kyverno 2 adequate · 3 strong Go 618,744 lines 8,313 2026-11-08 strong
tailscale/tailscale 2 adequate · 3 strong Go 649,868 lines 36,994 2026-10-25 strong
fabiolb/fabio 1 adequate · 4 strong Go 31,745 lines 7,346 2026-11-08 strong
milvus-io/milvus 2 adequate · 3 strong Go 2,186,085 lines 46,451 2026-10-22 strong
grafana/pyroscope 1 adequate · 4 strong Go 530,836 lines 11,711 2026-11-03 strong
centrifugal/centrifugo 1 adequate · 4 strong Go 125,526 lines 10,946 2026-11-03 strong
istio/istio 2 adequate · 3 strong Go 850,268 lines 38,469 2026-10-23 strong
pingcap/tidb 2 adequate · 3 strong Go 2,035,379 lines 40,670 2026-10-22 strong
goss-org/goss 2 adequate · 3 strong Go 26,999 lines 5,991 2026-11-08 strong
prometheus-operator/prometheus-operator 5 strong Go 235,978 lines 9,994 2026-11-03 strong
cortexproject/cortex 2 adequate · 3 strong Go 417,542 lines 5,877 2026-11-08 strong
inngest/inngest 2 adequate · 3 strong Go 590,332 lines 5,905 2026-11-07 strong
cubefs/cubefs 1 adequate · 4 strong Go 659,437 lines 5,677 2026-11-08 strong
codenotary/immudb 2 adequate · 3 strong Go 270,603 lines 9,049 2026-11-03 strong
fluxcd/flagger 1 adequate · 4 strong Go 110,118 lines 5,421 2026-11-08 strong
dokku/dokku 2 adequate · 3 strong Go 142,420 lines 32,202 2026-10-23 strong
tsuru/tsuru 2 adequate · 3 strong Go 177,936 lines 5,326 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.