npm consists of three distinct components:

* the website

* the Command Line Interface (CLI)

* the registry

- the website

- the Command Line Interface (CLI)

- the registry

Use the [*website*](https://npmjs.com) to discover packages, set up profiles, and manage other aspects of your npm experience. For example, you can set up [organizations](https://www.npmjs.com/features) to manage access to public or private packages.

Use the [_website_](https://npmjs.com) to discover packages, set up profiles, and manage other aspects of your npm experience. For example, you can set up [organizations](https://www.npmjs.com/features) to manage access to public or private packages.

The [*CLI*](https://docs.npmjs.com/cli/npm) runs from a terminal, and is how most developers interact with npm.

The [*registry*](https://docs.npmjs.com/misc/registry) is a large public database of JavaScript software and the meta-information surrounding it.

The [_CLI_](https://docs.npmjs.com/cli/npm) runs from a terminal, and is how most developers interact with npm.

The [_registry_](https://docs.npmjs.com/misc/registry) is a large public database of JavaScript software and the meta-information surrounding it.

## Use npm to . . .

* Adapt packages of code for your apps, or incorporate packages as they are.

* Download standalone tools you can use right away.

* Run packages without downloading using [npx](https://docs.npmjs.com/cli/commands/npx).

* Share code with any npm user, anywhere.

* Restrict code to specific developers.

* Create organizations to coordinate package maintenance, coding, and developers.

* Form virtual teams by using organizations.

* Manage multiple versions of code and code dependencies.

* Update applications easily when underlying code is updated.

* Discover multiple ways to solve the same puzzle.

* Find other developers who are working on similar problems and projects.

- Adapt packages of code for your apps, or incorporate packages as they are.

- Download standalone tools you can use right away.

- Run packages without downloading using [npx](https://docs.npmjs.com/cli/commands/npx).

- Share code with any npm user, anywhere.

- Restrict code to specific developers.

- Create organizations to coordinate package maintenance, coding, and developers.

- Form virtual teams by using organizations.

- Manage multiple versions of code and code dependencies.

- Update applications easily when underlying code is updated.

- Discover multiple ways to solve the same puzzle.

- Find other developers who are working on similar problems and projects.

## Getting started

## Sharing packages and collaborating with others

If you choose to share your packages publicly, there is no cost. To use and share private packages, you need to upgrade your account. To share with others, create organizations, called **[npm organizations][orgs-docs]**, and invite others to work with you, privately (for a fee) or publicly (for free).

If you choose to share your packages publicly, there is no cost. To use and share private packages, you need to upgrade your account. To share with others, create organizations, called **[npm organizations][orgs-docs]**, and invite others to work with you, privately (for a fee) or publicly (for free).

You can also use a private npm package registry like [GitHub Packages](https://github.com/features/packages) or the open source [Verdaccio](https://verdaccio.org) project. This lets you develop packages internally that are not shared publicly.

You can also use a private npm package registry like [GitHub Packages](https://github.com/features/packages) or the open source [Verdaccio](https://verdaccio.org) project. This lets you develop packages internally that are not shared publicly.

## Learn more

While relevant CLI commands are covered throughout this user documentation, the CLI includes command line help, its own [documentation section, and instant help (man pages)][cli-docs].

[orgs-docs]: /organizations

[install-npm]: /downloading-and-installing-node-js-and-npm

[cli-docs]: /cli-documentation