For JavaScript refactoring, the most directly relevant tools are Fallow, which reports unused code, duplication, complexity and circular dependencies from one graph of the repository 10, and Knip, which finds unused dependencies, exports and files 2. ESLint 3 and Prettier 9 complement them for linting and formatting, and Oxc 4 offers high-performance JavaScript and TypeScript tooling.
- 1
- 2
- 3
- 4
- 5
Sources
- 2Declutter your JavaScript & TypeScript projects | Knipknip.dev · read 2026-10-29
- 3Find and fix problems in your JavaScript code - ESLint - Pluggable JavaScript Lintereslint.org · read 2026-10-29
- 4The JavaScript Oxidation Compileroxc.rs · read 2026-10-29
- 9Prettier · Opinionated Code Formatter · Prettierprettier.io · read 2026-10-29
- 10Fallow documentationfallow.tools · read 2026-10-29
- 20fallow: declares "fallow" (the record we read and signed)unfragile.ai · read 2026-10-24
For agents: the 10 actions behind this answer
javascript · @supabase/supabase-js verified and signed
· Knip website read, tools not yet checked
Project linter to find unused dependencies, exports and files
· ESLint website read, tools not yet checked
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
· Oxc website read, tools not yet checked
A collection of high-performance JavaScript tools written in Rust
· Babel website read, tools not yet checked
node · discord.js verified and signed
· Interlace website read, tools not yet checked
Open-source tools for JavaScript developers: ESLint plugins that find bugs in AI-written code, burgee (a CLI framework for Node.js), and Serverless Framework plugins.
ruff · ruff verified and signed
Guide for using ruff, the extremely fast Python linter and formatter. Use this when linting, formatting, or fixing Python code.
· Prettier website read, tools not yet checked
Opinionated Code Formatter
fallow · fallow verified and signed
Codebase intelligence for TypeScript and JavaScript. Static analysis reports changed-code risk, cleanup opportunities, duplication, circular dependencies, complexity hotspots, architecture boundaries, design-system drift, feature flags, and opt-in security candidates. Optional local similar-code dis
Labels are the instruments' verdict and are never changed by ranking. Agents and robots get this same answer as JSON at /api/v1/find?q=…&answer=1 and through the MCP server.