Go repositories reading adequate

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 157 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
gogs/gogs 3 adequate · 2 strong Go 247,120 lines 47,897 2026-10-23 adequate
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
flexprice/flexprice 3 adequate · 2 strong Go 931,077 lines 6,871 2026-11-08 adequate
harness/harness 4 adequate · 1 strong Go 661,685 lines 38,682 2026-10-23 adequate
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
restic/restic 4 adequate · 1 strong Go 103,491 lines 36,753 2026-10-23 adequate
anchore/syft 3 adequate · 1 strong Go 580,029 lines 9,819 2026-11-03 adequate
aquasecurity/trivy 3 adequate · 2 strong Go 355,517 lines 38,620 2026-10-22 adequate
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
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
grafana/mimir 4 adequate · 1 strong Go 1,431,844 lines 5,277 2026-11-07 adequate
metallb/metallb 3 adequate · 2 strong Go 166,100 lines 8,393 2026-11-03 adequate
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
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
concourse/concourse 3 adequate · 2 strong Go 481,544 lines 7,941 2026-11-03 adequate
flyteorg/flyte 4 adequate · 1 strong Go 611,810 lines 7,845 2026-11-03 adequate
opentofu/opentofu 4 adequate · 1 strong Go 656,372 lines 30,575 2026-10-22 adequate
projectcalico/calico 4 adequate · 1 strong Go 1,178,755 lines 7,411 2026-11-03 adequate
openfaas/faas 3 adequate · 2 strong Go 13,589 lines 26,253 2026-10-23 adequate
grafana/loki 3 adequate · 2 strong Go 1,196,883 lines 29,048 2026-10-22 adequate
nsqio/nsq 3 adequate · 2 strong Go 26,831 lines 25,771 2026-10-23 adequate
cilium/cilium 3 adequate · 2 strong Go 1,479,547 lines 25,711 2026-10-23 adequate
bruin-data/ingestr 2 adequate · 3 strong Go 480,986 lines 4,031 2026-11-07 adequate
rancher/rancher 3 adequate · 2 strong Go 735,297 lines 25,997 2026-10-22 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.