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
junegunn/fzf 1 adequate · 3 strong Go 54,765 lines 83,258 2026-10-25 strong
jesseduffield/lazygit 2 adequate · 3 strong Go 180,850 lines 82,672 2026-10-25 strong
weaviate/weaviate 2 adequate · 3 strong Go 1,605,084 lines 16,901 2026-11-08 strong
dagger/dagger 2 adequate · 3 strong Go 2,283,896 lines 16,364 2026-11-08 strong
caddyserver/caddy 1 adequate · 3 strong Go 116,020 lines 76,094 2026-10-25 strong
infiniflow/ragflow 3 adequate · 2 strong Go 1,383,831 lines 92,747 2026-10-23 adequate
d2lang/d2 2 adequate · 2 strong Go 1,945,777 lines 25,785 2026-11-03 adequate
cayleygraph/cayley 1 adequate · 4 strong Go 53,038 lines 15,066 2026-11-07 adequate
quantumnous/new-api 3 adequate · 2 strong Go 598,468 lines 50,868 2026-10-28 adequate
prometheus/prometheus 1 adequate · 4 strong Go 488,660 lines 66,304 2026-10-25 strong
semaphoreui/semaphore 2 adequate · 3 strong Go 176,491 lines 14,365 2026-11-07 strong
hynetworks/hysteria 3 adequate · 2 strong Go 42,772 lines 22,838 2026-11-03 adequate
prometheus/node_exporter 3 adequate · 2 strong Go 53,643 lines 13,893 2026-11-08 adequate
ory/kratos 3 adequate · 1 strong Go 440,218 lines 13,901 2026-11-07 adequate
traefik/traefik 2 adequate · 3 strong Go 383,128 lines 64,966 2026-10-25 strong
minio/minio 3 adequate · 2 strong Go 394,523 lines 61,351 2026-10-25 adequate
pocketbase/pocketbase 3 adequate · 2 strong Go 193,665 lines 61,180 2026-10-25 adequate
rclone/rclone 3 adequate · 2 strong Go 443,935 lines 60,003 2026-10-25 adequate
netdata/netdata 3 adequate · 2 strong Go 2,132,100 lines 81,091 2026-10-22 adequate
go-gitea/gitea 2 adequate · 3 strong Go 666,058 lines 58,199 2026-10-25 strong
kubeshark/kubeshark 3 adequate · 2 strong Go 22,459 lines 12,126 2026-11-07 adequate
kubescape/kubescape 2 adequate · 3 strong Go 435,437 lines 11,840 2026-11-07 strong
etcd-io/etcd 1 adequate · 4 strong Go 251,842 lines 52,320 2026-10-25 strong
hashicorp/terraform 1 adequate · 3 strong Go 776,373 lines 49,738 2026-10-25 strong
pinchtab/pinchtab 1 adequate · 4 strong Go 414,881 lines 10,437 2026-11-08 strong
velero-io/velero 2 adequate · 3 strong Go 533,084 lines 10,352 2026-11-08 strong
cli/cli 4 strong Go 329,468 lines 46,408 2026-10-25 strong
reviewdog/reviewdog 1 adequate · 4 strong Go 28,961 lines 9,716 2026-11-07 strong
spf13/cobra 4 strong Go 19,916 lines 44,668 2026-10-25 strong
gokcehan/lf 2 adequate · 2 strong Go 21,012 lines 9,522 2026-11-08 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.