Contribution

• I'd be willing to implement this feature (contributing guide)

Describe the user story

Corepack introduced a feature called "auto-pinning" in 0.26.0, which writes the package manager version to a packageManager field in package.json:

• @mcollina's original issue Provide reproducible build by default nodejs/corepack#399
• feat: Pins the package manager as it's used for the first time nodejs/corepack#413

Two things will reduce the usage of this auto-pinning feature:

• Corepack disabled auto-pinning by default in 0.33.0
• Corepack will be removed from Node.js v25+

Currently, pnpm auto-pins (without a hash) in packageManager in package.json on pnpm init.

For existing projects, I don't see functionality to add a packageManager field to package.json using only pnpm.

Is there any appetite for a feature to auto-pin packageManager (only if it doesn't exist) on usage of mutative commands such as:

• pnpm add
• pnpm remove
• others?

(if controversial, disabled by default)

Describe the solution you'd like

package.json

{
  "dependencies": {}
}

pnpm add sharp with the package.json above will yield:

{
  "dependencies": {
    "sharp": "^0.34.3"
  },
  "packageManager": "pnpm@10.13.1"
}

Alternatives considered

A separate, focused command like pnpm pin or something, that would only write packageManager to package.json

Describe the drawbacks of your solution

Community objection to auto-pinning, such as this issue:

• COREPACK_ENABLE_AUTO_PIN should default to 0 nodejs/corepack#485

Describe alternatives you've considered

Manually setting packageManager in package.json using npm pkg set packageManager="pnpm@$(pnpm -v)"