razor-unused

razor:unused

Runs a mechanical audit — declared dependencies (package.json, requirements.txt/pyproject.toml) with no matching import anywhere in the project's source — and presents the findings. Never removes a dependency itself; the user decides.

1. Run the script

node "${CLAUDE_PLUGIN_ROOT}/scripts/unused-deps.js" <projectDir>

Default <projectDir> to the current working directory if the user didn't name one. The script:

• reads declared deps for whichever ecosystems have a manifest present (node, python — the ecosystems razor's gates already cover),
• walks source files (skipping node_modules, dist, .git, and other generated/vendored dirs; test files ARE included — a test-only import still counts as used),
• normalizes declared names against import roots in the suppressing direction (e.g. python-dotenv counts as used when the code imports dotenv) — a false "unused" is the failure mode the script avoids, not the one it risks,
• splits misses into two buckets: unused (no mention anywhere — source imports, package.json scripts, or a root config file) and needs a resolver-grade check (the name turns up in a script or config file — eslint/babel/webpack/vite/jest/etc. — or is a @types/*/toolchain dep, meaning it's likely invoked as a CLI tool, plugin, or type-only package rather than imported).

For a node project, the script also detects whether knip is installed or resolvable from the target project. Grep genuinely cannot resolve four classes: binaries invoked from package.json scripts, config-only plugins, true @types pairing, and dependencies that only satisfy another package's peerDependencies (this last one can produce a false "unused" verdict, since grep has no visibility into installed packages' own manifests). When knip is present, the report names it by name as the authoritative escalation for those classes. When it isn't, the report says nothing about it — razor never suggests installing a new tool into the target project.