← ← Back to all products
All badges & lifecycle API →
BunEnd of Life (EOL) Dates & Support Status
Active
Runtimes & JDKsLatest Version: 1.4.2Latest Release: Sep 4, 2026
Bun is an all-in-one JavaScript runtime, bundler, transpiler, and package manager focused on speed.
Support summary
Bun 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
1
Latest Version
1.4.2
Active Support
1
EOL
0
Lifecycle Timeline
Sep 7, 2023As of Sep 27, 2026
1Active · Date not announced
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 |
|---|---|---|---|---|---|---|
| 1 | Sep 7, 2023 | Maintained | Date not announced | 1.4.2 | No | Active |
Data sources
Embed this badge
Show Bun'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/bun/)HTML
<a href="https://eol.wiki/bun/"><img src="https://eol.wiki/badge/bun.svg" alt="Bun end-of-life status" height="20"></a>Frequently Asked Questions
Is it safe to continue using Bun 1?
Bun 1 is currently supported and receiving updates. You can continue using it safely until its end-of-life date.
What is the latest version of Bun?
The latest version of Bun is 1.4.2, released in the 1 release cycle.
How many versions of Bun are currently supported?
Bun currently has 1 actively supported version(s): 1.
When does Bun 1 reach end of life?
Bun 1 does not have a specific end-of-life date announced yet.
What should I do when Bun reaches end of life?
When a Bun 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.