package-scope-access-level-and-visibility.mdx · cryptotaxi247/documentation-1

dependabot/npm_and_yarn/main/copy-to-clipboard-4.0.2

mdx 30 lines 1.43 KB

Raw

1	---
2	title: npm package scope, access level, and visibility
3	---
4
5	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.
6
7	<Note>
8
9	Note: To create organization-scoped packages, you must first create an organization. For more information, see "[Creating an organization](https://docs.npmjs.com/creating-an-organization)".
10
11	</Note>
12
13	## npm Package Access Matrix
14
15	<DataTable
16	headers={["Scope", "Access level", "Can view and download", "Can write (publish)"]}
17	rows={[
18	["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"],
19	["Org", "Public", "Everyone", "Members of a team in the organization with read and write access to the package"],
20	["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"],
21	["User", "Public", "Everyone", "The package owner and users who have been granted read and write access to the package"],
22	["Unscoped", "Public", "Everyone", "The package owner and users who have been granted read and write access to the package"]
23	]}
24	/>
25
26	<Note>
27
28	Note: Only user accounts can create and manage unscoped packages. Organizations can only manage scoped packages.
29
30	</Note>