Skip to main content

CAP.L0.NO_BASELINE_TO_IGNORE — `--ignore-baseline` was passed and there is no baseline

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

--ignore-baseline tells the run to report every finding, including the ones an accepted baseline would hide. This run has no baseline, so the flag changed nothing.

Why say so​

Because the alternative is a flag that quietly does nothing and a report that looks exactly like the one the flag was supposed to produce. Somebody passes it, sees a normal report, and concludes the baseline was bypassed — when what actually happened is that there was never a baseline to bypass.

That matters most in the case where it is used: checking whether a baseline is hiding something. An answer of "nothing extra appeared" means something completely different depending on whether a baseline exists.

What to do​

If you expected a baseline, check where it is configured and whether the path resolves from the directory the command ran in. If you did not, drop the flag.

  • The audit suite — the baseline file, and the adoption path it exists for