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.

All bands Strong Adequate 83 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
saltcorn/saltcorn 2 adequate · 3 strong JavaScript 414,546 lines 2,089 2026-11-03 strong
final-form/react-final-form 3 strong JavaScript 25,645 lines 7,434 2026-10-23 adequate
scality/cloudserver 2 adequate · 3 strong JavaScript 206,787 lines 1,954 2026-11-03 strong
juliapluto/pluto.jl 2 adequate · 2 strong JavaScript 76,187 lines 5,384 2026-10-25 adequate
dialmasterorg/youtarr 3 adequate · 2 strong JavaScript 320,103 lines 1,792 2026-11-03 adequate
forwardemail/forwardemail.net 4 adequate · 1 strong JavaScript 1,313,913 lines 1,702 2026-11-03 adequate
countly/countly-server 1 adequate · 4 strong JavaScript 625,954 lines 5,921 2026-10-23 strong
dotenvx/dotenvx 3 adequate · 1 strong JavaScript 35,019 lines 5,848 2026-10-23 adequate
mailtrain-org/mailtrain 3 adequate · 2 strong JavaScript 84,135 lines 5,757 2026-10-23 adequate
clientio/joint 2 adequate · 2 strong JavaScript 283,136 lines 5,394 2026-10-23 adequate
cloudera/hue 1 adequate · 3 strong JavaScript 1,530,482 lines 1,410 2026-11-03 strong
sentinl/sentinl 2 adequate · 1 strong JavaScript 18,084 lines 1,319 2026-11-03 adequate
200ok-ch/organice 4 adequate · 1 strong JavaScript 40,424 lines 2,698 2026-10-28 adequate
gopeak/dectask 2 adequate · 1 strong JavaScript 491,656 lines 1,265 2026-11-03 adequate
heyputer/everything 3 adequate JavaScript 1,751,334 lines 3,709 2026-10-23 adequate
tuiqiao/cboard 3 adequate · 1 strong JavaScript 275,270 lines 3,098 2026-10-23 adequate
padloc/padloc 2 adequate · 3 strong JavaScript 184,127 lines 2,936 2026-10-23 strong
cskefu/cskefu 4 adequate · 1 strong JavaScript 200,134 lines 2,900 2026-10-23 adequate
kritt-ai/open-kritt 3 adequate · 2 strong JavaScript 86,714 lines 2,330 2026-10-23 adequate
smallbets/userbase 3 adequate · 2 strong JavaScript 54,426 lines 2,337 2026-10-23 adequate
cloudboost/cloudboost 2 adequate · 3 strong JavaScript 265,457 lines 1,460 2026-10-23 adequate
oca/web 2 adequate · 2 strong JavaScript 37,323 lines 1,240 2026-10-23 adequate
springernature/frontend-express-demo 3 adequate · 1 strong JavaScript 249 lines 2 2026-10-05 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.