← ← Back to all products
All badges & lifecycle API →
WeakforcedEnd of Life (EOL) Dates & Support Status
Active
Tools & MonitoringLatest Version: 3.2.0Latest Release: Aug 20, 2026
Weakforced is an anti-abuse and brute-force protection daemon for mail and authentication systems.
Support summary
Weakforced currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
No announced EOL date is currently listed.
Supported cycles
1
0 lts
Versions
9
Latest Version
3.2.0
Active Support
1
EOL
8
Lifecycle Timeline
Dec 11, 2018As of Sep 27, 2026
3.2Active · Date not announced
3.0EOL · Aug 20, 2026
2.12EOL · Aug 20, 2025
2.10EOL · Nov 5, 2025
2.8EOL · Dec 20, 2023
2.6EOL · Dec 5, 2022
2.4EOL · Nov 24, 2021
2.2EOL · Aug 5, 2020
2.0EOL · Nov 25, 2019
ActiveSecurityEOLHistorical phase unknown
Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 3.2 | Aug 20, 2026 | Maintained | Date not announced | 3.2.0 | No | Active |
| 3.0 | Aug 20, 2025 | Ended | Aug 20, 2026 | 3.0.1 | No | EOL |
| 2.12 | Aug 23, 2024 | Ended | Aug 20, 2025 | 2.12.1 | No | EOL |
| 2.10 | Dec 5, 2023 | Ended | Nov 5, 2025 | 2.10.3 | No | EOL |
| 2.8 | Dec 5, 2022 | Ended | Dec 20, 2023 | 2.8.0 | No | EOL |
| 2.6 | Nov 24, 2021 | Ended | Dec 5, 2022 | 2.6.2 | No | EOL |
| 2.4 | Aug 5, 2020 | Ended | Nov 24, 2021 | 2.4.1 | No | EOL |
| 2.2 | Nov 7, 2019 | Ended | Aug 5, 2020 | 2.2.2 | No | EOL |
| 2.0 | Dec 11, 2018 | Ended | Nov 25, 2019 | 2.0.1 | No | EOL |
Data sources
Sources
Embed this badge
Show Weakforced's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.
Markdown
[](https://eol.wiki/weakforced/)HTML
<a href="https://eol.wiki/weakforced/"><img src="https://eol.wiki/badge/weakforced.svg" alt="Weakforced end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of Weakforced have reached end of life?
The following Weakforced versions have reached end of life and no longer receive security updates: 3.0, 2.12, 2.10, 2.8, 2.6, 2.4, 2.2, 2.0. It is recommended to upgrade to a supported version.
Is it safe to continue using Weakforced 3.0?
Weakforced 3.0 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 Weakforced?
The latest version of Weakforced is 3.2.0, released in the 3.2 release cycle.
How many versions of Weakforced are currently supported?
Weakforced currently has 1 actively supported version(s): 3.2.
When does Weakforced 3.2 reach end of life?
Weakforced 3.2 does not have a specific end-of-life date announced yet.
What should I do when Weakforced reaches end of life?
When a Weakforced 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.