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 |
|---|---|---|---|---|---|
| meshtastic/firmware 4 adequate · 1 strong | C++ | 333,656 lines | 8,344 | 2026-10-25 | |
| ledger/ledger 1 adequate · 2 strong | C++ | 114,949 lines | 6,063 | 2026-10-28 | |
| activeloopai/deeplake 2 adequate · 2 strong | C++ | 252,241 lines | 9,258 | 2026-10-23 | |
| jolibrain/deepdetect 3 adequate · 1 strong | C++ | 150,976 lines | 2,551 | 2026-11-03 | |
| falcosecurity/falco 4 adequate · 1 strong | C++ | 59,618 lines | 9,510 | 2026-10-22 | |
| timeplus-io/proton 3 adequate · 2 strong | C++ | 2,133,893 lines | 2,281 | 2026-11-03 | |
| bloomberg/blazingmq 5 adequate | C++ | 682,071 lines | 3,218 | 2026-10-23 | |
| rfgplk/micron.cpp 2 adequate · 1 strong | C++ | 716,818 lines | 13 | 2026-10-04 |
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.