getreadystack/runtime-eol-deploy-block-audit repository overview

⁠Runtime EOL and Deploy-Block Audit for Docker, CI and AWS Lambda

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

docker pull runtime-eol-deploy-block-audit

⁠FAQ

What does Runtime EOL Guard actually do?

It scans a Dockerfile, GitHub Actions workflow, serverless.yml, .csproj, Gemfile or requirements.txt and flags every runtime version that has passed end-of-life or is close to it. Each finding names the real EOL date, the AWS Lambda block-create and block-update dates where those apply, and the supported version to move to instead.

Who is this for?

Platform and DevOps engineers who own the deploy pipeline — the person paged when a Lambda function refuses to update or a CI job fails on a retired runner label. It also suits anyone reviewing infrastructure code an AI assistant generated, because those suggestions reflect the versions that were current while the model was trained.

Why not just use endoflife.date or Dependabot?

endoflife.date publishes the dates but cannot read your repository. Dependabot and Renovate update packages inside a manifest, not the platform underneath it: base images, CI runner labels and Lambda runtime identifiers. Runtime EOL Guard joins the two halves, finding the pinned version in your file and attaching the date it stops working.

⁠Full version

This is one working piece, and it works on its own. What it does NOT do:

• 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.

Only in the full version

Get the full version⁠

Free · MIT