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.
| Repository | Language | Size | Stars | Read | Band |
|---|---|---|---|---|---|
| dokploy/dokploy 3 adequate · 2 strong | TypeScript | 1,408,971 lines | 37,974 | 2026-10-23 | |
| netless-io/flat 3 adequate · 2 strong | TypeScript | 67,848 lines | 6,442 | 2026-11-07 | |
| 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 | |
| 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 | |
| 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 | |
| shardeum/shardeum 1 adequate · 3 strong | TypeScript | 81,075 lines | 31,185 | 2026-10-23 | |
| dubinc/dub 3 adequate · 2 strong | TypeScript | 544,812 lines | 24,827 | 2026-10-25 | |
| simstudioai/sim 4 adequate · 1 strong | TypeScript | 2,097,460 lines | 29,991 | 2026-10-23 | |
| requarks/wiki 3 adequate · 2 strong | TypeScript | 499,188 lines | 29,079 | 2026-10-23 | |
| signoz/signoz 3 adequate · 2 strong | TypeScript | 1,323,026 lines | 32,428 | 2026-10-22 | |
| teableio/teable 3 adequate · 2 strong | TypeScript | 1,458,621 lines | 21,849 | 2026-10-25 | |
| failproofai/failproofai 3 adequate · 2 strong | TypeScript | 472,881 lines | 7,653 | 2026-11-03 | |
| humanlayer/12-factor-agents 3 adequate · 1 strong | TypeScript | 36,341 lines | 26,849 | 2026-10-23 | |
| labring/laf 3 adequate · 2 strong | TypeScript | 124,612 lines | 7,547 | 2026-11-03 | |
| kubernetes-sigs/headlamp 3 adequate · 2 strong | TypeScript | 422,437 lines | 7,553 | 2026-11-03 | |
| refly-ai/refly 4 adequate · 1 strong | TypeScript | 390,787 lines | 7,545 | 2026-11-03 | |
| promptfoo/promptfoo 4 adequate · 1 strong | TypeScript | 1,407,640 lines | 26,341 | 2026-10-23 | |
| streetwriters/notesnook 3 adequate · 1 strong | TypeScript | 300,203 lines | 14,845 | 2026-10-28 | |
| briefercloud/briefer 5 adequate | TypeScript | 99,260 lines | 4,327 | 2026-11-07 | |
| linkwarden/linkwarden 4 adequate · 1 strong | TypeScript | 77,398 lines | 19,845 | 2026-10-25 | |
| activepieces/activepieces 4 adequate · 1 strong | TypeScript | 2,038,668 lines | 25,189 | 2026-10-23 | |
| coderamp-labs/pad.ws 3 adequate · 1 strong | TypeScript | 13,941 lines | 4,204 | 2026-11-08 | |
| tolgee/tolgee-platform 3 adequate · 2 strong | TypeScript | 567,495 lines | 4,151 | 2026-11-07 |
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.