Go repositories reading strong

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 160 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
xtls/xray-core 4 strong Go 198,141 lines 42,595 2026-11-03 strong
filosottile/age 1 adequate · 3 strong Go 13,918 lines 23,752 2026-11-07 strong
fatedier/frp 2 adequate · 3 strong Go 76,027 lines 109,669 2026-10-25 strong
jandedobbeleer/oh-my-posh 1 adequate · 3 strong Go 150,102 lines 23,720 2026-11-07 strong
micro/go-micro 2 adequate · 3 strong Go 180,548 lines 23,083 2026-11-07 strong
nektos/act 2 adequate · 3 strong Go 47,791 lines 72,471 2026-10-28 strong
v2fly/v2ray-core 1 adequate · 4 strong Go 168,905 lines 34,745 2026-11-03 strong
dgraph-io/dgraph 1 adequate · 4 strong Go 333,436 lines 21,821 2026-11-07 strong
gohugoio/hugo 2 adequate · 3 strong Go 320,168 lines 89,961 2026-10-25 strong
gin-gonic/gin 4 strong Go 29,423 lines 89,259 2026-10-25 strong
lionsoul2014/ip2region 1 adequate · 3 strong Go 34,637 lines 19,851 2026-11-07 strong
keploy/keploy 2 adequate · 3 strong Go 686,017 lines 19,518 2026-11-07 strong
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
caddyserver/caddy 1 adequate · 3 strong Go 116,020 lines 76,094 2026-10-25 strong
dolthub/dolt 2 adequate · 3 strong Go 622,064 lines 24,806 2026-11-03 strong
prometheus/prometheus 1 adequate · 4 strong Go 488,660 lines 66,304 2026-10-25 strong
getsops/sops 1 adequate · 3 strong Go 32,320 lines 23,594 2026-11-03 strong
traefik/traefik 2 adequate · 3 strong Go 383,128 lines 64,966 2026-10-25 strong
go-gitea/gitea 2 adequate · 3 strong Go 666,058 lines 58,199 2026-10-25 strong
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
usememos/memos 1 adequate · 4 strong Go 288,908 lines 64,024 2026-10-23 strong
hashicorp/terraform 1 adequate · 3 strong Go 776,373 lines 49,738 2026-10-25 strong
cli/cli 4 strong Go 329,468 lines 46,408 2026-10-25 strong
spf13/cobra 4 strong Go 19,916 lines 44,668 2026-10-25 strong
charmbracelet/bubbletea 1 adequate · 3 strong Go 17,212 lines 45,155 2026-10-25 strong
crowdsecurity/crowdsec 1 adequate · 4 strong Go 238,531 lines 15,441 2026-11-03 strong
juanfont/headscale 2 adequate · 3 strong Go 191,055 lines 44,187 2026-10-25 strong
semaphoreui/semaphore 2 adequate · 3 strong Go 176,491 lines 14,365 2026-11-03 strong

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.