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
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
gokcehan/lf 2 adequate · 2 strong Go 21,012 lines 9,522 2026-11-08 adequate
cadence-workflow/cadence 1 adequate · 4 strong Go 1,094,390 lines 9,511 2026-11-08 strong
certimate-go/certimate 4 adequate · 1 strong Go 193,084 lines 9,422 2026-11-08 adequate
owasp-amass/amass 5 adequate Go 39,830 lines 15,457 2026-11-03 adequate
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
schollz/croc 3 adequate · 2 strong Go 83,381 lines 40,474 2026-10-25 adequate
safing/portmaster 4 adequate · 1 strong Go 208,941 lines 14,019 2026-11-03 adequate
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
dnscrypt/dnscrypt-proxy 4 adequate · 1 strong Go 24,544 lines 13,808 2026-11-03 adequate
kyverno/kyverno 2 adequate · 3 strong Go 618,744 lines 8,313 2026-11-08 strong
rook/rook 3 adequate · 2 strong Go 304,456 lines 13,700 2026-11-03 adequate
yaoapp/yao 3 adequate · 2 strong Go 573,872 lines 8,183 2026-11-07 adequate
gogs/gogs 3 adequate · 2 strong Go 247,120 lines 47,897 2026-10-23 adequate
tailscale/tailscale 2 adequate · 3 strong Go 649,868 lines 36,994 2026-10-25 strong
hashicorp/vault 3 adequate · 2 strong Go 1,105,396 lines 36,317 2026-10-25 adequate
bishopfox/sliver 4 adequate · 1 strong Go 386,022 lines 12,222 2026-11-03 adequate
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
flexprice/flexprice 3 adequate · 2 strong Go 931,077 lines 6,871 2026-11-08 adequate
centrifugal/centrifugo 1 adequate · 4 strong Go 125,526 lines 10,946 2026-11-03 strong
harness/harness 4 adequate · 1 strong Go 661,685 lines 38,682 2026-10-23 adequate
istio/istio 2 adequate · 3 strong Go 850,268 lines 38,469 2026-10-23 strong
hashicorp/consul 3 adequate · 2 strong Go 900,713 lines 30,088 2026-10-25 adequate
glanceapp/glance 4 adequate · 1 strong Go 19,829 lines 37,640 2026-10-23 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.