TypeScript repositories reading adequate

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 197 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
grafana/grafana 5 adequate TypeScript 2,241,114 lines 77,718 2026-10-25 adequate
readest/readest 3 adequate · 2 strong TypeScript 836,775 lines 25,904 2026-11-03 adequate
unleash/unleash 2 adequate · 3 strong TypeScript 514,429 lines 13,895 2026-11-07 adequate
formbricks/formbricks 4 adequate · 1 strong TypeScript 789,484 lines 13,022 2026-11-07 adequate
illacloud/illa-builder 4 adequate · 1 strong TypeScript 171,261 lines 12,333 2026-11-07 adequate
tryghost/ghost 4 adequate · 1 strong TypeScript 1,185,913 lines 55,439 2026-10-25 adequate
blinkospace/blinko 4 adequate · 1 strong TypeScript 92,021 lines 11,156 2026-11-08 adequate
leon-ai/leon 4 adequate · 1 strong TypeScript 243,899 lines 17,644 2026-11-03 adequate
evolution-foundation/evolution-api 2 adequate · 3 strong TypeScript 43,849 lines 10,026 2026-11-08 adequate
nocodb/nocodb 4 adequate · 1 strong TypeScript 983,582 lines 65,436 2026-10-22 adequate
keystonejs/keystone 3 adequate · 2 strong TypeScript 138,717 lines 9,987 2026-11-07 adequate
termix-ssh/termix 4 adequate · 1 strong TypeScript 1,920,750 lines 15,806 2026-11-03 adequate
paradevai/paradev 4 adequate · 1 strong TypeScript 2,784,458 lines 15,869 2026-11-03 adequate
coaidev/coai 4 adequate · 1 strong TypeScript 68,084 lines 9,334 2026-11-07 adequate
labring/fastgpt 3 adequate · 2 strong TypeScript 997,571 lines 29,931 2026-10-28 adequate
growthbook/growthbook 4 adequate · 1 strong TypeScript 1,185,125 lines 8,526 2026-11-07 adequate
directus/directus 3 adequate · 2 strong TypeScript 689,516 lines 38,722 2026-10-25 adequate
keygraphhq/shannon 4 adequate · 1 strong TypeScript 66,267 lines 49,255 2026-10-23 adequate
nextauthjs/next-auth 3 adequate · 2 strong TypeScript 64,348 lines 28,373 2026-10-28 adequate
umami-software/umami 3 adequate · 2 strong TypeScript 258,912 lines 39,009 2026-10-25 adequate
webiny/webiny-js 2 adequate · 2 strong TypeScript 956,045 lines 8,048 2026-11-07 adequate
siyuan-note/siyuan 3 adequate · 2 strong TypeScript 1,109,533 lines 46,899 2026-10-23 adequate
tldraw/tldraw 3 adequate · 2 strong TypeScript 795,440 lines 51,043 2026-10-22 adequate
openpanel-dev/openpanel 3 adequate · 2 strong TypeScript 378,281 lines 7,243 2026-11-08 adequate
plasmicapp/plasmic 3 adequate · 2 strong TypeScript 1,379,564 lines 7,126 2026-11-08 adequate
masscodeio/masscode 4 adequate · 1 strong TypeScript 475,175 lines 7,085 2026-11-08 adequate
hexclave/hexclave 4 adequate · 1 strong TypeScript 684,619 lines 6,878 2026-11-07 adequate
super-productivity/super-productivity 3 adequate · 2 strong TypeScript 1,184,736 lines 23,207 2026-10-28 adequate
mail-0/zero 3 adequate · 2 strong TypeScript 141,857 lines 10,878 2026-11-03 adequate
dokploy/dokploy 3 adequate · 2 strong TypeScript 1,408,971 lines 37,974 2026-10-23 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.