Matrix Nuke

To find and safely remove dead code, use Matrix Nuke to detect dead exports, orphaned files, and unused imports. It requires a code index when available and reads package.json to enforce safety rules before reporting issues.

Detect circular dependencies and unused npm packages by running a structural analysis that cross-references your package.json and config files. Matrix Nuke identifies import cycles and flags unused dependencies for triage.

Yes, you can run a single-file analysis instead of a full scan. Matrix Nuke supports path-limited scans, allowing you to target specific files for dead exports, unused imports, and code-hygiene issues.

The best way to identify commented-out code and stale TODOs is using generative AI inspection. Matrix Nuke flags unnecessary comments, console.log leftovers, and duplicated code with confidence scoring for triage.

Dead code removal respects .nukeignore files and treats framework entry points as filtered. Matrix Nuke applies explicit safety rules and supports scan, safe, and aggressive modes to prevent unsafe deletions.

Yes, static analysis for dead code works without a Matrix code index by falling back to Grep. Matrix Nuke prefers using a code index but fully supports deterministic structural analysis using the Grep fallback.