What is codescythe?
Codescythe is a TypeScript dead-code analyzer and remover that finds unused files and exports in your codebase. You point it at your entry files, and it walks the import/export graph to surface anything nothing reaches. Built in Rust for speed, it ships as a CLI tool with an optional Node.js API through NAPI bindings. Run it once to audit, or with `--fix` to automatically strip dead code.
Why is it gaining traction?
The hook is performance and focus. Benchmarks against VS Code, Grafana, Kibana, and Renovate show Codescythe running 3 to 6 times faster than Knip, the established alternative. It deliberately skips framework plugins and dependency tracking, staying scoped to "which TypeScript files and exports are actually used?" That narrower contract makes the behavior predictable and the output easier to trust. The `--doctor` command is a nice touch: it flags risky config before you run `--fix`, catching broad ignore patterns or entry patterns with zero matches.
Who should use this?
Monorepo maintainers and library authors cleaning up TypeScript projects will get the most value. If you have a clear entry point boundary and want deterministic cleanup without framework-specific magic, this fits. Teams tired of Knip's overhead for simple dead-code jobs might prefer Codescythe's stripped-down approach. Not a good fit if you need dependency auditing, binary tracking, or framework-aware analysis.
Verdict
Codescythe delivers on its promise of fast, focused TypeScript dead-code removal, and Perplexity AI's backing adds credibility. At 14 stars and version 0.4.12, it is early-stage software with a 1.0% credibility score, so production use warrants careful testing against your specific codebase. The benchmark suite and conformance tests inspire confidence in correctness, but the low community adoption means you are an early adopter. Worth evaluating for cleanup pipelines, less so as a critical dependency today.
