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.
| Repository | Language | Size | Stars | Read | Band |
|---|---|---|---|---|---|
| grapesjs/grapesjs 4 strong | TypeScript | 110,620 lines | 26,348 | 2026-10-28 | |
| reactive-resume/reactive-resume 2 adequate · 3 strong | TypeScript | 479,667 lines | 44,763 | 2026-10-23 | |
| react-hook-form/react-hook-form 1 adequate · 3 strong | TypeScript | 100,595 lines | 44,878 | 2026-10-23 | |
| langfuse/langfuse 2 adequate · 3 strong | TypeScript | 1,270,259 lines | 35,231 | 2026-10-25 | |
| gristlabs/grist-core 2 adequate · 3 strong | TypeScript | 561,872 lines | 12,043 | 2026-11-03 | |
| rocketchat/rocket.chat 2 adequate · 3 strong | TypeScript | 1,267,556 lines | 46,294 | 2026-10-22 | |
| getagentseal/codeburn 2 adequate · 3 strong | TypeScript | 387,337 lines | 11,670 | 2026-11-03 | |
| genspark-ai/genoffice 2 adequate · 3 strong | TypeScript | 1,395,011 lines | 11,629 | 2026-11-03 | |
| honojs/hono 1 adequate · 3 strong | TypeScript | 96,209 lines | 32,387 | 2026-10-25 | |
| super-productivity/super-productivity 3 adequate · 2 strong | TypeScript | 1,184,736 lines | 23,207 | 2026-10-28 | |
| blinkospace/blinko 4 adequate · 1 strong | TypeScript | 92,021 lines | 11,156 | 2026-11-03 | |
| mail-0/zero 3 adequate · 2 strong | TypeScript | 141,857 lines | 10,878 | 2026-11-03 | |
| ant-design/ant-design-pro 2 adequate · 2 strong | TypeScript | 75,053 lines | 38,884 | 2026-10-23 | |
| triliumnext/trilium 2 adequate · 3 strong | TypeScript | 1,092,422 lines | 38,507 | 2026-10-23 | |
| dokploy/dokploy 3 adequate · 2 strong | TypeScript | 1,408,971 lines | 37,974 | 2026-10-23 | |
| jitsi/jitsi-meet 5 adequate | TypeScript | 404,655 lines | 30,010 | 2026-10-25 | |
| typeorm/typeorm 2 adequate · 3 strong | TypeScript | 334,851 lines | 36,659 | 2026-10-23 | |
| copilotkit/openbot 3 adequate · 2 strong | TypeScript | 1,161,748 lines | 10,300 | 2026-11-03 | |
| appsmithorg/appsmith 4 adequate · 1 strong | TypeScript | 1,679,190 lines | 41,105 | 2026-10-22 | |
| karakeep-app/karakeep 3 adequate · 2 strong | TypeScript | 411,629 lines | 29,381 | 2026-10-25 | |
| evolution-foundation/evolution-api 2 adequate · 3 strong | TypeScript | 43,849 lines | 10,026 | 2026-11-03 | |
| kong/insomnia 3 adequate · 2 strong | TypeScript | 311,699 lines | 40,072 | 2026-10-22 | |
| mattermost/mattermost 3 adequate · 2 strong | TypeScript | 2,141,621 lines | 39,409 | 2026-10-22 | |
| hcengineering/platform 3 adequate · 2 strong | TypeScript | 976,972 lines | 27,822 | 2026-10-25 | |
| portainer/portainer 3 adequate · 2 strong | TypeScript | 485,620 lines | 38,704 | 2026-10-22 | |
| modem-dev/hunk 2 adequate · 3 strong | TypeScript | 399,621 lines | 9,746 | 2026-11-03 | |
| ghostfolio/ghostfolio 3 adequate · 2 strong | TypeScript | 176,242 lines | 9,644 | 2026-11-03 | |
| iofficeai/aionui 5 adequate | TypeScript | 399,087 lines | 33,727 | 2026-10-23 | |
| continuedev/continue 3 adequate · 2 strong | TypeScript | 420,952 lines | 36,290 | 2026-10-22 | |
| artilleryio/artillery 2 adequate · 2 strong | TypeScript | 67,827 lines | 9,111 | 2026-11-03 |
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.