Suppression does not match any active finding

How to fix

1. Remove unused suppression entries.
2. Refresh suppressions only for findings that are still active.
3. Run validation again to confirm no stale entries remain.

What it means

A suppression entry remains after the finding it targeted disappeared or changed fingerprint.

Why it matters

Unused suppressions create configuration clutter and can confuse future reviews.

Common causes

• The finding was fixed.
• The file path or fingerprint changed.
• A broad suppression was copied forward unnecessarily.

Example bad pattern

A suppression stays in the file after the matching AP-DEP-004 finding is gone.

Example good pattern

The suppression file only contains entries that match current approved findings.

Related files/config

• .archpilot/suppressions.json
• .archpilot/exceptions.json

Related CLI commands

• archpilot validate
• archpilot validate --ci