What it requires. Flow definitions with no active version should be deleted or archived rather than left in the org. The scanner project notes they can still cause unintended record changes during testing or be invoked as subflows, and they sit as clutter between an admin and the automation that matters.
Why it matters. An org full of dead definitions makes every audit, deployment and impact assessment slower, and a definition that looks dormant is not always inert.
How to fix it. Delete flow definitions that are no longer needed, exporting the metadata first where a record is required.
Source. Lightning Flow Scanner, inactive-flow
Is this rule worth checking?
Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.