# Installer massdriver avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de massdriver pour les workflows d'agents IA.

## installation

```sh
sudo av install brew:massdriver
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install massdriver
```

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:massdriver
- **Gestionnaire de paquets:** Homebrew
- **Version:** 2.2.1
- **Résumé source:** Manage applications and infrastructure on Massdriver Cloud
- **Page d'accueil:** <https://www.massdriver.cloud/>
- **Dépôt:** <https://github.com/massdriver-cloud/mass>
- **Dernière mise à jour:** 2026-07-31T21:29:53Z
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- mass (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 2.2.1
## Historique du projet et usages

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.

### Historique du projet

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.

### Historique d'adoption

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.

### Modes d'utilisation

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.

### Pourquoi les passionnés de paquets s'y intéressent

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.

### Chronologie

- 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.

### Sources

- <https://api.github.com/repos/massdriver-cloud/mass>
- <https://docs.massdriver.cloud/>
- <https://docs.massdriver.cloud/reference/cli/overview>
- <https://github.com/massdriver-cloud/mass>
- <https://github.com/massdriver-cloud/mass/releases?page=9>
- source_facts.package-manager-url


## Notes de sécurité

infrastructure mutation or orchestration signal.

- **Risque Geiger:** orange / moyen
- 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)


## Sources

- 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