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
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
crunchydata/postgres-operator 2 adequate · 3 strong Go 124,157 lines 4,456 2026-11-03 strong
openflagr/flagr 2 adequate · 3 strong Go 70,879 lines 2,611 2026-11-08 strong
altinity/clickhouse-operator 2 adequate · 3 strong Go 533,997 lines 2,578 2026-11-08 strong
oauth2-proxy/oauth2-proxy 2 adequate · 3 strong Go 105,439 lines 15,241 2026-10-23 strong
wal-g/wal-g 2 adequate · 3 strong Go 161,733 lines 4,326 2026-11-03 strong
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
infisical/agent-vault 3 adequate · 2 strong Go 84,822 lines 2,414 2026-11-08 adequate
kopia/kopia 1 adequate · 3 strong Go 173,900 lines 14,410 2026-10-23 strong
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
dnscontrol/dnscontrol 1 adequate · 3 strong Go 271,662 lines 3,993 2026-11-03 strong
1backend/1backend 3 adequate · 2 strong Go 284,568 lines 2,355 2026-11-07 adequate
tinode/chat 2 adequate · 3 strong Go 79,424 lines 13,530 2026-10-23 strong
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
ory/oathkeeper 2 adequate · 3 strong Go 90,646 lines 3,608 2026-11-03 strong
argoproj/argo-rollouts 2 adequate · 3 strong Go 270,335 lines 3,616 2026-11-03 strong
juggleim/im-server 3 adequate · 2 strong Go 96,676 lines 3,538 2026-11-03 adequate
authorizerdev/authorizer 2 adequate · 3 strong Go 228,170 lines 2,117 2026-11-08 strong
infracost/infracost 2 adequate · 2 strong Go 247,713 lines 12,584 2026-10-23 adequate
encoredev/encore 2 adequate · 3 strong Go 346,649 lines 12,523 2026-10-23 strong
zarf-dev/zarf 3 adequate · 2 strong Go 236,718 lines 2,082 2026-11-08 adequate
future-architect/vuls 3 adequate · 2 strong Go 121,626 lines 12,300 2026-10-23 adequate
gruntwork-io/terragrunt 3 adequate · 1 strong Go 469,261 lines 9,859 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.