Laravel and Symfony support windows
Frameworks publish their own maintenance schedules, separate from PHP's support windows. A framework branch can still be maintained while the PHP version it runs on is not, and the other way round. Check both.
Laravel
The Laravel 13 release notes say that every Laravel release gets bug fixes for 18 months and security fixes for 2 years. As checked on 14 October 2026:
| Version | Bug fixes until | Security fixes until |
|---|---|---|
| 12 | 13 August 2026 | 24 February 2027 |
| 13 | Q3 2027 | 17 March 2028 |
Laravel 12 is in its security-fix-only period. Laravel 11's security fixes ended on 12 March 2026. The schedule gives only a quarter for the end of Laravel 13 bug fixes. The collected endoflife.date record (data/sources/eol-laravel.json) uses 30 September 2027 for it, which is that site's reading, not a date Laravel published.
Symfony
Symfony's release pages list each branch's maintenance end by month. As checked on 14 October 2026:
| Branch | Type | Requires | End of bug fixes | End of security fixes |
|---|---|---|---|---|
| 6.4 | long-term support | PHP 8.1.0 | November 2026 | November 2027 |
| 7.4 | long-term support | PHP 8.2.0 | November 2028 | November 2029 |
| 8.1 | not labelled long-term | PHP 8.4.0 | January 2027 (end of support) | January 2027 |
The 8.1 page lists one "End of support" date and no separate security period. Symfony 6.4's bug fixes end in November 2026; after that it gets only security fixes. The pages give months, not days. The endoflife.date records use the last day of the month (for example 30 November 2026 for 6.4).
Limitations
The Drupal and WordPress records in data/sources/eol-drupal.json and eol-wordpress.json have not been checked against their publishers. drupal.org could not be reached from the maintenance environment on 14 October 2026, so no Drupal dates appear here. WordPress's own support policy was not checked either.
Related: PHP support windows, package signals.