raineorshine/npm-check-updates

Find newer versions of package dependencies than what your package.json allows

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 36 minutes ago
Added to GitGenius on September 6th, 2026
Created on September 7th, 2013
Open Issues & Pull Requests: 34 (+0)
GitHub issues: Enabled
Number of forks: 372
Total Stargazers: 10,311 (+0)
Total Subscribers: 61 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.0 hours
Mean response time: 40.9 days
90th percentile: 4.3 days
Tracked items: 212

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 8% of issues opened in the past year have been closed. Three people close 82% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 16
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 949 days
Stale 30+ days: 8
Stale 90+ days: 2

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (59)
  • enhancement (46)
  • faq (23)
  • unable-to-reproduce (12)
  • dependency-bug (10)
  • out-of-scope (8)
  • awaiting reply (6)
  • duplicate (4)

Detailed Description

npm-check-updates is a command-line tool that finds and applies newer versions of package dependencies to your package.json file while respecting semantic versioning constraints.

The tool solves the problem of keeping dependencies current without manual version checking. It scans your package.json, queries available versions for each dependency, and identifies upgrades that respect your existing versioning policies—for example, converting "react": "^18.3.1" to "react": "^19.2.7" while maintaining the caret constraint. The tool only modifies package.json itself; you run npm install separately to fetch the actual packages. It works across npm, yarn, pnpm, deno, and bun ecosystems and offers both CLI and programmatic module interfaces.

The tool suits developers who want to stay current with dependencies but need control over which upgrades to apply. Interactive mode lets you select specific packages to update, with sensible defaults that pre-select patch and minor upgrades while flagging major versions for review. The README does not compare it to alternatives. It provides filtering options to target specific packages or exclude others using wildcards, globs, or regex patterns. Color-coded output distinguishes patch upgrades in green, minor in cyan, and major in red.

The project maintains active development with regular updates addressing edge cases and expanding compatibility. The codebase is written in TypeScript and distributed as pure ESM while remaining usable from CommonJS. The tool enforces specific Node.js version requirements and keeps pace with changes in the npm ecosystem.