CRA Annex II User Docs Lint
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.
19 rules over the user documentation that ships with your product: support-period end date, vulnerability reporting contact, EU declaration of conformity address, secure decommissioning.
Install
cra-annex-ii-docs-lint file
Node 18+. The same 19 rules as the VS Code extension, from a terminal or CI.
Free
- Lints the documentation file you have open with all 19 rules and puts every missing, vague or expired Annex II item on its line - 15 findings (11 errors, 4 warnings) on the bundled dirty fixture, 0 on the clean one. No key, no upload, finished on its own.
--ruleslists every rule
With a licence ($29 once)
- Scope and ownership: one command sweeps every documentation file in the workspace and exports a dated Annex II evidence report (Markdown + CSV) you keep with your technical file. $29 once, one licence key per person or team seat.
cra-annex-ii-docs-lint --dir ./templates --report html --out report.html
A compliance consultant reviewing one technical file bills about EUR 150 per hour.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "cra-annex-ii-docs-lint": { "command": "cra-annex-ii-docs-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 Annex II User Docs Lint
run: pip install rulestamp-cra-annex-ii-docs-lint && cra-annex-ii-docs-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-annex-ii-docs-lint
cra-annex-ii-docs-lint --help
Metadata
Release files for rulestamp-cra-annex-ii-docs-lint 1.0.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_annex_ii_docs_lint-1.0.7.tar.gz | 16.1 kB | Without provenance | Details for rulestamp_cra_annex_ii_docs_lint-1.0.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_cra_annex_ii_docs_lint-1.0.7-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_cra_annex_ii_docs_lint-1.0.7-py3-none-any.whl |
Total release size: 34.5 kB
Release files / rulestamp_cra_annex_ii_docs_lint-1.0.7.tar.gz
| Download URL | rulestamp_cra_annex_ii_docs_lint-1.0.7.tar.gz |
|---|---|
| Size | 16.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6e0c292a474d5c5e7ea872e346e4e0a680ec152ea8ceef372803a836de50e818
|
|
BLAKE2b-256 checksum How to use checksums |
66b34714cd1459adfe23de823f0892deff1f72b79776bd7cf93cb13a1d9fcd43
|
| 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_annex_ii_docs_lint-1.0.7-py3-none-any.whl
| Download URL | rulestamp_cra_annex_ii_docs_lint-1.0.7-py3-none-any.whl |
|---|---|
| Size | 18.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9ae7498094d9e9b65e64199d7ffc816a2aa7e77553ed30d58642457b88abb0ef
|
|
BLAKE2b-256 checksum How to use checksums |
872a2b53e76922022b9ff7f02a2df5a4c69ecb06b6e8c4baa867e6c6f786ccbe
|
| 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-annex-ii-docs-lint 1.0.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.