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.
| Repository | Language | Size | Stars | Read | Band |
|---|---|---|---|---|---|
| owncloud/ocis 2 adequate · 3 strong | Go | 652,310 lines | 2,171 | 2026-10-28 | |
| pgrok/pgrok 1 adequate · 4 strong | Go | 6,159 lines | 3,645 | 2026-10-23 | |
| deepfence/secretscanner 1 adequate · 3 strong | Go | 2,911 lines | 3,401 | 2026-10-23 | |
| datazip-inc/olake 2 adequate · 3 strong | Go | 129,636 lines | 1,571 | 2026-10-28 | |
| victoriametrics/victorialogs 2 adequate · 3 strong | Go | 252,099 lines | 2,399 | 2026-10-23 | |
| kubernetes-sigs/aws-iam-authenticator 2 adequate · 3 strong | Go | 19,135 lines | 2,338 | 2026-10-23 | |
| betterleaks/betterleaks 2 adequate · 3 strong | Go | 101,331 lines | 2,322 | 2026-10-23 | |
| warrant-dev/warrant 2 adequate · 3 strong | Go | 44,969 lines | 1,341 | 2026-10-28 | |
| codeberg.org/emersion/soju 2 adequate · 3 strong | Go | 24,899 lines | 230 | 2026-11-08 |
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.