EOL.Wiki EOL.Wiki
← ← Back to all products

Composer

Active
Tools & Monitoring Latest Version: 2.10.1 Latest Release: Jun 4, 2026

Composer is the dependency manager for PHP, managing libraries and packages for PHP projects.

Versions

12

Latest Version

2.10.1

Active Support

2

EOL

10

Lifecycle Timeline

Today
2.10
2.10
2.9
2.9
2.8
2.8
2.7
2.7
2.6
2.6
2.5
2.5
2.4
2.4
2.3
2.3
2.2
2.2
2.1
2.1
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
2.10May 28, 2026YesNo2.10.1No
Active
2.9Nov 13, 2025NoMay 28, 20262.9.8No
EOL
2.8Oct 2, 2024NoNov 13, 20252.8.12No
EOL
2.7Feb 8, 2024NoOct 2, 20242.7.9No
EOL
2.6Sep 1, 2023NoFeb 8, 20242.6.6No
EOL
2.5Dec 20, 2022NoSep 1, 20232.5.8No
EOL
2.4Aug 16, 2022NoDec 20, 20222.4.4No
EOL
2.3Mar 30, 2022NoAug 16, 20222.3.10No
EOL
2.2Dec 22, 2021YesNo2.2.28
Yes
Active
2.1Jun 3, 2021NoDec 22, 20212.1.14No
EOL
2.0Oct 24, 2020NoJun 3, 20212.0.14No
EOL
1Apr 5, 2016NoOct 24, 20201.10.28No
EOL

Frequently Asked Questions

Which versions of Composer have reached end of life?
The following Composer versions have reached end of life and no longer receive security updates: 2.9, 2.8, 2.7, 2.6, 2.5, 2.4, 2.3, 2.1 (and 2 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Composer 2.9?
Composer 2.9 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Composer?
The latest version of Composer is 2.10.1, released in the 2.10 release cycle.
How many versions of Composer are currently supported?
Composer currently has 2 actively supported version(s): 2.10, 2.2.
When does Composer 2.10 reach end of life?
Composer 2.10 does not have a specific end-of-life date announced yet.
What should I do when Composer reaches end of life?
When a Composer version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.