Consent Proof Record Lint (GDPR Art.7)
Runs the same checker as our npm package on a Node.js runtime that pip installs for you (
nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
Reads the consent record your code stored and names every proof field GDPR Article 7(1) needs and your log is missing.
Install
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.
--ruleslists 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.
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": "consent-proof-record-lint", "args": ["--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: pip install rulestamp-consent-proof-record-lint && consent-proof-record-lint --dir . --ci
The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Install (PyPI)
pip install rulestamp-consent-proof-record-lint
consent-proof-record-lint --help
Metadata
Release files for rulestamp-consent-proof-record-lint 1.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rulestamp_consent_proof_record_lint-1.0.6.tar.gz | 16.3 kB | Without provenance | Details for rulestamp_consent_proof_record_lint-1.0.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_consent_proof_record_lint-1.0.6-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_consent_proof_record_lint-1.0.6-py3-none-any.whl |
Total release size: 34.8 kB
Release files / rulestamp_consent_proof_record_lint-1.0.6.tar.gz
| Download URL | rulestamp_consent_proof_record_lint-1.0.6.tar.gz |
|---|---|
| Size | 16.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
65d6a4830933bdf45c05bbd0a59b0c7fb4a2f5ea411d7a37648796d99eee90c7
|
|
BLAKE2b-256 checksum How to use checksums |
2558036065ce627216b223843a64d93b3e18e80e4397d668ae9c76d63d2c7612
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_consent_proof_record_lint-1.0.6-py3-none-any.whl
| Download URL | rulestamp_consent_proof_record_lint-1.0.6-py3-none-any.whl |
|---|---|
| Size | 18.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2c9a2cee5e455bd6efff8551a0ce7150aaa0f20f9f153aa2fbf4fe8aaa99ae53
|
|
BLAKE2b-256 checksum How to use checksums |
e928d0e8f3fdb7203017a8100e897166bd79605620e57462de633d272e8c7bf7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-consent-proof-record-lint 1.0.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.