EINTEGRITY npm Origin: Build & delivery Last updated 13 Oct 2026

npm ERR! code EINTEGRITY — sha512 integrity checksum failed

A downloaded package’s hash doesn’t match the integrity value in package-lock.json — a corrupted cache, a changed tarball, or a lockfile from a different registry.

Exact message you may see integrity checksum failednpm ERR! code EINTEGRITY
Explore the map of this error Full error map →
Seen on: npm

Meaning

npm verifies every tarball against the lockfile’s integrity field. Mismatches come from a corrupted local cache, a registry mirror serving different tarballs, or lockfiles edited/merged incorrectly.

Common causes

  • Corrupted npm cache
  • Lockfile generated against a different registry/mirror
  • Bad merge in package-lock.json
  • Proxy modifying downloads

⚡ Quick fix

  1. npm cache verify (or npm cache clean --force)
  2. Delete node_modules and reinstall with npm ci
  3. Regenerate the lockfile if it was hand-merged
  4. Use the same registry for everyone (commit .npmrc)

Detailed fix by platform

npm

  1. Clean and reinstall:
    bash
    npm cache verify
rm -rf node_modules
npm ci

How to diagnose

  1. Package — Which tarball fails?
  2. Registry — Same registry as the lockfile?
  3. Cache — Does a clean cache fix it?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):

BadDigest — Upload error: checksum mismatch (BadDigest / Content-MD5 did not match / XAmzContentSHA256Mismatch) (API)BadDigestcb() never called — npm ERR! cb() never called! (npm)cb() never calledE404 — npm ERR! code E404 — 404 Not Found: package@version is not in this registry (npm)E404ERESOLVE — npm ERR! code ERESOLVE — unable to resolve dependency tree (npm)ERESOLVEERR_PNPM_OUTDATED_LOCKFILE — ERR_PNPM_OUTDATED_LOCKFILE Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with package.json (npm)ERR_PNPM_OUTDATED_LOC…Invalid Version — npm ERR! Invalid Version: (semver parse error) (npm)Invalid Versionnpm ci no lockfile — npm ERR! The `npm ci` command can only install with an existing package-lock.json or npm-shrinkwrap.json (npm)npm ci no lockfilenpm ci out of sync — npm ERR! `npm ci` can only install packages when your package.json and package-lock.json are in sync (npm)npm ci out of syncEINTEGRITY

Explore the map of this error Full error map →

🧠 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.