Consent Proof Record Lint (GDPR Art.7)

Reads the consent record your code stored and names every proof field GDPR Article 7(1) needs and your log is missing.

Install

npx @readystack/consent-proof-record-lint file

Node 18+. The same 14 rules as the VS Code extension, from a terminal or CI.

Free

• Lints the consent-record JSON file open in your editor against 14 rules and names every missing or invalid proof field with its article: subject reference, collected_at, UTC offset, per-purpose granularity, notice version, notice text hash, pre-checked defaults, withdrawal route, controller identity, expiry, expiry longer than 13 months, already expired, legal basis, TCF cmp_id. On the bundled fixtures that is 0 findings for clean.json and 15 findings on dirty.json — 10 errors and 5 warnings across 4 records, tripping all 14 rules.
• --rules lists every rule

With a licence ($29 once)

• Runs every consent-record file in the workspace in one pass instead of the one file you have open, and writes a dated evidence report you keep and hand to the auditor. Same 14 rules; the axis is scope and ownership, not a crippled free tier.

@readystack/consent-proof-record-lint --dir ./templates --report html --out report.html

A GDPR consultant reviewing a consent log bills $150 to $250 an hour.

Use from an AI agent (MCP)

Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:

{ "mcpServers": { "consent-proof-record-lint": { "command": "npx", "args": ["-y", "@readystack/consent-proof-record-lint", "--mcp"] } } }

Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.

Use in CI

- name: Consent Proof Record Lint (GDPR Art.7)
  run: npx -y @readystack/consent-proof-record-lint --dir . --ci

(container: docker run --rm -v "$PWD:/work" getreadystack/consent-proof-record-lint --dir /work --ci)

The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.

Get a licence