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
charmbracelet/bubbletea 2 adequate · 2 strong Go 17,212 lines 45,155 2026-11-08 adequate
docker/compose 2 adequate · 2 strong Go 100,495 lines 38,439 2026-11-08 adequate
ollama/ollama 3 adequate · 2 strong Go 372,565 lines 181,897 2026-10-25 adequate
icewhaletech/casaos 3 adequate · 2 strong Go 15,752 lines 37,362 2026-11-07 adequate
k3s-io/k3s 3 adequate · 2 strong Go 84,520 lines 34,238 2026-11-08 adequate
netbirdio/netbird 2 adequate · 3 strong Go 711,266 lines 30,142 2026-11-08 adequate
grafana/loki 3 adequate · 2 strong Go 1,198,537 lines 29,048 2026-11-08 adequate
openfaas/faas 3 adequate · 2 strong Go 13,589 lines 26,253 2026-11-08 adequate
cilium/cilium 3 adequate · 2 strong Go 1,479,577 lines 25,711 2026-11-08 adequate
dapr/dapr 3 adequate · 2 strong Go 700,639 lines 26,155 2026-11-07 adequate
argoproj/argo-cd 3 adequate · 2 strong Go 879,458 lines 24,240 2026-11-08 adequate
gocolly/colly 1 adequate · 2 strong Go 9,497 lines 25,578 2026-11-07 adequate
vxcontrol/pentagi 3 adequate · 2 strong Go 527,143 lines 33,140 2026-11-03 adequate
syncthing/syncthing 3 adequate · 2 strong Go 162,965 lines 90,121 2026-10-25 adequate
openimsdk/open-im-server 4 adequate · 1 strong Go 80,189 lines 16,721 2026-11-08 adequate
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
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
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
bishopfox/sliver 4 adequate · 1 strong Go 386,022 lines 12,222 2026-11-08 adequate
netdata/netdata 3 adequate · 2 strong Go 2,132,100 lines 81,091 2026-10-22 adequate
kubeshark/kubeshark 3 adequate · 2 strong Go 22,459 lines 12,126 2026-11-07 adequate
anchore/syft 3 adequate · 1 strong Go 580,037 lines 9,819 2026-11-08 adequate
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.