npm package scope, access level, and visibility

Table of contents

Visibility of npm packages depends on the scope (namespace) in which the package is contained, and the access level (private or public) set for the package.

Note: To create organization-scoped packages, you must first create an organization. For more information, see "Creating an organization".

npm Package Access Matrix

ScopeAccess levelCan view and downloadCan write (publish)
OrgPrivateMembers of a team in the organization with read access to the packageMembers of a team in the organization with read and write access to the package
OrgPublicEveryoneMembers of a team in the organization with read and write access to the package
UserPrivateThe package owner and users who have been granted read access to the packageThe package owner and users who have been granted read and write access to the package
UserPublicEveryoneThe package owner and users who have been granted read and write access to the package
UnscopedPublicEveryoneThe package owner and users who have been granted read and write access to the package

Note: Only user accounts can create and manage unscoped packages. Organizations can only manage scoped packages.

Edit this page on GitHub
4 contributorsandrewnessinjimandrewnessinjimlukekarryslukekarrysethomsonethomsonMylesBorinsMylesBorins
Last edited by andrewnessinjim on June 25, 2024

Table of contents