| Server IP : 66.29.132.122 / Your IP : 3.145.37.250 Web Server : LiteSpeed System : Linux business142.web-hosting.com 4.18.0-553.lve.el8.x86_64 #1 SMP Mon May 27 15:27:34 UTC 2024 x86_64 User : admazpex ( 531) PHP Version : 7.2.34 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : OFF | Pkexec : OFF Directory : /proc/self/root/opt/alt/alt-nodejs12/root/lib/node_modules/npm/docs/content/cli-commands/ |
Upload File : |
--- section: cli-commands title: npm-owner description: Manage package owners --- # npm-owner(1) ## Manage package owners ### Synopsis ```bash npm owner add <user> [<@scope>/]<pkg> npm owner rm <user> [<@scope>/]<pkg> npm owner ls [<@scope>/]<pkg> aliases: author ``` ### Description Manage ownership of published packages. * ls: 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. * add: Add a new user as a maintainer of a package. This user is enabled to modify metadata, publish new versions, and add other owners. * rm: Remove a user from the package owner list. This immediately revokes their privileges. Note 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. If you have two-factor authentication enabled with `auth-and-writes` then you'll need to include an otp on the command line when changing ownership with `--otp`. ### See Also * [npm publish](/cli-commands/npm-publish) * [npm registry](/using-npm/registry) * [npm adduser](/cli-commands/npm-adduser) * [npm disputes](/using-npm/disputes)