CRA Readiness Audit for EU Cyber Resilience Act
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.
Flags the lines in your repo that break the EU Cyber Resilience Act - default passwords, disabled TLS checks, floating base images, an expired security.txt - naming the Annex each one fails.
Install
cra-readiness-audit file
Node 18+. The same 28 rules as the VS Code extension, from a terminal or CI.
Free
- Check the open file against all 28 rules; Check only the lines you select; Reopen the last findings, with line numbers and severity; Read every rule that ships inside, with its Annex reference
--ruleslists every rule
With a licence ($29 once)
- Check every file in the repository; Findings report as CSV, JSON or HTML; JSON output a build step can fail on
cra-readiness-audit --dir ./templates --report html --out report.html
Blended EU engineering-and-consulting effort on CRA work is estimated at EUR 45 an hour, and the cheapest tooled route published runs EUR 4,000 per project per year.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "cra-readiness-audit": { "command": "cra-readiness-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: CRA Readiness Audit for EU Cyber Resilience Act
run: pip install rulestamp-cra-readiness-audit && cra-readiness-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-cra-readiness-audit
cra-readiness-audit --help
Metadata
Release files for rulestamp-cra-readiness-audit 0.1.7
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_cra_readiness_audit-0.1.7.tar.gz | 16.9 kB | Without provenance | Details for rulestamp_cra_readiness_audit-0.1.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_cra_readiness_audit-0.1.7-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_cra_readiness_audit-0.1.7-py3-none-any.whl |
Total release size: 35.6 kB
Release files / rulestamp_cra_readiness_audit-0.1.7.tar.gz
| Download URL | rulestamp_cra_readiness_audit-0.1.7.tar.gz |
|---|---|
| Size | 16.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7163715f3b05cbdcc8d1a9250ab8101dddcc4a7aff17e38ac752ae47c7270134
|
|
BLAKE2b-256 checksum How to use checksums |
da7b69b61f6cdf851f24230e8e6f542e40b2146c861c95e8be1e7b4425ededeb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_cra_readiness_audit-0.1.7-py3-none-any.whl
| Download URL | rulestamp_cra_readiness_audit-0.1.7-py3-none-any.whl |
|---|---|
| Size | 18.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4481c11adc6369390b2bc0a6e88e5f1ecadf59548d24effcb3434bf62330f737
|
|
BLAKE2b-256 checksum How to use checksums |
ff6c3e676b75fc8ea98e2b4a75ff2519ea2a739fe107bdae4f188b5bd219445a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-cra-readiness-audit 0.1.7
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.