unknown-suppression

What it catches#

asitis-disable names a rule that does not exist, or no rule at all.

An asitis-disable comment that names a rule id not in the registry, one that is still planned, or one of the three suppression rules (which a comment cannot turn off). Also a comment with no rule id at all, and a directive that does not exist, such as asitis-disable-line. Nothing is suppressed, and the finding the comment was meant for stays. When the id is close to a real one, the message suggests it.

Why it matters#

A typo in the rule id means nothing is suppressed, and a comment without a rule id would otherwise silence everything.

<!-- asitis-disable-next-line duplicate-rules -- the two paths are alternatives -->
- Run `make release` after tagging.

<!-- asitis-disable-next-line duplicate-rule -- the two paths are alternatives -->
- Run `make release` after tagging.

How to fix#

Fix the rule id or delete the comment. Copy the id from the finding you are suppressing; the index lists every active rule. The directives are asitis-disable-next-line and asitis-disable-file, and a rule id is required: there is no comment that disables everything.

Suppress or configure#

For one finding, put a comment on the line above it. The reason after -- is optional but worth writing:

<!-- asitis-disable-next-line unknown-suppression -- why this one is fine -->

For a whole file:

<!-- asitis-disable-file unknown-suppression -- why this file is an exception -->

For every file, turn it off or change its severity in .asitisrc.json:

{ "rules": { "unknown-suppression": "off" } }

A .asitisrc.json overrides entry limits a change to some paths, and a baseline (asitis lint --format json --write-baseline) accepts today's findings so only new ones fail the build.

Source#

asitis CLI contract: Suppression, read on 14 October 2026.