npm CLI supports dependency installation, script execution, and publishing workflows across the JavaScript ecosystem.
Reliability breakdown
Component scores measured daily from GitHub activity (2026-07-18).
Activity on 34 of 90 tracked days in the last 90 and 20 of 30 in the last 30.
Merged 105 of 136 PRs opened and closed 61 of 63 issues opened over the last 90 tracked days — PR flow carries 55% of this component, issue flow 45%.
161 releases in the last 180 days, 94 in the last 90 and 35 in the last 30 — a steady cadence scores highest.
Last push 4 days ago — freshness decays as pushes age (roughly halves every 83 days without a push).
580 open issues against 9,958 stars — about 58 open issues per 1,000 stars. Lighter backlogs score higher.
Modeled — lower is better; concentration of commits in few maintainers. Contributors graph
Topics
Jump into the topic listings this repository belongs to.
npm CLI is the command-line package manager used across the JavaScript ecosystem for installing dependencies, running scripts, and publishing packages. It is central to many frontend and backend workflows because it connects projects to the wider package registry and automation conventions. For most JavaScript developers, npm CLI is a core part of daily development and release processes.
Join the conversation
Share what you know about cli — write a review from your real experience, ask an implementation question, or publish a post about how you use it.
Share your experience
Explain what worked, what broke down, and what another team should know before adopting cli.
Project Q&A
Browse implementation threads tied directly to npm/cli. Each question links through to the full answer page.
Be the first to ask how teams run cli in production. Every question you post becomes a durable, searchable answer page other developers can find.
Ask the first questionRelated posts
These posts come from the same topic surface as this repo, so readers can move from project evaluation into practical writeups and migration notes without leaving context.
Share how your team uses cli — a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.
Write the first post