← ← Back to all products
Express
Active
FrameworksLatest Version: 5.2.1Latest Release: Dec 1, 2025
Express is a minimal and flexible Node.js web application framework providing HTTP utility methods and middleware.
Support summary
Express 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
2
0 lts
Versions
5
Latest Version
5.2.1
Active Support
2
EOL
3
Lifecycle Timeline
Today ↓
5
5
4
4
3
3
2
2
1
1
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 5 | Sep 9, 2024 | Yes | No | 5.2.1 | No | Active |
| 4 | Apr 9, 2014 | Yes | No | 4.22.2 | No | Active |
| 3 | Oct 23, 2012 | No | Jul 5, 2015 | 3.21.2 | No | EOL |
| 2 | Mar 17, 2011 | No | Jul 1, 2012 | 2.5.11 | No | EOL |
| 1 | Nov 16, 2010 | No | Mar 1, 2011 | 1.0.9 | No | EOL |
Data sources
Sources
Frequently Asked Questions
Which versions of Express have reached end of life?
The following Express versions have reached end of life and no longer receive security updates: 3, 2, 1. It is recommended to upgrade to a supported version.
Is it safe to continue using Express 3?
Express 3 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 Express?
The latest version of Express is 5.2.1, released in the 5 release cycle.
How many versions of Express are currently supported?
Express currently has 2 actively supported version(s): 5, 4.
When does Express 5 reach end of life?
Express 5 does not have a specific end-of-life date announced yet.
What should I do when Express reaches end of life?
When a Express 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.