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
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
flyteorg/flyte 4 adequate · 1 strong Go 611,810 lines 7,845 2026-11-03 adequate
open-telemetry/opentelemetry-collector 4 strong Go 330,563 lines 7,728 2026-11-03 strong
opentofu/opentofu 4 adequate · 1 strong Go 656,372 lines 30,575 2026-10-22 adequate
gitleaks/gitleaks 2 adequate · 3 strong Go 27,496 lines 30,233 2026-10-22 strong
kubeedge/kubeedge 2 adequate · 3 strong Go 317,215 lines 7,621 2026-11-03 strong
evcc-io/evcc 2 adequate · 3 strong Go 445,388 lines 7,506 2026-11-03 strong
projectcalico/calico 4 adequate · 1 strong Go 1,178,755 lines 7,411 2026-11-03 adequate
nats-io/nats-server 2 adequate · 3 strong Go 475,473 lines 20,797 2026-10-25 strong
openfaas/faas 3 adequate · 2 strong Go 13,589 lines 26,253 2026-10-23 adequate
gopasspw/gopass 2 adequate · 3 strong Go 109,465 lines 7,307 2026-11-03 strong
trufflesecurity/trufflehog 2 adequate · 3 strong Go 525,605 lines 28,647 2026-10-22 strong
nsqio/nsq 3 adequate · 2 strong Go 26,831 lines 25,771 2026-10-23 adequate
uber-go/zap 4 strong Go 26,094 lines 24,677 2026-10-23 strong
thanos-io/thanos 1 adequate · 4 strong Go 287,337 lines 14,258 2026-10-28 strong
opencost/opencost 2 adequate · 3 strong Go 262,294 lines 6,801 2026-11-03 strong
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
pulumi/pulumi 2 adequate · 2 strong Go 2,142,280 lines 25,806 2026-10-22 adequate
ccfos/nightingale 2 adequate · 3 strong Go 605,725 lines 13,401 2026-10-28 strong
chaitin/safeline 5 adequate Go 26,650 lines 22,918 2026-10-23 adequate
goodrain/rainbond 3 adequate · 2 strong Go 288,206 lines 6,293 2026-11-03 adequate
bfenetworks/bfe 3 adequate · 2 strong Go 291,829 lines 6,272 2026-11-03 adequate
kubernetes/kube-state-metrics 1 adequate · 4 strong Go 50,382 lines 6,234 2026-11-03 strong
kserve/kserve 5 adequate Go 918,094 lines 6,184 2026-11-03 adequate
kiali/kiali 2 adequate · 3 strong Go 505,142 lines 3,647 2026-11-08 strong
montferret/ferret 1 adequate · 3 strong Go 295,995 lines 6,021 2026-11-03 strong
coder/coder 3 adequate · 2 strong Go 1,735,038 lines 17,287 2026-10-25 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.