Complete end-of-life dates, support windows, and security status for all Numpy versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.14 | 1.14.6 | Jan 6, 2018 | Jan 7, 2020 | 2314 days past EOL | EOL |
| 1.15 | 1.15.4 | Jul 23, 2018 | Jul 23, 2020 | 2116 days past EOL | EOL |
| 1.16 | 1.16.6 | Jan 14, 2019 | Jan 13, 2021 | 1942 days past EOL | EOL |
| 1.17 | 1.17.5 | Jul 26, 2019 | Jul 26, 2021 | 1748 days past EOL | EOL |
| 1.18 | 1.18.5 | Dec 22, 2019 | Dec 22, 2021 | 1599 days past EOL | EOL |
| 1.19 | 1.19.5 | Jun 20, 2020 | Jun 21, 2022 | 1418 days past EOL | EOL |
| 1.20 | 1.20.3 | Jan 30, 2021 | Jan 31, 2023 | 1194 days past EOL | EOL |
| 1.21 | 1.21.6 | Jun 22, 2021 | Jun 23, 2023 | 1051 days past EOL | EOL |
| 1.22 | 1.22.4 | Dec 31, 2021 | Jan 1, 2024 | 859 days past EOL | EOL |
| 1.23 | 1.23.5 | Jun 22, 2022 | Jun 24, 2024 | 684 days past EOL | EOL |
| 1.24 | 1.24.4 | Dec 18, 2022 | Dec 19, 2024 | 506 days past EOL | EOL |
| 1.25 | 1.25.2 | Jun 17, 2023 | Jun 18, 2025 | 325 days past EOL | EOL |
| 1.26 | 1.26.4 | Sep 16, 2023 | Sep 17, 2025 | 234 days past EOL | EOL |
| 2.0 | 2.0.2 | Jun 16, 2024 | Jun 17, 2026 | 39 days remaining | Warning |
| 2.1 | 2.1.3 | Aug 18, 2024 | Aug 19, 2026 | 102 days remaining | Warning |
| 2.2 | 2.2.6 | Dec 8, 2024 | Dec 9, 2026 | 214 days remaining | Active |
| 2.3 | 2.3.5 | Jun 7, 2025 | Jun 8, 2027 | 395 days remaining | Active |
| 2.4 | 2.4.4 | Dec 20, 2025 | Dec 21, 2027 | 591 days remaining | Active |
When a Numpy 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 Numpy 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 →