macOS
brew install bunlocal Homebrew formula metadata
sudo port install bunMacPorts ports tree · devel/bun/Portfile · ソース: api.github.com
brew
bun のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。
インストール
brew install bunlocal Homebrew formula metadata
sudo port install bunMacPorts ports tree · devel/bun/Portfile · ソース: api.github.com
nix profile install nixpkgs#bunnixpkgs package indexes · pkgs/by-name/bu/bun/package.nix · ソース: api.github.com
sudo pacman -S bunArch Linux sync databases · bun · ソース: geo.mirror.pkgbuild.com
choco install bunChocolatey community package catalog · bun · ソース: community.chocolatey.org
scoop install main/bunScoop official bucket manifest trees · bucket/bun.json · ソース: api.github.com
winget install --id Oven-sh.Bun -eWindows Package Manager source index · Oven-sh.Bun · ソース: cdn.winget.microsoft.com
概要
Incredibly fast JavaScript runtime, bundler, test runner, and package manager
履歴
Bun is an all-in-one JavaScript and TypeScript toolkit: runtime, package manager, script runner, test runner, package runner, and bundler shipped as a single executable.
Bun was created as a response to the accumulated layers of Node.js-era JavaScript tooling. The official 1.0 announcement, published on September 8, 2023, framed Bun as a stable, production-ready toolkit for running, building, testing, and debugging JavaScript and TypeScript.
The project is powered by JavaScriptCore rather than V8 and is designed as a faster, leaner, more modern replacement for Node.js while preserving compatibility with npm packages, Node-style module resolution, CommonJS, ES modules, Web APIs, and many Node built-ins.
Bun's documentation later described it as written in Rust and powered by JavaScriptCore, while the GitHub README emphasizes that the single `bun` command includes the runtime plus test runner, script runner, package manager, and package runner.
Bun moved from an alternative runtime curiosity into mainstream JavaScript tooling after the 1.0 release because it promised speed without forcing developers to abandon existing package.json projects. Official install paths include shell installer, npm, Homebrew, Docker, and Windows PowerShell, and package-manager metadata now lists it across Homebrew, Chocolatey, MacPorts, Nix, pacman, Scoop, and winget.
Its adoption is tied to projects experimenting with faster local feedback loops: replacing Node for script execution, replacing npm/yarn/pnpm for installs, replacing Jest/Vitest in some tests, and replacing separate bundlers for simple build cases.
Common commands include `bun run` for scripts and TypeScript files, `bun install` for npm-compatible dependency installation, `bun test` for tests, `bun build` for bundling, and `bunx` for executing packages. Configuration is optional and lives in local or global `bunfig.toml` files for Bun-specific settings.
Bun's package manager writes `node_modules`, reads package.json, uses a global cache, and supports workspaces and npm registry configuration. Because it aims to run existing Node.js applications with little or no change, usage often starts as a drop-in replacement for selected scripts rather than a full-stack rewrite.
Bun is significant because it collapses several previously separate JavaScript package tools into one binary. For package historians, it marks a major post-Node/npm phase where runtime, package manager, test runner, and bundler compete as integrated developer platforms rather than independent commands.
It is also important because it made package-manager performance and lockfile workflows part of a runtime's identity. Bun's rise pressured the broader ecosystem to treat install speed, TypeScript startup, test speed, and Node compatibility as one developer-experience surface.
セキュリティ状態
bun に一致するローカルシークレット処理マニフェストは見つかりませんでした。将来の対応で安定したパッケージ URL を使えるよう、Nucleus パッケージメタデータはここに公開されています。
エージェントに無人実行させる前に、このツールが平文の認証情報を読むか、リモート状態を書き込むか、成果物を公開するか、プラグインを起動するかを確認してください。
local files
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Config paths the tool may read or write during local use.
bunfig.toml~/.bunfig.toml$XDG_CONFIG_HOME/.bunfig.tomlCredential-bearing paths to review before unattended agent runs.
bunfig.toml~/.bunfig.toml$XDG_CONFIG_HOME/.bunfig.toml実行可能ファイル
| コマンド | 種類 | 公開範囲 | メモ |
|---|---|---|---|
bun | cli | グローバル実行可能ファイル | |
bunx | cli | グローバル実行可能ファイル |
鮮度
これらの信号は、ページ生成時期、パッケージマネージャの活動、上流リリース比較を分けて示します。バージョン遅れは、証拠 URL と比較可能なバージョンがある場合だけ警告されます。
https://github.com/oven-sh/bun
インストールメタデータ
| パッケージキー | brew:bun |
|---|---|
| バージョン | 1.3.14 |
| パッケージマネージャ | Homebrew |
| パッケージマネージャページ | https://formulae.brew.sh/formula/bun |
| ホームページ | https://bun.com/ |
| リポジトリ | https://github.com/oven-sh/bun |
| 上流ドキュメント | https://bun.com/docs |
| ライセンス | MIT AND LGPL-2.0-or-later AND Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND IJG AND LGPL-2.1-or-later AND Zlib AND (Apache-2.0 WITH LLVM-exception) |
| ソースアーカイブ | https://github.com/oven-sh/bun.git |
| 最終更新 | 2026-06-03T16:56:51Z |
| Pulse | updated |
| ビルド依存関係 | cmake, llvm@21, ninja, rust |
| Bottle | 利用可能 (対象 arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux) |
| Homebrew post-install | 定義済み |
| サービス | 宣言なし |
レジストリ情報
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | bun |
| Version Scheme | 0 |
| Revision | 0 |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
ソースデータベース一致
一致は外部パッケージマネージャインデックスから取得され、ローカルの Automic Vault パッケージリンクとは分けて表示されます。
bun
nix profile install nixpkgs#bunbun 1.3.14-1
Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one
https://github.com/oven-sh/bun
sudo pacman -S bunbun
sudo port install bunbun
choco install bunmain/bun
scoop install main/bunOven-sh.Bun
winget install --id Oven-sh.Bun -eソース経路
このページは scripts/generate-pkg-sqlite.py が生成した非公開のパッケージ SQLite アーティファクトから av-web によって提供されます。
View the package source record on GitHub.