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
egonex-ai/understand-anything 4 strong TypeScript 126,416 lines 87,881 2026-10-23 strong
chartdb/chartdb 3 adequate · 2 strong TypeScript 236,472 lines 23,054 2026-11-03 adequate
withastro/astro 2 adequate · 3 strong TypeScript 338,410 lines 63,745 2026-10-25 strong
makeplane/plane 5 adequate TypeScript 551,674 lines 62,026 2026-10-25 adequate
heyputer/puter 1 adequate · 4 strong TypeScript 762,175 lines 43,960 2026-10-28 strong
toeverything/affine 2 adequate · 3 strong TypeScript 1,158,373 lines 73,777 2026-10-23 strong
heygen-com/hyperframes 2 adequate · 3 strong TypeScript 1,596,271 lines 70,605 2026-10-23 strong
tryghost/ghost 4 adequate · 1 strong TypeScript 1,185,913 lines 55,439 2026-10-25 adequate
foundry376/mailspring 4 strong TypeScript 391,468 lines 17,992 2026-11-03 strong
calcom/cal.com 2 adequate · 3 strong TypeScript 771,503 lines 48,648 2026-10-25 strong
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
termix-ssh/termix 4 adequate · 1 strong TypeScript 1,920,750 lines 15,806 2026-11-03 adequate
payloadcms/payload 2 adequate · 3 strong TypeScript 992,903 lines 45,678 2026-10-25 strong
paradevai/paradev 4 adequate · 1 strong TypeScript 2,784,458 lines 15,869 2026-11-03 adequate
caprover/caprover 2 adequate · 3 strong TypeScript 30,923 lines 15,197 2026-11-03 strong
botpress/botpress 2 adequate · 3 strong TypeScript 320,899 lines 14,975 2026-11-03 strong
labring/fastgpt 3 adequate · 2 strong TypeScript 997,571 lines 29,931 2026-10-28 adequate
browseros-ai/browseros 2 adequate · 3 strong TypeScript 538,005 lines 14,235 2026-11-03 strong
novuhq/novu 2 adequate · 3 strong TypeScript 1,128,292 lines 40,086 2026-10-25 strong
trpc/trpc 4 strong TypeScript 180,519 lines 40,667 2026-10-25 strong
outline/outline 2 adequate · 3 strong TypeScript 417,213 lines 40,701 2026-10-25 strong
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
prisma/orm 1 adequate · 4 strong TypeScript 1,661,335 lines 47,664 2026-10-23 strong
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
apify/crawlee 2 adequate · 3 strong TypeScript 181,805 lines 26,278 2026-10-28 strong

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.