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 |
|---|---|---|---|---|---|
| openfoodfoundation/openfoodnetwork 2 adequate · 3 strong | Ruby | 501,787 lines | 1,286 | 2026-10-25 | |
| maizzle/framework 1 adequate · 4 strong | TypeScript | 42,401 lines | 1,620 | 2026-10-23 | |
| obsei/obsei 2 adequate · 3 strong | Python | 47,651 lines | 1,441 | 2026-10-23 | |
| codeberg.org/emersion/soju 2 adequate · 3 strong | Go | 24,899 lines | 230 | 2026-11-08 | |
| zinggai/zingg 1 adequate · 3 strong | Java | 64,729 lines | 1,261 | 2026-10-23 | |
| element-hq/element-x-ios 4 strong | Swift | 191,749 lines | 947 | 2026-10-25 | |
| gitlab.com/coolercontrol/coolercontrol 2 adequate · 3 strong | — | 250,554 lines | 573 | 2026-10-25 | |
| baristaze/swe_guidelines 1 adequate · 4 strong | Python | 237,263 lines | 94 | 2026-10-25 | |
| git.sr.ht/~rjarry/aerc 2 adequate · 3 strong | — | 67,761 lines | — | 2026-10-25 | |
| yegamble/vidra 1 adequate · 3 strong | Python | 288,345 lines | — | 2026-10-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.