Vue 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 |
|---|---|---|---|---|---|
| automaapp/automa 1 adequate · 3 strong | Vue | 76,330 lines | 21,710 | 2026-11-03 | |
| hulaspark/hula 2 adequate · 2 strong | Vue | 168,421 lines | 7,796 | 2026-11-03 | |
| vuecomponent/ant-design-vue-pro 3 adequate · 1 strong | Vue | 20,657 lines | 10,920 | 2026-10-23 | |
| kanriapp/kanri 2 adequate · 2 strong | Vue | 35,715 lines | 2,081 | 2026-11-03 | |
| frappe/crm 3 adequate · 2 strong | Vue | 134,513 lines | 3,845 | 2026-10-23 | |
| frappe/helpdesk 2 adequate · 3 strong | Vue | 136,050 lines | 3,442 | 2026-10-23 |
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.