← ← Back to all products
Guzzle
Active
Libraries & SDKsLatest Version: 7.12.3Latest Release: Jun 23, 2026
Guzzle is a PHP HTTP client library for sending HTTP requests and integrating with web services.
Support summary
Guzzle currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
No announced EOL date is currently listed.
Supported cycles
1
0 lts
Versions
5
Latest Version
7.12.3
Active Support
1
EOL
4
Lifecycle Timeline
Today ↓
7
7
6
6
5
5
4
4
3
3
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 7 | Jun 27, 2020 | Yes | No | 7.12.3 | No | Active |
| 6 | May 26, 2015 | No | Oct 31, 2023 | 6.5.8 | No | EOL |
| 5 | Oct 12, 2014 | No | Oct 31, 2019 | 5.3.4 | No | EOL |
| 4 | Mar 29, 2014 | No | Oct 31, 2016 | 4.2.4 | No | EOL |
| 3 | Jan 28, 2014 | No | Oct 31, 2016 | 3.8.1 | No | EOL |
Data sources
Sources
Frequently Asked Questions
Which versions of Guzzle have reached end of life?
The following Guzzle versions have reached end of life and no longer receive security updates: 6, 5, 4, 3. It is recommended to upgrade to a supported version.
Is it safe to continue using Guzzle 6?
Guzzle 6 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 Guzzle?
The latest version of Guzzle is 7.12.3, released in the 7 release cycle.
How many versions of Guzzle are currently supported?
Guzzle currently has 1 actively supported version(s): 7.
When does Guzzle 7 reach end of life?
Guzzle 7 does not have a specific end-of-life date announced yet.
What should I do when Guzzle reaches end of life?
When a Guzzle 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.