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
ollama/ollama 3 adequate · 2 strong Go 372,565 lines 181,897 2026-10-25 adequate
xtls/xray-core 4 strong Go 198,141 lines 42,595 2026-11-03 strong
gocolly/colly 1 adequate · 2 strong Go 9,497 lines 25,578 2026-11-07 adequate
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
vxcontrol/pentagi 3 adequate · 2 strong Go 527,143 lines 33,140 2026-11-03 adequate
gohugoio/hugo 2 adequate · 3 strong Go 320,168 lines 89,961 2026-10-25 strong
syncthing/syncthing 3 adequate · 2 strong Go 162,965 lines 90,121 2026-10-25 adequate
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
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
dolthub/dolt 2 adequate · 3 strong Go 622,064 lines 24,806 2026-11-03 strong
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
getsops/sops 1 adequate · 3 strong Go 32,320 lines 23,594 2026-11-03 strong
hynetworks/hysteria 3 adequate · 2 strong Go 42,772 lines 22,838 2026-11-03 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

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.