Error: Cannot find matching keyid (Corepack signature verification)
An older Corepack couldn’t verify the signature of a newly published pnpm/yarn release after npm rotated its signing keys.
Seen on:
npm
Meaning
Corepack versions bundled with older Node 18/20 releases don’t know the new keys (2025 rotation).
Common causes
- Outdated Corepack bundled with Node
- packageManager pin downloading a new release
⚡ Quick fix
- Update Corepack: npm install -g corepack@latest
- Upgrade Node
- Temporarily set COREPACK_INTEGRITY_KEYS=0
Detailed fix by platform
npm
npm install -g corepack@latest && corepack enable
How to diagnose
- Version — corepack --version
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 2 Oct 2026