1NPM-OWNER(1)                                                      NPM-OWNER(1)
2
3
4

NAME

6       npm-owner - Manage package owners
7
8   Synopsis
9         npm owner add <user> [<@scope>/]<pkg>
10         npm owner rm <user> [<@scope>/]<pkg>
11         npm owner ls [<@scope>/]<pkg>
12
13         aliases: author
14
15       Note: This command is unaware of workspaces.
16
17   Description
18       Manage ownership of published packages.
19
20       • ls:  List  all the users who have access to modify a package and push
21         new versions.  Handy when you need to know who to bug for help.
22
23       • add: Add a new user as a maintainer of a package.  This user  is  en‐
24         abled to modify metadata, publish new versions, and add other owners.
25
26       • rm:  Remove a user from the package owner list.  This immediately re‐
27         vokes their privileges.
28
29
30       Note that there is only one level of access.  Either you can  modify  a
31       package,  or  you can't.  Future versions may contain more fine-grained
32       access levels, but that is not implemented at this time.
33
34       If you have two-factor authentication enabled with auth-and-writes (see
35       npm help npm-profile) then you'll need to include an otp on the command
36       line when changing ownership with --otp.
37
38   Configuration
39       <!-- AUTOGENERATED CONFIG DESCRIPTIONS  START  -->  <!--  automatically
40       generated,  do  not edit manually --> <!-- see lib/utils/config/defini‐
41       tions.js -->
42
43   registry
44       • Default: "https://registry.npmjs.org/"
45
46       • Type: URL
47
48
49       The base URL of the npm registry.  <!-- automatically generated, do not
50       edit manually --> <!-- see lib/utils/config/definitions.js -->
51
52
53   otp
54       • Default: null
55
56       • Type: null or String
57
58
59       This  is  a  one-time  password  from  a two-factor authenticator. It's
60       needed when publishing or changing package permissions with npm access.
61
62       If not set, and a registry  response  fails  with  a  challenge  for  a
63       one-time  password,  npm will prompt on the command line for one.  <!--
64       automatically  generated,  do  not   edit   manually   -->   <!--   see
65       lib/utils/config/definitions.js -->
66
67       <!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
68
69
70   See Also
71       • npm help profile
72
73       • npm help publish
74
75       • npm help registry
76
77       • npm help adduser
78
79
80
81
82                                 January 2022                     NPM-OWNER(1)
Impressum