Erlang 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.
| Repository | Language | Size | Stars | Read | Band |
|---|---|---|---|---|---|
| emqx/emqx 2 adequate · 3 strong | Erlang | 927,180 lines | 16,763 | 2026-10-25 | |
| processone/ejabberd 1 adequate · 3 strong | Erlang | 179,463 lines | 6,734 | 2026-10-25 | |
| dgiot/dgiot 3 adequate | Erlang | 139,323 lines | 4,861 | 2026-10-28 | |
| vernemq/vernemq 2 adequate · 2 strong | Erlang | 91,911 lines | 3,637 | 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.