Pre-Consent Tracker Audit for EU Client Websites
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.
Finds the analytics, pixels, fonts and embeds that fire before your cookie banner is answered - in the source, before you deploy. 24 rules.
Install
consent-audit-eu file
Node 18+. The same 24 rules as the VS Code extension, from a terminal or CI.
Free
- Audit the open file against all 24 rules; Audit just the lines you select; Reopen the last report, with line numbers and severity; Read every rule that ships inside, in plain English
--ruleslists every rule
With a licence ($29 once)
- Audit the whole client repository; Dated evidence report (CSV, JSON or HTML); Re-audit on every save; Machine-readable output for CI; Apply the mechanical fixes
consent-audit-eu --dir ./templates --report html --out report.html
Consent scanners are billed per domain every month - CookieYes $10-$55 per domain per month, Cookiebot around EUR 30 since it doubled its base price in August 2025 - and they only see the page after it is live.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "consent-audit-eu": { "command": "consent-audit-eu", "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: Pre-Consent Tracker Audit for EU Client Websites
run: pip install rulestamp-consent-audit-eu && consent-audit-eu --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-audit-eu
consent-audit-eu --help
Metadata
Release files for rulestamp-consent-audit-eu 0.1.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_audit_eu-0.1.6.tar.gz | 15.1 kB | Without provenance | Details for rulestamp_consent_audit_eu-0.1.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_consent_audit_eu-0.1.6-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_consent_audit_eu-0.1.6-py3-none-any.whl |
Total release size: 31.7 kB
Release files / rulestamp_consent_audit_eu-0.1.6.tar.gz
| Download URL | rulestamp_consent_audit_eu-0.1.6.tar.gz |
|---|---|
| Size | 15.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
47826cd23d9f19e99274ee6065a48d9c8f7fc077f39c27b2ba7e2148ed1c4ca9
|
|
BLAKE2b-256 checksum How to use checksums |
301833b028d9fb5a79005ae710bfa6c3fad20beab9c023d23ba2472fc562019b
|
| 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_audit_eu-0.1.6-py3-none-any.whl
| Download URL | rulestamp_consent_audit_eu-0.1.6-py3-none-any.whl |
|---|---|
| Size | 16.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d221d1db391ca571af92ba8a59150030b941d2f85daec9e437f1a0a984a3207b
|
|
BLAKE2b-256 checksum How to use checksums |
796a7322463f8103848f9659930773709d32e2d991043ff351b3ee24d3e015e7
|
| 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-audit-eu 0.1.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.