nadeesha/ts-prune
Find unused exports in a typescript project. 🛀 observed · 2026-08-28
Health v2 · maintenance only
10/100
- Activity 42
- Release rhythm 8
- Longevity 100
Flags: archived
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 2686
- days_rel: n/a
- days_push: 348
- n_releases_24m: 0
Adoption not part of the score
2067 stars · 68 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
ts-prune is a zero-configuration CLI tool that finds potentially unused exports in TypeScript projects. It is now in maintenance mode, with knip recommended for new projects.
Use cases
- find unused exports in a typescript project
- clean up dead code from my codebase
- reduce bundle size by removing unused exports
- detect exports that are never imported
- audit typescript codebase for dead code in CI
When to choose
- you have an existing TypeScript project already using ts-prune
- you want a fast, zero-config dead export detector
- you only need critical fixes and stability rather than new features
When to avoid
- starting a new project - use knip instead
- you need advanced features like unused files, dependencies, or monorepo support
- your project is not TypeScript/JavaScript
Facets
cli-tool · maturity maintenance
linter developer-tools static-site-generator developer-tools version-control cli cross-platform dead-code-detection unused-exports typescript code-quality zero-config command-line nodejs
2 sources
- readme: https://github.com/nadeesha/ts-prune · fetched 2026-08-28 · bbdd716c117b
- registry_npm: https://registry.npmjs.org/ts-prune · fetched 2026-08-29 · c35bd0b3be25
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| nadeesha/ts-prune | main | 10 |
For agents
markdown · JSON · MCP: product_card(name="nadeesha/ts-prune")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem