# Install corepack with Homebrew, Nix, pacman, zypper

Package acting as bridge between Node projects and their package managers. Version 0.35.0 via Homebrew; verified 2026-05-15. Also installable with nix: nix profile install nixpkgs#corepack.

## Install

```sh
sudo av install brew:corepack
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install corepack
```

  Evidence: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#corepack
```

  Evidence: nixpkgs package indexes: pkgs/by-name/co/corepack/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

- pacman (92%):

```sh
sudo pacman -S corepack
```

  Evidence: Arch Linux sync databases: corepack from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

- zypper (92%):

```sh
sudo zypper install corepack-default
```

  Evidence: openSUSE Tumbleweed package metadata: corepack-default from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst

## Package facts

- **Package key:** brew:corepack
- **Package manager:** Homebrew
- **Version:** 0.35.0
- **Source summary:** Package acting as bridge between Node projects and their package managers
- **Homepage:** <https://github.com/nodejs/corepack>
- **Last updated:** 2026-05-15T21:25:02Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- corepack (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 0.35.0
## Project history and usage

Corepack is a Node.js package-manager shim and version manager that bridges a project to the package manager version it declares. It is most associated with Yarn and pnpm workflows, where the package.json packageManager field can select the expected tool and version.

### Project history

The nodejs/corepack repository was created in 2020. Its README describes Corepack as a zero-runtime-dependency Node.js script that lets projects use Yarn, npm, and pnpm without installing each package manager globally.

Corepack was distributed with Node.js from version 14.19.0 up to, but not including, 25.0.0. That bundling made it a notable piece of Node's package-management story even for users who never installed the standalone package directly.

### Adoption history

Corepack adoption followed the rise of package-manager pinning in JavaScript projects. Instead of relying on whatever yarn or pnpm binary happened to be globally installed, a project could declare the package manager in package.json and let Corepack fetch or activate a compatible version.

### How it is used

Common usage is to enable Corepack, then run package-manager commands such as yarn install or pnpm install in a project. Corepack reads package.json metadata, resolves the intended package manager version, and manages cached package-manager binaries rather than acting as the dependency installer itself.

### Why package nerds care

Corepack is package-nerd infrastructure about package managers themselves. It moved version pinning for Yarn and pnpm closer to the Node runtime and made the package.json packageManager field operational, which changed how distributions and CI images think about globally installed JavaScript package tools.

### Timeline

- 2020: nodejs/corepack repository created.
- 2021-2022: Corepack distributed with Node.js 14.19.0 and newer supported Node release lines.
- 2026: v0.35.0 released upstream as Node.js no longer bundles Corepack starting with the Node 25 line.

### Related projects

- Corepack is related to Node.js, npm, Yarn, pnpm, the package.json packageManager field, and JavaScript CI/runtime distribution images.

### Sources

- <https://github.com/nodejs/corepack>
- <https://github.com/nodejs/corepack#readme>
- <https://github.com/nodejs/corepack/releases>
- <https://nodejs.org/api/corepack.html>
- <https://nodejs.org/api/packages.html#packagemanager>


## Security Notes

infrastructure mutation or orchestration signal.

- **Geiger risk:** orange / medium
- infrastructure mutation or orchestration signal


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: package.json
## Other Package-Manager Records

- Nix - corepack: normalized package name match | nixpkgs package indexes: pkgs/by-name/co/corepack/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- pacman - corepack - 0.34.6-1: normalized package name match | Arch Linux sync databases: corepack from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Zero-runtime-dependency Node.js script | https://github.com/nodejs/corepack
- zypper - corepack-default - 6.1-5.4: normalized package name match | openSUSE Tumbleweed package metadata: corepack-default from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Default version of corepack | https://github.com/AdamMajer/nodejs-packaging


## Combined YAML source

View the package source record on GitHub. [combined/corepack.yml](https://github.com/mxcl/pkgdb/blob/main/combined/corepack.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph