⌁ LESS DIFF. MORE UNDERSTANDING.

See the chain reaction.

Your lockfile changed. Follow every dependency back to the packages you actually chose.

{ }

Two lockfiles.
One explorable change map.

BEFOREpackage-lock.jsonDrop your base lockfile, or choose a file

AFTERpackage-lock.jsonDrop your updated lockfile, or choose a file

Real upgrade cases Pinned public snapshots. Loaded only when selected.

Change map

SYNTHETIC EXAMPLE

PACKAGE / INSTALLED LOCATIONVERSION

Sort

A review you can take with you.

Exports contain package names, paths and source metadata. Review them before sharing.

About this map & analysis notes

Paths show reachability in the two locked trees, not why npm selected a version. Each change is matched by installed location. Moved packages appear as removed and added. Signals are prompts for review, not vulnerability findings. Linked workspaces are outside the path model.

npm lockfile format ↗

01 /

Start with the change.

Added, removed, version and metadata changes. Every installed location stays distinct.

02 /

Follow the dependency.

Select a root to narrow the map. Compare a package’s shortest path before and after.

03 /

Bring evidence to your PR.

Export a readable Markdown review. No account, API key or registry access needed.