Dependency Lockfile Explorer

Inspect npm lockfile dependency paths, nested resolution and duplicate locked versions without running an installer.

On-device No sign-up Free to use

Trace locked dependencies controls

Showing an example. Edit to see your own.

Drop your file here

or choose one from your device

One file · .json, application/json

    Processed in your browser. Your inputs stay on this device.

    Result

    Showing an example.

    Trace npm lockfile paths and inspect duplicate package versions.

    A root dependency demo ^1.0.0 locked at node_modules/demo version 1.2.0 produces one dependency row with first path root -> demo and no duplicate-version flag.

    Loading the tool. Your result will appear here.

    https://usefreetools.net/dependency-lockfile-explorer · 20 November 2026

    Was this helpful?

    How to use Dependency Lockfile Explorer

    1. Paste or upload an npm package-lock.json with lockfileVersion 2 or 3.
    2. Run the traversal to resolve declared dependencies through nested package paths.
    3. Inspect duplicate versions, unresolved edges and package records not reached from the root.
    4. Download the edge report for a separate dependency or security review.

    Example: Dependency Lockfile Explorer

    Trace npm lockfile paths and inspect duplicate package versions.

    You add
    npm package-lock.json: {"lockfileVersion":3,"packages":{"":{"dependencies":{"demo":"^1.0.0"}},"node_modules/demo":{"version":"1.2.0"}}}
    You get
    A root dependency demo ^1.0.0 locked at node_modules/demo version 1.2.0 produces one dependency row with first path root -> demo and no duplicate-version flag.

    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.

    Page updated · Project managed by Tony Hines · Report a problem with Dependency Lockfile Explorer