# Installer brush avec Homebrew, MacPorts, Nix, pacman Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de brush pour les workflows d'agents IA. ## installation ```sh sudo av install brew:brush ``` Commandes d'installation supplémentaires: ### macOS - Homebrew (100%): ```sh brew install brush ``` Preuve: local Homebrew formula metadata - MacPorts (94%): ```sh sudo port install brush ``` Preuve: MacPorts ports tree: shells/brush/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ### Linux - Nix (92%): ```sh nix profile install nixpkgs#brush ``` Preuve: nixpkgs package indexes: pkgs/by-name/br/brush/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - pacman (92%): ```sh sudo pacman -S brush ``` Preuve: Arch Linux sync databases: brush from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz ## Faits du paquet - **Clé du paquet:** brew:brush - **Gestionnaire de paquets:** Homebrew - **Version:** 0.4.0 - **Résumé source:** Bourne RUsty SHell (command interpreter) - **Page d'accueil:** - **Dépôt:** - **Dernière mise à jour:** 2026-06-15T10:20:11-04:00 - **Généré:** 2026-08-03T19:37:03+00:00 ## exécutables - brush (alias) ## Comportement d'installation - Bouteille: non disponible ## Version et fraîcheur - page générée: 2026-08-03 - version du gestionnaire: 0.4.0 ## Historique du projet et usages brush, the Bourne RUsty SHell, is a Rust shell that aims to run existing Bash and POSIX shell scripts while adding modern interactive behavior such as syntax highlighting and autosuggestions. Its packaging story is notable because it is a new shell trying to be installable as a boring system command rather than only as a Rust crate. ### Historique du projet The project presents itself as a modern Bash- and POSIX-compatible shell written in Rust. Its README emphasizes compatibility with existing `.bashrc` files, aliases, functions, and completions, while the compatibility reference documents a test suite that compares behavior against Bash. Unlike experimental shells that define a new language first, brush starts from the existing shell ecosystem. Its published identity is conservative: preserve Bash behavior, add Rust implementation benefits and interactive features, and expose an embeddable `brush_core::Shell` for Rust programs. ### Historique d'adoption The official installation section lists Homebrew, Arch Linux, MSYS2, cargo-binstall, GitHub release binaries, and Nix, while the provided package facts also list Homebrew, MacPorts, Nix, and pacman. That puts brush in the normal multi-distribution pipeline for shell tools despite being a young implementation. Adoption is still early compared with Bash, zsh, fish, or Oil/YSH, but the presence of distribution packages and a crates.io-oriented install path gives it several routes into developer workstations. ### Modes d'utilisation brush can be launched as an interactive shell and is designed to read existing Bash startup files. The README says `.bashrc` should work unchanged, with optional `~/.brushrc` and TOML configuration for brush-specific behavior. Its current use case is compatibility testing, interactive daily-driver experimentation, and embedding shell behavior inside Rust programs. The compatibility reference marks many Bash features as supported while still documenting gaps such as `select`, `wait -n`, and some background-job details. ### Pourquoi les passionnés de paquets s'y intéressent Shells are unusually package-sensitive because installing them is not enough: users may add them to login-shell databases, invoke them from scripts, and expect startup files and completions to work. brush is interesting because it tries to enter that old Unix contract while being implemented in Rust. For maintainers, brush is a compact example of the modern Rust reimplementation wave applied to one of the hardest compatibility targets: Bash. ### Chronologie - 2025: brush documentation describes itself as Bash- and POSIX-compatible and ready for many daily-driver use cases. - 2025: Official README documents Homebrew, Arch Linux, MSYS2, cargo-binstall, GitHub release, and Nix installation routes. - 2026: Provided package facts show brush packaged in Homebrew, MacPorts, Nix, and pacman ecosystems. ### Related projects - GNU Bash is the primary compatibility target and behavioral oracle. - POSIX shell is the standards baseline named by the project. - reedline provides the line-editing experience cited by brush for highlighting and suggestions. - Nushell, fish, zsh, and Oil/YSH are adjacent shells, though brush is more explicitly Bash-compatible than most of them. ### Sources - - - - source_facts.package-manager ## Notes de sécurité generalized runtime or code generation signal. - **Risque Geiger:** yellow / moyen - generalized runtime or code generation 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: ~/.bashrc, ~/.brushrc, ~/.config/brush/config.toml ## Autres enregistrements de gestionnaires de paquets - Nix - brush: normalized package name match | nixpkgs package indexes: pkgs/by-name/br/brush/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - pacman - brush - 0.4.0-1: normalized package name match | Arch Linux sync databases: brush from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Bash/POSIX-compatible shell implemented in Rust | https://github.com/reubeno/brush - MacPorts - brush: normalized package name match | MacPorts ports tree: shells/brush/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/brush.yml](https://github.com/mxcl/pkgdb/blob/main/combined/brush.yml) ## Sources - 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