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
grpc-ecosystem/go-grpc-middleware 4 strong Go 14,363 lines 6,759 2026-10-23 strong
kptdev/kpt 1 adequate · 4 strong Go 125,440 lines 1,900 2026-11-03 strong
unkeyed/unkey 2 adequate · 3 strong Go 743,381 lines 5,455 2026-10-25 strong
cloudquery/cloudquery 1 adequate · 4 strong Go 163,747 lines 6,544 2026-10-23 strong
codeberg.org/readeck/readeck 2 adequate · 3 strong Go 179,340 lines 1,191 2026-11-07 strong
openchoreo/openchoreo 3 adequate · 2 strong Go 717,077 lines 1,759 2026-11-03 adequate
tracewayapp/traceway 3 adequate · 2 strong Go 344,922 lines 1,752 2026-11-03 adequate
netlify/gocommerce 5 strong Go 12,329 lines 1,616 2026-11-03 adequate
kgateway-dev/kgateway 2 adequate · 3 strong Go 467,140 lines 5,723 2026-10-23 strong
peerdb-io/peerdb 2 adequate · 3 strong Go 197,242 lines 3,310 2026-10-28 strong
devtron-labs/devtron 4 adequate · 1 strong Go 685,387 lines 5,621 2026-10-23 adequate
treeverse/lakefs 3 adequate · 2 strong Go 420,320 lines 5,578 2026-10-23 adequate
getprobo/probo 4 adequate · 1 strong Go 1,310,001 lines 1,494 2026-11-03 adequate
versity/versitygw 3 adequate · 2 strong Go 294,698 lines 3,076 2026-10-28 adequate
edgenesis/shifu 2 adequate · 3 strong Go 41,636 lines 1,436 2026-11-03 strong
pomerium/pomerium 2 adequate · 3 strong Go 329,649 lines 5,064 2026-10-23 strong
clidey/whodb 2 adequate · 3 strong Go 464,188 lines 5,041 2026-10-23 strong
casosorg/casos 3 adequate · 1 strong Go 97,031 lines 1,396 2026-11-03 adequate
flipt-io/flipt 3 adequate · 2 strong Go 142,451 lines 4,926 2026-10-23 adequate
liftbridge-io/liftbridge 3 adequate · 2 strong Go 77,374 lines 2,805 2026-10-28 adequate
openziti/zrok 3 adequate · 2 strong Go 303,988 lines 4,783 2026-10-23 adequate
jenkins-x/jx 2 adequate · 3 strong Go 7,014 lines 4,691 2026-10-23 strong
ergo-services/ergo 2 adequate · 1 strong Go 132,016 lines 4,682 2026-10-23 adequate
cerbos/cerbos 3 adequate · 2 strong Go 345,006 lines 4,631 2026-10-23 adequate
enterpilot/gomodel 2 adequate · 3 strong Go 550,673 lines 1,298 2026-11-03 strong
elastic/apm-server 5 strong Go 114,220 lines 1,271 2026-11-03 strong
rudderlabs/rudder-server 3 adequate · 2 strong Go 406,513 lines 4,505 2026-10-23 adequate
dagucloud/dagu 4 adequate · 1 strong Go 995,418 lines 4,428 2026-10-23 adequate
smallstep/cli 3 adequate · 2 strong Go 46,801 lines 4,355 2026-10-23 adequate
deepflowio/deepflow 3 adequate · 2 strong Go 547,342 lines 4,305 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.