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 198 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
portkey-ai/gateway 4 adequate · 1 strong TypeScript 107,020 lines 13,259 2026-10-23 adequate
logto-io/logto 3 adequate · 2 strong TypeScript 639,179 lines 14,750 2026-10-22 adequate
builderio/figma-html 1 adequate · 2 strong TypeScript 954 lines 3,713 2026-11-03 adequate
seerr-team/seerr 4 adequate · 1 strong TypeScript 191,027 lines 13,005 2026-10-23 adequate
rybbit-io/rybbit 3 adequate · 2 strong TypeScript 425,399 lines 13,154 2026-10-23 adequate
deta/surf 2 adequate · 2 strong TypeScript 144,831 lines 3,617 2026-11-03 adequate
zilliztech/claude-context 2 adequate · 2 strong TypeScript 25,289 lines 12,644 2026-10-23 adequate
openvidu/openvidu 3 adequate · 2 strong TypeScript 98,179 lines 2,138 2026-11-08 adequate
mlogclub/bbs-go 3 adequate · 2 strong TypeScript 89,827 lines 3,500 2026-11-03 adequate
lmnr-ai/lmnr 4 adequate · 1 strong TypeScript 787,004 lines 3,472 2026-11-03 adequate
getumbrel/umbrel 4 adequate · 1 strong TypeScript 389,357 lines 12,441 2026-10-23 adequate
invertase/react-native-firebase 2 adequate · 2 strong TypeScript 336,590 lines 12,322 2026-10-23 adequate
deepstreamio/deepstream.io 5 adequate TypeScript 32,889 lines 7,181 2026-10-28 adequate
superglue-ai/superglue 3 adequate · 2 strong TypeScript 130,034 lines 2,065 2026-11-08 adequate
actionsflow/actionsflow 2 adequate · 3 strong TypeScript 28,526 lines 3,373 2026-11-03 adequate
caviraoss/pagelm 3 adequate · 1 strong TypeScript 16,410 lines 2,061 2026-11-07 adequate
nimbalyst/nimbalyst 3 adequate · 2 strong TypeScript 1,718,299 lines 2,016 2026-11-08 adequate
vriteio/andesine 4 adequate · 1 strong TypeScript 510,965 lines 2,005 2026-11-08 adequate
openreplay/openreplay 4 adequate · 1 strong TypeScript 473,270 lines 13,032 2026-10-22 adequate
openstatushq/openstatus 3 adequate · 2 strong TypeScript 728,788 lines 9,160 2026-10-25 adequate
papermark/papermark 3 adequate · 1 strong TypeScript 261,851 lines 9,215 2026-10-25 adequate
bagisto/nextjs-commerce 3 adequate · 1 strong TypeScript 33,970 lines 6,432 2026-10-28 adequate
msgbyte/tianji 4 adequate · 1 strong TypeScript 290,177 lines 3,119 2026-11-03 adequate
sanity-io/sanity 3 adequate · 1 strong TypeScript 832,408 lines 6,377 2026-10-28 adequate
sindresorhus/is 1 adequate · 2 strong TypeScript 6,550 lines 1,795 2026-11-08 adequate
evershopcommerce/evershop 4 adequate · 1 strong TypeScript 396,687 lines 10,524 2026-10-23 adequate
towardsthecloud/cloudburn 3 adequate · 2 strong TypeScript 109,998 lines 1,800 2026-11-07 adequate
oomol-lab/open-connector 3 adequate · 2 strong TypeScript 1,636,740 lines 6,111 2026-10-28 adequate
chaitin/pandawiki 3 adequate · 2 strong TypeScript 160,969 lines 10,334 2026-10-23 adequate
voidauth/voidauth 4 adequate · 1 strong TypeScript 33,913 lines 2,904 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.