ReleaseRun Badges for PHP
Live version freshness, EOL status, CVE counts, and health badges for PHP. Embed in your README, docs, or dashboard.
Live Badges
Loading latest version badges...
Why Use PHP Health Badges?
PHP’s annual release cycle and short security-only windows mean versions fall out of support faster than most teams realise. A health badge in your project’s README shows users whether their PHP version is still getting security patches — before the next WordPress or Laravel update forces the conversation.
ReleaseRun badges go beyond Shields.io. Where Shields.io shows a version number, our badges show security posture: CVE counts, EOL countdowns, and a composite health grade based on freshness (35%), security (35%), and support status (30%).
Common Use Cases
- Package maintainers: Show which PHP versions your Composer package supports and highlight when any of them are approaching end of security support. PHP 8.1 losing security fixes catches more people than they expect.
- Hosting teams: Embed badges in internal dashboards to track PHP versions across shared hosting environments. One customer on PHP 7.4 is one customer with unpatched CVEs.
- WordPress plugin developers: Add version health badges to plugin documentation so site operators can verify they’re running a supported PHP version.
What Makes These Different
Every badge pulls live data from the endoflife.date API and the NIST National Vulnerability Database. Data refreshes every 6 hours. Badges are edge-cached for 5 minutes — fast enough for CI/CD pipelines and documentation sites.
PHP Versions
Security Overview
CVE vulnerability data is sourced from the NIST National Vulnerability Database (NVD) and refreshed every 6 hours.
Check specific version CVEs using the badge builder above or visit our PHP hub page for detailed security analysis.
Upgrade Guidance
Running an older version of PHP? Here's what to consider when planning your upgrade:
- Check breaking changes in release notes
- Review EOL dates for your current version
- Test in staging before production rollout
- Consider LTS versions for stability
See the official PHP documentation for detailed upgrade instructions.
Version Comparison
Not sure which PHP version to use? Compare versions side by side.
Embed Builder
Usage Guide
Copy any snippet below to embed a PHP health badge in your project.
Markdown
[](https://releaserun.com/php/)HTML
<a href="https://releaserun.com/php/"><img src="https://img.releaserun.com/badge/health/php.svg" alt="PHP Health"></a>reStructuredText
.. image:: https://img.releaserun.com/badge/health/php.svg
:target: https://releaserun.com/php/
:alt: PHP HealthData sources: endoflife.date (version lifecycle), NIST NVD (CVE data)
Related Articles
How to Add Version Health Badges to Your Project
Your README shows a build status badge, a coverage badge, and maybe a license badge. None of them tell users…
PostgreSQL vs MySQL in 2026: Pick Your Failure Mode
PostgreSQL vs MySQL in 2026: Pick Your Failure Mode I’ve watched “database selection” turn into an on-call problem six months…
Frequently Asked Questions
- What do the badges show for PHP?
- ReleaseRun badges display real-time version freshness, end-of-life status, CVE vulnerability counts, and an overall health score for PHP releases.
- How do I embed a PHP badge in my README?
- Use the embed builder above to select your version and badge type, then copy the generated Markdown or HTML snippet into your README.
- How often is PHP badge data updated?
- Badge data refreshes every 6 hours from endoflife.date and NIST NVD. Badges are cached for 5 minutes at the CDN edge.
- Can I customize the badge style?
- Yes, append ?style=flat-square or ?style=for-the-badge to the badge URL. The embed builder lets you preview all available styles.