How to use Dependency Lockfile Explorer
- Paste or upload an npm package-lock.json with lockfileVersion 2 or 3.
- Run the traversal to resolve declared dependencies through nested package paths.
- Inspect duplicate versions, unresolved edges and package records not reached from the root.
- Download the edge report for a separate dependency or security review.
Example: Dependency Lockfile Explorer
Trace npm lockfile paths and inspect duplicate package versions.
Supported inputs and limits
- One JSON input up to 2 MiB, 30,000 JSON values, 40 nesting levels, 3,000 packages and 10,000 dependency edges.
- Supports npm package-lock versions 2 and 3 with packages records.
- Workspace/link records are refused;
- Yarn, pnpm, Composer and npm v1 are unsupported.
- Dependency paths use nearest nested node_modules resolution and report the first discovered route.
More details
Peer requirements, semver satisfaction and platform installation selection are not evaluated.
No hooks, registry fetches or vulnerability scans run.
JSON numeric literals are limited to 128 characters and must retain their decimal value through browser Number conversion; integers outside the safe integer range and unsupported precision are refused.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
Questions about Dependency Lockfile Explorer
Does the report check whether packages are vulnerable?
It reports locked versions and dependency paths only. It does not query advisories, verify package provenance or claim that a dependency is safe.
Why does one package name show several versions?
Different nested paths can lock different versions. The duplicate flag means the name has more than one locked version in the supplied inventory.
Are the displayed paths every possible route?
Each edge is listed, but the explanatory root path is the first discovered route. A shared dependency can be reachable through additional parents not repeated as full paths.