File Explorer

1.TH "NPM-OWNER" "1" "February 2026" "NPM@11.11.0" ""2.SH "NAME"3\fBnpm-owner\fR - Manage package owners4.SS "Synopsis"5.P6.RS 27.nf8npm owner add <user> <package-spec>9npm owner rm <user> <package-spec>10npm owner ls <package-spec>11 12alias: author13.fi14.RE15.SS "Description"16.P17Manage ownership of published packages.18.RS 019.IP \(bu 420ls: List all the users who have access to modify a package and push new versions. Handy when you need to know who to bug for help.21.IP \(bu 422add: Add a new user as a maintainer of a package. This user is enabled to modify metadata, publish new versions, and add other owners.23.IP \(bu 424rm: Remove a user from the package owner list. This immediately revokes their privileges.25.RE 026 27.P28Note that there is only one level of access. Either you can modify a package, or you can't. Future versions may contain more fine-grained access levels, but that is not implemented at this time.29.P30If you have two-factor authentication enabled with \fBauth-and-writes\fR (see npm help npm-profile) then you'll need to go through a second factor flow when changing ownership or include an otp on the command line with \fB--otp\fR.31.SS "Configuration"32.SS "\fBregistry\fR"33.RS 034.IP \(bu 435Default: "https://registry.npmjs.org/"36.IP \(bu 437Type: URL38.RE 039 40.P41The base URL of the npm registry.42.SS "\fBotp\fR"43.RS 044.IP \(bu 445Default: null46.IP \(bu 447Type: null or String48.RE 049 50.P51This is a one-time password from a two-factor authenticator. It's needed when publishing or changing package permissions with \fBnpm access\fR.52.P53If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one.54.SS "\fBworkspace\fR"55.RS 056.IP \(bu 457Default:58.IP \(bu 459Type: String (can be set multiple times)60.RE 061 62.P63Enable running a command in the context of the configured workspaces of the current project while filtering by running only the workspaces defined by this configuration option.64.P65Valid values for the \fBworkspace\fR config are either:66.RS 067.IP \(bu 468Workspace names69.IP \(bu 470Path to a workspace directory71.IP \(bu 472Path to a parent workspace directory (will result in selecting all workspaces within that folder)73.RE 074 75.P76When set for the \fBnpm init\fR command, this may be set to the folder of a workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.77.P78This value is not exported to the environment for child processes.79.SS "\fBworkspaces\fR"80.RS 081.IP \(bu 482Default: null83.IP \(bu 484Type: null or Boolean85.RE 086 87.P88Set to true to run the command in the context of \fBall\fR configured workspaces.89.P90Explicitly setting this to false will cause commands like \fBinstall\fR to ignore workspaces altogether. When not set explicitly:91.RS 092.IP \(bu 493Commands that operate on the \fBnode_modules\fR tree (install, update, etc.) will link workspaces into the \fBnode_modules\fR folder. - Commands that do other things (test, exec, publish, etc.) will operate on the root project, \fIunless\fR one or more workspaces are specified in the \fBworkspace\fR config.94.RE 095 96.P97This value is not exported to the environment for child processes.98.SS "See Also"99.RS 0100.IP \(bu 4101npm help "package spec"102.IP \(bu 4103npm help profile104.IP \(bu 4105npm help publish106.IP \(bu 4107npm help registry108.IP \(bu 4109npm help adduser110.RE 0111