Suppression expired

How to fix

1. Remove the suppression if the finding is fixed.
2. Fix the underlying issue if it is still active.
3. Create a fresh governed exception only if the risk is still intentionally accepted.

What it means

A suppression is still present after its configured expiry.

Why it matters

Expired suppressions can hide architecture risk beyond the approved window.

Common causes

• The underlying finding was not fixed before expiry.
• The suppression file was not reviewed.
• The expiry date was set too aggressively.

Example bad pattern

A suppression expired last month but still hides an active finding.

Example good pattern

Expired suppressions are removed or replaced by reviewed exceptions.

Related files/config

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

Related CLI commands

• archpilot validate
• archpilot validate --ci