A freshness check has two failure modes that look identical in most tools.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+.
Run the checked-in example
node bin/warehouse-freshness-auditor.mjs \
--policy examples/clean/freshness.policy.json \
--snapshot examples/clean/snapshot.json \
--now 2026-09-18T09:00:00ZRead the result
A late table whose cause could not be settled exits 2 rather than 1: the cause is part of what this tool exists to report, and cause-undetermined says so. Governing the upstream tables in the policy is what turns such a run into a clean exit 1 with the chain named.
Scope
Every bound is enforced before the work it bounds, not after. The snapshot's size is taken from stat before the file is opened.