Upcoming breaking changes for npm v12
51–60 of 221 posts
Re: Upcoming breaking changes for npm v12
#521. Publishing users must approve each and every release from a smartphone app.
2. Publishing users must provide verified government ID.
The first step prevents the types of attacks where an attacker gets control of a maintainer's computer and publishes a new release.
The second step discourages attacks where a user tries to get a malicious package used by others.
When combined with the security features that already exist, e.g. delays and automatic scanning, it would make it considerably harder to pull off a successful attack.
Re: Upcoming breaking changes for npm v12
#53Re: Upcoming breaking changes for npm v12
#54I would've assumed lockfile-by-default. We're still going with auto-updating?
Re: Upcoming breaking changes for npm v12
#55Re: Upcoming breaking changes for npm v12
#56Earlier quoted context omitted.
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 ado…
To be fair, the vibes (at the time) were that Microsoft has changed. Probably, in some way, a zero-interest rate phenomena.
Re: Upcoming breaking changes for npm v12
#57Re: Upcoming breaking changes for npm v12
#58Earlier quoted context omitted.
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 ado…
MSFT acquisition of NPM was a massive shit show, they fired many staff engineers and people that were at github for quite a while. Top comment was a liar.
Would you rather the company went under after it ran out of money and had to fire everyone instead? Not to mention a quarter of the company was laid off the year before the acquisition.
Re: Upcoming breaking changes for npm v12
#59npm is basically pnpm now
Re: Upcoming breaking changes for npm v12
#60this release fixes a vulnerability reported 10 years ago https://www.kb.cert.org/vuls/id/319816