enodia

enodia asks your deployed services what version they’re running, checks those versions against vendor lifecycle calendars, and tells you what’s already dead, what’s dying, and where your fleet has drifted apart. You describe your services once — enodia handles the rest.

Actively released

Packages, raw archives, and a container image, for Linux/macOS/Windows. See Getting started to install it, or the Changelog for what’s new.

Why enodia

Most tools cover one half of the problem: they either track upstream releases, or they know what you’ve deployed — rarely both, and none of them join it against vendor lifecycle dates.

Tool	Tracks upstream releases	Knows what you deployed	Lifecycle dates
eol CLI	—	—	yes
nvchecker	yes	—	—
Renovate / Dependabot	yes (dependencies)	—	—
what’s-up-docker	yes (containers only)	containers only	—
Uptime Kuma	—	up/down only	—
enodia	yes	yes	yes

A minute of enodia

enodia.yaml

schemaVersion: 1
targets:
  - id: jira-main
    product: jira
    address: https://jira.example.com

  - id: gitlab-main
    product: gitlab
    address: https://gitlab.example.com
    credentials: gitlab-token

credentials:
  gitlab-token:
    kind: token-header
    header: PRIVATE-TOKEN
    value: "${GITLAB_TOKEN}"

$ enodia check
ID           PRODUCT  PATCH   LIFECYCLE  BRANCH     SEVERITY  REASON  CVES
jira-main    jira     behind  active     newer_lts  warn      -       -
gitlab-main  gitlab   behind  eol        newer      fail      -       -

That’s the whole loop: describe a target once, run enodia check, get back three independent facts per target — patch status, lifecycle status, and whether a newer branch exists — plus a severity computed from policy you control. Point a cve: block at a БДУ ФСТЭК and/or NVD export (enodia cve update downloads them) and the CVES column fills in with the known vulnerabilities of each exact installed version — and, on ten Linux distributions, of each installed package — see CVE correlation.

Where to go next

• Getting started — what actually runs today, and your first enodia.yaml.
• Concepts — the two-phase design, the three verdict axes, and why time is a parameter, not the system clock.
• Configuration — every field enodia.yaml and credentials.yaml accept.
• CLI reference — every command, straight from --help.
• CVE correlation — known vulnerabilities per installed version, from БДУ ФСТЭК, NVD and vendors’ own data, and per installed package on Linux hosts.
• Supported products — all 123 probes.

The name

Enodia, “she of the wayside”, is an epithet of Hecate: torchbearer, keeper of crossroads. Fitting for something that lights up what is decaying and stands where you choose which way to upgrade.