Rule suppression
Also known as Rule suppression, Rule suppression in software engineering
Definition
An explicit instruction that prevents a static-analysis rule from reporting a selected code location.
What it means
Rule suppression records that a team has considered a finding and chosen not to report it in a specific context. Good suppressions explain the reason, scope, owner, and review horizon. They are different from deleting a rule globally because the exception remains visible near the affected code.
Example
A parser intentionally uses a dynamic construct that a type checker cannot understand. The code includes a narrow suppression with a comment and a test that protects the invariant.
Limitations
Suppressions can become permanent bypasses when comments lack ownership or expiry. A suppression may also hide a new defect if copied into unrelated code. Prefer fixing the underlying rule or improving its model when the pattern is common.
How to use the signal
Require a narrow reason and review horizon so an exception remains an auditable decision rather than a silent bypass.
Weave can help track whether suppression-heavy changes create later rework or review questions. Keep suppression syntax and policy in the analysis system, and use workflow evidence to decide where cleanup has value.
How this relates to Weave
Weave can help track whether suppression-heavy changes create later rework or review questions. Keep suppression syntax and policy in the analysis system, and use workflow evidence to decide where cleanup has value.
Explore Engineering intelligence