Go repositories

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 316 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
glanceapp/glance 4 adequate · 1 strong Go 19,829 lines 37,640 2026-10-23 adequate
restic/restic 4 adequate · 1 strong Go 103,491 lines 36,753 2026-10-23 adequate
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
aquasecurity/trivy 3 adequate · 2 strong Go 355,517 lines 38,620 2026-10-22 adequate
cubefs/cubefs 1 adequate · 4 strong Go 659,437 lines 5,677 2026-11-08 strong
seaweedfs/seaweedfs 4 adequate · 1 strong Go 1,161,579 lines 35,929 2026-10-22 adequate
projectdiscovery/nuclei 4 adequate · 1 strong Go 199,880 lines 32,261 2026-10-23 adequate
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
fission/fission 3 adequate · 2 strong Go 269,456 lines 8,939 2026-11-03 adequate
ory/keto 3 adequate · 2 strong Go 117,225 lines 5,413 2026-11-07 adequate
tsuru/tsuru 2 adequate · 3 strong Go 177,936 lines 5,326 2026-11-08 strong
grafana/mimir 4 adequate · 1 strong Go 1,431,844 lines 5,277 2026-11-07 adequate
navidrome/navidrome 2 adequate · 3 strong Go 322,101 lines 23,847 2026-10-25 strong
getanteon/anteon 2 adequate · 3 strong Go 25,709 lines 8,514 2026-11-03 strong
metallb/metallb 3 adequate · 2 strong Go 166,100 lines 8,393 2026-11-03 adequate
wukongim/wukongim 2 adequate · 3 strong Go 1,940,751 lines 4,986 2026-11-08 strong
cockroachdb/cockroach 2 adequate · 3 strong Go 2,370,315 lines 32,606 2026-10-22 strong
knadh/listmonk 5 adequate Go 85,144 lines 23,587 2026-10-25 adequate
cloudreve/cloudreve 5 adequate Go 163,302 lines 28,873 2026-10-23 adequate
grafana/k6 5 strong Go 275,771 lines 32,010 2026-10-22 strong
usefathom/fathom 4 adequate · 1 strong Go 8,780 lines 8,034 2026-11-03 adequate
kubevela/kubevela 3 adequate · 2 strong Go 547,074 lines 7,920 2026-11-03 adequate
werf/werf 2 adequate · 3 strong Go 202,006 lines 4,738 2026-11-08 strong
concourse/concourse 3 adequate · 2 strong Go 481,544 lines 7,941 2026-11-03 adequate

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.