What it does
Paste the old and the new version of a dependency file, for example the two sides of a pull request. The tool lists the dependencies that were added, removed or changed (with the version from and to), separated into runtime and development, and raises flags for changes that deserve a closer look. It can copy a Markdown summary for the pull request description.
Supported files
- package.json: dependencies, optionalDependencies, peerDependencies, devDependencies and the install scripts.
- package-lock.json: lockfile versions 2 and 3 (the
packagesmap). Version 1 lockfiles are reported with a clear message. - requirements.txt: requirement lines,
-rand-cnotes,--index-url,--extra-index-url,--find-linksand--trusted-host. - pyproject.toml: PEP 621 (
[project]), dependency groups and Poetry ([tool.poetry]), plus the package sources of Poetry and uv. - go.mod:
require,replace,excludeandretract. - Cargo.toml: dependencies, dev-dependencies, build-dependencies, workspace dependencies and target-specific tables.
The format is detected from the text. If the detection is wrong, choose the format by hand.
What it checks
- Version ranges: no constraint,
*,latestor another moving tag, ranges with no upper limit (>=) and very broad0.xranges. - Where a package comes from: git repositories (lower severity when pinned to a commit), direct download and tarball URLs, plain
httpaddresses, local file paths and Goreplacelines. - Install scripts: new, changed or removed
preinstall,install,postinstallandpreparescripts in package.json, and lockfile entries markedhasInstallScript. - Registries and indexes: a changed or added
--index-urlor--extra-index-url(the usual route of dependency confusion), added download locations and trusted hosts, and changed package sources. - Versions: major version jumps and major version downgrades.
- Moves and duplicates: a package moved from development to runtime, and a name that is listed twice in different sections.
- Lockfiles: entries resolved from a host other than the official npm registry, entries without an integrity hash, and the same version with a different hash.
What it cannot catch
- Existence and reputation. The tool never looks anything up. It cannot tell whether a package exists, whether the name is a typo of a popular package, how old or popular it is, or whether it has known vulnerabilities. For existence and reputation checks use the Package Existence Checker or a dedicated scanner.
- What the new code does. A new version number says nothing about the code in it. A change without flags is not a safe change.
- Transitive dependencies in manifests. A manifest lists only direct dependencies. Use the lockfile to see the rest.
- Everything outside the supported syntax. Unusual constructs, dynamic requirements and other file formats are not understood. Unknown lines are reported as notes where possible.
- The version rules are heuristic: they compare the first number of a range, not real resolved versions.
Limits
Each file can be up to 8,000,000 characters. The comparison runs in a background Web Worker so the page stays responsive, and a 5 MB lockfile is read in a few seconds. At most 5,000 changes and 2,000 flags are kept, and the page shows the first rows with a button for the rest. A comparison that takes longer than 20 seconds is stopped.
Reading errors
If a file cannot be read, the tool says which box it is in and shows the line and column and the text around it where the format allows (JSON, TOML, requirements.txt and go.mod).
Privacy
This tool runs entirely in your browser. What you enter is processed on your device and is not sent to a server. The page does not write your input to local storage, cookies or the URL, and it makes no network requests to look up packages.