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 |
|---|---|---|---|---|---|
| lf-edge/ekuiper 2 adequate · 3 strong | Go | 305,770 lines | 1,747 | 2026-11-08 | |
| kube-logging/logging-operator 2 adequate · 3 strong | Go | 192,507 lines | 1,716 | 2026-11-08 | |
| krakend/krakend-ce 2 adequate · 3 strong | Go | 5,635 lines | 2,702 | 2026-11-03 | |
| goplus/xgo 1 adequate · 3 strong | Go | 89,812 lines | 9,487 | 2026-10-23 | |
| absmach/magistrala 2 adequate · 3 strong | Go | 119,482 lines | 2,658 | 2026-11-03 | |
| bitnami/sealed-secrets 2 adequate · 3 strong | Go | 25,226 lines | 9,316 | 2026-10-23 | |
| supabase/auth 5 strong | Go | 116,528 lines | 2,592 | 2026-11-03 | |
| teamhanko/hanko 1 adequate · 4 strong | Go | 96,639 lines | 9,045 | 2026-10-23 | |
| 99designs/aws-vault 2 adequate · 3 strong | Go | 7,412 lines | 9,000 | 2026-10-23 | |
| prometheus/alertmanager 1 adequate · 4 strong | Go | 119,424 lines | 8,669 | 2026-10-23 | |
| ovh/utask 2 adequate · 3 strong | Go | 42,874 lines | 1,413 | 2026-11-08 | |
| lightningnetwork/lnd 2 adequate · 3 strong | Go | 914,706 lines | 8,204 | 2026-10-23 | |
| projectcapsule/capsule 2 adequate · 3 strong | Go | 262,751 lines | 2,211 | 2026-11-03 | |
| fluxcd/flux2 2 adequate · 3 strong | Go | 67,121 lines | 8,458 | 2026-10-22 | |
| luraproject/lura 1 adequate · 4 strong | Go | 23,265 lines | 6,805 | 2026-10-23 | |
| grpc-ecosystem/go-grpc-middleware 4 strong | Go | 14,363 lines | 6,759 | 2026-10-23 | |
| kptdev/kpt 1 adequate · 4 strong | Go | 125,440 lines | 1,900 | 2026-11-03 | |
| unkeyed/unkey 2 adequate · 3 strong | Go | 743,381 lines | 5,455 | 2026-10-25 | |
| cloudquery/cloudquery 1 adequate · 4 strong | Go | 163,747 lines | 6,544 | 2026-10-23 | |
| codeberg.org/readeck/readeck 2 adequate · 3 strong | Go | 179,340 lines | 1,191 | 2026-11-07 | |
| go-vikunja/vikunja 1 adequate · 4 strong | Go | 448,773 lines | 5,828 | 2026-10-23 | |
| kgateway-dev/kgateway 2 adequate · 3 strong | Go | 467,140 lines | 5,723 | 2026-10-23 | |
| peerdb-io/peerdb 2 adequate · 3 strong | Go | 197,242 lines | 3,310 | 2026-10-28 | |
| edgenesis/shifu 2 adequate · 3 strong | Go | 41,636 lines | 1,436 | 2026-11-03 | |
| pomerium/pomerium 2 adequate · 3 strong | Go | 329,649 lines | 5,064 | 2026-10-23 | |
| clidey/whodb 2 adequate · 3 strong | Go | 464,188 lines | 5,041 | 2026-10-23 | |
| jenkins-x/jx 2 adequate · 3 strong | Go | 7,014 lines | 4,691 | 2026-10-23 | |
| enterpilot/gomodel 2 adequate · 3 strong | Go | 550,673 lines | 1,298 | 2026-11-03 | |
| elastic/apm-server 5 strong | Go | 114,220 lines | 1,271 | 2026-11-03 | |
| octelium/octelium 2 adequate · 3 strong | Go | 391,302 lines | 4,112 | 2026-10-23 |
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.