dylang/npm-check

Check for outdated, incorrect, and unused dependencies.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 32 minutes ago
Added to GitGenius on September 9th, 2026
Created on June 9th, 2014
Open Issues & Pull Requests: 232 (+0)
GitHub issues: Enabled
Number of forks: 234
Total Stargazers: 6,640 (+0)
Total Subscribers: 45 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

npm-check is a command-line tool that identifies outdated, incorrect, and unused dependencies in Node.js projects.

The tool addresses the common problem of dependency management by scanning your project to detect packages that have newer versions available, packages listed in package.json but not actually used in your code, and packages with incorrect configurations. It works by analyzing require and import statements in your codebase and comparing installed versions against the npm registry, providing direct links to package documentation to help you decide whether to update.

npm-check suits developers who want a straightforward way to maintain their dependency trees without manual checking. It works well for projects of any size and is particularly useful in CI/CD pipelines where you can set it to return a non-zero exit code when updates are needed. The tool distinguishes itself through an interactive update mode that lets you selectively upgrade packages with minimal typing, support for scoped packages and private registries, and the ability to check globally installed packages. It respects your existing npm installation and works with alternative package managers like pnpm and ied through environment variable configuration.

The project maintains active engagement with its codebase through regular updates and bug fixes. Development shows responsiveness to user-reported issues and incorporates feedback into new releases. The maintainer actively addresses compatibility concerns as the Node.js and npm ecosystems evolve, ensuring the tool continues to work reliably across different versions and configurations.