The product contains code that is not essential for execution, i.e., makes no state changes and has no side effects that alter data or control flow - or is unreachable under any circumstances - such that removal of the code would have no impact to intended functionality or correctness.
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)