VERICTO-042 and VERICTO-030 match the same statement, and the CLI reports one finding per statement: the strongest, here VERICTO-030. So this page shows what the CLI really prints for the example, which is VERICTO-030. The detection is the same: the statement is reported either way.
How to stop it from happening again
VERICTO-042 · UPDATE without WHERE clause · Severity: Critical
The statement the rule reports
-- reprice.sql
UPDATE products SET price = 0;
Real CLI output
$ npx @vericto/vericto-cli@2.3.0 check --offline reprice.sql
note: offline mode: 42 standard rules at default severities, engine 5.1.0. Custom rules, overrides, sensitive columns, allowlists and the audit trail apply online only.
✖ reprice.sql BLOCKED VERICTO-030 critical
UpdateStmt > WhereClause = NULL
fix: UPDATE products SET {col} = $1 WHERE id = $2
1 blocked · 0 allowed · 0 flagged · 0 monitored (ruleset standard@engine-5.1.0 · mode: offline (engine 5.1.0, 42 standard rules, no workspace policy))
✖ Vericto blocked 1 statement (ruleset standard@engine-5.1.0 · mode: offline (engine 5.1.0, 42 standard rules, no workspace policy))
✖ reprice.sql BLOCKED VERICTO-030 critical
UpdateStmt > WhereClause = NULL
fix: UPDATE products SET {col} = $1 WHERE id = $2
This is Vericto enforcing a rule — the exit code is intentional, not a crash.
To allow a finding on purpose, add an inline comment on the statement:
-- vericto:ignore[VERICTO-030] <reason> (a reason is required)
The corrected version
-- reprice.sql
UPDATE products SET price = 0 WHERE id = 1;
$ npx @vericto/vericto-cli@2.3.0 check --offline reprice.sql
note: offline mode: 42 standard rules at default severities, engine 5.1.0. Custom rules, overrides, sensitive columns, allowlists and the audit trail apply online only.
0 blocked · 1 allowed · 0 flagged · 0 monitored (ruleset standard@engine-5.1.0 · mode: offline (engine 5.1.0, 42 standard rules, no workspace policy))
Try it free, no account
The CLI checks your .sql files on your machine with the 42 standard rules: no sign-up, no API key, and no SQL leaves your computer. It is open source (AGPL-3.0-only).
npx @vericto/vericto-cli@2.3.0 check --offline migrations/
On every pull request
The vericto/check-sql GitHub Action (Apache-2.0) runs the same offline check on the .sql files a PR changes and annotates the findings on the PR. Save it as .github/workflows/vericto.yml:
on: pull_request
jobs:
vericto:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v7
with: { fetch-depth: 0 }
- uses: vericto/check-sql@v1
with: { offline: true, upload-sarif: false }
At runtime, for AI agents
The SQL an AI agent writes never goes through a PR. The Vericto TCP proxy checks each statement between the application or agent and the database, and the MCP check_sql tool lets the agent check SQL before it runs it. Both use the runtime profile, which also blocks schema changes.
The AST condition in the engine
The rule is a deterministic predicate over the AST, in src/rules/evaluator.rs of the open source engine (AGPL-3.0-only), at this page's commit:
"VERICTO-042" => find(stmts, |s| {
s.kind == StatementKind::Update && s.where_presence != WherePresence::Present
})
.map(|s| violation(rule, s, suggest_update(s))),
Related rules
- VERICTO-030: UPDATE without WHERE on main table