Skip to main content
Rule ID: AE-SUPPRESS-002 · Severity: High · Category: Governance · Auto-fixable: No

​
Why this rule

A permanent suppression with no expiry and no approver is an unbounded waiver. It silently removes a finding from the score indefinitely with no human accountability attached. Unlike a time-bounded suppression — which expires and forces a re-evaluation — a permanent waiver with no approver can survive security reviews, team rotations, and architectural changes without ever being questioned. Charter refuses to honor it until a named approver accepts the risk. See Suppression governance for how waivers are evaluated.

​
What triggers it

Charter audits every active suppression — non-expired entries in .charter-suppress.yml and inline # charter:ignore directives matched to a finding — and flags any entry that is an explicit permanent waiver without a named approver. A suppression is a permanent waiver when its expires field is set to the literal value permanent. If that entry has no approver: field (or the approver is blank), Charter:
  1. Flags the entry at High severity
  2. Does not honor the suppression — the underlying finding remains active and is included in scoring
An unapproved permanent waiver is not honored. The original finding continues to affect the score until either an approver: is added or the suppression is converted to a time-bounded entry.
Suppressions with a future expires date, or with no expires at all (which applies a default TTL), are not permanent waivers and do not require an approver.

​
Examples

Permanent waiver with no approver — flagged High, suppression not honored:
.charter-suppress.yml
An entry that fires both AE-SUPPRESS-001 and AE-SUPPRESS-002:
.charter-suppress.yml

​
How to fix

1

Identify unapproved permanent waivers

Run charter explain with AE-SUPPRESS-002 — Charter lists every permanent waiver missing an approver, including the file location and the rule being suppressed.
2

Add an approver or convert to time-bounded

Choose one of two paths:Option A — Add an approver (keep the permanent waiver, add accountability):
Option B — Convert to time-bounded (eliminate the permanent waiver). The rule ID is positional on charter suppress:
3

Confirm the finding clears

Run charter doctor to verify the finding no longer appears and the suppression is now honored.
AE-SUPPRESS-003 (Informational) surfaces when the overall suppression rate is high across the repo. AE-SUPPRESS-002 (High) is about accountability on permanent waivers specifically — the two rules are complementary, not redundant.

​
Score impact

High (−10 per finding). No hard cap — caps are reserved for raw-secret and Blocker findings. The underlying finding also remains active and contributes its own deduction, since the unapproved permanent waiver is not honored. See Scoring and caps.

​
Edge cases

An expires value that is not YYYY-MM-DD or permanent fails closed — the engine treats the entry as inert, suppresses nothing, and the finding stays active. The malformed entry is not audited by AE-SUPPRESS-002 (only non-expired file entries and matched inline directives are audited).
A approver: field containing only whitespace counts as missing and fires the finding.
Secrets are suppressible like any rule. An unapproved permanent AE-SEC-001 or AE-SEC-002 suppression fires this rule and is not honored — the ≤49 raw-secret score cap remains in effect. An approved permanent secret suppression lifts the cap.
An entry that is both reason-less and a permanent waiver without an approver fires both AE-SUPPRESS-001 (Medium, −4) and AE-SUPPRESS-002 (High, −10) independently.

AE-SUPPRESS-001

Requires a reason on every suppression — the documentation companion to this rule.

AE-SUPPRESS-003

Informational — surfaces when the overall suppression rate across the repo is high.

​
CLI