C++ repositories

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.

All bands Strong Adequate 52 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
pixie-io/pixie 3 adequate · 2 strong C++ 881,907 lines 6,552 2026-11-03 adequate
plotjuggler/plotjuggler 2 adequate · 1 strong C++ 382,417 lines 6,285 2026-11-03 adequate
wazuh/wazuh 3 adequate · 2 strong C++ 1,868,854 lines 17,378 2026-10-23 adequate
infiniflow/infinity 3 adequate · 2 strong C++ 674,232 lines 4,756 2026-11-03 adequate
memgraph/memgraph 4 adequate · 1 strong C++ 926,307 lines 4,643 2026-11-03 adequate
fisco-bcos/fisco-bcos 2 adequate · 2 strong C++ 333,949 lines 2,617 2026-11-07 adequate
esphome/esphome 2 adequate · 3 strong C++ 857,176 lines 11,722 2026-10-25 strong
griddb/griddb 2 adequate · 3 strong C++ 988,535 lines 2,473 2026-11-07 strong
domoticz/domoticz 2 adequate · 3 strong C++ 481,546 lines 3,829 2026-11-03 strong
tstack/lnav 3 adequate · 2 strong C++ 480,460 lines 10,716 2026-10-25 adequate
vesoft-inc/nebula 1 adequate · 4 strong C++ 427,390 lines 12,443 2026-10-23 strong
manticoresoftware/manticoresearch 1 adequate · 3 strong C++ 653,246 lines 12,067 2026-10-23 strong
heavyai/heavydb 2 adequate · 3 strong C++ 869,449 lines 3,120 2026-11-03 strong
meshtastic/firmware 4 adequate · 1 strong C++ 333,656 lines 8,344 2026-10-25 adequate
ledger/ledger 1 adequate · 2 strong C++ 114,949 lines 6,063 2026-10-28 adequate
activeloopai/deeplake 2 adequate · 2 strong C++ 252,241 lines 9,258 2026-10-23 adequate
jolibrain/deepdetect 3 adequate · 1 strong C++ 150,976 lines 2,551 2026-11-03 adequate
falcosecurity/falco 4 adequate · 1 strong C++ 59,618 lines 9,510 2026-10-22 adequate
timeplus-io/proton 3 adequate · 2 strong C++ 2,133,893 lines 2,281 2026-11-03 adequate
firebase/firebase-ios-sdk 1 adequate · 3 strong C++ 816,312 lines 6,980 2026-10-23 strong
bloomberg/blazingmq 5 adequate C++ 682,071 lines 3,218 2026-10-23 adequate
rfgplk/micron.cpp 2 adequate · 1 strong C++ 716,818 lines 13 2026-10-04 adequate

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.