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

NAME

6       npm-access - Set access level on published packages
7
8   Synopsis
9         npm access public [<package>]
10         npm access restricted [<package>]
11
12         npm access grant <read-only|read-write> <scope:team> [<package>]
13         npm access revoke <scope:team> [<package>]
14
15         npm access 2fa-required [<package>]
16         npm access 2fa-not-required [<package>]
17
18         npm access ls-packages [<user>|<scope>|<scope:team>]
19         npm access ls-collaborators [<package> [<user>]]
20         npm access edit [<package>]
21
22   Description
23       Used to set access controls on private packages.
24
25       For  all  of  the  subcommands,  npm access will perform actions on the
26       packages in the current working directory if no package name is  passed
27       to the subcommand.
28
29       • public  /  restricted: Set a package to be either publicly accessible
30         or restricted.
31
32       • grant / revoke: Add or remove the ability of users and teams to  have
33         read-only or read-write access to a package.
34
35       • 2fa-required / 2fa-not-required: Configure whether a package requires
36         that anyone publishing it have two-factor authentication  enabled  on
37         their account.
38
39       • ls-packages: Show all of the packages a user or a team is able to ac‐
40         cess, along with the access level, except for read-only public  pack‐
41         ages (it won't print the whole registry listing)
42
43       • ls-collaborators:  Show  all  of the access privileges for a package.
44         Will only show permissions for packages to which you  have  at  least
45         read  access.  If  <user>  is passed in, the list is filtered only to
46         teams that user happens to belong to.
47
48       • edit: Set the access privileges for a package at once using $EDITOR.
49
50
51   Details
52       npm access always operates directly on the  current  registry,  config‐
53       urable from the command line using --registry=<registry url>.
54
55       Unscoped packages are always public.
56
57       Scoped  packages default to restricted, but you can either publish them
58       as public using npm publish --access=public, or  set  their  access  as
59       public using npm access public after the initial publish.
60
61       You must have privileges to set the access of a package:
62
63       • You are an owner of an unscoped or scoped package.
64
65       • You are a member of the team that owns a scope.
66
67       • You  have been given read-write privileges for a package, either as a
68         member of a team or directly as an owner.
69
70
71       If you have two-factor authentication enabled then you'll have to  pass
72       in an otp with --otp when making access changes.
73
74       If  your  account is not paid, then attempts to publish scoped packages
75       will fail with an HTTP 402 status code (logically enough),  unless  you
76       use --access=public.
77
78       Management of teams and team memberships is done with the npm team com‐
79       mand.
80
81   See Also
82       • libnpmaccess https://npm.im/libnpmaccess
83
84       • npm help team
85
86       • npm help publish
87
88       • npm help config
89
90       • npm help registry
91
92
93
94
95                                  April 2021                     NPM-ACCESS(1)
Impressum