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 199 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
kubero-dev/kubero 3 adequate · 2 strong TypeScript 64,210 lines 4,445 2026-10-23 adequate
swetrix/swetrix 4 adequate · 1 strong TypeScript 328,922 lines 1,211 2026-11-03 adequate
vercel/workflow 3 adequate · 2 strong TypeScript 515,794 lines 2,478 2026-10-28 adequate
bigcapitalhq/bigcapital 5 adequate TypeScript 454,295 lines 3,956 2026-10-23 adequate
aliasvault/aliasvault 4 adequate · 1 strong TypeScript 392,127 lines 3,307 2026-10-23 adequate
silexlabs/silex 3 adequate · 2 strong TypeScript 135,226 lines 3,016 2026-10-23 adequate
crbnos/carbon 4 adequate · 1 strong TypeScript 2,055,286 lines 2,756 2026-10-23 adequate
marmelab/atomic-crm 3 adequate · 2 strong TypeScript 78,583 lines 1,432 2026-10-28 adequate
kyantech/palmr 4 adequate · 1 strong TypeScript 111,183 lines 2,395 2026-10-23 adequate
talivia-group/talivia 2 adequate · 2 strong TypeScript 106,240 lines 2,372 2026-10-23 adequate
ever-co/ever-demand 3 adequate · 2 strong TypeScript 198,163 lines 1,868 2026-10-23 adequate
openshiporg/openship 3 adequate · 1 strong TypeScript 88,200 lines 1,654 2026-10-23 adequate
frigadehq/trench 4 adequate · 1 strong TypeScript 6,113 lines 1,665 2026-10-23 adequate
featureprobe/featureprobe 4 adequate · 1 strong TypeScript 88,667 lines 1,640 2026-10-23 adequate
saleor/storefront 3 adequate · 2 strong TypeScript 93,437 lines 1,635 2026-10-23 adequate
eirno/cracked-oura 4 adequate TypeScript 10,782 lines 419 2026-10-25 adequate
scottblodgett/voice-biomarker-poc 3 adequate TypeScript 1,372 lines — 2026-10-13 adequate
aventine-labs/aegis-js 2 adequate TypeScript 4,238 lines — 2026-10-06 adequate
aventine-labs/testudo 1 adequate · 2 strong TypeScript 8,261 lines — 2026-10-06 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.