Analyze an npm package-lock.json, yarn.lock, or pnpm-lock.yaml: total package count, duplicated package versions with who pulled in each, dev/prod split, registry breakdown, and the largest dependency subtree. All parsing happens client-side.
Paste an npm package-lock.json, yarn.lock, or pnpm-lock.yaml to see duplicate-version packages, dev/prod split, and registry breakdown.
Supports npm package-lock.json (both lockfileVersion 1's nested tree and 2/3's flat packages map), Yarn Classic yarn.lock, and pnpm-lock.yaml. Yarn Berry (v2+) lockfiles are detected but not fully parsed. All parsing happens client-side — nothing is uploaded anywhere.
Analyze an npm package-lock.json, yarn.lock, or pnpm-lock.yaml: total package count, duplicated package versions with who pulled in each, dev/prod split, registry breakdown, and the largest dependency subtree. All parsing happens client-side.
Paste or load the lockfile into the Lockfile Analyzer. It lists packages present in several versions and shows which packages referenced each version.
Yes, it handles npm package-lock.json, yarn.lock and pnpm-lock.yaml.
Yes, where the lockfile records it. The analysis shows total and unique package counts, the prod/dev split, a registry breakdown and, for npm lockfiles, the largest dependency subtree.
Yes, the Outdated tab checks the packages in your lockfile against the npm registry, and the Size tab checks install and gzip sizes for packages you pick.
No. This tool runs entirely in your browser — your input is processed locally on your device and is never uploaded or stored on a server.