npm package scope, access level, and visibility | npm Docs

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

Scope	Access level	Can view and download	Can write (publish)
Org	Private	Members of a team in the organization with read access to the package	Members of a team in the organization with read and write access to the package
Org	Public	Everyone	Members of a team in the organization with read and write access to the package
User	Private	The package owner and users who have been granted read access to the package	The package owner and users who have been granted read and write access to the package
User	Public	Everyone	The package owner and users who have been granted read and write access to the package
Unscoped	Public	Everyone	The 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.

Sunbelt Computer Software

PL/B Language Development and Support

npm package scope, access level, and visibility

npm Package Access Matrix

Table of contents