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 158 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
googlecloudplatform/berglas 2 adequate · 2 strong Go 8,880 lines 1,303 2026-11-08 adequate
xalgorix/xalgorix 3 adequate · 2 strong Go 382,352 lines 1,291 2026-11-08 adequate
streamdal/plumber 1 adequate · 4 strong Go 85,392 lines 2,154 2026-11-03 adequate
matrixorigin/matrixone 3 adequate · 2 strong Go 2,468,474 lines 2,062 2026-11-03 adequate
go-rod/rod 4 adequate · 1 strong Go 59,487 lines 7,138 2026-10-23 adequate
openyurtio/openyurt 3 adequate · 2 strong Go 182,888 lines 2,010 2026-11-03 adequate
aquasecurity/tfsec 1 adequate · 3 strong Go 34,052 lines 7,059 2026-10-23 adequate
codeberg.org/forgejo/forgejo 3 adequate · 2 strong Go 846,421 lines 5,540 2026-10-25 adequate
skyhook-io/radar 3 adequate · 2 strong Go 1,131,982 lines 4,048 2026-10-28 adequate
openchoreo/openchoreo 3 adequate · 2 strong Go 717,077 lines 1,759 2026-11-03 adequate
tracewayapp/traceway 3 adequate · 2 strong Go 344,922 lines 1,752 2026-11-03 adequate
netlify/gocommerce 5 strong Go 12,329 lines 1,616 2026-11-03 adequate
the-open-agent/openagent 4 adequate · 1 strong Go 203,347 lines 5,710 2026-10-23 adequate
devtron-labs/devtron 4 adequate · 1 strong Go 685,387 lines 5,621 2026-10-23 adequate
treeverse/lakefs 3 adequate · 2 strong Go 420,320 lines 5,578 2026-10-23 adequate
getprobo/probo 4 adequate · 1 strong Go 1,310,001 lines 1,494 2026-11-03 adequate
versity/versitygw 3 adequate · 2 strong Go 294,698 lines 3,076 2026-10-28 adequate
casosorg/casos 3 adequate · 1 strong Go 97,031 lines 1,396 2026-11-03 adequate
flipt-io/flipt 3 adequate · 2 strong Go 142,451 lines 4,926 2026-10-23 adequate
liftbridge-io/liftbridge 3 adequate · 2 strong Go 77,374 lines 2,805 2026-10-28 adequate
openziti/zrok 3 adequate · 2 strong Go 303,988 lines 4,783 2026-10-23 adequate
ergo-services/ergo 2 adequate · 1 strong Go 132,016 lines 4,682 2026-10-23 adequate
cerbos/cerbos 3 adequate · 2 strong Go 345,006 lines 4,631 2026-10-23 adequate
rudderlabs/rudder-server 3 adequate · 2 strong Go 406,513 lines 4,505 2026-10-23 adequate
dagucloud/dagu 4 adequate · 1 strong Go 995,418 lines 4,428 2026-10-23 adequate
smallstep/cli 3 adequate · 2 strong Go 46,801 lines 4,355 2026-10-23 adequate
deepflowio/deepflow 3 adequate · 2 strong Go 547,342 lines 4,305 2026-10-23 adequate
uptrace/uptrace 3 adequate · 2 strong Go 118,493 lines 4,306 2026-10-23 adequate
gmwalletapp/epusdt 3 adequate · 2 strong Go 43,160 lines 3,920 2026-10-23 adequate
openmeterio/openmeter 3 adequate · 2 strong Go 1,340,684 lines 2,401 2026-10-23 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.