Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%

brew install cargo-binstall

local Homebrew formula metadata

Linux

Nixverifiziert · 92%

nix profile install nixpkgs#cargo-binstall

nixpkgs package indexes · pkgs/by-name/ca/cargo-binstall/package.nix · Quelle: api.github.com

Arch Linux pacmanverifiziert · 92%

sudo pacman -S cargo-binstall

Arch Linux sync databases · cargo-binstall · Quelle: geo.mirror.pkgbuild.com

Windows

Scoopverifiziert · 92%

scoop install main/cargo-binstall

Scoop official bucket manifest trees · bucket/cargo-binstall.json · Quelle: api.github.com

Überblick

Paketzusammenfassung

Binary installation for rust projects

Projektlinks

Befehle und Aliase

cargo-binstall

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

2020: cargo-binstall repository created on GitHub.
2026: GitHub repository metadata shows active maintenance and a large user signal for a Cargo installer tool.
2026: README documents release-asset installation, quickinstall fallback, a first-party GitHub Action, signatures, and telemetry controls.

Related projects

cargo-binstall is related to cargo install, crates.io, GitHub/GitLab release assets, cargo-quickinstall, and cargo-update.
The README also names cargo-run-bin for project-scoped tool management, taiki-e/install-action for CI installation, and support metadata in Cargo.toml for maintainers who publish binaries.

Quellen

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

narrow executable package without higher-risk signals

Signale

metadata:no-higher-risk-signals

Installationsverhalten

In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

Befehl	Art	Sichtbarkeit	Hinweis
`cargo-binstall`	cli	globales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25

Manager-Version1.21.0

Manager aktualisiert2026-07-14

lokale DatenOK

Upstreamaktuell

neueste erkannte Versionv1.21.0

https://github.com/cargo-bins/cargo-binstall

OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüssel	brew:cargo-binstall
Version	1.21.0
Paketmanager	Homebrew
Paketmanager-Seite	https://formulae.brew.sh/formula/cargo-binstall
Homepage	https://github.com/cargo-bins/cargo-binstall
Repository	https://github.com/cargo-bins/cargo-binstall
Upstream-Dokumentation	https://github.com/cargo-bins/cargo-binstall#readme
Lizenz	GPL-3.0-only
Quellarchiv	https://github.com/cargo-bins/cargo-binstall/archive/refs/tags/v1.21.0.tar.gz
Zuletzt aktualisiert	2026-07-14T11:55:05Z
Pulse	updated
Build-Abhängigkeiten	rust
Bottle	verfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	nicht definiert
Dienst	keiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	cargo-binstall
Version Scheme	0
Revision	0
Head Version	HEAD
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	head stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

cargo-binstall

nix profile install nixpkgs#cargo-binstall

normalized package name match
Abgeglichen nach: Cargo Binstall

nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/ca/cargo-binstall/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

pacman95%

cargo-binstall 1.20.0-1

Binary installation for Rust projects

https://github.com/cargo-bins/cargo-binstall

sudo pacman -S cargo-binstall

License: GPL-3.0-only
Architecture: x86_64
3 Abhängigkeiten
normalized package name match
Abgeglichen nach: Cargo Binstall

Arch Linux sync databases · geo.mirror.pkgbuild.com · Arch Linux sync databases: cargo-binstall from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

Scoop95%

main/cargo-binstall

scoop install main/cargo-binstall

normalized package name match
Abgeglichen nach: Cargo Binstall

Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/cargo-binstall.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

Paketgraph

Links stammen aus dem lokalen Paketbeziehungsgraph, Ergänzungen, Abhängigkeitskanten, Ecosystem-Matches und Paket-Hub-Mitgliedschaft.

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Combined YAML source

View the package source record on GitHub.

combined/cargo-binstall.yml

Verwendete Quellen

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

cargo-binstall mit Homebrew, Nix, pacman, scoop installieren