Runtime Not Eol
endoflife.runtime-not-eol
Fails if any detected runtime under .lang.<language>.eol is past
its end-of-life date (is_eol == true). Skips cleanly when no
runtime EOL data is present (e.g. component has no detectable
runtime pin, or the endoflife collector did not run). All detected
runtimes must be non-EOL — multi-runtime components fail if any one
is EOL.
Compatible Integrations
This guardrail works with the following integrations. Click to see how to use Runtime Not Eol with each collector.
Enable This Guardrail
Add the parent policy to your lunar-config.yml to enable this guardrail.
policies:
- uses: github://earthly/lunar-lib/policies/endoflife@v1.0.5
include: [runtime-not-eol]
# with: ...How This Guardrail Works
This guardrail is part of the End-of-Life Runtime Guardrails policy. It evaluates data collected by integrations and produces a pass/fail check with actionable feedback.
When enabled, this check runs automatically on every PR and in AI coding workflows, providing real-time enforcement of your engineering standards.
Learn How Lunar Works →Configuration Options
These inputs can be configured in your lunar-config.yml to customize
how the parent policy (and this guardrail) behaves.
| Input | Required | Default | Description |
|---|
End-of-Life Runtime Guardrails
This guardrail is part of the End-of-Life Runtime Guardrails policy, which includes 2 guardrails for security and compliance.
Ready to Automate Your Standards?
See how Lunar can turn your AGENTS.md, engineering wiki, compliance docs, or postmortem action items into automated guardrails with our 200+ built-in guardrails.
AI agent rules & prompt files
Post-mortem action items
Security & compliance policies
Testing & quality requirements