Packages / bun

APT repository · deb.freshdeb.com/bunprinted 4 Nov 2026, 01:42 UTC

bun

Bun, a JavaScript and TypeScript runtime that aims to be a drop-in replacement for Node.js. The one binary also bundles code, runs tests and installs npm packages. This is the one freshdeb package not built from source, so you trust upstream's build for it. One release line for Debian 12 and 13, Ubuntu 22.04, 24.04 and 26.04 on amd64 and arm64.

Componentmain

follows every upstream release, minors and majors included. Currently 1.4.4.

Release line
Deliver to
bun 1.4.4-1+freshdeb~deb13

1Trust the signing key (once per machine)

sudo install -d -m 0755 /etc/apt/keyrings
curl -fsSL https://deb.freshdeb.com/freshdeb-archive-keyring.gpg \
  | sudo tee /etc/apt/keyrings/freshdeb-archive-keyring.gpg >/dev/null

Fingerprint 3BBD F03A 9C0B F890 F8CA 9510 7595 CC55 468F 3161. How to verify.

2Add the source

sudo tee /etc/apt/sources.list.d/freshdeb-bun.sources >/dev/null <<EOF
Types: deb
URIs: https://deb.freshdeb.com/bun
Suites: $(. /etc/os-release && echo $VERSION_CODENAME)
Components: main
Signed-By: /etc/apt/keyrings/freshdeb-archive-keyring.gpg
EOF

With auto, the shell reads the codename from /etc/os-release on the machine you paste this into.

3Install

sudo apt update && sudo apt install bun
apt policy bun   # expect 1.4.4-1+freshdeb~…

Before you install bun

Neither Debian nor Ubuntu ship bun. An install from upstream's script stays in ~/.bun/bin, and the PATH line it uses puts that first, so that copy keeps running. Remove it, or take it out of PATH, to use this package.

bun 1.4.4-1+freshdeb~deb13

How it's packaged

No distribution packages bun, so the packaging is ours, written the way Debian would. The build, the defaults and the layout follow upstream's wherever upstream has them.

Distributions
None of the supported releases ship Bun. The packaging is ours, around upstream's release binary.
Binary
Upstream's release binary, byte for byte and not stripped. Building Bun needs an exact LLVM, a Rust nightly, a previous Bun and a prebuilt JavaScriptCore, which the builders can't pin.
Checks
The release zips are pinned by sha256 (also in upstream's SHASUMS256.txt), and the build checks that the binary reports the pinned version and commit.
Layout
/usr/bin/bun and /usr/bin/bunx, with bash, zsh and fish completions from the pinned tag. LICENSE.md in /usr/share/doc/bun lists the statically linked libraries, with their licenses.
Updates
bun upgrade isn't turned off, so update with apt. As root and with unzip installed, bun upgrade replaces /usr/bin/bun behind dpkg's back, and the next package update overwrites that again. Without unzip it stops with an error.
Global packages
bun install -g installs to ~/.bun, not /usr.
Release lines
One, main, which follows every release: upstream supports only its latest.

Packing list

Every release line of bun and the distributions it's built for. Each line is its own APT component and only gets the releases it follows (main: every upstream release, minors and majors included). After upstream end of life it stops building but stays installable. Hatched cells have no build: usually that distribution already ships the same or a newer version itself.

LineComponentCurrentbookwormDebian 12trixieDebian 13jammyUbuntu 22.04nobleUbuntu 24.04resoluteUbuntu 26.04Support
main main 1.4.4 built: 1.4.4-1built: 1.4.4-1built: 1.4.4-1built: 1.4.4-1built: 1.4.4-1 –

Versions follow <upstream>-<revision>+freshdeb~<distro>, distro being deb12, deb13, ubuntu22.04, ubuntu24.04 or ubuntu26.04, for amd64 and arm64. Published versions are never rebuilt or replaced.

Contents

bun
The runtime, bundler, test runner and package manager, as bun and bunx, with shell completions.

Origin

Upstream
github.com/oven-sh/bunupstream's release binary, unchanged and not built from source, pinned by sha256
Packaging
our own, in Debian's styleno distribution packages bun
Built for
bookworm, trixie, jammy, noble, resoluteamd64, arm64, packaged natively
Files
package.yaml · debian/ · report an issuepackage.yaml explains every change

Also in Developer tools

Maintained by Blendbyte

Blendbyte builds cloud infrastructure, web apps, and developer tools. We've been shipping software to production for 20+ years.

These packages run in our own stack, which is why we keep them maintained. Issues and PRs get read. Good ones get merged.

Also from Blendbytenginx-modules.com: pre-built nginx dynamic modules (Brotli, GeoIP2, ModSecurity and more) for nginx.org's nginx, on the same Debian and Ubuntu releases.

Tindra: self-hosted error tracking and monitoring that works with Sentry SDKs. Packaged here, like everything else.