All integrationsSecurity

endoflife.date

Check whether the versions you run are still supported and until when, for about 500 programming languages, frameworks, databases, operating systems, cloud services and devices.

actions
8
triggers
2

Triggers

Start a workflow when something happens in endoflife.date.

  • New releaseTriggers when a product publishes a new version: a new patch, minor or major release of a programming language, framework, database, operating system or app, as recorded by endoflife.date
  • Release cycle reaching end of lifeTriggers when a version of a product reaches its end-of-life date, or a set number of days before it, so upgrades are planned before security updates stop

Actions

Steps a workflow can run in endoflife.date.

  • Check version supportFind out whether a version of a product is still supported and until when: its end-of-life date, the days left, the phase it is in, the newest version to update to, and whether a newer release cycle is out. Takes an exact version (3.12.4) or a release cycle (3.12).
  • Get latest releaseGet a product's newest release cycle and its newest version, with the release date, release notes and how long it will be supported.
  • Get productGet what endoflife.date knows about a product: its category, the vendor's release policy, the command that shows the version installed, its package identifiers, and how many of its release cycles are still supported.
  • List release cyclesList a product's release cycles, newest first, each with its support status, end-of-life date, days left and newest version. Narrow it to the supported cycles, the ones that have ended, or long-term support (LTS) cycles.
  • List cycles ending soonList the release cycles whose support ends in the next number of days, soonest first, across every product or only the ones you choose. Schedule it weekly to hear in good time which versions your team must upgrade.
  • List new releasesList the versions released since a date, newest first, across every product or only the ones you choose, with whether each starts a new release cycle.
  • List productsList the products endoflife.date tracks, by name: all of them (about 500), or only one category, one tag or names containing some text.
  • Find product by package URL or CPEFind which product a package from a software inventory or SBOM belongs to, from its package URL (pkg:npm/express@4.18.2), CPE name or Repology project, and the version it names. Hand both to 'Check version support'.

Automate endoflife.date with Lodol.

Connect endoflife.date and ask your AI for your first workflow.

Free plan, no credit card