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.
Cannot find matching keyid 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 not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in npm
Other ways to find it
Where this error sits
Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):
🧠 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.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 15 Oct 2026