OSS TanbouSign in with GitHub

Manage JavaScript project dependencies and published packages from the command line

About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
10,170
Primary language
JavaScript
License
Not determined
Repository last updated
Oct 1, 2026
On this page

Overview

npm CLI is a package manager for installing JavaScript packages, locking dependencies, running project scripts, and publishing packages to a registry. It ships with Node.js and can also use compatible third-party registries.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Manage dependencies and reproducible installation state

It installs dependencies declared in package.json and records the resolved graph in package-lock.json, helping teams and CI reproduce the same dependency tree.

Sources: [1][2]

Give project tasks a common command interface

Scripts in package.json provide a shared entry point for project-specific tests and builds. The CLI also searches for packages, inspects package information, and publishes releases.

Sources: [2]

Best fit

Use the standard Node.js and JavaScript workflow

Because npm ships with Node.js, it fits JavaScript projects ranging from libraries to applications. npm workspaces can manage multiple packages from one root.

Sources: [1][2]

Before adoption

Review script execution and service boundaries

Dependency installation can execute package lifecycle scripts. When evaluating untrusted dependencies, limit execution first, for example with --ignore-scripts. The CLI application uses Artistic License 2.0, while dependencies, the public registry, and the website have their own terms. Version 12.2.0 requires Node.js ^22.22.2, ^24.15.0, or >=26.0.0.

Sources: [4][2][3]

Official sources

  1. [1]npm/cli README at v12.2.0(2026-10-04)
  2. [2]npm CLI documentation(2026-10-04)
  3. [3]npm/cli package manifest at v12.2.0(2026-10-04)
  4. [4]npm/cli LICENSE at v12.2.0(2026-10-04)
  5. [5]npm CLI v12.2.0 release(2026-10-04)
Supplemental curator note

Evaluate both lockfile reproducibility and which scripts may run during installation. The CLI and npm registry have separate terms, so include private-registry and publishing requirements in the comparison.

Try it in 3 steps

  1. 1

    Create an evaluation package

    Use the installed npm to create package.json in an empty directory. This workflow was executed with npm 11.16.0; it does not claim that npm v12.2.0 was installed.

    mkdir npm-cli-demo && cd npm-cli-demo && npm init --yes
  2. 2

    Generate a lockfile safely

    Exercise lockfile generation without running dependency lifecycle scripts.

    npm install --package-lock-only --ignore-scripts
  3. 3

    Inspect package metadata

    Confirm that npm reads the name and version from the generated package.json.

    npm pkg get name version
Check the official README

Growth

Growth trends · Last 30 days

10,170 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days)
8
Open PRs
171

Development activity is still being collected.

Built with

Categories and tags

GitHub data

GitHub dataView detailed GitHub data

GitHub Topics

  • package-manager
  • npm
  • nodejs
  • javascript
  • tools
  • npm-cli
Stars
10,170
Forks
4,807
Watchers
242
Open issues
636
Contributors
1,021
Owner type
Organization
Primary language
JavaScript
License
Not determined
Repository last updated
Oct 1, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?