Tools
PHP Upgrade Checker
Find out which Composer packages stop you from upgrading to PHP 8.4, or any version from 8.0 to 8.5. Paste composer.lock and, optionally, composer.json: each package's declared php constraint is checked with Composer’s own rules, and the required PHP extensions are listed. Your files never leave your browser.
Your files stay on this device: they are read and checked in your browser, and nothing is uploaded. No Packagist lookups are made.
Nothing to check yet
Paste or drop composer.lock (and optionally composer.json) above, or .
About the PHP upgrade checker
Before moving a project to a new PHP release, you need to know which installed packages say they do not support it. Every package in composer.lock carries the php constraint from its own composer.json, for example ^7.4 or >=8.1. This tool reads those constraints, checks each one against the PHP version you pick, and lists the packages that rule it out. It also collects every ext-* extension the project and its packages require, so you can confirm the new PHP build has them.
Constraints are matched with the same rules as Composer's own composer/semver library: caret (^), tilde (~), wildcards (8.3.*), comparisons, hyphen ranges (7.4 - 8.3), AND with a space or comma, and OR with ||. The target is checked as the exact release, so PHP 8.4 means 8.4.0. That is why <8.4 excludes PHP 8.4 while <=8.4 allows it.
Not every package can be judged. A package with no php requirement gets its own count, and so does a constraint Composer cannot parse. Neither is counted as compatible, so the verdict never reads "ready" while something is unknown. The root project's own require.php from composer.json is reported separately. Dev packages from packages-dev are included and marked.
Both files are read in your browser and nothing is uploaded. The check only uses what the lock file declares: it does not look packages up on Packagist, so it cannot tell you whether a newer release of a blocking package supports your target. It also does not scan your own code for deprecated features.
Worked examples
Each constraint below was checked against PHP 8.4 (8.4.0) with this tool.
"require": { "php": "^7.4" }
// ^7.4 means >=7.4.0 <8.0.0
// PHP 8.4 → incompatibleThe caret allows updates that keep the major version, so ^7.4 stops before 8.0. Packages that support both write ^7.4 || ^8.0.
~8.3 → >=8.3.0 <9.0.0 PHP 8.4: compatible
~8.3.0 → >=8.3.0 <8.4.0 PHP 8.4: incompatible
8.3.* → >=8.3.0 <8.4.0 PHP 8.4: incompatibleWith two parts the tilde fixes only the major version; with three parts it fixes the minor version too, which makes ~8.3.0 behave like 8.3.*.
>=7.2 <8.4 PHP 8.4: incompatible
<=8.4 PHP 8.4: compatible
7.4 - 8.3 PHP 8.4: incompatible (means <8.4.0)
7.2 - 8.4 PHP 8.4: compatible (means <8.5.0)A partial upper version in a hyphen range covers that whole minor release, so 7.2 - 8.4 still allows 8.4.9.
# Which packages prevent PHP 8.4.0?
composer why-not php 8.4.0
# Extensions on the new PHP build
php -mcomposer why-not (also called prohibits) gives the same per-package answer once Composer runs in the project, and php -m lists the loaded extensions to compare with the list here.
Frequently asked questions
Which files do I need?
composer.lock gives the per-package results. composer.json adds the root project's own php requirement and its ext-* extensions. Either file works alone.
Does PHP 8.4 here mean 8.4.0 or any 8.4 release?
It means exactly 8.4.0, the version a fresh upgrade lands on. A constraint like >=8.4.2 would exclude it even though later 8.4 patch releases satisfy it.
Why is a package listed with no PHP constraint?
Its require has no php key, so Composer installs it on any PHP version. That says nothing about whether it actually works, so the tool counts it separately instead of calling it compatible.
A package blocks my upgrade. What next?
Look for a newer release of that package that allows the target, then run composer update vendor/package --with-all-dependencies. If none exists, replace the package or ask its maintainers.
Are my files uploaded anywhere?
No. Both files are parsed in your browser and the page sends nothing to a server, so private package names stay on your device.
Does it check whether PHP ships an extension?
No. It lists every ext-* requirement and who needs it, whatever the target version. Run php -m on the new build to see which extensions are loaded.