FM / commands

/home/techb158/.nvm/versions/node/v16.20.2/lib/node_modules/npm/docs/content/commands/

/home/techb158/.nvm/versions/node/v16.20.2/lib/node_modules/npm/docs/content/commands

Name	Size	Mode	Actions
npm-access.md	3359	0644	edit dl rm
npm-adduser.md	2315	0644	edit dl rm
npm-audit.md	14321	0644	edit dl rm
npm-bin.md	898	0644	edit dl rm
npm-bugs.md	2963	0644	edit dl rm
npm-cache.md	2999	0644	edit dl rm
npm-ci.md	9481	0644	edit dl rm
npm-completion.md	909	0644	edit dl rm
npm-config.md	3705	0644	edit dl rm
npm-dedupe.md	8160	0644	edit dl rm
npm-deprecate.md	1737	0644	edit dl rm
npm-diff.md	8971	0644	edit dl rm
npm-dist-tag.md	5079	0644	edit dl rm
npm-docs.md	2941	0644	edit dl rm
npm-doctor.md	4760	0644	edit dl rm
npm-edit.md	1077	0644	edit dl rm
npm-exec.md	11209	0644	edit dl rm
npm-explain.md	2793	0644	edit dl rm
npm-explore.md	1004	0644	edit dl rm
npm-find-dupes.md	6064	0644	edit dl rm
npm-fund.md	3605	0644	edit dl rm
npm-help-search.md	754	0644	edit dl rm
npm-help.md	1002	0644	edit dl rm
npm-hook.md	2390	0644	edit dl rm
npm-init.md	8986	0644	edit dl rm
npm-install-ci-test.md	7763	0644	edit dl rm
npm-install-test.md	7840	0644	edit dl rm
npm-install.md	23133	0644	edit dl rm
npm-link.md	11001	0644	edit dl rm
npm-logout.md	1746	0644	edit dl rm
npm-ls.md	8202	0644	edit dl rm
npm-org.md	1967	0644	edit dl rm
npm-outdated.md	5769	0644	edit dl rm
npm-owner.md	3100	0644	edit dl rm
npm-pack.md	3442	0644	edit dl rm
npm-ping.md	767	0644	edit dl rm
npm-pkg.md	7815	0644	edit dl rm
npm-prefix.md	1240	0644	edit dl rm
npm-profile.md	3899	0644	edit dl rm
npm-prune.md	5410	0644	edit dl rm
npm-publish.md	7289	0644	edit dl rm
npm-query.md	5069	0644	edit dl rm
npm-rebuild.md	4264	0644	edit dl rm
npm-repo.md	2721	0644	edit dl rm
npm-restart.md	1469	0644	edit dl rm
npm-root.md	1080	0644	edit dl rm
npm-run-script.md	7355	0644	edit dl rm
npm-search.md	3402	0644	edit dl rm
npm-set-script.md	2397	0644	edit dl rm
npm-shrinkwrap.md	923	0644	edit dl rm
npm-star.md	1707	0644	edit dl rm
npm-stars.md	741	0644	edit dl rm
npm-start.md	1663	0644	edit dl rm
npm-stop.md	1337	0644	edit dl rm
npm-team.md	4058	0644	edit dl rm
npm-test.md	1230	0644	edit dl rm
npm-token.md	4213	0644	edit dl rm
npm-uninstall.md	4021	0644	edit dl rm
npm-unpublish.md	4370	0644	edit dl rm
npm-unstar.md	1568	0644	edit dl rm
npm-update.md	11085	0644	edit dl rm
npm-version.md	6827	0644	edit dl rm
npm-view.md	5269	0644	edit dl rm
npm-whoami.md	798	0644	edit dl rm
npm.md	5586	0644	edit dl rm
npx.md	5730	0644	edit dl rm

Edit: /home/techb158/.nvm/versions/node/v16.20.2/lib/node_modules/npm/docs/content/commands/npm-access.md (3359B)

---
title: npm-access
section: 1
description: Set access level on published packages
---

### Synopsis

```bash
npm access public [<package>]
npm access restricted [<package>]
npm access grant <read-only|read-write> <scope:team> [<package>]
npm access revoke <scope:team> [<package>]
npm access 2fa-required [<package>]
npm access 2fa-not-required [<package>]
npm access ls-packages [<user>|<scope>|<scope:team>]
npm access ls-collaborators [<package> [<user>]]
npm access edit [<package>]
```

### 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.

* public / restricted (deprecated):
  Set a package to be either publicly accessible or restricted.

* grant / revoke (deprecated):
  Add or remove the ability of users and teams to have read-only or read-write
  access to a package.

* 2fa-required / 2fa-not-required (deprecated):
  Configure whether a package requires that anyone publishing it have two-factor
  authentication enabled on their account.

* ls-packages (deprecated):
  Show all of the packages a user or a team is able to access, along with the
  access level, except for read-only public packages (it won't print the whole
  registry listing)

* ls-collaborators (deprecated):
  Show all of the access privileges for a package. Will only show permissions
  for packages to which you have at least read access. If `<user>` is passed in,
  the list is filtered only to teams _that_ user happens to belong to.

* edit (not implemented)

### 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 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 read-write privileges for a package, either as a member
  of a team or directly as an owner.

If you have two-factor authentication enabled then you'll be prompted to
provide an otp token, 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

#### `registry`

* Default: "https://registry.npmjs.org/"
* Type: URL

The base URL of the npm registry.

#### `otp`

* Default: null
* Type: null or String

This is a one-time password from a two-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 one-time
password, npm will prompt on the command line for one.

### See Also

* [`libnpmaccess`](https://npm.im/libnpmaccess)
* [npm team](/commands/npm-team)
* [npm publish](/commands/npm-publish)
* [npm config](/commands/npm-config)
* [npm registry](/using-npm/registry)

cmd: