# massdriver を Homebrew でインストール
massdriver のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。
## インストール
```sh
sudo av install brew:massdriver
```
追加のインストールコマンド:
### macOS
- Homebrew (100%):
```sh
brew install massdriver
```
証拠: local Homebrew formula metadata
## パッケージ情報
- **パッケージキー:** brew:massdriver
- **パッケージマネージャ:** Homebrew
- **バージョン:** 2.2.1
- **ソース概要:** Manage applications and infrastructure on Massdriver Cloud
- **ホームページ:**
- **リポジトリ:**
- **最終更新:** 2026-07-31T21:29:53Z
- **生成日時:** 2026-08-03T19:37:03+00:00
## 実行可能ファイル
- mass (エイリアス)
## インストール挙動
- Bottle: 利用不可
## バージョンと鮮度
- ページ生成日: 2026-08-03
- マネージャ版: 2.2.1
## プロジェクトの歴史と使われ方
Massdriver's `mass` CLI is the command-line client for managing applications and infrastructure on Massdriver Cloud. It packages Massdriver platform workflows - bundles, deployments, environments, projects, repositories, resource types, schemas, and related operations - into a Go command-line tool.
### プロジェクトの歴史
The public `mass` repository was created in November 2022. The initial 1.0.0 release in March 2024 bundled imported API work, examples, embedded help docs, preview environments, bundle template functionality, bundle build and publish commands, and configuration support.
The project has continued as a fast-moving platform CLI. The official README points to Homebrew, prebuilt GitHub release binaries, and `go install`; the official docs describe the CLI as the interface for building and publishing bundles, managing deployments, and interacting with the Massdriver platform. By June 2026, GitHub listed 86 releases and version 2.1.1 as the latest release.
### 採用の歴史
Massdriver's adoption is narrower than general-purpose developer tools because it is tied to the Massdriver Cloud platform. GitHub shows a small but active repository, and the supplied package metadata lists Homebrew packaging.
Within Massdriver users' workflows, the CLI is important because it makes platform actions scriptable and CI-friendly: users can install it with Homebrew or download release binaries, then operate bundles, resources, repositories, projects, and environments from a terminal.
### 使われ方
The official CLI docs say configuration can come from environment variables or from `~/.config/massdriver/config.yaml`, with `$XDG_CONFIG_HOME/massdriver/config.yaml` honored when set. Required values include an organization ID and API key, with an optional URL for self-hosted environments.
The CLI is used to build and publish infrastructure bundles, manage deployments, and call platform subcommands. The docs frame Massdriver itself as an internal developer platform that turns infrastructure-as-code modules into reusable, self-service components with validation, policies, and deployment workflows.
### パッケージ好きにとっての重要性
Massdriver is package-nerd relevant as an example of a vendor/platform CLI that still follows normal package-manager expectations: Homebrew formula, release binaries, Go module installation, shell completion, and structured config under XDG-compatible paths.
For DevOps users, the value is not the standalone binary alone but the ability to put platform operations into repeatable scripts and CI jobs without using the web console.
### タイムライン
- 2022: GitHub repository created.
- 2024: Initial 1.0.0 release of the Mass CLI.
- 2024: Early 1.x releases add bundle linting, artifact import, public bundle publishing, and version command work.
- 2026: GitHub lists 2.1.1 as the latest release in June 2026.
### Related projects
- Massdriver's CLI is part of the Massdriver Cloud ecosystem, alongside the Massdriver Catalog, Massdriver GitHub Actions, and Massdriver SDKs.
- It interacts with infrastructure-as-code domains including Terraform, OpenTofu, Helm, and Bicep through Massdriver bundles.
### ソース
-
-
-
-
-
- source_facts.package-manager-url
## セキュリティノート
infrastructure mutation or orchestration signal.
- **Geiger リスク:** orange / 中
- infrastructure mutation or orchestration 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: ~/.config/massdriver/config.yaml, $XDG_CONFIG_HOME/massdriver/config.yaml
## Credential files
- Unix: ~/.config/massdriver/config.yaml, $XDG_CONFIG_HOME/massdriver/config.yaml
## Combined YAML source
View the package source record on GitHub. [combined/massdriver.yml](https://github.com/mxcl/pkgdb/blob/main/combined/massdriver.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