Numpy End of Life Dates

other

Developers rely on Numpy, a library for working with arrays and mathematical operations in Python, which has been a cornerstone of scientific computing since its creation. The NumPy project is maintained by a community of developers who contribute to its ongoing development and support. Numpy was first released in 2005 and has been widely adopted in various fields, including data analysis, machine learning, and scientific research. Its widespread use can be attributed to its ability to provide support for large, multi-dimensional arrays and matrices, and its extensive library of high-level mathematical functions.

The end-of-life landscape for Numpy is characterized by a total of 18 versions, with 13 of these versions having already reached their end-of-life. Currently, there are 5 active versions of Numpy, with the latest stable version being 2.0.2. The next version to expire is 2.0, which will reach its end-of-life on 2026-06-17, giving developers a clear deadline to plan their upgrades. The most recent version to reach its end-of-life was 1.26, which expired on 2025-09-17. This information is crucial for developers who need to ensure they are using supported versions of Numpy to avoid potential security risks and compatibility issues.

The security picture for Numpy is currently favorable, with a total of 0 CVEs tracked and 0 critical CVEs reported. As a result, there is no most affected version, and the library is not currently listed on the Known Exploited Vulnerabilities catalog. Given the absence of known security vulnerabilities, developers can continue to use Numpy with confidence, but it is still essential to keep track of end-of-life dates and plan upgrades accordingly to ensure ongoing support and maintenance. By staying informed about Numpy's end-of-life dates and supported versions, developers can minimize potential risks and ensure the continued stability and security of their applications.

Last updated: Oct 23, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
2.5 Jun 21, 2026—Jun 22, 2028in 608d2.5.4—Active
2.4 Dec 20, 2025—Dec 21, 2027in 424d2.4.6—Active
2.3 Jun 7, 2025—Jun 8, 2027in 228d2.3.5—Active
2.2 Dec 8, 2024—Dec 9, 2026in 47d2.2.6—EOL soon
2.1 Aug 18, 2024—Aug 19, 202665d ago2.1.3—EOL
2.0 Jun 16, 2024—Jun 17, 2026128d ago2.0.2—EOL
1.26 Sep 16, 2023—Sep 17, 2025401d ago1.26.4—EOL
1.25 Jun 17, 2023—Jun 18, 2025492d ago1.25.2—EOL
1.24 Dec 18, 2022—Dec 19, 2024673d ago1.24.4—EOL
1.23 Jun 22, 2022—Jun 24, 2024851d ago1.23.5—EOL
1.22 Dec 31, 2021—Jan 1, 20241026d ago1.22.4—EOL
1.21 Jun 22, 2021—Jun 23, 20231218d ago1.21.6—EOL
1.20 Jan 30, 2021—Jan 31, 20231361d ago1.20.3—EOL
1.19 Jun 20, 2020—Jun 21, 20221585d ago1.19.5—EOL
1.18 Dec 22, 2019—Dec 22, 20211766d ago1.18.5—EOL
1.17 Jul 26, 2019—Jul 26, 20211915d ago1.17.5—EOL
1.16 Jan 14, 2019—Jan 13, 20212109d ago1.16.6—EOL
1.15 Jul 23, 2018—Jul 23, 20202283d ago1.15.4—EOL
1.14 Jan 6, 2018—Jan 7, 20202481d ago1.14.6—EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions