cargo-bins

cargo-binstall: Install Rust Tools from Prebuilt Binaries

cargo-binstall finds and installs prebuilt binaries for Rust crates, reducing the wait and build requirements of cargo install. It is useful for developers and CI jobs when a compatible release artifact is available, with source installation as a fallback.

View on GitHub Compare
Stars
2.9k
Forks
122
Stars, last 30 days
+45

Our take

Health score

72/100

How it is scored
Activity
78
Community
76
Issues
61
Pull requests
74

+45 stars in the last 30 days

  • Releases more often than 93% of the projects we track
  • More contributors than 75% of the projects we track
  • Merges more pull requests than 75% of the projects we track

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

2,974

Forks

133

Change since Nov 17, 2026: 0 stars·0 forks

Overview

cargo-binstall is a Rust command-line installer that looks for prebuilt binaries associated with a crate, rather than compiling the crate from source as cargo install normally does. It uses crate metadata and searches linked releases, with a third-party artifact host as another option and source installation as a fallback.

It is intended for Rust developers who want a lower-friction way to install command-line tools, especially on constrained machines or in CI. It works best when a crate publishes compatible artifacts; crate authors can add metadata to help it locate those files.

Key Features

  • Installs Rust crate binaries when compatible prebuilt artifacts are available.
  • Falls back through supported artifact sources and ultimately to cargo install.
  • Supports similar command-line options to cargo install, including non-interactive use with --no-confirm.
  • Can install tools for multiple target platforms when matching packages are published.
  • Supports package signatures where maintainers provide signing information, with an option to require signed packages.
  • Offers crate authors metadata for describing artifact locations and formats.
  • Provides installation options for Linux, macOS, Windows, Homebrew, and GitHub Actions.

Use Cases

  • Rust developers installing command-line crates without waiting for a local source build, when a binary is available.
  • CI maintainers setting up Rust-based tools with --no-confirm or the project’s GitHub Actions setup.
  • Users on constrained devices who want to avoid the time or resource cost of compiling a crate.
  • Crate maintainers publishing release binaries who want users to install them through a standard Cargo-oriented workflow.

Getting Started

With Rust installed, build and install from source:

cargo install cargo-binstall --locked

See the README for prebuilt installation options, configuration, and crate author guidance.

Alternatives

  • conda: Conda installs binary packages and manages isolated environments across languages, while cargo-binstall installs prebuilt binaries for Rust crates.
  • pkgx: pkgx runs versioned tools on demand across multiple platforms, while cargo-binstall installs prebuilt Rust crate binaries as cargo tools.
ProjectLanguageLicenseStarsStatus
cargo-binstallRustGPL-3.02.9kNot checked yet
condaPython–7.5kActive
pkgxRustApache-2.09.9kActive

Considerations

  • Binary installation depends on compatible artifacts being published and discoverable. Some crates may require metadata or manual package options, and others will fall back to source compilation.
  • Signature verification support is limited to packages whose maintainers provide signing details. The README notes that relatively few ecosystem packages produce signatures.
  • When the quickinstall artifact host is used, anonymized installation statistics are collected by default. The README documents flags and configuration options to opt out.
  • The project is licensed under GPL-3.0, which may matter when incorporating or redistributing its code.

Found this useful?

Share it with someone who would like cargo-binstall.

Comparisons