File Explorer

1.TH "NPM-ACCESS" "1" "February 2026" "NPM@11.11.0" ""2.SH "NAME"3\fBnpm-access\fR - Set access level on published packages4.SS "Synopsis"5.P6.RS 27.nf8npm access list packages \[lB]<user>|<scope>|<scope:team>\[rB] \[lB]<package>\[rB]9npm access list collaborators \[lB]<package> \[lB]<user>\[rB]\[rB]10npm access get status \[lB]<package>\[rB]11npm access set status=public|private \[lB]<package>\[rB]12npm access set mfa=none|publish|automation \[lB]<package>\[rB]13npm access grant <read-only|read-write> <scope:team> \[lB]<package>\[rB]14npm access revoke <scope:team> \[lB]<package>\[rB]15.fi16.RE17.P18Note: This command is unaware of workspaces.19.SS "Description"20.P21Used to set access controls on private packages.22.P23For all of the subcommands, \fBnpm access\fR will perform actions on the packages in the current working directory if no package name is passed to the subcommand.24.RS 025.IP \(bu 426grant / revoke: Add or remove the ability of users and teams to have read-only or read-write access to a package.27.RE 028 29.SS "Details"30.P31\fBnpm access\fR always operates directly on the current registry, configurable from the command line using \fB--registry=<registry url>\fR.32.P33Unscoped packages are \fIalways public\fR.34.P35Scoped packages \fIdefault to restricted\fR, but you can either publish them as public using \fBnpm publish --access=public\fR, or set their access as public using \fBnpm access set status=public\fR after the initial publish.36.P37You must have privileges to set the access of a package:38.RS 039.IP \(bu 440You are an owner of an unscoped or scoped package.41.IP \(bu 442You are a member of the team that owns a scope.43.IP \(bu 444You have been given read-write privileges for a package, either as a member of a team or directly as an owner.45.RE 046 47.P48If you have two-factor authentication enabled then you'll be prompted to provide a second factor, or may use the \fB--otp=...\fR option to specify it on the command line.49.P50If your account is not paid, then attempts to publish scoped packages will fail with an HTTP 402 status code (logically enough), unless you use \fB--access=public\fR.51.P52Management of teams and team memberships is done with the \fBnpm team\fR command.53.SS "Configuration"54.SS "\fBjson\fR"55.RS 056.IP \(bu 457Default: false58.IP \(bu 459Type: Boolean60.RE 061 62.P63Whether or not to output JSON data, rather than the normal output.64.RS 065.IP \(bu 466In \fBnpm pkg set\fR it enables parsing set values with JSON.parse() before saving them to your \fBpackage.json\fR.67.RE 068 69.P70Not supported by all npm commands.71.SS "\fBotp\fR"72.RS 073.IP \(bu 474Default: null75.IP \(bu 476Type: null or String77.RE 078 79.P80This is a one-time password from a two-factor authenticator. It's needed when publishing or changing package permissions with \fBnpm access\fR.81.P82If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one.83.SS "\fBregistry\fR"84.RS 085.IP \(bu 486Default: "https://registry.npmjs.org/"87.IP \(bu 488Type: URL89.RE 090 91.P92The base URL of the npm registry.93.SS "See Also"94.RS 095.IP \(bu 496\fB\[rs]fBlibnpmaccess\[rs]fR\fR \fI\(lahttps://npm.im/libnpmaccess\(ra\fR97.IP \(bu 498npm help team99.IP \(bu 4100npm help publish101.IP \(bu 4102npm help config103.IP \(bu 4104npm help registry105.RE 0106