# whalebrew を Homebrew でインストール

whalebrew のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。

## インストール

```sh
sudo av install brew:whalebrew
```

追加のインストールコマンド:

### macOS

- Homebrew (100%):

```sh
brew install whalebrew
```

  証拠: local Homebrew formula metadata

## パッケージ情報

- **パッケージキー:** brew:whalebrew
- **パッケージマネージャ:** Homebrew
- **バージョン:** 0.5.0
- **ソース概要:** Homebrew, but with Docker images
- **ホームページ:** <https://github.com/whalebrew/whalebrew>
- **リポジトリ:** <https://github.com/whalebrew/whalebrew>
- **最終更新:** 2026-07-25T22:40:20+02:00
- **生成日時:** 2026-08-03T19:37:03+00:00

## 実行可能ファイル

- whalebrew (エイリアス)

## インストール挙動

- Bottle: 利用不可

## バージョンと鮮度

- ページ生成日: 2026-08-03
- マネージャ版: 0.5.0
## プロジェクトの歴史と使われ方

Whalebrew is a Go command-line tool that makes Docker images behave like native commands by installing executable wrappers for them. Its README summarizes the idea as Homebrew, but with Docker images: package a CLI in a container, then run it from the shell as though it were installed locally.

The project sits at the intersection of Docker packaging and developer workstation hygiene. It was designed for tools such as awscli, ffmpeg, wget, and other CLIs whose dependencies can be awkward or intrusive when installed directly on a host.

### プロジェクトの歴史

The Whalebrew repository was created in January 2017, during the period when Docker had become a common developer packaging substrate beyond server deployment. The first GitHub release, 0.0.1, followed on 26 January 2017, and a 0.1.0 release appeared in March 2017.

The README credits Justin Cormack's dockercommand-cli as the original idea, then extends that idea into a package-manager-like workflow: install an image, create a command wrapper, and run Docker with the current directory mounted into the container.

Whalebrew releases continued over a long period, with 0.2.x releases in 2019-2020, 0.3.x in 2021, 0.4.x in 2022-2023, and 0.5.0 in August 2024. That slow release cadence reflects a mature niche tool rather than a rapidly changing application platform.

### 採用の歴史

Whalebrew's adoption is strongest among developers who like the isolation of Docker images but want a local command UX. It maintains a set of known-compatible images under the whalebrew organization and also allows arbitrary Docker Hub images when their entrypoint and filesystem behavior fit the model.

The project never needed to become a universal package manager to be useful. Its value is narrower: it gives teams and individuals a repeatable way to distribute CLIs with complex dependencies while leaving the host relatively clean.

### 使われ方

A user installs an image such as whalebrew/wget, after which Whalebrew writes an executable wrapper such as /usr/local/bin/wget or another configured install path. Running that command invokes Docker, binds the current working directory into /workdir, sets the working directory, and forwards arguments to the container entrypoint.

Package authors make Whalebrew-friendly images by setting the command as the Docker image entrypoint and ensuring the tool works on files under /workdir. Optional Docker labels define the exposed command name, environment variables, volumes, ports, networks, working directory behavior, missing-volume behavior, and required Whalebrew version.

### パッケージ好きにとっての重要性

Whalebrew is package-nerd significant because it treats Docker images as package artifacts for command-line tools, not only as deployable services. It also shows the tension between native package managers and container packaging: native commands are fast and integrated, while containerized commands are isolated and portable but have startup and filesystem tradeoffs.

The generated wrapper format is intentionally simple: an executable file with a Whalebrew shebang and YAML describing how to run the image. That makes the package boundary inspectable, which matters for users who care exactly what a packaged command is doing.

### タイムライン

- 2017-01-22: The Whalebrew repository is created.
- 2017-01-26: GitHub release metadata records Whalebrew 0.0.1.
- 2017-03-23: GitHub release metadata records Whalebrew 0.1.0.
- 2019-2020: GitHub release metadata records the 0.2.x line.
- 2021: GitHub release metadata records Whalebrew 0.3.0 and 0.3.1.
- 2022-2023: GitHub release metadata records the 0.4.x line.
- 2024-08-02: GitHub release metadata records Whalebrew 0.5.0.

### Related projects

- dockercommand-cli is credited in the README as the original idea.
- Docker Hub and the whalebrew image organization provide the package substrate.
- Homebrew is the naming and UX analogy, while Docker is the execution substrate.

### ソース

- <https://github.com/justincormack/dockercommand-cli>
- <https://github.com/whalebrew/whalebrew>
- <https://github.com/whalebrew/whalebrew/blob/master/README.md>
- <https://github.com/whalebrew/whalebrew/releases>


## セキュリティノート

broad file, network, media, or database tool signal.

- **Geiger リスク:** blue / 中
- broad file, network, media, or database tool signal


## Configuration and credential file locations

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.


## Configuration files

- Unix: ${WHALEBREW_CONFIG_DIR}/config.yaml, ~/.whalebrew/config.yaml, $XDG_CONFIG_HOME/whalebrew/config.yaml, $XDG_DATA_DIRS/*/whalebrew/config.yaml

## Combined YAML source

View the package source record on GitHub. [combined/whalebrew.yml](https://github.com/mxcl/pkgdb/blob/main/combined/whalebrew.yml)


## ソース

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph
