Bun End of Life (EOL) Dates and End of Support (EOS) Dates
Bun 1.4.5 is the current supported release. Track Bun end of life dates — EOL, EOS and EOSL dates — across all 1 release. Also see Next.js end of support dates for related end-of-life information.
Currently Supported Bun Releases - Active EOS/EOSL Support (1)
| Release | Released | Security Support | Latest |
|---|---|---|---|
| 1 | (3 years and 2 months ago) | Active | 1.4.5 (2 days ago) |
If you are checking Bun end of life dates before you commit a project to it, the short answer is that this open-source JavaScript runtime has no published expiry date, and its support policy is thinner than the one Node.js follows. Here is what that means for your servers, your lockfile and your next version upgrade.
Bun End of Life: Is There an EOL Date for the Runtime?
No. The community-maintained tracker at endoflife.date lists Bun 1 as released on 7 September 2023 and flags the project as having no clearly defined support policy. Nothing on that page says when a given line stops getting security patches, so there is no EOL countdown to put in a calendar.
That differs from other open-source software developers rely on. Node.js publishes a date for every major line. The tracker's own advice for Bun is simply to run one of the supported release numbers listed in its table, which at the time of writing means 1.4.4, published on 22 October 2026.
Bun Support Policy and Release Schedule
Bun ships frequent releases from a single trunk rather than maintaining parallel long-term support branches. There is no release schedule that promises a fixed cadence, and no announced support timeline for older minors. In practice, Bun support means the newest stable release: that is an inference from how the project publishes, not a promise from its maintainers, so treat it as the working assumption for planning.
What a Version Number Tells You
A patch bump such as 1.4.3 to 1.4.4 carries bug fixes, while a new minor can add features or move internals. The 1.4.0 line, for example, rewrote the runtime from Zig to Rust. Read the release notes on GitHub before each update, because they are the only place behavior changes are announced.
Check Your Release With bun --version
Run bun --version in the terminal where you did the first install to see which build you are on, then compare it with the latest release. The official documentation covers the upgrade command, and you can install the newest build over the old one without touching your projects.
Support Timeline: Milestones From Bun 1.0 to 1.4.4
Because no schedule exists, the useful view is the history of what actually shipped. This table tracks the milestones that matter when judging the bun version you run.
| Release | Date | What changed |
|---|---|---|
| Bun 1.0 | 7 September 2023 | First stable release of the runtime |
| Bun 1.2 | January 2025 | Built-in S3 client and Bun.sql, text lockfile bun.lock by default |
| Bun 1.4.0 | August 2026 | Runtime rewritten in Rust |
| Bun 1.4.4 | 22 October 2026 | Latest release listed by endoflife.date |
Older lines are not listed with a separate maintenance window, so a project pinned to an early 1.x build has no documented source of patches.
What Happens After EOL: Security Patches and Unpatched Risk
Once a runtime stops receiving fixes, every newly disclosed vulnerability stays unpatched in that line. Scanners then flag the runtime itself, and your enterprise security team has no upstream fix to point to. That is the real risk behind any EOL notice, and it applies to Bun whenever you fall behind its newest release.
Node.js 20 as a Real Example of Unpatched Risk
Node.js 20 reached end-of-life on 30 April 2026, and a CVE such as CVE-2025-23166, a denial-of-service in the crypto code, shows why a pinned EOL line is a liability. CVE-2025-23167 (HTTP request smuggling) and CVE-2025-27210 (a Windows path traversal) landed against the same line. Fixes shipped in later 20.x builds, but anything disclosed after the cutoff gets no upstream security fix, so a production server pinned there stays exposed.
Why Bun Has No Runtime Sandbox
Bun runs code with full trust. Node.js has an opt-in permission flag and Deno is deny-by-default (Deno asks before file, network or environment access), so on an old Bun build you have only your own isolation, such as containers, to limit the damage.
JavaScript Runtime Lifespans: Node.js LTS Compared With Bun
Node.js is the benchmark for a predictable lifecycle. Each major version passes through Current, then Active LTS, then Maintenance LTS, and finally EOL, as the table shows.
| Node.js line | Status |
|---|---|
| Node.js 18 | End-of-life on 30 April 2025 |
| Node.js 20 | End-of-life on 30 April 2026 |
| Node.js 25 | End-of-life on 31 March 2026 |
| Node.js 22 | Maintenance LTS |
| Node.js 24 | Active LTS |
| Node.js 26 | Current |
Active LTS vs Maintenance LTS
Active LTS gets bug fixes and select improvements, while Maintenance LTS gets only critical fixes. Bun publishes no equivalent split, so every release is effectively treated as current.
Why Odd-Numbered Node.js Releases Matter
Deno has its own versioning, but Node.js is the clearer lifecycle reference here. Odd lines such as 25 never reach LTS and go straight to EOL after about six months, so they suit experiments rather than production. Bun has no odd/even convention, which is one more reason to follow its newest release.
Is the Bun Runtime Ready for Production? Ownership, License and Stability
Ownership matters for longevity. Anthropic announced its acquisition of Bun on 3 December 2025 and said Bun would stay open source and MIT-licensed, a promise you can verify on the project's GitHub page. Companies already run it in production: Claude Code is distributed as a Bun single-file executable, and Railway built its serverless functions product on Bun. Those are signs of commitment, not a written lifecycle guarantee, and the performance story is a separate question from how long a given release is maintained. The wider ecosystem and community are active, but you still own the upgrade discipline.
Node.js, npm and TypeScript Compatibility for the Bun Runtime
Bun positions itself as a drop-in replacement for Node.js that reads your package.json, resolves packages from the npm registry into node_modules and runs TypeScript directly on JavaScriptCore. Bun 1.4 passes about 97% of the node:http, node:fs and node:stream test suites, which is high but not complete, so check your own dependencies.
Package Manager, Test Runner and Bundler in One
One single binary bundles the package manager, test runner and bundler. You can run bun install or bun test inside an existing Node.js project without switching your server, keeping npm as the registry and the same node_modules layout. That makes the tooling a low-commitment way to adopt Bun, and a failed bun install is easy to roll back to npm if upstream fixes stop.
Where Compatibility Falls Short
Fastify, NestJS and APM agents such as Datadog and New Relic do not officially support Bun, and Strapi 5 cannot use it as a server runtime. A vendor benchmark says little about a server-side API that depends on a native addon, a common failure point. With no EOL guarantee from Bun, test your framework and any npm package with native code, and keep Node.js and npm as your fallback server stack.
How to Upgrade the Bun Runtime Safely
Run bun upgrade to move to the newest release, then rerun bun install and bun test before you deploy to production. Commit the updated lockfile so teammates and CI resolve identical dependencies, so an npm-based CI step and a Bun step stay in agreement. If your lockfile is still the older binary format, convert it to bun.lock first.
Pin Bun in Docker and CI
Install from a pinned script, and pin an exact Bun version in your Docker image tag and CI config so an unplanned release cannot change production builds, and install that exact build in every environment. Schedule a recurring check on the first of the month rather than upgrading ad hoc.
When the Runtime Reaches EOL: Migration or Extended Support
If Bun's missing lifecycle is a blocker, you have three options. Stay current with each release, plan a migration back to a supported Node.js LTS line, or, for Node.js specifically, buy never-ending support from a vendor such as HeroDevs once official EOL passes. Many teams build with Bun and run on Node.js, and Deno is a third option if a permission model matters more to you than Bun's tooling.
Track Bun Release Notes and EOL Updates
Subscribe to the RSS feed (the same tracker also covers Deno and Node.js) or the iCalendar feed on endoflife.date, which also publishes a JSON API, and watch the GitHub releases page for each new latest release. A tracked feed means an EOL announcement, if one ever appears, reaches you the same day.