eol-check

# Vulnetix EOL Check Skill ## Use when - Quarterly upgrade planning: which runtimes hit EOL in the next 90 days? - Audit: any past-EOL runtimes in production? - CI gate: block deploys if any EOL runtime is detected. - Container base-image EOL check (alpine 3.16, debian 10, etc.). - Cross-reference: an EOL runtime + an unpatched CVE = critical priority. ## Don't use for - Vulnerability scanning — use `/vulnetix:sca-scan` or `/vulnetix:soc-triage`. - License auditing — use `/vulnetix:license-check`. ## Conventions This skill follows [`_lib/contract.md`](../_lib/contract.md): the Vulnetix CLI is auto-installed by hooks, `.vulnetix/capabilities.yaml` is always present, every `vulnetix vdb` call is piped through a verified `jq` filter from [`_lib/jq/`](../_lib/jq/), independent calls run in parallel as concurrent Bash tool calls, and trailing follow-ups are limited to one line. See the contract for output style, memory write rules, and cooldowns. ## Step 1: Load capabilities Read `.vulnetix/capabilities.yaml`. Use `derived.primary_package_manager` and `repo.dockerfile` to decide which surfaces to scan. ## Step 2: Run gated scan ```bash vulnetix scan --block-eol -o json ``` Exit code is non-zero on EOL hits. Capture findings. ## Step 3: Cross-check runtimes For each detected runtime, fetch authoritative dates: ```bash vulnetix vdb product "<runtime>" -o json # node, python, java, golang, dotnet ``` ## Step 4: Render ``` | Runtime / package | Installed | EOL date |...