Skip to content
npm Docs
npmjs.comStatusSupport
About npm
Getting started
Packages and modules
Integrations
Organizations
npm Enterprise
npm CLI
CLI Commands
npmnpm accessnpm addusernpm auditnpm binnpm bugsnpm cachenpm cinpm completionnpm confignpm dedupenpm deprecatenpm diffnpm dist-tagnpm docsnpm doctornpm editnpm execnpm explainnpm explorenpm find-dupesnpm fundnpm helpnpm help-searchnpm hooknpm initnpm installnpm install-ci-testnpm install-testnpm linknpm logoutnpm lsnpm orgnpm outdatednpm ownernpm packnpm pingnpm prefixnpm profilenpm prunenpm publishnpm rebuildnpm reponpm restartnpm rootnpm run-scriptnpm searchnpm set-scriptnpm shrinkwrapnpm starnpm starsnpm startnpm stopnpm teamnpm testnpm tokennpm uninstallnpm unpublishnpm unstarnpm updatenpm versionnpm viewnpm whoaminpx
Configuring npm
Using npm

npm-owner

Manage package owners
Version 7.x (Current release)
  • Version 6.x (Legacy release)
  • Version 7.x (Current release)
Table of contents
Table of contents

Synopsis

npm owner add <user> [<@scope>/]<pkg>
npm owner rm <user> [<@scope>/]<pkg>
npm owner ls [<@scope>/]<pkg>
aliases: author

Note: This command is unaware of workspaces.

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 (see npm-profile) then you'll need to include an otp on the command line when changing ownership with --otp.

See Also