Skip to main content

SEC.SKIPPED.NOTHING_CHECKED — The security run examined nothing

  • Category: security
  • Level: 0
  • Downtime class: none — the notice is about the run, not about a statement
  • Stability: stable
  • Suites: security

What it means​

sqlens:security produced no security check at all. The run resolved its flags, addressed a connection, and examined nothing.

This is not a clean result, and it is reported as undetermined rather than left silent for exactly that reason: an empty report and a report over a healthy database look identical, and the second is the reading a person makes.

Why you are seeing it today​

The sqlens:security command is currently a shell. It is registered and addressable, and the sub-runs it will orchestrate — the migration capture, the live catalog reading, the security readers — are not wired into it yet. Every run therefore ends here.

Use sqlens:audit in the meantime. It already runs the security rules over a live catalog, with the severity gate and the three-valued report, and it is where the findings this suite will eventually aggregate come from today.

Why the exit code is still 0​

An undetermined moves the exit code only under strict_undetermined — a decision your project makes once, not one this command makes for you. The report says what happened; the strict flag says what it costs.

// config/sqlens.php — make an unanswerable check fail the run
'strict_undetermined' => true,

With that set, this notice fails the run, which is the correct behavior for a pipeline that must not proceed on an unexamined database.

What it will mean later​

This id does not disappear with the scaffold. Once the suite orchestrates its sub-runs, a run whose filters admit nothing — a category scope that excludes security, a level that admits no rule — reports the same notice for the same reason. A suite that checked nothing says so, whatever the reason.