Risk Register Lint — NIS2 Art. 21(2)
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.
16 rules: ten Art. 21(2) measures (a)-(j) plus owner, 1-5 score, treatment and 12-month review for Markdown risk registers
Install
nis2-risk-register-lint file
Node 18+. The same 16 rules as the VS Code extension, from a terminal or CI.
Free
- Check one risk register against all 16 rules (ten Art. 21(2) measures plus owner, score, treatment and 12-month review) with line numbers, no key needed.
--ruleslists every rule
With a licence ($29 once)
- Scan every register in the workspace in one pass and export a dated audit evidence file that maps each finding to its Art. 21(2) letter.
nis2-risk-register-lint --dir ./templates --report html --out report.html
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "nis2-risk-register-lint": { "command": "nis2-risk-register-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: Risk Register Lint — NIS2 Art. 21(2)
run: pip install rulestamp-nis2-risk-register-lint && nis2-risk-register-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-nis2-risk-register-lint
nis2-risk-register-lint --help
Metadata
Release files for rulestamp-nis2-risk-register-lint 1.0.1
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_nis2_risk_register_lint-1.0.1.tar.gz | 15.6 kB | Without provenance | Details for rulestamp_nis2_risk_register_lint-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_nis2_risk_register_lint-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_nis2_risk_register_lint-1.0.1-py3-none-any.whl |
Total release size: 33.5 kB
Release files / rulestamp_nis2_risk_register_lint-1.0.1.tar.gz
| Download URL | rulestamp_nis2_risk_register_lint-1.0.1.tar.gz |
|---|---|
| Size | 15.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d3f5170b41ad436b184e2fe761b7a165ee411807140fa3c713a2722815fe1ae5
|
|
BLAKE2b-256 checksum How to use checksums |
dddc679365db03375dabe65955313ac4da661cf14ca5209237ffc658dceccc66
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_nis2_risk_register_lint-1.0.1-py3-none-any.whl
| Download URL | rulestamp_nis2_risk_register_lint-1.0.1-py3-none-any.whl |
|---|---|
| Size | 17.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3f7688bd078ddb4f0989af880666a1828b204c252b6a01ecfb05cd67758303f0
|
|
BLAKE2b-256 checksum How to use checksums |
e79a910840d1005d36c22b884ad3f6d07e129dac397569bd84f824fcec4ccb9f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-nis2-risk-register-lint 1.0.1
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.