CRA 24/72/14 Reporting Lint (Article 14)
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 your SECURITY.md against the EU Cyber Resilience Act reporting clock that started on 11 September 2026 — 24 hours, 72 hours, 14 days, to ENISA and your coordinating CSIRT.
Install
cra-24-72-14-reporting-lint file.md
Node 18+. The same 18 rules as the VS Code extension, from a terminal or CI.
Free
- Checks the Markdown file you have open against all 18 rules, offline, with the article and the replacement line for every finding — no watermark, no counter, nothing withheld.
--ruleslists every rule
With a licence ($29 once)
- Sweeps every Markdown file in the workspace in one pass, works out which checks are answered nowhere in the repository rather than merely missing from one file, and writes one dated CRA-24-72-14-READINESS.md to hand to an auditor.
cra-24-72-14-reporting-lint --dir ./templates --report html --out report.html
One hour of EU product-compliance consulting runs $150-250, and a first documentation review is rarely one hour.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "cra-24-72-14-reporting-lint": { "command": "cra-24-72-14-reporting-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: CRA 24/72/14 Reporting Lint (Article 14)
run: pip install rulestamp-cra-24-72-14-reporting-lint && cra-24-72-14-reporting-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-cra-24-72-14-reporting-lint
cra-24-72-14-reporting-lint --help
Metadata
Release files for rulestamp-cra-24-72-14-reporting-lint 1.0.9
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_24_72_14_reporting_lint-1.0.9.tar.gz | 17.4 kB | Without provenance | Details for rulestamp_cra_24_72_14_reporting_lint-1.0.9.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_cra_24_72_14_reporting_lint-1.0.9-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_cra_24_72_14_reporting_lint-1.0.9-py3-none-any.whl |
Total release size: 37.1 kB
Release files / rulestamp_cra_24_72_14_reporting_lint-1.0.9.tar.gz
| Download URL | rulestamp_cra_24_72_14_reporting_lint-1.0.9.tar.gz |
|---|---|
| Size | 17.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
af7ce9fe5e1b9d7c6f90965d0fcd0394033b4b8730b2c931defbaff557f82620
|
|
BLAKE2b-256 checksum How to use checksums |
e515da8e81a8b2ab5af54e77de5554cd7608f2d6451ea3941e16006a0899c625
|
| 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_24_72_14_reporting_lint-1.0.9-py3-none-any.whl
| Download URL | rulestamp_cra_24_72_14_reporting_lint-1.0.9-py3-none-any.whl |
|---|---|
| Size | 19.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7d3bf4d73c12cae80682755ea2cce857419752f901f8d4da34190d06e0a2d05f
|
|
BLAKE2b-256 checksum How to use checksums |
5282978308c56e3f515c7377cf1ef6824be67b9bb18f98799b40fc2f9da87540
|
| 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-24-72-14-reporting-lint 1.0.9
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.