DORA Art. 30 ICT Contract Clause 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.
Twenty-two checks over the ICT vendor contracts in your repository - every missing Article 30 clause named, with the wording to paste in.
Install
dora-ict-contract-clause-lint file
Node 18+. The same 22 rules as the VS Code extension, from a terminal or CI.
Free
- Lint one open ICT vendor contract to the end: every missing DORA Article 30 clause named, with the article reference and the wording to paste in.
--ruleslists every rule
With a licence ($29 once)
- One pass over every contract in the repository plus an exported per-vendor, per-clause evidence table for the register of information and the Q4 audit file.
dora-ict-contract-clause-lint --dir ./templates --report html --out report.html
Outside counsel reading one ICT contract against DORA Article 30 takes two to four hours at roughly EUR 300 an hour for EU financial-regulatory work.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "dora-ict-contract-clause-lint": { "command": "dora-ict-contract-clause-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: DORA Art. 30 ICT Contract Clause Lint
run: pip install rulestamp-dora-ict-contract-clause-lint && dora-ict-contract-clause-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-dora-ict-contract-clause-lint
dora-ict-contract-clause-lint --help
Metadata
Release files for rulestamp-dora-ict-contract-clause-lint 1.0.8
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_dora_ict_contract_clause_lint-1.0.8.tar.gz | 15.8 kB | Without provenance | Details for rulestamp_dora_ict_contract_clause_lint-1.0.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_dora_ict_contract_clause_lint-1.0.8-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_dora_ict_contract_clause_lint-1.0.8-py3-none-any.whl |
Total release size: 33.8 kB
Release files / rulestamp_dora_ict_contract_clause_lint-1.0.8.tar.gz
| Download URL | rulestamp_dora_ict_contract_clause_lint-1.0.8.tar.gz |
|---|---|
| Size | 15.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cc2fa0303264edbf1cbfd336376306f56046cb1374fdc8dd253dff5d23ee9661
|
|
BLAKE2b-256 checksum How to use checksums |
8e292373affad964c36036e5f3ca6a4c52ddfb37bf8b519a9dd9c394e7ccf6ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_dora_ict_contract_clause_lint-1.0.8-py3-none-any.whl
| Download URL | rulestamp_dora_ict_contract_clause_lint-1.0.8-py3-none-any.whl |
|---|---|
| Size | 18.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e2e49adabc16b31c13f164b7a8b1a52fb8c8850980ae0864f9df65b68635e8e3
|
|
BLAKE2b-256 checksum How to use checksums |
52958dc4b37ebf2e3bc5ae10e3c82ff497cdee99548d7f930bd92f8f73b04904
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-dora-ict-contract-clause-lint 1.0.8
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.