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
coderamp-labs/pad.ws 3 adequate · 1 strong TypeScript 13,941 lines 4,204 2026-11-08 adequate
tolgee/tolgee-platform 3 adequate · 2 strong TypeScript 567,495 lines 4,151 2026-11-07 adequate
openhealthforall/open-health 3 adequate · 2 strong TypeScript 16,121 lines 3,966 2026-11-07 adequate
helicone/helicone 3 adequate · 2 strong TypeScript 533,770 lines 6,257 2026-11-03 adequate
getpaseo/paseo 5 adequate TypeScript 1,229,645 lines 21,796 2026-10-23 adequate
leaperone/multipost-extension 2 adequate · 2 strong TypeScript 40,312 lines 3,684 2026-11-08 adequate
chaskiq/chaskiq 3 adequate · 2 strong TypeScript 164,980 lines 3,576 2026-11-08 adequate
vantage-sh/ec2instances.info 3 adequate · 1 strong TypeScript 46,606 lines 5,776 2026-11-03 adequate
triggerdotdev/trigger.dev 4 adequate · 1 strong TypeScript 1,140,244 lines 16,444 2026-10-25 adequate
signalapp/signal-desktop 2 adequate · 2 strong TypeScript 1,151,574 lines 16,556 2026-10-25 adequate
worklenz/worklenz 3 adequate · 2 strong TypeScript 825,246 lines 3,280 2026-11-07 adequate
deepfence/threatmapper 4 adequate · 1 strong TypeScript 334,276 lines 5,328 2026-11-03 adequate
ether/etherpad 3 adequate · 2 strong TypeScript 182,891 lines 18,595 2026-10-23 adequate
rowboatlabs/rowboat 3 adequate · 2 strong TypeScript 340,761 lines 18,059 2026-10-23 adequate
colanode/colanode 4 adequate · 1 strong TypeScript 92,407 lines 5,185 2026-11-03 adequate
dtyq/magic 4 adequate · 1 strong TypeScript 2,432,747 lines 5,063 2026-11-03 adequate
langwatch/langwatch 3 adequate · 2 strong TypeScript 2,135,310 lines 5,009 2026-11-03 adequate
inkeep/open-knowledge 3 adequate · 1 strong TypeScript 1,718,706 lines 4,776 2026-11-03 adequate
amplication/amplication 3 adequate · 2 strong TypeScript 285,370 lines 16,008 2026-10-23 adequate
mattermost/mattermost-mobile 3 adequate · 1 strong TypeScript 570,838 lines 2,726 2026-11-07 adequate
apitable/apitable 4 adequate · 1 strong TypeScript 780,846 lines 15,643 2026-10-23 adequate
harnessmd/munder-difflin 2 adequate · 2 strong TypeScript 378,405 lines 9,149 2026-10-28 adequate
laudspeaker/laudspeaker 3 adequate · 2 strong TypeScript 155,304 lines 2,629 2026-11-07 adequate
plait-board/drawnix 3 adequate · 2 strong TypeScript 15,466 lines 14,974 2026-10-23 adequate
magnitudedev/browser-agent 1 adequate · 2 strong TypeScript 26,528 lines 4,138 2026-11-03 adequate
microfeed/microfeed 3 adequate · 2 strong TypeScript 122,109 lines 4,132 2026-11-03 adequate
emdash-cms/emdash 3 adequate · 2 strong TypeScript 1,271,053 lines 13,904 2026-10-23 adequate
portkey-ai/gateway 4 adequate · 1 strong TypeScript 107,020 lines 13,259 2026-10-23 adequate
twinnydotdev/twinny 4 adequate · 1 strong TypeScript 107,996 lines 3,688 2026-11-03 adequate
logto-io/logto 3 adequate · 2 strong TypeScript 639,179 lines 14,750 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.