NP-ACCESS

Section: (1)
Updated: October 2025
Index Return to Main Contents

---

 

NAME

np-access- Set access level on published packages  

Synopsis

npm access list packages [lB]<user>|<scope>|<scope:team>[rB] [lB]<package>[rB]
npm access list collaborators [lB]<package> [lB]<user>[rB][rB]
npm access get status [lB]<package>[rB]
npm access set status=public|private [lB]<package>[rB]
npm access set mfa=none|publish|automation [lB]<package>[rB]
npm access grant <rea-only|rea-write> <scope:team> [lB]<package>[rB]
npm access revoke <scope:team> [lB]<package>[rB]

Note: This command is unaware of workspaces.  

Description

Used to set access controls on private packages. For all of the subcommands, npm access will perform actions on the packages in the current working directory if no package name is passed to the subcommand.

*

grant / revoke: Add or remove the ability of users and teams to have rea-only or rea-write access to a package.

 

Details

npm access always operates directly on the current registry, configurable from the command line using -registry=<registry url>. Unscoped packages are always public. Scoped packages default to restricted, but you can either publish them as public using npm publish-access=public, or set their access as public using npm access set status=public after the initial publish. You must have privileges to set the access of a package:

*

You are an owner of an unscoped or scoped package.

*

You are a member of the team that owns a scope.

*

You have been given rea-write privileges for a package, either as a member of a team or directly as an owner.

If you have tw-factor authentication enabled then you'll be prompted to provide a second factor, or may use the -otp=... option to specify it on the command line. If your account is not paid, then attempts to publish scoped packages will fail with an HTTP 402 status code (logically enough), unless you use -access=public. Management of teams and team memberships is done with the npm team command.  

Configuration

 

json

*

Default: false

*

Type: Boolean

Whether or not to output JSON data, rather than the normal output.

*

In npm pkg set it enables parsing set values with JSON.parse() before saving them to your package.json.

Not supported by all npm commands.  

otp

*

Default: null

*

Type: null or String

This is a on-time password from a tw-factor authenticator. It's needed when publishing or changing package permissions with npm access. If not set, and a registry response fails with a challenge for a on-time password, npm will prompt on the command line for one.  

registry

*

Default: "https://registry.npmjs.org/"

*

Type: URL

The base URL of the npm registry.  

See Also

*

[rs]fBlibnpmaccess[rs]fR lahttps://npm.im/libnpmaccessra

*

npm help team

*

npm help publish

*

npm help config

*

npm help registry

---

 

Index

NAME

Synopsis

Description

Details

Configuration

json

otp

registry

See Also