deadcode

Dead code detection uses static analysis to locate unused imports, variables, exports, and unreachable branches. It scans single files, modules, or entire repositories across common languages and suggests safe removals that require your confirmation before deletion.

Unreachable code consists of branches or statements that cannot execute during runtime. Static analysis identifies these by parsing language-aware syntax trees to map execution paths and flag orphaned files or unused imports without running the program.

Yes, scope-aware analysis supports whole-project scans to identify orphaned files not referenced anywhere and unused imports. This detection applies across multiple common languages and generates safe, non-destructive deletion suggestions.

Yes, the static analysis implements language-aware parsing to handle multiple common languages. It detects unused exports, dead variables, and unreachable branches by adapting its parsing logic to the specific syntax of each language in your project.

Dead code cleanup is non-destructive and requires user confirmation before any code changes. It only provides safe deletion suggestions for unused imports and orphaned files, ensuring you maintain control over the refactoring process.

Pruning unused exports requires static analysis to map all references across your codebase. By detecting dead exports and orphaned files, you can safely reduce technical debt through confirmed, targeted code removal.