Complete end-of-life dates, support windows, and security status for all Font Awesome versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1 | 1.0.0 | Mar 3, 2012 | Supported indefinitely | Supported | Active |
| 2 | 2.0.0 | Jun 4, 2012 | Supported indefinitely | Supported | Active |
| 3 | 3.2.1 | Jan 2, 2013 | Supported indefinitely | Supported | Active |
| 4 | 4.7.0 | Oct 23, 2013 | Supported indefinitely | Supported | Active |
| 5 LTS | 5.15.4 | Feb 5, 2018 | Already EOL | Supported | Active |
| 6 LTS | 6.7.2 | Feb 7, 2022 | Already EOL | Supported | Active |
| 7 | 7.2.0 | Jul 22, 2025 | Already EOL | Supported | Active |
When a Font Awesome version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Font Awesome should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →