# honcho を Homebrew, Nix でインストール

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

## インストール

```sh
sudo av install brew:honcho
```

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

### macOS

- Homebrew (100%):

```sh
brew install honcho
```

  証拠: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#honcho
```

  証拠: nixpkgs package indexes: pkgs/by-name/ho/honcho/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## パッケージ情報

- **パッケージキー:** brew:honcho
- **パッケージマネージャ:** Homebrew
- **バージョン:** 2.0.0
- **ソース概要:** Python clone of Foreman, for managing Procfile-based applications
- **ホームページ:** <https://github.com/nickstenning/honcho>
- **リポジトリ:** <https://github.com/nickstenning/honcho>
- **生成日時:** 2026-08-03T19:37:03+00:00

## 実行可能ファイル

- honcho (エイリアス)

## インストール挙動

- Bottle: 利用不可

## バージョンと鮮度

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

Honcho is a Python port of David Dollar's Foreman, built to run and manage applications described by a `Procfile`. It belongs to the Heroku/12-factor family of development tools: a small CLI reads process declarations, loads optional environment variables, and starts a local process group with prefixed logs.

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

The upstream README and Read the Docs site describe Honcho as a Python port of Foreman. That origin matters because Foreman popularized the `Procfile` workflow outside Heroku: put `web`, `worker`, and other process roles in one file, then run a single command during development.

Honcho's changelog shows a conventional Python CLI maturation path. By 2015 it had an explicit changelog and version command, then accumulated Windows fixes, process-output fixes, custom Procfile handling, and service export support.

### 採用の歴史

Honcho spread through Python packaging first and then into system package managers such as Homebrew and Nix. Its adoption is tied less to a large ecosystem of plugins and more to a durable need: Python developers wanted Foreman-style Procfile orchestration without depending on the Ruby implementation.

### 使われ方

A typical workflow is to write a `Procfile`, optionally write a `.env` file, and run `honcho start`. The docs also cover using Procfiles to coordinate related services during development and exporting process definitions to init systems.

Changelog milestones show the tool broadening from basic local process management into operational handoff features, including Upstart, supervisord, runit, and systemd export support.

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

Honcho is a classic package-manager bridge package: small, stable CLI; language-specific origin; useful across many app stacks. It also illustrates how a simple file convention, `Procfile`, became portable infrastructure vocabulary across Ruby, Python, shell, and other implementations.

### タイムライン

- 2015: Honcho starts keeping a changelog at version 0.6.0.
- 2016: Version 0.7.0 adds runit export support and `PROCFILE` environment-variable handling.
- 2017: Version 1.0.0 adds process-name environment exposure and shared no-colour/no-prefix flags.
- 2021: Version 1.1.0 adds systemd unit export support.
- 2024: Version 2.0.0 drops older Python/PyPy versions and adds Python 3.11 through 3.13 support.

### Related projects

- Foreman is the direct ancestor and design reference.
- Heroku Procfile documentation and the 12-factor config model provide the workflow conventions Honcho follows.
- systemd, runit, supervisord, and Upstart are related because Honcho can export process definitions for those service managers.

### ソース

- Homebrew input metadata: package-manager identity and executable.
- Honcho README and Read the Docs: project purpose, Foreman relationship, Procfile and `.env` workflow.
- Honcho changelog: release and feature milestones.


## セキュリティノート

narrow executable package without higher-risk signals.

- **Geiger リスク:** グリーン / 低
- narrow executable package without higher-risk signals


## 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: Procfile, .env
## 他のパッケージマネージャ記録

- Nix - honcho: normalized package name match | nixpkgs package indexes: pkgs/by-name/ho/honcho/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

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


## ソース

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