Software Version / Package Tools

Dependency Version Comparator

Compare two dependency lists - package.json, composer.json or requirements.txt - to see what was added, removed, upgraded or downgraded.

Paste the old and new dependency lists - the tool matches packages by name and labels every change as major, minor, patch, range-only or downgrade.

Before (old dependency list)

After (new dependency list)

Accepts package.json (dependencies, devDependencies, peerDependencies, optionalDependencies), composer.json (require, require-dev), requirements.txt lines (name==1.2.3), or plain name version / name@version lines. Everything is compared in your browser.

Hide unchanged

More Software Version / Package Tools

View all 9

Python Requirements Version Helper Package Name Validator Composer Version Constraint Helper Version Range Calculator npm Package Version Checker SemVer Validator Version Increment Generator Version Comparator

Review every major change against the package's changelog before merging - that is where breaking changes live.

What Is the Dependency Version Comparator?

It is a focused diff for dependency files. A normal text diff shows that lines changed; this tool tells you how each dependency changed, so a major upgrade hidden in a long update pull request stands out.

When to Use It

Reviewing a Dependabot or Renovate pull request that touches many packages.
Comparing dependencies between two branches, releases or services.
Writing release notes that mention upgraded libraries.

How to Use It

Paste the old file on the left and the new one on the right. JSON files (package.json, composer.json) and line-based lists (requirements.txt, name@version) are detected automatically.
Click Compare. Untick "Hide unchanged" to see every package.

Example

express from ^4.18.2 to ^5.0.1 is labelled Major; axios from 1.5.0 to 1.7.2 is Minor; moment removed and dayjs added are listed separately.

Understanding the Result

The change type compares the lowest version named in each spec - ^4.18.2 counts as 4.18.2. "Range changed" means the same base version with a different operator (for example ^1.2.0 to ~1.2.0). Packages whose spec is a URL or tag are shown as "Changed".

Limitations

It compares what the files declare, not what a lockfile actually installed. Packages are matched by exact name. To check a single npm spec against published versions, use the npm Package Version Checker; for two individual versions, use the Version Comparator.