Changing package visibility

You can change the visibility of a scoped package from the website or command line.

You must be the owner of the user account or organization that owns the package in order to change package visibility.

For more information about package visibility, see "Package scope, access level, and visibility".

Making a public package private

If you want to restrict access and visibility for a public package you own, you can make the package private. When you make a package private, its access will be updated immediately and it will be removed from the website within a few minutes of the change.

Using the website

1. On the npm website, go to the package page.
2. On the package page, click Settings.
3. Under "Package Access", select "Is Package Private?"
4. Click Update package settings.

Using the command line

To make a public package private on the command line, run the following command, replacing <package-name> with the name of your package:

For more information, see the npm access documentation.

Making a private package public

Using the website

1. On the npm website, go to the package page.
2. On the package page, click Settings.
3. Under "Package Access", deselect "Is Package Private?"
4. Click Update package settings.

Using the command line

To make a private package public on the command line, run the following command, replacing <package-name> with the name of your package:

For more information, see the npm access CLI documentation.

Edit this page on GitHub

5 contributorslukekarrysZearinnanianlisaodylanatsmithethomson

Last edited by lukekarrys on October 23, 2023