TypeScript 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 299 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
nhost/nhost 3 adequate · 2 strong TypeScript 977,425 lines 9,365 2026-10-23 adequate
bigbluebutton/bigbluebutton 4 adequate · 1 strong TypeScript 445,094 lines 9,250 2026-10-23 adequate
builderio/builder 1 adequate · 3 strong TypeScript 11,872 lines 8,870 2026-10-23 strong
ever-co/ever-gauzy 4 adequate · 1 strong TypeScript 1,924,904 lines 8,513 2026-10-23 adequate
highlight/highlight 2 adequate · 3 strong TypeScript 465,955 lines 9,384 2026-10-22 strong
trykimu/videoeditor 2 adequate · 3 strong TypeScript 26,693 lines 2,285 2026-11-03 strong
webiny/webiny-js 1 adequate · 3 strong TypeScript 956,045 lines 8,048 2026-10-23 strong
angular/angularfire 2 adequate · 2 strong TypeScript 33,761 lines 7,796 2026-10-23 adequate
vendurehq/vendure 2 adequate · 3 strong TypeScript 612,894 lines 8,530 2026-10-22 strong
kubeshop/monokle 4 adequate · 1 strong TypeScript 129,420 lines 2,140 2026-11-03 adequate
growthbook/growthbook 4 adequate · 1 strong TypeScript 1,185,125 lines 8,526 2026-10-22 adequate
websoft9/websoft9 5 adequate TypeScript 183,805 lines 2,132 2026-11-03 adequate
lightdash/lightdash 2 adequate · 3 strong TypeScript 2,110,585 lines 6,164 2026-10-25 strong
nimbalyst/nimbalyst 3 adequate · 2 strong TypeScript 1,718,299 lines 2,016 2026-11-03 adequate
parabolinc/parabol 4 adequate · 1 strong TypeScript 380,042 lines 2,017 2026-11-03 adequate
masscodeio/masscode 4 adequate · 1 strong TypeScript 475,175 lines 7,085 2026-10-23 adequate
plasmicapp/plasmic 3 adequate · 2 strong TypeScript 1,379,564 lines 7,126 2026-10-23 adequate
evidence-dev/evidence 2 adequate · 3 strong TypeScript 216,191 lines 7,049 2026-10-23 strong
vriteio/andesine 4 adequate · 1 strong TypeScript 510,965 lines 2,005 2026-11-03 adequate
getnao/nao 3 adequate · 2 strong TypeScript 1,409,840 lines 1,980 2026-11-03 adequate
sync-in/server 3 adequate · 2 strong TypeScript 144,642 lines 1,951 2026-11-03 adequate
hexclave/hexclave 4 adequate · 1 strong TypeScript 684,619 lines 6,878 2026-10-23 adequate
bugbakery/audapolis 1 adequate · 4 strong TypeScript 16,774 lines 1,905 2026-11-03 strong
tanstack/form 4 strong TypeScript 123,755 lines 6,742 2026-10-23 strong
lukevella/rallly 2 adequate · 3 strong TypeScript 170,601 lines 5,275 2026-10-25 strong
mercurjs/mercur 2 adequate · 3 strong TypeScript 555,380 lines 1,882 2026-11-03 strong
apiparklab/apipark 4 adequate · 1 strong TypeScript 151,014 lines 1,823 2026-11-03 adequate
towardsthecloud/cloudburn 3 adequate · 2 strong TypeScript 109,998 lines 1,800 2026-11-03 adequate
sonicjs-org/sonicjs 3 adequate · 2 strong TypeScript 290,370 lines 1,785 2026-11-03 adequate
classroomio/classroomio 4 adequate · 1 strong TypeScript 856,472 lines 1,736 2026-11-03 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.