Check exported data-class retention policies for owners, durations, legal-hold states, deletion-job references and conflicting environments.
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
npm run example # examples/clean, exit 0
node bin/data-retention-policy-linter.mjs --root examples/broken # exit 1
node bin/data-retention-policy-linter.mjs --root examples/held # exit 1
node bin/data-retention-policy-linter.mjs --root examples/incomplete # exit 2Read the result
recommendation is one of eligible, blocked, blocked-by-hold or undecided, in reverse order of precedence: a hold outranks everything, an unknown outranks a known problem, and only eligible permits deletion.
Scope
This tool reads four exported documents. Everything it says is a statement about those documents, and the list below is what it deliberately does not do and cannot conclude.