codebase-cleanup

To find unused files safely, you can build a static import graph to detect orphaned modules while protecting common entry points like index, app, server, and main files from deletion. The tool generates categorized findings with confidence levels and requires explicit permission before removing anything.

The best way to detect duplicate and temporary files is by hashing identical files and scanning for common backup artifacts like .bak, .tmp, and .DS_Store. This process flags redundant and stale files not modified in over a year for high-confidence cleanup and review.

Orphan detection works by recursively scanning your project with specified excludes and building a static import reference graph. It flags source files that are not imported anywhere and are not identified as protected entry points, helping you reduce repository bloat.

Yes, you can safely delete dead code while keeping an audit log. The workflow uses a safe delete or move strategy, generates a detailed report, and only executes removal after explicit user permission, providing deletion logs for auditing purposes.

Yes, the cleanup process protects configuration files like package.json from accidental deletion. It explicitly avoids suggesting deletion of common entry and config indicators, ensuring your application entry points remain intact during repository maintenance.