React Native End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all React Native versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 0.60 | 0.60.6 | Jul 3, 2019 | Jul 9, 2020 | 2222 days past EOL | EOL |
| 0.61 | 0.61.5 | Sep 24, 2019 | Mar 13, 2021 | 1975 days past EOL | EOL |
| 0.62 | 0.62.3 | Mar 26, 2020 | Aug 18, 2021 | 1817 days past EOL | EOL |
| 0.63 | 0.63.5 | Jul 8, 2020 | Oct 2, 2021 | 1772 days past EOL | EOL |
| 0.64 | 0.64.4 | Mar 12, 2021 | Jan 19, 2022 | 1663 days past EOL | EOL |
| 0.65 | 0.65.3 | Aug 17, 2021 | Mar 30, 2022 | 1593 days past EOL | EOL |
| 0.66 | 0.66.5 | Oct 1, 2021 | Jun 23, 2022 | 1508 days past EOL | EOL |
| 0.67 | 0.67.5 | Jan 18, 2022 | Nov 6, 2022 | 1372 days past EOL | EOL |
| 0.68 | 0.68.7 | Mar 30, 2022 | Jan 13, 2023 | 1304 days past EOL | EOL |
| 0.69 | 0.69.12 | Jun 22, 2022 | Jun 22, 2023 | 1144 days past EOL | EOL |
| 0.70 | 0.70.15 | Sep 5, 2022 | Dec 7, 2023 | 976 days past EOL | EOL |
| 0.71 | 0.71.19 | Jan 12, 2023 | Apr 23, 2024 | 838 days past EOL | EOL |
| 0.72 | 0.72.17 | Jun 21, 2023 | Aug 14, 2024 | 725 days past EOL | EOL |
| 0.73 | 0.73.11 | Dec 6, 2023 | Oct 23, 2024 | 655 days past EOL | EOL |
| 0.74 | 0.74.7 | Apr 22, 2024 | Jan 27, 2025 | 559 days past EOL | EOL |
| 0.75 | 0.75.5 | Aug 14, 2024 | Feb 19, 2025 | 536 days past EOL | EOL |
| 0.76 | 0.76.9 | Oct 23, 2024 | Apr 8, 2025 | 488 days past EOL | EOL |
| 0.77 | 0.77.3 | Jan 21, 2025 | Jun 12, 2025 | 423 days past EOL | EOL |
| 0.78 | 0.78.3 | Feb 19, 2025 | Aug 12, 2025 | 362 days past EOL | EOL |
| 0.79 | 0.79.7 | Apr 8, 2025 | Oct 8, 2025 | 305 days past EOL | EOL |
| 0.80 | 0.80.3 | Jun 12, 2025 | Dec 10, 2025 | 242 days past EOL | EOL |
| 0.81 | 0.81.6 | Aug 12, 2025 | Feb 11, 2026 | 179 days past EOL | EOL |
| 0.82 | 0.82.1 | Oct 8, 2025 | Apr 7, 2026 | 124 days past EOL | EOL |
| 0.83 | 0.83.10 | Dec 10, 2025 | Jun 9, 2026 | 61 days past EOL | EOL |
| 0.84 | 0.84.1 | Feb 11, 2026 | TBD | Supported | Active |
| 0.85 | 0.85.3 | Apr 7, 2026 | TBD | Supported | Active |
| 0.86 | 0.86.2 | Jun 9, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/react-native)
What does React Native end of life mean for your organization?
When a version of React Native 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 React Native 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.
Your options when React Native reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL React Native versions. This is a bridge, not a permanent solution — plan your migration in parallel.
React Native has 24 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for React Native exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.