Lua 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 |
|---|---|---|---|---|---|
| kong/kong 3 adequate · 2 strong | Lua | 452,581 lines | 44,291 | 2026-10-22 | |
| koreader/koreader 2 adequate · 3 strong | Lua | 235,459 lines | 30,020 | 2026-10-25 | |
| folke/lazy.nvim 1 adequate · 3 strong | Lua | 19,093 lines | 21,602 | 2026-10-25 | |
| apache/apisix 2 adequate · 3 strong | Lua | 608,990 lines | 17,251 | 2026-10-23 | |
| scipag/vulscan 2 adequate | Lua | 2,178 lines | 3,793 | 2026-11-03 | |
| awesomewm/awesome 2 adequate · 2 strong | Lua | 152,314 lines | 6,967 | 2026-10-25 | |
| jitsi/docker-jitsi-meet 3 adequate · 1 strong | Lua | 13,416 lines | 3,619 | 2026-10-23 | |
| nerolabs/brinybest 1 adequate · 1 strong | Lua | 3,362 lines | — | 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.