JavaScript 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 |
|---|---|---|---|---|---|
| yjs/yjs 4 strong | JavaScript | 27,136 lines | 22,972 | 2026-10-23 | |
| graphite-project/graphite-web 4 strong | JavaScript | 48,331 lines | 6,133 | 2026-11-03 | |
| parse-community/parse-server 2 adequate · 3 strong | JavaScript | 196,484 lines | 21,401 | 2026-10-23 | |
| decaporg/decap-cms 2 adequate · 3 strong | JavaScript | 304,253 lines | 19,441 | 2026-10-23 | |
| sitespeedio/sitespeed.io 3 adequate · 2 strong | JavaScript | 95,335 lines | 5,047 | 2026-11-03 | |
| sweetalert2/sweetalert2 1 adequate · 3 strong | JavaScript | 15,921 lines | 18,097 | 2026-10-23 | |
| hubotio/hubot 1 adequate · 3 strong | JavaScript | 11,693 lines | 16,801 | 2026-10-23 | |
| optimalbits/bull 2 adequate · 3 strong | JavaScript | 20,676 lines | 16,257 | 2026-10-23 | |
| fleetbase/fleetbase 3 adequate · 2 strong | JavaScript | 84,265 lines | 4,498 | 2026-11-03 | |
| iterative/cml 1 adequate · 3 strong | JavaScript | 9,059 lines | 4,190 | 2026-11-03 | |
| automatisch/automatisch 2 adequate · 3 strong | JavaScript | 152,769 lines | 14,000 | 2026-10-23 | |
| siteserver/cms 2 adequate · 3 strong | JavaScript | 387,461 lines | 3,918 | 2026-11-03 | |
| nextapps-de/flexsearch 2 adequate · 3 strong | JavaScript | 65,916 lines | 13,810 | 2026-10-23 | |
| plankanban/planka 4 adequate · 1 strong | JavaScript | 142,784 lines | 12,635 | 2026-10-23 | |
| rabbitmq/rabbitmq-server 2 adequate · 2 strong | JavaScript | 637,210 lines | 13,937 | 2026-10-22 | |
| reactioncommerce/reaction 1 adequate · 4 strong | JavaScript | 190,064 lines | 12,399 | 2026-10-23 | |
| pipedreamhq/pipedream 3 adequate · 1 strong | JavaScript | 1,761,825 lines | 11,757 | 2026-10-23 | |
| gladysassistant/gladys 3 adequate · 2 strong | JavaScript | 570,115 lines | 3,269 | 2026-11-03 | |
| debug-js/debug 2 strong | JavaScript | 1,665 lines | 11,458 | 2026-10-23 | |
| sveltia/sveltia-cms 1 adequate · 3 strong | JavaScript | 637,043 lines | 3,034 | 2026-11-03 | |
| hackmdio/codimd 2 adequate · 3 strong | JavaScript | 28,978 lines | 10,158 | 2026-10-23 | |
| architect/architect 1 adequate · 2 strong | JavaScript | 5,322 lines | 2,628 | 2026-11-03 | |
| sismics/docs 4 adequate · 1 strong | JavaScript | 118,907 lines | 2,574 | 2026-11-03 | |
| idurar/idurar-erp-crm 2 adequate · 3 strong | JavaScript | 25,926 lines | 8,909 | 2026-10-23 | |
| documize/community 2 adequate · 3 strong | JavaScript | 201,640 lines | 2,425 | 2026-11-03 | |
| formio/formio 2 adequate · 3 strong | JavaScript | 119,932 lines | 2,328 | 2026-11-03 | |
| pump-io/pump.io 2 adequate · 3 strong | JavaScript | 118,278 lines | 2,240 | 2026-11-03 | |
| elasticsearch-dump/elasticsearch-dump 3 adequate · 2 strong | JavaScript | 9,995 lines | 7,942 | 2026-10-23 | |
| ever-co/ever-traduora 2 adequate · 3 strong | JavaScript | 69,623 lines | 2,139 | 2026-11-03 | |
| matterwiki/matterwiki 3 adequate · 2 strong | JavaScript | 4,536 lines | 2,093 | 2026-11-03 |
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.