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
coder/coder 3 adequate · 2 strong Go 1,735,038 lines 17,287 2026-10-25 adequate
hashicorp/nomad 2 adequate · 3 strong Go 855,891 lines 16,986 2026-10-25 strong
gofr-dev/gofr 1 adequate · 4 strong Go 273,089 lines 20,841 2026-10-23 strong
easegress-io/easegress 2 adequate · 3 strong Go 137,875 lines 5,873 2026-11-03 strong
bluenviron/mediamtx 2 adequate · 3 strong Go 111,343 lines 20,495 2026-10-23 strong
go-task/task 4 strong Go 63,386 lines 16,196 2026-10-25 strong
bettercap/bettercap 4 adequate · 1 strong Go 112,414 lines 20,181 2026-10-23 adequate
apache/casbin 1 adequate · 3 strong Go 80,755 lines 20,467 2026-10-23 strong
gotify/server 2 adequate · 3 strong Go 29,734 lines 15,991 2026-10-25 strong
superstreamlabs/memphis 1 adequate · 4 strong Go 356,809 lines 3,444 2026-11-08 strong
mikefarah/yq 1 adequate · 3 strong Go 66,439 lines 16,017 2026-10-25 strong
linkerd/linkerd2 2 adequate · 3 strong Go 285,803 lines 11,521 2026-10-28 strong
vitessio/vitess 3 adequate · 2 strong Go 1,681,787 lines 21,390 2026-10-22 adequate
zitadel/zitadel 4 adequate · 1 strong Go 1,141,569 lines 15,115 2026-10-25 adequate
gravitational/teleport 3 adequate · 2 strong Go 2,308,336 lines 21,071 2026-10-22 adequate
envoyproxy/gateway 1 adequate · 4 strong Go 1,439,869 lines 3,126 2026-11-08 strong
taubyte/tau 3 adequate · 1 strong Go 327,203 lines 5,183 2026-11-03 adequate
influxdata/telegraf 2 adequate · 3 strong Go 731,313 lines 17,880 2026-10-23 strong
nezhahq/nezha 3 adequate · 2 strong Go 120,080 lines 10,377 2026-10-28 adequate
victoriametrics/victoriametrics 1 adequate · 4 strong Go 509,859 lines 17,898 2026-10-23 strong
kubesphere/kubesphere 4 adequate · 1 strong Go 224,690 lines 17,066 2026-10-23 adequate
wtfutil/wtf 4 strong Go 47,870 lines 17,129 2026-10-23 strong
seldonio/seldon-core 3 adequate · 2 strong Go 322,460 lines 4,784 2026-11-03 adequate
pion/webrtc 4 strong Go 81,527 lines 16,851 2026-10-23 strong
argoproj/argo-workflows 4 adequate · 1 strong Go 415,344 lines 17,050 2026-10-23 adequate
prest/prest 1 adequate · 4 strong Go 73,876 lines 4,630 2026-11-03 strong
erda-project/erda 4 adequate · 1 strong Go 1,189,849 lines 2,757 2026-11-08 adequate
bearer/bearer 3 adequate · 2 strong Go 167,299 lines 2,779 2026-11-07 adequate
mosn/mosn 1 adequate · 4 strong Go 266,382 lines 4,507 2026-11-03 strong
ory/hydra 3 adequate · 1 strong Go 303,323 lines 17,624 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.