Staged publishing and new install-time controls for npm

https://github.blog/changelog/2026-05-22-staged-publishing-and-new-install-time-controls-for-npm/

Comments

supriyo-biswasMay 23, 2026, 8:07 AM
Is any form of code analysis out of the question? Static and dynamic analysis of the code would seem like a promising idea rather than just trying to defer the update and hence the problem.
sieabahlparkMay 24, 2026, 12:52 AM
[dead]
weinzierlMay 23, 2026, 7:33 AM
Seen favorably, staged publishing is a band aid. Seen more realistically I believe that in the long run it will even hurt our efforts for more secure infra.
buildfocusMay 23, 2026, 8:02 AM
How could it possibly hurt?

For trusted publishing, it's not a band-aid, it's a significant improvement that kills an entire class of CI takeover publish attacks. I'm sure attackers will find another way but it's a big gap this is closing up.

koinedadMay 23, 2026, 2:27 AM
Nice…maybe will help some of the recent attacks
turkeyboiMay 23, 2026, 3:40 AM
If maintainers actually use it
Klaster_1May 23, 2026, 3:56 AM
This is the biggest question I also had after reading the blog post. Given the recent chain of attacks, wouldn't it make sense to enforce staged publish by default or at least gradually move over to it?
sieabahlparkMay 24, 2026, 12:52 AM
[dead]
madarcoMay 23, 2026, 8:12 AM
meanwhile pnpm 10.x by default won't donwload packages younger than a day
stabblesMay 23, 2026, 8:25 AM
Is one day enough to find vulnerabilities? Who keeps an eye on new releases? Otherwise the problem continues to exist, just delayed by one day.
captn3m0May 23, 2026, 8:43 AM
There’s almost a dozen cybersecurity companies scanning NPM publishes in real-time and analysing them.
jamietannaMay 23, 2026, 9:13 AM
*11.x
warmwafflesMay 23, 2026, 3:51 PM
Perfect, now we'll start seeing people automate auto publishing because they don't want to explicitly push a button to publish it.
bob1029May 23, 2026, 8:10 AM
[dead]
eff-nixMay 23, 2026, 5:36 AM
[dead]
NicoHartmannMay 23, 2026, 7:45 AM
[dead]