{"full_name":"npm/npm","owner":"npm","name":"npm","shard":"1","url":"https://github.com/npm/npm","description":"This repository is moving to: https://github.com/npm/cli","homepage":"http://npm.community","topics":[],"tag_pages":[],"language":null,"license":null,"avatar":"https://avatars.githubusercontent.com/u/6078720?v=4","created_at":"2009-09-29T17:21:24Z","pushed_at":"2020-08-07T14:31:21Z","metrics":{"stars":17602,"forks":2969,"watchers":0,"issues":18652,"prs":2135,"releases":261,"issues_open":2162,"issues_closed":16490,"prs_open":0,"prs_closed":1696,"prs_merged":439,"discussions":0},"growth":{"day":{"stars":0,"forks":0,"base_day":"2026-11-15"}},"history":{"dates":["2026-11-10","2026-11-11","2026-11-12","2026-11-13","2026-11-14","2026-11-15","2026-11-16"],"stars":[17602,17603,17601,17601,17601,17602,17602],"forks":[2969,2969,2969,2969,2969,2969,2969],"watchers":[null,0,0,0,0,0,0],"issues_open":[null,2162,2162,2162,2162,2162,2162],"prs_open":[null,0,0,0,0,0,0]},"boards":{},"same_owner":[],"issues":[{"number":9863,"title":"Reinstalling npm v3 fails on Docker.","comments":150,"created_at":"2015-10-06T18:47:39Z"},{"number":17246,"title":"rollbackFailedOptional: verb npm-session xxxxxxxxxxxxxxxxxx","comments":72,"created_at":"2017-06-16T02:35:17Z"},{"number":17722,"title":"package-lock.json and optional packages","comments":69,"created_at":"2017-07-11T13:57:33Z"},{"number":17268,"title":"Error: EACCES: permission denied, mkdir '/usr/local/lib/node_modules/electron/.electron'","comments":63,"created_at":"2017-06-17T04:37:59Z"},{"number":19032,"title":"Installing node.js get error - after npm install - cannot find module internal/util/types (Windows 10 64bit)","comments":56,"created_at":"2017-11-01T19:43:48Z"},{"number":16677,"title":"npm5 Error: \"Cannot read property 'find' of undefined\"","comments":54,"created_at":"2017-05-21T21:59:21Z"},{"number":9896,"title":"cannot convert undefined or null to object","comments":53,"created_at":"2015-10-08T04:13:06Z"},{"number":17146,"title":"npm WARN registry Unexpected warning for https://registry.npmjs.org/: ","comments":51,"created_at":"2017-06-12T10:48:12Z"}],"discussions":[],"latest_release":{"name":"","tag":"v6.1.0","published_at":"2018-05-24T05:35:24Z","body":"Look at that!  A feature bump!  `npm@6` was super-exciting not just because it used a bigger number than ever before, but also because it included a super shiny new command: `npm audit`.  Well, we've kept working on it since then and have some really nice improvements for it.  You can expect more of them, and the occasional fix, in the next few releases as more users start playing with it and we get more feedback about what y'all would like to see from something like this.\r\n\r\nI, for one, have started running it (and the new subcommand...) in all my projects, and it's one of those things that I don't know how I ever functioned -without- it!  This will make a world of difference to so many people as far as making the npm ecosystem a higher-quality, safer commons for all of us.\r\n\r\nThis is also a good time to remind y'all that we have a new [RFCs repository](https://github.com/npm/rfcs), along with a new process for them.  This repo is open to anyone's RFCs, and has already received some great ideas about where we can take the CLI (and, to a certain extent, the registry).  It's a great place to get feedback, and completely replaces feature requests in the main repo, so we won't be accepting feature requests there at all anymore.  Check it out if you have something you'd like to suggest, or if you want to keep track of what the future might look like!\r\n\r\n### NEW FEATURE: `npm audit fix`\r\n\r\nThis is the biggie with this release!  `npm audit fix` does exactly what it says on the tin.  It takes all the actionable reports from your `npm audit` and runs the installs automatically for you, so you don't have to try to do all that mechanical work yourself!\r\n\r\nNote that by default, `npm audit fix` will stick to semver-compatible changes, so you should be able to safely run it on most projects and carry on with your day without having to track down what breaking changes were included.  If you want your (toplevel) dependencies to accept semver-major bumps as well, you can use `npm audit fix --force` and it'll toss those in, as well.  Since it's running the npm installer under the hood, it also supports `--production` and `--only=dev` flags, as well as things like `--dry-run`, `--json`, and `--package-lock-only`, if you want more control over what it does.\r\n\r\nGive it a whirl and tell us what you think! See `npm help audit` for full docs!\r\n\r\n* [`3800a660d`](https://github.com/npm/npm/commit/3800a660d99ca45c0175061dbe087520db2f54b7) Add `npm audit fix` subcommand to automatically fix detected vulnerabilities.  ([@zkat](https://github.com/zkat))\r\n\r\n### OTHER NEW `audit` FEATURES\r\n\r\n* [`1854b1c7f`](https://github.com/npm/npm/commit/1854b1c7f09afceb49627e539a086d8a3565601c) [#20568](https://github.com/npm/npm/pull/20568) Add support for `npm audit --json` to print the report in JSON format.  ([@finnp](https://github.com/finnp))\r\n* [`85b86169d`](https://github.com/npm/npm/commit/85b86169d9d0423f50893d2ed0c7274183255abe) [#20570](https://github.com/npm/npm/pull/20570) Include number of audited packages in `npm install` summary output.  ([@zkat](https://github.com/zkat))\r\n* [`957cbe275`](https://github.com/npm/npm/commit/957cbe27542d30c33e58e7e6f2f04eeb64baf5cd) `npm-audit-report@1.2.1`: Overhaul audit install and detail output format.  The new format is terser and fits more closely into the visual style of the CLI, while still providing you with the important bits of information you need.  They also include a bit more detail on the footer about what actions you can take!  ([@zkat](https://github.com/zkat))\r\n\r\n### NEW FEATURE: GIT DEPS AND `npm init <pkg>`!\r\n\r\nAnother exciting change that came with `npm@6` was the new `npm init` command that allows for community-authored generators.  That means you can, for example, do `npm init react-app` and it'll one-off download, install, and run [`create-react-app`](https://npm.im/create-react-app) for you, without requiring or keeping around any global installs.  That is, it basically just calls out to [`npx`](ht","is_prerelease":false},"readme":true,"readme_zh":false,"news":[],"stale":false,"snapshot_at":"2026-11-16T09:23:14Z","history_start":"2026-09-06"}