Skip to main content

CAP.L0.ORPHANED_IGNORE — an ignore entry that no longer silences anything

  • Category: safety
  • Level: 0
  • Stability: stable
  • Suites: audit

An entry in the ignore list resolves to a real rule and matched nothing in this run.

Why it is worth a notice​

An ignore is a statement: we know about this, and we accept it here. Once the thing it referred to is gone, the entry stops being that statement and becomes archaeology — and it keeps silencing a rule for a table or a path where nobody has decided anything.

The risk is concrete: a stale entry scoped by path or object name goes on suppressing findings about whatever occupies that name next.

What to do​

Remove the entry. If the finding it covered is genuinely still expected and just did not occur in this run — a rule whose object was outside the audited scope, for instance — widen the run before concluding the entry is dead.

Not an error​

This does not fail the run on its own. It is a report about the project's own configuration, and pruning it is a decision rather than a fix.