Back

Upcoming breaking changes for NPM v12

59 points2 hoursgithub.blog
Tiberium1 hour ago

I hope GitHub changes their vibecoded badges, what does RETIRED even signify in this context? Why does the preview have to be in ominous red?

mort9658 minutes ago

Hahaha that's amazing, just a big red "RETIRED" badge above their blog post? What the hell

petetnt21 minutes ago

Breaking changes have had that tag for ages

efortis43 minutes ago

this release fixes a vulnerability reported 10 years ago

https://www.kb.cert.org/vuls/id/319816

cute_boi56 minutes ago

They should have added a 1-day age limit by default, so security scanners have some time.

KolmogorovComp30 minutes ago

I don't think it'd necessarily be a good decision, sometimes CVE are actively exploited and need quick patching.

A better safety net would be to require active 2FA proof for every package update.

jnwatson21 minutes ago

If you need a quick patch, you pass another parameter to turn off the 1 day. 1 day delay will prevent more problems than it makes.

TZubiri1 hour ago

Looks good? But doesn't this just change the compromise window from first installation to first run?

insanitybit21 minutes ago

Yes, but that's actually a huge win. I can't know what a package needs to do at install time - the dev knows that. But I know what my tests and program need to do at runtime because it's my job to understand those things.

The dev has to be responsible for ensuring that their build scripts are safe, I need to be responsible for ensuring that my runtime is safe.

It'd be great to have more tools for untrusting libraries (iframes are awesome for this on the frontend) but this is still a massive win.

grassfedgeek24 minutes ago

"First run" doesn't exist for JavaScript libs used only in web apps. So for that entire class of packages this change makes them safe.

semiquaver39 minutes ago

Ok? Not sure what a package manager can do about the fact that eventually you want to run the things you install.

christophilus1 hour ago

Better than nothing. That’s the same problem every package manager has.

Someone123436 minutes ago

I’m sure we’d all welcome your alternative and or superior proposals.

Without that, this just comes across like unconstructive commentary.

This moves the needle a little your proposals or the lack thereof don’t move it at all. So I’ll take this over nothing.

mschuster9127 minutes ago

An idea might be to not just pin "package xyz allowed", but "package xyz postinstall allowed with hash <1234>".

aniceperson1 hour ago

didn't know npm was owned by github.. well, that explains things...

shagie37 minutes ago

NPM Is Joining GitHub - https://news.ycombinator.com/item?id=22594549 (March 16, 2020; 571 comments; 1829 points) - https://github.blog/news-insights/company-news/npm-is-joinin...

Some of it aged... interesting.

Top comment:

> Microsoft doesn’t do everything right but the GitHub acquisition has honestly gone better than I ever expected. Rather than forcing GitHub to adopt Microsoft centric policies, Microsoft has adopted more GitHub stuff, especially from a product POV. GitHub still runs as a separate company (different logins and health care and hiring systems) with its own policies and point of view.

> ...

joeyhage1 hour ago

Most people know this but the _real_ reason it explains things is that GitHub is owned by Microsoft. Oh, and Microsoft moved GitHub to Azure

BowBun41 minutes ago

yes, since 2020