The npm blog has been discontinued.
Updates from the npm team are now published on the GitHub Blog and the GitHub Changelog.
Posts tagged: npm registry
- Changes to npm Unpublish Policy - January 2020 (January 30th, 2020)
- Two-factor authentication protection for packages (July 13th, 2018)
- CouchDB browse views unavailable (May 15th, 2018)
- new pgp machinery (April 16th, 2018)
- Re-inventing npmjs.com (April 3rd, 2018)
- Customer Convos: SendBird (March 29th, 2018)
- Customer Convos: Sqreen (February 26th, 2018)
- Incident report: npm, Inc. operations incident of January 6, 2018 (January 11th, 2018)
- npm operational incident, 6 Jan 2018 (January 7th, 2018)
- npm private modules outage on December 12th (December 27th, 2017)
- New Package Moniker rules (December 26th, 2017)
- CouchDB vulnerabilities and the npm registry (November 15th, 2017)
- Customer Convos: The Google Cloud Team (November 15th, 2017)
- Protect your npm account with two-factor authentication and read-only tokens (October 4th, 2017)
- API rate limiting rolling out (August 30th, 2017)
- Edge node architecture with npm Enterprise (August 15th, 2017)
- We have a tendency to police our code ecosystems and it's harmful to those ecosystems and community (August 4th, 2017)
- `crossenv` malware on the npm registry (August 2nd, 2017)
- upcoming change: verified email required (July 19th, 2017)
- Introducing npx: an npm package runner (July 11th, 2017)
- Customer Convo: Dan Gebhardt, Cerebris (June 29th, 2017)
- Credentials resets (June 6th, 2017)
- npm@5 is now `npm@latest` (May 31st, 2017)
- basic auth to be limited soon (May 18th, 2017)
- Deprecating the /-/all registry endpoint (February 23rd, 2017)
- How we deploy at npm (October 19th, 2016)
- package tarball read outage today (July 6th, 2016)