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
Featured: chosen by hand.
hedgedoc/hedgedoc 3 adequate · 2 strong TypeScript 102,585 lines 7,445 2026-10-25 adequate
Every other reading, as the automated checks produced it.
nestjs/nest 2 adequate · 2 strong TypeScript 177,709 lines 76,747 2026-11-07 adequate
n8n-io/n8n 3 adequate · 2 strong TypeScript 2,603,095 lines 206,044 2026-10-25 adequate
deepseek-ai/deepseek-harness 3 adequate · 2 strong TypeScript 1,525,400 lines 259,316 2026-10-23 adequate
firecrawl/firecrawl 3 adequate · 2 strong TypeScript 470,651 lines 194,582 2026-10-23 adequate
cherryhq/cherry-studio 2 adequate · 3 strong TypeScript 1,888,876 lines 53,228 2026-11-03 adequate
medusajs/medusa 3 adequate · 2 strong TypeScript 1,234,100 lines 37,094 2026-11-05 adequate
excalidraw/excalidraw 3 adequate · 2 strong TypeScript 265,420 lines 133,081 2026-10-25 adequate
chatboxai/chatbox 4 adequate · 1 strong TypeScript 454,392 lines 42,243 2026-11-03 adequate
immich-app/immich 3 adequate · 2 strong TypeScript 519,332 lines 115,030 2026-10-25 adequate
nativescript/nativescript 2 adequate · 2 strong TypeScript 660,707 lines 25,694 2026-11-07 adequate
different-ai/openwork 3 adequate · 2 strong TypeScript 2,338,449 lines 24,434 2026-11-07 adequate
pubkey/rxdb 3 adequate · 2 strong TypeScript 221,177 lines 23,419 2026-11-07 adequate
wandb/openui 4 adequate · 1 strong TypeScript 17,107 lines 22,744 2026-11-07 adequate
paperclipai/paperclip 3 adequate · 2 strong TypeScript 1,907,436 lines 111,349 2026-10-23 adequate
getmaxun/maxun 3 adequate · 2 strong TypeScript 92,252 lines 18,013 2026-11-07 adequate
lobehub/lobehub 5 adequate TypeScript 1,864,469 lines 82,950 2026-10-25 adequate
gitbookio/gitbook 2 adequate · 2 strong TypeScript 133,833 lines 29,086 2026-11-03 adequate
twentyhq/twenty 4 adequate · 1 strong TypeScript 1,827,816 lines 59,954 2026-10-28 adequate
hoppscotch/hoppscotch 4 adequate · 1 strong TypeScript 399,641 lines 80,511 2026-10-25 adequate
hypit-ai/hypit 3 adequate · 2 strong TypeScript 188,034 lines 27,688 2026-11-03 adequate
onlook-dev/onlook 3 adequate · 2 strong TypeScript 184,925 lines 27,094 2026-11-03 adequate
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
chartdb/chartdb 3 adequate · 2 strong TypeScript 236,472 lines 23,054 2026-11-03 adequate
unleash/unleash 2 adequate · 3 strong TypeScript 514,429 lines 13,895 2026-11-07 adequate
makeplane/plane 5 adequate TypeScript 551,674 lines 62,026 2026-10-25 adequate
tryghost/ghost 4 adequate · 1 strong TypeScript 1,185,913 lines 55,439 2026-10-25 adequate
leon-ai/leon 4 adequate · 1 strong TypeScript 243,899 lines 17,644 2026-11-03 adequate
nocodb/nocodb 4 adequate · 1 strong TypeScript 983,582 lines 65,436 2026-10-22 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.