Font Awesome 1 · Version Status
Font Awesome 1 End of Life Date
Font Awesome 1 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Font Awesome 1 is past end of life. This version no longer receives security patches. Past EOL — migrate to a supported version immediately.
EOL Date
date not published
Past EOL
Latest Release
1.0.0
Standard release
Release Date
Mar 3, 2012
Font Awesome 1 series
Lifecycle detail
Font Awesome 1 was released on March 3, 2012. It is not an LTS release; Font Awesome reserves longer patch windows for its LTS versions. Its most recent patch is 1.0.0, published March 10, 2012.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Font Awesome 1 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All Font Awesome Versions
| Version | Latest | EOL Date | Status |
|---|
| → 1 |
1.0.0 |
Supported |
EOL |
| 2 |
2.0.0 |
Supported |
EOL |
| 3 |
3.2.1 |
Supported |
EOL |
| 4 |
4.7.0 |
Supported |
EOL |
| 5 LTS |
5.15.4 |
EOL |
Active |
| 6 LTS |
6.7.2 |
EOL |
Active |
| 7 |
7.3.1 |
EOL |
Active |
What does Font Awesome 1 end of life mean?
When Font Awesome 1 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Font Awesome 1 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Font Awesome 7 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Font Awesome 1 reach end of life?
Font Awesome 1 has already reached end of life, though the vendor has not published an exact date.
Is Font Awesome 1 still supported?
No. Font Awesome 1 reached end of life on date not published and is no longer receiving security patches.
What should I upgrade to from Font Awesome 1?
The recommended upgrade from Font Awesome 1 is
Font Awesome 7 — the latest actively supported version. Check the
Font Awesome full timeline for all supported versions.
What are the security risks of running Font Awesome 1 past EOL?
When Font Awesome 1 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Font Awesome should migrate immediately or implement compensating controls.