npm

npm is a JavaScript package registry and command-line tool for publishing and using shared code. The Registry and CLI are free for public package use, and the Free plan gives public package authors unlimited public packages. npm accepts package.json folders, gzipped tarballs, URLs, name-and-version or name-and-tag references, and Git URLs. Its package tools support dependency resolution, lockfiles, workspaces, private registry authentication, and offline installation. It runs on Linux, macOS, Windows, and other operating systems through Node.js installers or version managers. For private packages, the Paid user account plan costs $7 a month. Pro costs $7 a month for individual creators and includes unlimited private packages with package-based permissions. Teams costs $7 per user per month and offers unlimited private packages with team-based permissions. Organizations can manage members, teams, roles, permissions, and package access. All plans include basic support and automatic security warnings. Paid billing starts when card information is submitted, and the first month is charged immediately.

npm serves public package sharing without a plan charge and offers paid options for private packages and permissions. Consider the immediate first-month charge when starting a paid plan.

npm may suit JavaScript developers who publish, find, or install packages. Public package authors can use the free Registry, while creators and organizations can choose paid plans for private packages and access controls.

npm is the central registry and command-line workflow for sharing and installing JavaScript packages. It suits JavaScript developers who need broad public distribution, reproducible project dependencies, or private package publishing. The key trade-off is clear: public work is free, while private publishing and collaboration require a monthly plan.

Overview

GitHub operates both the npm Registry and npm CLI. The public Registry contains more than two million packages and is relied upon by more than 17 million developers worldwide, giving npm unusual reach for finding and distributing JavaScript code. That scale is most valuable when a project depends on established community packages or when a publisher wants a large audience for reusable work.

The free Registry and CLI are available to the community, and the Free plan allows unlimited public packages. That makes npm a strong default for open distribution, but it does not make private publishing free. Paid billing begins as soon as a credit card is submitted, with the first month charged immediately.

For broader comparisons, see our JavaScript Package Managers, Package Managers and Package Registries lists.

Key features

Package formats and dependency control

npm accepts package.json folders, gzipped tarballs, URLs, name-and-version references, name-and-tag references and Git URLs. That range accommodates conventional releases as well as direct or source-based inputs. Dependency resolution, lockfile support and workspaces cover ordinary application installs and multi-package project structures; lockfiles are particularly useful when a team needs repeatable dependency selections.

Private registry authentication and offline installation extend the workflow beyond public downloads. npm is focused on JavaScript development and code sharing, so its strengths are most relevant to Node.js and related JavaScript projects rather than teams seeking a language-neutral artifact system.

Security and collaboration

Free, Pro and Teams plans include automatic security warnings and unlimited public packages. npm documentation covers two-factor authentication for accounts, organizations, publishing and settings changes, giving administrators several points at which to require stronger account protection.

Organizations can manage members, teams, roles, permissions and package access. Pro applies permissions at the package level, while Teams applies them through teams, a better fit when access follows organizational groups. Documentation also covers private packages in CI/CD workflows and Docker use, which helps teams incorporate private dependencies into automated delivery.

Pricing

The Free plan is the right economic choice for public libraries and open-source publishing, since its public-package allowance is unlimited. It gives up private publishing, so a project with proprietary modules must move to a paid user account or Pro. The paid user account covers private installation and publishing at the same $7 monthly price, while Pro adds package-based permissions for individual creators. Teams costs per user, but its team-based permissions make it more suitable when several people or groups share private packages. Basic support is included with every plan.

There is no trial period stated for paid plans. Because the first month is charged immediately when card details are submitted, budget for the subscription from the moment of activation rather than expecting a delayed start.

Platforms

npm runs on Linux, macOS and Windows. Other operating systems can be supported through Node.js installers or version managers, making the CLI less dependent on a single desktop environment. The same cross-platform reach is useful for mixed development teams and CI systems built around Node.js.

Who it's for

Choose npm if you publish JavaScript packages, consume a large public ecosystem, or need dependency resolution, lockfiles and workspaces in one familiar workflow. The Free plan is especially well suited to public package authors. Individual developers with proprietary modules should look at the $7 Pro option when package-level access control matters; organizations should use Teams when permissions need to follow team membership.

Look elsewhere if your priority is a free private registry, a package system centered on another language, or a runtime-and-toolkit bundle rather than a JavaScript registry and CLI.

Pros and cons

Pros

• Unlimited public packages on the Free plan, removing a publication cap for open-source authors.
• A registry of more than two million packages and a community of more than 17 million developers, providing broad distribution and discovery.
• Dependency resolution, lockfiles, workspaces, offline installation and private-registry authentication cover varied project workflows.
• Automatic security warnings and documented two-factor controls add practical safeguards across free and paid plans.
• Pro and Teams both allow unlimited private packages, with permissions shaped for individuals or organizations.

Cons

• Private publishing is not included in the Free plan and starts at a recurring $7 monthly charge.
• Teams is billed per user, so organization costs rise with each additional account.
• Paid billing starts immediately after credit-card submission, leaving no stated trial period.
• The product is explicitly JavaScript-focused, making it a less natural fit for teams seeking a general package platform.

Alternatives

pnpm is a free package manager for readers who want another JavaScript-oriented option across Android, Linux, macOS and Windows.

Deno Sandbox is worth considering when an API- or web-based sandbox is the priority; its free plan includes 1M requests per month and 10 hours of active CPU, with usage billing beyond that model.

JSPM suits readers seeking free, open-source import-map package management and CDN services across desktop, web, API and self-hosted environments.

vlt is an alternative for a self-hosted or web registry with a free tier offering 2GB of storage and delivery, upstream proxying, user management and token management.

Bun is the better direction when you want an open-source, MIT-licensed JavaScript runtime and toolkit rather than a registry-centered tool.

Pantry offers public packages, 30 days of full analytics and 50MB of artifacts on its free plan, which may appeal to publishers focused on those allowances.

Yarn is a free, open-source package manager with no paid plans or usage limits stated.

Verdict

npm is the strongest default for JavaScript developers who value the reach of a massive public registry and need mature dependency, workspace and publishing workflows. Choose Free for unlimited public packages, Pro for individual private publishing with package permissions, or Teams when organizational access must be managed by groups. Look elsewhere if private use must remain free or if your work is better served by a broader runtime, sandbox or non-JavaScript package system.