Sns Smc End of Life Dates
other
Developers rely on Sns Smc to streamline their workflow and ensure timely project completion. Created to address the need for efficient tracking of end-of-life dates and supported versions, this tool has been maintained by its developers to provide accurate and up-to-date information. With a history of providing reliable data, Sns Smc has become an essential resource for those looking to plan their upgrades and migrations in advance. The maintenance of Sns Smc is a testament to its importance in the development community, where staying ahead of end-of-life dates is crucial for security and compatibility.
The end-of-life landscape for Sns Smc is characterized by a total of 12 versions, with 10 of these versions having already reached their end-of-life. Currently, only 2 versions remain active, indicating that the majority of Sns Smc's versions are no longer supported. The next version to expire will be version 3.8, which is set to reach its end-of-life on 2026-11-23. This information is critical for developers who are still using this version, as they will need to plan their upgrade to a supported version before this date. The last version to reach its end-of-life was version 3.7, which expired on 2025-12-10, serving as a reminder to stay vigilant about the support status of the tools and software being used.
The security picture for Sns Smc is relatively clear, with a total of 0 CVEs tracked and 0 critical CVEs reported. As a result, there is no most affected version, and no Known Exploited Vulnerabilities (KEV) status to report. This lack of security vulnerabilities is a positive indicator, but developers should still remain cautious and ensure they are using a supported version of Sns Smc to minimize any potential risks. By staying informed about the end-of-life dates and security status of Sns Smc, developers can take proactive steps to protect their projects and maintain the security and integrity of their workflow.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 3.9 | Apr 22, 2026 | — | No | — | — | — | Active | |
| 3.8 | Jun 10, 2025 | Aug 24, 2026 | Nov 23, 2026 | in 122d | — | — | Active | |
| 3.7 | Dec 17, 2024 | Sep 10, 2025 | Dec 10, 2025 | 226d ago | — | — | EOL | |
| 3.6 | Jul 30, 2024 | Mar 18, 2025 | Jun 18, 2025 | 401d ago | — | — | EOL | |
| 3.5 | Nov 8, 2023 | Jul 30, 2024 | Oct 30, 2024 | 632d ago | — | — | EOL | |
| 3.4 | Apr 11, 2023 | Nov 8, 2023 | Nov 8, 2023 | 989d ago | — | — | EOL | |
| 3.3 | Aug 30, 2022 | Apr 11, 2023 | Apr 11, 2023 | 1200d ago | — | — | EOL | |
| 3.2 | May 24, 2022 | Aug 30, 2022 | Aug 30, 2022 | 1424d ago | — | — | EOL | |
| 3.1 | Dec 3, 2021 | May 24, 2022 | May 24, 2022 | 1522d ago | — | — | EOL | |
| 3.0 | Jun 17, 2021 | Dec 3, 2021 | Dec 3, 2021 | 1694d ago | — | — | EOL | |
| 2 | Mar 31, 2017 | Jun 17, 2021 | Jun 17, 2021 | 1863d ago | — | — | EOL | |
| 1 | Dec 16, 2015 | Mar 31, 2017 | Mar 31, 2017 | 3402d ago | — | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
