Skip to main content

CAP.L0.BASELINE_ABSENT — a baseline is configured and the file is not there

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

sqlens.baseline.path names a file, and there is no file at that path. The run continued with no accepted findings — which is also what a project with no baseline at all looks like.

Why say so​

Because the two are indistinguishable in a report, and they mean opposite things. A project that accepts nothing has a clean slate; a project whose baseline went missing has just had every accepted finding come back at once, and the reader is looking at a wall of new findings with no reason given.

That is the expensive direction of the two, and it is the quiet one. Nothing fails, nothing is refused, and the numbers all look like a first run.

What to do​

If you expected a baseline, check that the path is right and that the file is committed — it is resolved relative to the application root, so a file outside the repository will not be found wherever the command is run from.

If the baseline has not been created yet, this notice is expected: run sqlens:baseline and it goes away. Creating the file is exactly how a project starts accepting findings, so a configured path with nothing behind it yet is an ordinary state rather than a mistake.

If you no longer want a baseline, set sqlens.baseline.path to null. Leaving it pointed at a file you deleted is the one shape this notice is here to stop being silent.