Most quality checks answer "did the data pass?" with two values, and put everything they could not evaluate into the same bucket as everything that was fine. That is the failure mode this tool is built against.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+; inspect the source before using it on your own files.
Run the checked-in example
node bin/data-quality-rule-runner.mjs \
--rules examples/clean/quality.rules.json \
--data examples/cleanRead the result
A consumer that pipes stdout must handle an empty stdout on exit 2. Emitting a fake report for a run that never started would be worse.
Where this check stops
Every bound is enforced before the work it bounds, not after. A dataset's size is taken from stat before the file is opened.
Before adapting the command to your own workflow, review the accepted inputs, exit codes and safety boundaries in the README.
Compiled with AI assistance from checked-in public documentation and example scripts. Run the example and review the repository's current documentation before relying on its result.