EU Data Residency Lint (Terraform, GDPR Ch. V)
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.
Every cloud region in your infrastructure code, mapped to a country and the transfer basis it needs.
Install
eu-data-residency-lint file
Node 18+. The same 18 rules as the VS Code extension, from a terminal or CI.
Free
- Open any Terraform, Bicep or YAML file and see every cloud region that leaves the EEA — 18 checks against a 64-region table, each finding naming the country and the legal basis that region would need. No key, no limit, no watermark.
--ruleslists every rule
With a licence ($29 once)
- Sweep the whole repository in one command and keep a dated Chapter V transfer register in Markdown: every file, line, region, country and adequacy status in one document you can hand to an auditor.
eu-data-residency-lint --dir ./templates --report html --out report.html
External privacy counsel bills from $200/hour, and a Chapter V transfer review is billed by the file.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "eu-data-residency-lint": { "command": "eu-data-residency-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: EU Data Residency Lint (Terraform, GDPR Ch. V)
run: pip install rulestamp-eu-data-residency-lint && eu-data-residency-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-eu-data-residency-lint
eu-data-residency-lint --help
Metadata
Release files for rulestamp-eu-data-residency-lint 1.0.3
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_eu_data_residency_lint-1.0.3.tar.gz | 17.9 kB | Without provenance | Details for rulestamp_eu_data_residency_lint-1.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_eu_data_residency_lint-1.0.3-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_eu_data_residency_lint-1.0.3-py3-none-any.whl |
Total release size: 38.1 kB
Release files / rulestamp_eu_data_residency_lint-1.0.3.tar.gz
| Download URL | rulestamp_eu_data_residency_lint-1.0.3.tar.gz |
|---|---|
| Size | 17.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7e7de56551457f85c9d2f6a675c32f4a2f8a7838c035c6f1d88ac71ca915f2d8
|
|
BLAKE2b-256 checksum How to use checksums |
b4e26a82aee7466f83e54148f6fd80349e297d78c5350469d002e5d0e572c127
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_eu_data_residency_lint-1.0.3-py3-none-any.whl
| Download URL | rulestamp_eu_data_residency_lint-1.0.3-py3-none-any.whl |
|---|---|
| Size | 20.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3ba5e8fd3696c7570e85b68ce3aacdb4f1e8020e0a2939443d008e7fbf58482b
|
|
BLAKE2b-256 checksum How to use checksums |
213a2fa1fa591ef9d6d99b502b8b3725572328097d679198d6fd0808f947e0d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-eu-data-residency-lint 1.0.3
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.