macOS
brew install cargo-binstallprovider-native install command
brew / rank 1233
Binary installation for rust projects. Version 1.21.1 via Homebrew; verified 2026-07-25.
install
brew install cargo-binstallprovider-native install command
overview
Binary installation for rust projects
history
cargo-binstall is a Cargo subcommand for installing Rust command-line tools from prebuilt binaries when possible, falling back to source builds when needed. Its package-history importance is that it tackles the pain of `cargo install` compile times without requiring every Rust tool author to become a full package maintainer.
The public cargo-binstall repository was created in December 2020. The README describes Binstall as a low-complexity alternative to building from source with `cargo install` or manually downloading release archives.
The project evolved around reuse of existing ecosystem metadata: it fetches crate information from crates.io, checks the linked repository for matching releases and artifacts, can fall back to quickinstall artifacts, supports alternate targets, and uses `cargo install` as a last resort.
cargo-binstall is packaged through Homebrew, Nix, Arch Linux, and Scoop according to the supplied source facts, and its README documents Homebrew installation plus official shell one-liners and a first-party GitHub Action.
Adoption is also indirect: the README notes that cargo-update can automatically use Binstall if present, and that taiki-e/install-action has dedicated support for selected tools while using Binstall for others.
Users typically run `cargo binstall <crate>` to install a binary crate from a matching release artifact. For CI, the README recommends `--no-confirm`, and for maintainers it documents optional `[package.metadata.binstall]` configuration in Cargo.toml.
The SUPPORT.md documentation explains how maintainers can specify package URLs, archive formats, binary directories, disabled strategies, target overrides, and cfg expressions so Binstall can find release artifacts reliably.
cargo-binstall is significant because Rust's source-first install story is elegant but expensive. For command-line tools, users often want the package-manager experience of downloading a binary, while maintainers may already publish GitHub release artifacts.
For package nerds it occupies the space between language registries and system package managers: it reads crates.io metadata and Cargo.toml hints, locates release assets, respects targets and signatures where available, and only compiles when the binary path fails.
security posture
narrow executable package without higher-risk signals.
green risk · low confidence · appliance
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
cargo-binstall | executable | indexed executable | Discovered from the local executable index. |
freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
install metadata
| Package key | brew:cargo-binstall |
|---|---|
| Version | 1.21.1 |
| Package manager | Homebrew |
| Homepage | https://github.com/cargo-bins/cargo-binstall |
| Repository | https://github.com/cargo-bins/cargo-binstall |
| Last updated | 2026-07-25T14:57:32Z |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
source trail
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
View the package source record on GitHub.