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 156 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
dapr/dapr 3 adequate · 2 strong Go 700,639 lines 26,155 2026-11-07 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
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
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
owasp-amass/amass 5 adequate Go 39,830 lines 15,457 2026-11-03 adequate
schollz/croc 3 adequate · 2 strong Go 83,381 lines 40,474 2026-10-25 adequate
safing/portmaster 4 adequate · 1 strong Go 208,941 lines 14,019 2026-11-03 adequate
dnscrypt/dnscrypt-proxy 4 adequate · 1 strong Go 24,544 lines 13,808 2026-11-03 adequate
rook/rook 3 adequate · 2 strong Go 304,456 lines 13,700 2026-11-03 adequate
gogs/gogs 3 adequate · 2 strong Go 247,120 lines 47,897 2026-10-23 adequate
hashicorp/vault 3 adequate · 2 strong Go 1,105,396 lines 36,317 2026-10-25 adequate
bishopfox/sliver 4 adequate · 1 strong Go 386,022 lines 12,222 2026-11-03 adequate
kubeshark/kubeshark 3 adequate · 2 strong Go 22,459 lines 12,126 2026-11-03 adequate
harness/harness 4 adequate · 1 strong Go 661,685 lines 38,682 2026-10-23 adequate
docker/compose 2 adequate · 2 strong Go 100,495 lines 38,439 2026-10-23 adequate
hashicorp/consul 3 adequate · 2 strong Go 900,713 lines 30,088 2026-10-25 adequate
icewhaletech/casaos 2 adequate · 3 strong Go 15,752 lines 37,362 2026-10-23 adequate
glanceapp/glance 4 adequate · 1 strong Go 19,829 lines 37,640 2026-10-23 adequate
restic/restic 4 adequate · 1 strong Go 103,491 lines 36,753 2026-10-23 adequate
anchore/syft 3 adequate · 1 strong Go 580,029 lines 9,819 2026-11-03 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.