ce-deadcode-hunter

Dead code analysis identifies unreachable code by cross-checking structural evidence, coverage artifacts, and dynamic reachability validation. It handles complex module wiring and conditional imports to accurately classify unreachable paths.

Dead code is truly unreachable, while untested code is reachable but lacks test coverage. This analysis separates the two by validating dynamic reachability and classifying paths into Dead, Untested, or Needs investigation categories.

Safe dead code removal requires evidence-backed classification with risk labels. This tool produces removal candidates by cross-checking coverage artifacts and structural evidence, ensuring only non-contributing code is pruned.

Static analysis can handle conditional imports and complex module wiring by applying dynamic reachability validation. This ensures accurate detection of unreachable code paths even in codebases with non-standard import structures.

Dead code auditing uses Test Quality Method Option A, B, or C routing to focus the analysis. Selecting an option initiates the workflow to classify unreachable and untested paths with evidence-backed risk labels.

Automated dead code removal should be approached cautiously when test coverage gaps exist. Code classified as Needs investigation requires manual review, as dynamic reachability cannot be fully validated without comprehensive test artifacts.