Laravel and PHP versions in a deal: what a buyer reads in your composer.lock
A Laravel product runs on two clocks, the framework and PHP. Both publish the day their fixes stop, and a buyer's reviewer reads both from your lock file and your servers. The dates, the pairs that run out together, and a one-hour check to do first.
The short answer. A Laravel product carries two clocks: the framework and the PHP version under it. Laravel gives every major release 18 months of bug fixes and two years of security fixes, and ships a new major about once a year. PHP gives every branch two years of full support and then security fixes only, ending on 31 December of a stated year. In a sale, a buyer's reviewer reads both clocks from three places: composer.lock, composer.json and the server itself. A version past its security date becomes a finding. Whether that finding stays a line in a report or moves into the price depends on how far the upgrade is, what the application holds, and whether the seller wrote it down first.
The dates that matter now
As of November 2026, the published schedules read as follows. Laravel's are on its support policy page, PHP's on php.net supported versions.
| Component | Runs on PHP | Bug fixes until | Security fixes until |
|---|---|---|---|
| Laravel 10 | 8.1 to 8.3 | 6 August 2024 | 4 February 2025, ended |
| Laravel 11 | 8.2 to 8.4 | 3 September 2025 | 12 March 2026, ended |
| Laravel 12 | 8.2 to 8.5 | 13 August 2026 | 24 February 2027 |
| Laravel 13 | 8.3 to 8.5 | Q3 2027 | 17 March 2028 |
| PHP 8.1 | 31 December 2025, ended | ||
| PHP 8.2 | 31 December 2024 | 31 December 2026 | |
| PHP 8.3 | 31 December 2025 | 31 December 2027 | |
| PHP 8.4 | 31 December 2026 | 31 December 2028 | |
| PHP 8.5 | 31 December 2027 | 31 December 2029 |
Two rules from the Laravel page are easy to miss. There is no long-term support release any more: every major gets the same two years. And for the first-party libraries around the framework, only the latest major release receives bug fixes. An application on the current framework can still run an older major of one of those packages, and that package is already outside its maintenance window.
The two clocks run together
The pairs in the table decide how much room a product has. A few combinations come up again and again in reviews.
- Laravel 12 on PHP 8.2. PHP 8.2 loses security fixes on 31 December 2026 and Laravel 12 on 24 February 2027. Two dates eight weeks apart. Moving PHP alone to 8.4 buys time on the language, but the framework still runs out in February.
- Laravel 11 on any PHP. The framework is already without fixes. Laravel 13 needs PHP 8.3 at least, so a product on PHP 8.2 has to move the language and two framework majors.
- Laravel 10 and older. Laravel 10 does not run on PHP above 8.3, so the language cannot be kept current while the framework stays. Every year on it adds distance to the upgrade.
- Laravel 13 on PHP 8.4 or 8.5. Covered into 2028. The question a buyer asks here is different: is there a habit of upgrading once a year, or was this the one upgrade in five years?
Where a reviewer reads the versions
Nobody takes a version from a slide. In a technical due diligence the reviewer reads it from the project and the servers, and compares the sources with each other.
- composer.lock names the exact version of every package that is installed, laravel/framework included. It is the most precise source, and the first file a reviewer opens.
- composer.json names what the code allows: the range for each package and the PHP requirement. A range like ^10.0 tells the reviewer which major the team builds against. A setting under config.platform can make Composer resolve packages for a PHP version that is not the one on the server, so the reviewer checks the runtime as well.
- The runtime. The PHP binary on production, the base image in a Dockerfile, the version selected in a hosting panel. A lock file written for PHP 8.4 running on PHP 8.2 in production is a finding of its own.
php artisan aboutprints the Laravel and PHP versions an environment actually runs, with its debug and cache settings. - composer audit. Composer checks the installed packages against security advisories, through the Packagist.org API by default, and reports packages their authors marked as abandoned. The command exits with code 1 when it finds anything, which is why reviewers like to see it in a build pipeline. The options are described in the Composer documentation.
The comparison matters as much as each source. A product whose lock file, requirement and runtime agree reads as maintained. Three different answers to "which PHP does this run on" read as a question about what else nobody tracks.
How a version becomes a deal point
A framework past its security date is rarely a deal breaker on its own. Applications run the morning after the date exactly as they ran the night before. The finding grows with four things.
- Distance. One major release is usually a planned task: the official upgrade guide, the tests, a release. Three majors and a PHP jump is a project, and its size depends on code nobody has read for years: custom packages, abandoned dependencies, overridden framework classes.
- Tests. With a test suite that covers the main flows, an upgrade can be verified. Without one, every estimate carries a wide margin, and buyers price margins.
- What the application holds. An internal tool on an old framework is a maintenance item. An application that stores customer data, payments or health records on an unpatched stack is a security exposure, and it gets a higher severity.
- Who found it. A finding the seller disclosed, with an estimate and a date, reads as a managed item. The same finding discovered by the buyer during exclusivity reads as a surprise, and surprises turn into price adjustments, holdbacks or conditions before closing.
From our own work: when we moved a production site from an old Laravel release on PHP 7.4 to Laravel 13 on PHP 8.4, the code changes were the smaller part. The work that made it safe was a temporary staging copy closed at the server level, with an anonymised database, a rollback kit for the old code and the old PHP, and a check of every page in every language before and after. A reviewer asks for exactly that kind of evidence when an upgrade is part of the plan.
A one-hour check before anyone asks
- Run
php artisan abouton production and on staging. Write down the Laravel and PHP versions each one really runs. - Open composer.lock and find laravel/framework. Compare the major with the table above.
- Look at the PHP requirement and any platform setting in composer.json. Make sure they match the server.
- Run
composer audit --lockedand save the output. Every advisory and abandoned package on it is a line a buyer will also see. - For each item, write one sentence: the date, the planned move, and when. That paragraph is most of what a disclosure needs.
If you would rather not do the comparison by hand, drop composer.lock and composer.json into our free stack check. It reads the files in your browser, never sends them anywhere, and lays out every dated item with what it means in a deal. All the dates above, with PHP, Symfony, Drupal, Node.js and the databases next to them, live in our technology deadlines calendar, which you can add to your own calendar so new dates arrive by themselves.
When a check is not enough
Versions are the easiest part of a technical review to fix, and the easiest to find. They say little about architecture, who owns the accounts, how secrets are kept or whether the team can ship the upgrade it plans. If a buyer will read the company soon, a red-flag memo puts severity, cost and time to fix next to each item. If the sale is a year or more away, exit readiness closes the items month by month, so the list a buyer receives is short and already explained.
Questions
How long is a Laravel version supported?
Every Laravel major release gets 18 months of bug fixes and two years of security fixes, and a new major arrives about once a year, usually in the first quarter. There is no long-term support release any more. Laravel 12 gets security fixes until 24 February 2027 and Laravel 13 until 17 March 2028, according to the support policy on laravel.com.
Which PHP version should a Laravel product run on now?
PHP 8.4, if the framework allows it. It gets security fixes until 31 December 2028. PHP 8.5 runs a year longer. Laravel 12 runs on PHP 8.2 to 8.5 and Laravel 13 on 8.3 to 8.5, so a product on Laravel 12 can move the language first and the framework next.
Is an unsupported Laravel version a deal breaker?
Rarely on its own. It becomes a deal point when the upgrade is several majors away, when there are no tests to verify it, when the application holds customer data, or when the buyer finds it before the seller discloses it. Disclosed with an estimate and a date, it usually stays a managed item.
Does the stack check upload my composer.lock?
No. The stack check reads the files in your own browser and never sends them to a server. The page counts only that a check was run. A lock file names package versions, not business logic, so it is also the file that gives the most exact result.
