Node.js EOL checker and security releases

How the check works

The tool loads two official files in your browser: the release schedule that the Node.js Release Working Group publishes, and the release index at nodejs.org that lists every version with a flag for security releases. Your version never leaves the page. If either file cannot be loaded, the tool falls back to a built-in snapshot of the schedule and says so.

A Node.js line moves through fixed stages. It starts as Current, where new features land. Even-numbered lines then become Active LTS, which means long-term support with regular updates, followed by Maintenance LTS, which gets only critical fixes and security fixes. At end of life it gets nothing. Odd-numbered lines never become LTS and are supported for less than a year, so they are not meant for production.

Reading the result

There are four outcomes. End of life means the line gets no security fixes, so move to an LTS line. Update means the line is supported but a newer release exists, and when security releases are among the ones you missed the tool lists them with links to the release notes, which name each fixed CVE. Plan means you are current but the line ends within about six months. OK means you are on the latest release of a supported line.

Updating Node.js means more than updating your own machine. Container images, build servers and hosting platforms each carry their own copy, so a base image keeps the old version until you rebuild it. After you update, run node -v again on the running service to be sure the change took.

The table at the bottom shows every line from Node.js 18 on with its status and dates, which is the quickest way to pick the line to move to. To hear about releases early, subscribe to the low-volume nodejs-sec mailing list that the project runs for security announcements, and plan the update for the day the release lands.