nodejs/corepack

Package manager version manager for Node.js projects

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 24 minutes ago
Added to GitGenius on September 18th, 2026
Created on March 12th, 2020
Open Issues & Pull Requests: 141 (+0)
GitHub issues: Enabled
Number of forks: 279
Total Stargazers: 3,806 (+0)
Total Subscribers: 33 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.2 hours
Mean response time: 22.7 days
90th percentile: 60.6 days
Tracked items: 156

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 7% of issues opened in the past year have never received a reply. 97% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 60% of issues opened in the past year have been closed, leaving a working backlog. Three people close 73% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 66
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 632 days
Stale 30+ days: 56
Stale 90+ days: 44

Recent activity

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

Top labels

  • good first issue (1)

Detailed Description

Corepack is a package manager version manager for Node.js projects that ensures teams use the correct version of npm, pnpm, or yarn as specified in their project configuration.

The problem Corepack solves is version inconsistency across development environments and CI/CD pipelines. Different team members or machines may have different package manager versions installed, leading to inconsistent behavior and lock file changes. Corepack works by reading the package manager version requirement from the project's package.json file and automatically downloading and using that exact version, transparently intercepting calls to npm, pnpm, and yarn commands.

Corepack suits projects where enforcing a specific package manager version across all contributors is important for reproducibility. It is particularly valuable for teams using monorepos or projects with strict dependency management requirements. The tool is built into Node.js distributions, so it requires no separate installation for most users. Projects that need to pin their package manager version should declare it in package.json using the packageManager field, and Corepack will handle the rest without requiring developers to manually manage multiple package manager installations.

Development activity on the project shows consistent engagement with pull requests being reviewed and merged regularly. The maintainers respond to issues and incorporate community contributions into the codebase. The project receives updates that address both bug fixes and feature enhancements, indicating active stewardship of the tool's functionality and compatibility with evolving Node.js and package manager ecosystems.