npm is rotating write-scoped npm Granular Access Tokens that bypass 2FA as a precaution following a now-contained security incident. This doesn't affect GitHub personal access tokens. Maintainers should upgrade the npm CLI to v12+ and consider Trusted Publishing.
Strengthening npm supply-chain security: packages are now scanned for malware at publish time, before they can be installed.
We're also introducing disclosure for legitimate dual-use tools so they aren't blocked by default.
npm v12 is here. npm install now blocks lifecycle scripts, git, and remote-URL dependencies by default — a more secure baseline out of the box.
We're also starting to phase out npm 2FA-bypass tokens for account changes and direct publishing. Details 👇
starting today, developers building npm projects on @GitHub Actions can request a provenance statement to be published alongside their package, giving consumers a verifiable way to link a package back to its source repository and build instructions.
Now you can create tokens with fine-grained permissions for automating your publishing and org management workflows. And a new code explorer allows you to view content of a package directly in the npm portal.
⚡️ #7#: Use npm query and jq to dig into your dependencies
You can use the new "npm query" command and jq to answer interesting questions about your package's dependencies
#terminalrocks#
Today we opened an RFC with a proposal of how npm can collaborate with @projectsigstore to link packages to their source and build, a significant improvement to the supply chain security of the JavaScript ecosystem.
🚀 we just shipped npm v8.16.0 with the new `npm query` command
📦 this new feature allows developers to quickly ask & answer questions about their project's dependencies. you can learn more here:
⬇️ to get it now, run:
$ npm install -g npm
We've launched a number of security enhancements to npm including:
* Improved login and publish experience /w CLI
* Connecting GitHub + Twitter accounts
* All packages have been resigned and a new command `npm audit signatures`
Read more at:
do you publish from a npm workspace & use a root-level ignore file? if so, you should update to npm v8.11.0 or the latest versions of Node.js 16/17/18 to avoid a recently discovered vulnerability that wouldn't respect these files.
read the advisory here:
GitHub has been actively investigating the attack campaign around stolen OAuth tokens, of which @npmjs was a victim organization. Today we’re sharing our final impact analysis for npm as well as additional findings.
🔒 an enhanced npm 2FA experience is now available in public beta. it includes:
* support for physical security keys and biometric devices
* support for multiple second factors
* a new 2FA configuration menu
and more!
🚀 Our CLI team just shipped their weekly release!
📦 npm@8.9.0 makes `npm owner` workspace-aware & also comes with some docs, deps & core updates/fixes.
⬇️ Get it now:
$ npm install -g npm
See more in the changelog:
A new @npmjs cli release is out! 🚀
📦 npm@8.8.0 adds a new `--install-links` option to opt into packing+install dependencies defined using the `file:` protocol instead of symlinking.
⬇️ Get it now:
$ npm install -g npm
See more in the changelog:
we've got a jam packed Open RFC call today w/ some exciting topics like: v9 roadmap, `npm query` + dependency selector syntax, command-specific configuration & more...
come join us live at 2pm EST:
#npm# #nodejs# #javascript#