You will get the warnings but default npm in Node will still run the scripts.
npm 12 has the relevant breaking changes: https://github.blog/changelog/2026-06-09-upcoming-breaking-c...
Node 27 will likely ship with it:
https://github.com/nodejs/Release/issues/1161
https://github.com/npm/cli/issues/9997
In Zod 4.6.6 compromised by malware?nodejs
Release
JavaScript2015–2026
nodejs / Release
Release
Node.js Release Working Group
23Distinct people
23Mentions
0Explicit recommenders
4.4KGitHub stars
What to know before exploring
What it is
Node.js Release Working Group
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- nodejs/node · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 8:59:20 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year23 dated mentions
Observed mentions: 2015-09-03 15:44:12 UTC to 2026-10-12 14:10:06 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 4 | 2 | 2 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 7 | 0 | 7 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
From the project README
An excerpt from the repository, fetched Nov 12, 2026.
Read the project’s introduction
Node.js Release Working Group
Release schedule
Release
Status
Codename
Initial Release
Active LTS Start
Maintenance Start
End-of-life
22.x
Maintenance LTS
Jod
2024-04-24
2024-10-29
2025-10-21
2027-04-30
24.x
Maintenance LTS
Krypton
2025-05-06
2025-10-28
2026-10-20
2028-04-30
26.x
Active LTS
Lithium
2026-05-05
2026-10-28
2027-10-20
2029-04-30
Release
Status
Codename
Alpha Start
Current Start
LTS Start
End-of-life
27.x
Alpha
2026-10-28
2027-04-22
2027-10-20
2030-04-30
Dates are subject to change.
The Release schedule is available also as a JSON file.
Release Phases
There are four phases that a Node.js release can be in: 'Alpha', 'Current',
'Active Long Term Support (LTS)', and 'Maintenance'. Starting with Node.js 27,
every release line goes through the 'Alpha' phase before its first 'Current'
release, and every release line is promoted to LTS. Those release lines stay in
'Active LTS' for the whole 30 months of Long Term Support and do not go through
the 'Maintenance' phase. See the
Evolving the Node.js Release Schedule announcement for details.
Release lines up to and including Node.js 26 follow the previous schedule: they
do not go through the 'Alpha' phase, and odd-numbered release lines were not
promoted to LTS - they did not go through the 'Active LTS' or 'Maintenance'
phases.
Alpha - Should incorporate most of the changes that land on nodejs/node
main branch, including semver-major (breaking) changes. Alpha releases (for
example, 27.0.0-alpha.0.0.0) are signed, tagged, and tested through
CITGM, but their API and ABI may change between releases. They are intended
for library authors and CI pipelines, not for production use.
Current - Should incorporate most of the non-major (non-breaking)
changes that land on nodejs/node main branch.
Active LTS - New features, bug fixes, and updates that have been audited by
the Release team and have been determined to be appropriate and stable for the
release line.
Maintenance (release lines up to Node.js 26 only) - Critical bug fixes and
security updates. New features may be added at the discretion of the Release
team - typically only in cases where the new feature supports migration to
later release lines.
Changes required for critical security and bug fixes may lead to semver-major
changes landing within a Current or LTS release stream, such situations will be
rare and will land as semver-minor. Although, those changes should have a
revert option included.
The term 'supported release lines' will be used to refer to all release lines
that are not End-of-Life.
End-of-Life Releases
Release
Status
Codename
Initial Release
Active LTS Start
Maintenance LTS Start
End-of-life
v0.10.x
End-of-Life
-
2013-03-11
-
2015-10-01
2016-10-31
v0.12.x
End-of-Life
-
2015-02-06
-
2016-04-01
2016-12-31
4.x
End-of-Life
Argon
2015-09-08
2015-10-01
2017-04-01
2018-04-30
5.x
End-of-Life
2015-10-29
-
2016-06-30
6.x
End-of-Life
Boron
2016-04-26
2016-10-18
2018-04-30
2019-04-30
7.x
End-of-Life
2016-10-25
-
2017-06-30
8.x
End-of-Life
Carbon
2017-05-30
2017-10-31
2019-01-01
2019-12-31
9.x
End-of-Life
2017-10-01
-
2018-06-30
10.x
End-of-Life
Dubnium
2018-04-24
2018-10-30
2020-05-19
2021-04-30
11.x
End-of-Life
2018-10-23
-
2019-06-01
12.x
End-of-Life
Erbium
2019-04-23
2019-10-21
2020-11-30
2022-04-30
13.x
End-of-Life
2019-10-22
-
2020-06-01
14.x
End-of-Life
Fermium
2020-04-21
2020-10-27
2021-10-19
2023-04-30
15.x
End-of-Life
2020-10-20
-
2021-06-01
16.x
End-of-Life
Gallium
2021-04-20
2021-10-26
2022-10-18
2023-09-11
17.x
End-of-Life
2021-10-19
-
2022-06-01
18.x
End-of-Life
Hydrogen
2022-04-19
2022-10-25
2023-10-18
2025-04-30
19.x
End-of-Life
2022-10-18
-
2023-06-01
20.x
End-of-Life
Iron
2023-04-18
2023-10-24
2024-10-22
2026-04-30
21.x
End-of-Life
2023-10-17
-
2024-04-01
2024-06-01
23.x
End-of-Life
2024-10-15
-
2025-04-01
2025-06-01
25.x
End-of-Life
2025-10-15
-
2026-04-01
2026-06-01
Mandate
The Release working group's purpose is:
Management/execution of the release and support process for all releases.
Its responsibilities are:
Define the release process.
Define the content of releases.
Generate and create releases.
Test Releases.
Manage the Alpha, Current, and LTS branches including backporting changes to
these branches.
Define the policy for what gets backported to release streams.
The Release working group is structured into teams and membership in
the working group does not automatically result in membership in these
teams. These teams are:
Releasers team
Backporters team
CITGM team
The releasers team is entrusted with the secrets and CI access to be able
build and sign releases. Additions to the releasers team must be approved
by the TSC following the process outlined in GOVERNANCE.md.
The Release team manages the process/content of LTS releases
and the required backporting for these releases. Additions to the Release
team needs sign off from the rest of the Release team.
The Canary in the Gold Mine (CITGM) team maintains CITGM as one of
the key sanity checks for releases. This team maintains the CITGM
repository and works to keep CITGM builds running and passing regularly.
This also includes maintaining the CI jobs in collaboration with the Build
Working Group.
Release Plan
Starting with Node.js 27, a new release line is branched from main once a
year, in October, and receives Alpha releases for six months. The first Alpha
release of a new release line happens around the same time the previous release
line transitions to Long Term Support. Each April, the release line in Alpha
gets its first semver-major release (for example, 27.0.0) and enters the
'Current' phase.
Every release line stays 'Current' for six months, then transitions to Long
Term Support in October. The transition to Long Term Support will happen in a
semver-minor release. Every release line receives 30 months of Long Term
Support, for a total of 36 months from its first Current release to
End-of-Life.
Relea
Read the full README on GitHub