OSSeva Blog
OperationsHow to Choose a Node.js Extended Support Vendor: 12 Questions to Ask
What should you ask a Node.js extended support vendor?
Ask 12 questions: which lines it covers, what it patches, how fast, how fixes arrive and what proof you get. A Node.js extended support vendor ships security fixes for a line the Node.js project has stopped patching: Node.js 18 ended on 30 April 2025 and Node.js 20 on 30 April 2026. OSSeva is one vendor on the list below, and its own page on Node.js extended support answers the same questions.
Running Node.js in production? OSSeva patches and supports it, end-of-life versions included.
Node.js extended support: what is coveredThe 12 questions, and what three vendors publish
Most answers are on the vendor's own pages, and the ones that are not belong in your contract. The table shows what HeroDevs, TuxCare and OSSeva state publicly, read on 17 November 2026. "Not stated" means the page read does not say, not that the vendor does not do it.
| # | Question | HeroDevs NES | TuxCare ELS | OSSeva |
|---|---|---|---|---|
| 1 | Which Node.js lines are covered, and is 22 included after 30 April 2027? | 12, 14, 16, 18, 20 | 12, 14, 16, 18, 20; 22 added when it reaches end of life | 14, 16, 18, 20; 22 after its end of life |
| 2 | What does it patch: the runtime only, or V8, OpenSSL and libuv too? | CVE fixes for all severity levels in end-of-life Node.js | Direct and transitive dependency fixes, per its page | Runtime, including V8 and libuv fixes |
| 3 | What is the written patch window? | Targets of 14 days (Critical) and 30 days (High) | "SLA-backed", no timings on the Node.js page | Critical within 48 hours, High within 7 days |
| 4 | When does the clock start: disclosure, a fixed upstream release or your ticket? | Earlier of a verified customer report or public disclosure | Not stated | See the support SLA |
| 5 | How is an ended line assessed, given the project treats it as always affected? | Not stated | Not stated | V8 and libuv CVEs assessed against each covered line |
| 6 | How do fixes arrive? | Container images and binaries | Through npm and your existing toolchain, signed | Signed Docker images, apt and yum packages, binaries |
| 7 | What evidence do you get for an auditor? | One CVE entry per fix | SBOM and VEX per patched release | Attestation package on Assure |
| 8 | Are base images and npm dependencies in scope? | Not stated | Dependency fixes included | Image rebuilds, npm scanning on Assure |
| 9 | What support hours and response times apply? | P0 acknowledged within 24 hours | 24/7 expert assistance | Operate: 24/7, 15-minute P1 |
| 10 | How is it priced and for how long? | Custom pricing, billed annually | Quote based on your environment | Per application runtime |
| 11 | What does a bad patch cost you: is there a rollback path? | Not stated | Updates tested for compatibility | Not stated on the page read; ask |
| 12 | What is the exit plan to a supported line? | Not stated | Not stated | Upgrade planning on Assure, migration on Operate |
Question 5 matters because the Node.js project does not assess ended lines: each security announcement says end-of-life versions are always affected. A vendor therefore has to decide for itself whether a CVE reaches the line you run, and the reasoning should be visible to you in a record per CVE.
Which questions decide the shortlist?
Questions 1, 3 and 7 decide most shortlists, because they set coverage, speed and proof.
- Coverage (1, 2, 8): if one of your services runs Node.js 16 or 14, HeroDevs and TuxCare list those lines and OSSeva lists 14 and 16 as well; the question is which versions each vendor will cover for the length of your plan.
- Speed (3, 4): the windows are not like for like. HeroDevs calls its figures targets met with extraordinary or commercially reasonable efforts, and counts from the earlier of your report or disclosure. Ask every vendor for its window in writing and the start of its clock.
- Proof (7): if an auditor will read the file, ask for SBOM and VEX documents and a CVE record per fix before you sign.
HeroDevs is the better fit when your exposure is mostly JavaScript and front-end frameworks next to Node.js. TuxCare suits teams that want fixes through npm and already buy its other runtime coverage. OSSeva suits Node.js that runs alongside brokers, databases and Java under one contract. How the three models work is in NES, ELS and stay-put support for Node.js.
What should the contract say?
Put the answers to questions 1 to 4 and 10 in the contract, not only on a web page, because the Node.js project itself calls commercial support for an ended line a temporary solution. Add an exit clause tied to your upgrade date. To price the other side of the choice, use the upgrade vs extended support calculator and read what it costs to patch unsupported Node.js.
Frequently asked questions
Who provides extended support for Node.js 18 and 20?
HeroDevs, TuxCare and OSSeva publish patched builds for both lines. The Node.js end-of-life page names HeroDevs, NodeSource and TuxCare through the OpenJS Foundation's Ecosystem Sustainability Program.
What is the most important question to ask a vendor?
The written patch window and when its clock starts, because it sets how long a known CVE stays open on your line.
Do vendors publish prices?
HeroDevs shows custom pricing billed annually and TuxCare asks for a quote based on your environment. OSSeva prices per application runtime and does not publish a price list.
Can I switch vendor later?
Yes, if the delivery is a drop-in image, package or binary and the contract has no long exit penalty. Check both before you sign.
How this was checked
Every vendor fact comes from that vendor's own page, read on 17 November 2026: herodevs.com/support/node-nes, docs.herodevs.com/sla, herodevs.com/pricing and tuxcare.com/endless-lifecycle-support/nodejs-eol-support. Node.js dates are from the release schedule and endoflife.date. OSSeva's column comes only from claims already on this site, and we did not run any vendor's builds. Vendor pages change, so re-read them before you buy.
Tags
Related articles
Who Provides Node.js Security Patches After End of Life? (Node 18 and 20)
October 6, 2026OperationsNES, ELS and Stay-Put Support for Node.js: How the Models Differ
November 17, 2026Security.NET 8 Extended Support After 10 November 2026: Who Patches It Now
October 6, 2026OperationsWhat It Costs to Patch Unsupported Node.js: Upgrade vs Extended Support
November 17, 2026OperationsUpgrade Node.js or Buy Third-Party Patches? A Decision Framework
November 17, 2026OperationsHow to Choose a PostgreSQL Extended Support Vendor
November 17, 2026Get a quote
Ready to get your open source under control?
Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.
Prefer to talk or read more first?