.TH "NPM\-ACCESS" "1" "November 2023" "9.2.0"
.SH "NAME"
\fBnpm-access\fR
.SH Synopsis
<!\-\- AUTOGENERATED USAGE DESCRIPTIONS \-\->

.SH Description
.P
Used to set access controls on private packages\.
.P
For all of the subcommands, \fBnpm access\fP will perform actions on the packages
.br
in the current working directory if no package name is passed to the
.br
subcommand\.

.RS 1
.IP \(bu 2
public / restricted (deprecated):
.br
Set a package to be either publicly accessible or restricted\.
.IP \(bu 2
grant / revoke (deprecated):
.br
Add or remove the ability of users and teams to have read\-only or read\-write
.br
access to a package\.
.IP \(bu 2
2fa\-required / 2fa\-not\-required (deprecated):
.br
Configure whether a package requires that anyone publishing it have two\-factor
.br
authentication enabled on their account\.
.IP \(bu 2
ls\-packages (deprecated):
.br
Show all of the packages a user or a team is able to access, along with the
.br
access level, except for read\-only public packages (it won't print the whole
.br
registry listing)
.IP \(bu 2
ls\-collaborators (deprecated):
.br
Show all of the access privileges for a package\. Will only show permissions
.br
for packages to which you have at least read access\. If \fB<user>\fP is passed in,
.br
the list is filtered only to teams \fIthat\fR user happens to belong to\.
.IP \(bu 2
edit (not implemented)

.RE
.SH Details
.P
\fBnpm access\fP always operates directly on the current registry, configurable
.br
from the command line using \fB\-\-registry=<registry url>\fP\|\.
.P
Unscoped packages are \fIalways public\fR\|\.
.P
Scoped packages \fIdefault to restricted\fR, but you can either publish them as
.br
public using \fBnpm publish \-\-access=public\fP, or set their access as public using
.br
\fBnpm access public\fP after the initial publish\.
.P
You must have privileges to set the access of a package:

.RS 1
.IP \(bu 2
You are an owner of an unscoped or scoped package\.
.IP \(bu 2
You are a member of the team that owns a scope\.
.IP \(bu 2
You have been given read\-write privileges for a package, either as a member
.br
of a team or directly as an owner\.

.RE
.P
If you have two\-factor authentication enabled then you'll be prompted to
.br
provide an otp token, or may use the \fB\-\-otp=\.\.\.\fP option to specify it on
.br
the command line\.
.P
If your account is not paid, then attempts to publish scoped packages will
.br
fail with an HTTP 402 status code (logically enough), unless you use
.br
\fB\-\-access=public\fP\|\.
.P
Management of teams and team memberships is done with the \fBnpm team\fP command\.
.SH Configuration
<!\-\- AUTOGENERATED CONFIG DESCRIPTIONS \-\->

.SH See Also

.RS 1
.IP \(bu 2
\fBlibnpmaccess\fP
.IP \(bu 2
npm team
.IP \(bu 2
npm publish
.IP \(bu 2
npm config
.IP \(bu 2
npm registry

.RE