Runtime EOL and Deploy-Block Audit for Docker, CI and AWS Lambda
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.
Finds the end-of-life runtimes an AI assistant still writes for you — node:20, python3.9, ubuntu-22.04, nodejs20.x — and prints the exact date each one stops deploying.
Install
runtime-eol-deploy-block-audit file
Node 18+. The same 54 rules as the VS Code extension, from a terminal or CI.
Free
- Checks the open file (or just the selected lines) against all 54 rules and names the real EOL date plus the replacement version — no key, no cap, nothing hidden.
--ruleslists every rule
With a licence ($29 once)
- Scans every file in the workspace in one pass, exports a dated audit report (CSV/JSON/HTML), emits CI JSON to fail a build on a crossed block date, re-checks on save, and runs your own internal deadline rules.
runtime-eol-deploy-block-audit --dir ./templates --report html --out report.html
A US platform engineer averages $63.95/hour (ZipRecruiter, September 2026). This is about 27 minutes of that, once.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "runtime-eol-deploy-block-audit": { "command": "runtime-eol-deploy-block-audit", "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: Runtime EOL and Deploy-Block Audit for Docker, CI and AWS Lambda
run: pip install rulestamp-runtime-eol-deploy-block-audit && runtime-eol-deploy-block-audit --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-runtime-eol-deploy-block-audit
runtime-eol-deploy-block-audit --help
Metadata
Release files for rulestamp-runtime-eol-deploy-block-audit 0.1.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_runtime_eol_deploy_block_audit-0.1.7.tar.gz | 15.7 kB | Without provenance | Details for rulestamp_runtime_eol_deploy_block_audit-0.1.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_runtime_eol_deploy_block_audit-0.1.7-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_runtime_eol_deploy_block_audit-0.1.7-py3-none-any.whl |
Total release size: 33.3 kB
Release files / rulestamp_runtime_eol_deploy_block_audit-0.1.7.tar.gz
| Download URL | rulestamp_runtime_eol_deploy_block_audit-0.1.7.tar.gz |
|---|---|
| Size | 15.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
88f62fd9f0a736c647c208da128b67a5dbeab3b13d83a187d628136abb5332b0
|
|
BLAKE2b-256 checksum How to use checksums |
ab3aaf43b074073cd047dbd2e852a61b57c5b631ef76b8ba9a468b7eb789d647
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_runtime_eol_deploy_block_audit-0.1.7-py3-none-any.whl
| Download URL | rulestamp_runtime_eol_deploy_block_audit-0.1.7-py3-none-any.whl |
|---|---|
| Size | 17.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d239fdcc8a745a961e0526259f0f998a3f30cfd715d79beec98f56090da8a162
|
|
BLAKE2b-256 checksum How to use checksums |
2e242295fc2c85847e51cc3617953727c9f50b368ebb561b99105a8c43a5c55a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-runtime-eol-deploy-block-audit 0.1.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.