C 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.
| Repository | Language | Size | Stars | Read | Band |
|---|---|---|---|---|---|
| madler/zlib 3 adequate · 1 strong | C | 60,730 lines | 7,108 | 2026-10-25 | |
| codeberg.org/dnkl/fuzzel 3 adequate · 1 strong | C | 28,463 lines | 925 | 2026-11-07 | |
| codeberg.org/grunfink/snac2 4 adequate · 1 strong | C | 36,941 lines | 571 | 2026-11-07 | |
| codeberg.org/dnkl/foot 3 adequate · 1 strong | C | 63,483 lines | 2,234 | 2026-10-25 |
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.