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
pulumi/pulumi 2 adequate · 2 strong Go 2,142,280 lines 25,806 2026-10-22 adequate
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
kserve/kserve 5 adequate Go 918,094 lines 6,184 2026-11-03 adequate
coder/coder 3 adequate · 2 strong Go 1,735,038 lines 17,287 2026-10-25 adequate
bettercap/bettercap 4 adequate · 1 strong Go 112,414 lines 20,181 2026-10-23 adequate
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
taubyte/tau 3 adequate · 1 strong Go 327,203 lines 5,183 2026-11-03 adequate
nezhahq/nezha 3 adequate · 2 strong Go 120,080 lines 10,377 2026-10-28 adequate
kubesphere/kubesphere 4 adequate · 1 strong Go 224,690 lines 17,066 2026-10-23 adequate
seldonio/seldon-core 3 adequate · 2 strong Go 322,460 lines 4,784 2026-11-03 adequate
argoproj/argo-workflows 4 adequate · 1 strong Go 415,344 lines 17,050 2026-10-23 adequate
openimsdk/open-im-server 4 adequate · 1 strong Go 80,175 lines 16,721 2026-10-23 adequate
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
ory/hydra 3 adequate · 1 strong Go 303,323 lines 17,624 2026-10-22 adequate
esm-dev/esm.sh 3 adequate · 2 strong Go 41,171 lines 4,187 2026-11-03 adequate
bytebase/bytebase 3 adequate · 2 strong Go 1,396,358 lines 14,623 2026-10-23 adequate
casdoor/casdoor 4 adequate · 1 strong Go 292,198 lines 14,643 2026-10-23 adequate
juicedata/juicefs 3 adequate · 2 strong Go 229,965 lines 14,567 2026-10-23 adequate
kumahq/kuma 3 adequate · 2 strong Go 790,571 lines 4,015 2026-11-03 adequate
hashicorp/packer 2 adequate · 2 strong Go 95,277 lines 15,812 2026-10-22 adequate
1backend/1backend 3 adequate · 2 strong Go 284,568 lines 2,355 2026-11-07 adequate
gogf/gf 2 adequate · 2 strong Go 609,547 lines 13,287 2026-10-23 adequate
akuity/kargo 5 adequate Go 563,773 lines 3,754 2026-11-03 adequate
getlago/lago 5 adequate Go 16,657 lines 10,627 2026-10-25 adequate
juggleim/im-server 3 adequate · 2 strong Go 96,676 lines 3,538 2026-11-03 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.