Automic VaultAutomic Vault

brew

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

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install brush

local Homebrew formula metadata

MacPortsvérifié · 94%
sudo port install brush

MacPorts ports tree · shells/brush/Portfile · Source: api.github.com

Linux

Nixvérifié · 92%
nix profile install nixpkgs#brush

nixpkgs package indexes · pkgs/by-name/br/brush/package.nix · Source: api.github.com

Arch Linux pacmanvérifié · 92%
sudo pacman -S brush

Arch Linux sync databases · brush · Source: geo.mirror.pkgbuild.com

aperçu

Résumé du paquet

Bourne RUsty SHell (command interpreter)

historique

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.

posture de sécurité

Niveau de risque : yellow

generalized runtime or code generation signal.

Classificateur de risque

risque yellow · confiance moyen · runtime

Pourquoi

  • generalized runtime or code generation signal

Signaux

  • text:interpreter,shell

Comportement d'installation

  • Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
  • Les métadonnées de bottle Homebrew sont disponibles pour 6 plateformes.
  • Les métadonnées de compilation listent 1 dépendances de compilation.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

local files

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

Config paths the tool may read or write during local use.

Unix
~/.bashrc~/.brushrc~/.config/brush/config.toml

exécutables

Exécutables installés

CommandeTypeExpositionNote
brushcliexécutable global

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-07-25
version du gestionnaire0.4.0
gestionnaire mis à jour2026-06-15
données localesOK
amontnot checked
dernière version détectéenon détecté

https://github.com/reubeno/brush

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:brush
Version0.4.0
Gestionnaire de paquetsHomebrew
Page du gestionnaire de paquetshttps://formulae.brew.sh/formula/brush
Page d'accueilhttps://brush.sh
Dépôthttps://github.com/reubeno/brush
Docs amonthttps://brush.sh/docs
LicenceMIT
Archive sourcehttps://github.com/reubeno/brush/archive/refs/tags/brush-shell-v0.4.0.tar.gz
Dernière mise à jour2026-06-15T10:20:11-04:00
Pulseupdated
Dépendances de compilationrust
Bouteilledisponible (sur arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
post-install Homebrewnon défini
Serviceaucun déclaré

faits du registre

Détails de la base source

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namebrush
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

correspondances dans les bases sources

Autres enregistrements de gestionnaires de paquets

Les correspondances proviennent d’index externes de gestionnaires de paquets et restent séparées des liens de paquets Automic Vault locaux.

Nix95%

brush

nix profile install nixpkgs#brush
  • normalized package name match
  • Correspondance par : Brush
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/br/brush/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
pacman95%

brush 0.4.0-1

Bash/POSIX-compatible shell implemented in Rust

https://github.com/reubeno/brush

sudo pacman -S brush
  • License: MIT
  • Architecture: x86_64
  • 2 Dépendances
  • normalized package name match
  • Correspondance par : Brush
Arch Linux sync databases · geo.mirror.pkgbuild.com · Arch Linux sync databases: brush from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz
MacPorts95%

brush

sudo port install brush
  • normalized package name match
  • Correspondance par : Brush
MacPorts ports tree · api.github.com · MacPorts ports tree: shells/brush/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Sources utilisées

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment