EOL.Wiki EOL.Wiki
← ← Back to all products

scikit-learn

Active
Libraries & SDKs Latest Version: 1.9.0 Latest Release: Jun 2, 2026

scikit-learn is the standard Python machine learning library for classical ML (classification, regression, clustering). Only the latest minor receives fixes; dependency/Python deprecation follows SPEC 0 (~3 years). Latest 1.9 and 1.7-1.8 require Python 3.10+.

Versions

9

Latest Version

1.9.0

Active Support

1

EOL

8

Lifecycle Timeline

Today
1.9
1.9
1.8
1.8
1.7
1.7
1.6
1.6
1.5
1.5
1.4
1.4
1.3
1.3
1.2
1.2
1.1
1.1
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
1.9Jun 2, 2026YesNo1.9.0No
Active
1.8Dec 10, 2025NoYes1.8.0No
EOL
1.7Jun 5, 2025NoYes1.7.2No
EOL
1.6Dec 9, 2024NoYes1.6.1No
EOL
1.5May 21, 2024NoYes1.5.2No
EOL
1.4Jan 18, 2024NoYes1.4.2No
EOL
1.3Jun 30, 2023NoYes1.3.2No
EOL
1.2Dec 8, 2022NoYes1.2.2No
EOL
1.1May 12, 2022NoYes1.1.3No
EOL

Frequently Asked Questions

Which versions of scikit-learn have reached end of life?
The following scikit-learn versions have reached end of life and no longer receive security updates: 1.8, 1.7, 1.6, 1.5, 1.4, 1.3, 1.2, 1.1. It is recommended to upgrade to a supported version.
Is it safe to continue using scikit-learn 1.8?
scikit-learn 1.8 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of scikit-learn?
The latest version of scikit-learn is 1.9.0, released in the 1.9 release cycle.
How many versions of scikit-learn are currently supported?
scikit-learn currently has 1 actively supported version(s): 1.9.
When does scikit-learn 1.9 reach end of life?
scikit-learn 1.9 does not have a specific end-of-life date announced yet.
What should I do when scikit-learn reaches end of life?
When a scikit-learn version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.