Biometric Consent Audit (BIPA / CUBI / CO)
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.
14 rules over face, fingerprint and voiceprint code: written release, destruction schedule, the 1095-day cap and the three EU AI Act prohibitions
Install
biometric-consent-audit file
Node 18+. The same 14 rules as the VS Code extension, from a terminal or CI.
Free
- Audit the file you have open and see every biometric consent, destruction-schedule, retention and prohibited-use finding with its statute subsection
--ruleslists every rule
With a licence ($29 once)
- Scan the whole workspace and export a dated evidence report (Markdown + CSV) grouped per file and per statute subsection
biometric-consent-audit --dir ./templates --report html --out report.html
US privacy counsel bills roughly $400-$600 an hour for a pre-launch review of biometric code
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "biometric-consent-audit": { "command": "biometric-consent-audit", "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: Biometric Consent Audit (BIPA / CUBI / CO)
run: pip install rulestamp-biometric-consent-audit && biometric-consent-audit --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-biometric-consent-audit
biometric-consent-audit --help
Metadata
Release files for rulestamp-biometric-consent-audit 1.0.4
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_biometric_consent_audit-1.0.4.tar.gz | 17.0 kB | Without provenance | Details for rulestamp_biometric_consent_audit-1.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_biometric_consent_audit-1.0.4-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_biometric_consent_audit-1.0.4-py3-none-any.whl |
Total release size: 36.3 kB
Release files / rulestamp_biometric_consent_audit-1.0.4.tar.gz
| Download URL | rulestamp_biometric_consent_audit-1.0.4.tar.gz |
|---|---|
| Size | 17.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
62bfbc755ad3549693e1bf4ec409f579e6db0b37d55e09146672134442050255
|
|
BLAKE2b-256 checksum How to use checksums |
83cb83cbda81c8fe41fc2c42b8c12b8d099a4d8717882ca3fdefd580cd41391e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_biometric_consent_audit-1.0.4-py3-none-any.whl
| Download URL | rulestamp_biometric_consent_audit-1.0.4-py3-none-any.whl |
|---|---|
| Size | 19.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b1967a61d723b17635b9a8a9cca192cfaf1c4411289c944751ea3da058a920c7
|
|
BLAKE2b-256 checksum How to use checksums |
7aa8df6bd55c8af1d1b280989f036e63b4407a3f0bd5e34df88352e8b21f7722
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-biometric-consent-audit 1.0.4
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.