# Install cargo-all-features with Homebrew, Nix, pacman Cargo subcommands to build and test all feature flag combinations. Version 1.12.0 via Homebrew; verified from local package data. ## Install ```sh sudo av install brew:cargo-all-features ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install cargo-all-features ``` Evidence: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#cargo-all-features ``` Evidence: nixpkgs package indexes: pkgs/by-name/ca/cargo-all-features/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - pacman (92%): ```sh sudo pacman -S cargo-all-features ``` Evidence: Arch Linux sync databases: cargo-all-features from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz ## Package facts - **Package key:** brew:cargo-all-features - **Package manager:** Homebrew - **Package manager page:** - **Version:** 1.12.0 - **Source summary:** Cargo subcommands to build and test all feature flag combinations - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** Apache-2.0 OR MIT - **Source archive:** - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - cargo-all-features (cli) - cargo-build-all-features (cli) - cargo-check-all-features (cli) - cargo-test-all-features (cli) - cargo-all-features (alias) - cargo-build-all-features (alias) - cargo-check-all-features (alias) - cargo-test-all-features (alias) ## Build dependencies - rust ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 1.12.0 - Local data: ok - Upstream repository: https://github.com/frewsxcv/cargo-all-features - Upstream latest detected: 1.12.0 (current) - info: No package-manager update timestamp was available. ## Project history and usage cargo-all-features is a small Cargo subcommand suite for building, checking, and testing Rust crates across combinations of feature flags. It addresses a Rust-specific packaging problem: feature combinations can compile differently, and CI matrices often miss bad interactions. ### Project history The public repository was created in May 2020. Its README frames the tool around Cargo package and workspace commands that run subcommands across all feature flag combinations. The project stayed intentionally narrow: it provides `cargo all-features` plus build, check, and test variants, with configuration kept in Cargo.toml under package metadata. ### Adoption history Adoption is niche but practical among Rust crate maintainers who use optional dependencies and feature-gated APIs. The supplied package-manager facts list Homebrew, Nix, and Arch Linux packages, showing that the tool became available beyond `cargo install`. The README's rationale is CI maintenance: manually updating per-feature jobs is easy to forget, and testing only individual flags is not exhaustive. ### How it is used Users run commands such as `cargo all-features build`, `cargo all-features check`, or `cargo all-features test` at a package or workspace root. The tool then exercises feature flag combinations for the requested Cargo subcommand. Configuration lives in Cargo.toml under `[package.metadata.cargo-all-features]`, where users can skip incompatible feature sets, include or deny selected features, cap combination size, and split work into chunks for CI. ### Why package nerds care cargo-all-features is package-nerd useful because Rust feature flags are part of package identity. A crate version is not just one build; it may expose many combinations that downstream packages rely on. Its value is not broad fame but sharp ergonomics: it turns a maintenance-prone CI matrix into a Cargo-native check that package authors can run locally or in automation. ### Timeline - 2020: cargo-all-features repository created on GitHub. - 2020: Git tags include an early 0.1.0 tag and later 1.x releases. - 2026: Repository metadata shows the project still available with Rust, Cargo, testing, and feature-flag topics. ### Related projects - cargo-all-features is related to Cargo feature flags, Cargo workspaces, and Rust CI systems that need to test optional dependency combinations. - It is conceptually adjacent to cargo-hack, another Rust ecosystem tool often used for feature-combination checking, though this batch's official sources only document cargo-all-features itself. ### Sources - - - - - source_facts.package-manager ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - narrow executable package without higher-risk signals ## 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: Cargo.toml ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** cargo-all-features - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Other Package-Manager Records - Nix - cargo-all-features: normalized package name match | nixpkgs package indexes: pkgs/by-name/ca/cargo-all-features/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - pacman - cargo-all-features - 1.12.0-3: normalized package name match | Arch Linux sync databases: cargo-all-features from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | A Cargo subcommand to build and test all feature flag combinations | https://github.com/frewsxcv/cargo-all-features ## Related links - [Source-control packages](https://www.automicvault.com/pkg/source-control-tools/) - Belongs to a source-control command family. - [Package publisher tools](https://www.automicvault.com/pkg/package-publishers/) - Belongs to a package publishing or registry command family. - [Developer build packages](https://www.automicvault.com/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata. - [Networking and protocol packages](https://www.automicvault.com/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata. - [rust](https://www.automicvault.com/pkg/brew/rust/) - Build dependency declared by Homebrew. - [cargo-hack](https://www.automicvault.com/pkg/brew/cargo-hack/) - Package names and metadata indicate a similar tool family. Shared terms: cargo, combinations, feature. - [cargo-about](https://www.automicvault.com/pkg/brew/cargo-about/) - Package names and metadata indicate a similar tool family. Shared terms: all, cargo. - [cargo-all-features](https://www.automicvault.com/pkg/cargo/cargo-all-features/) - Same normalized package name exists in another local package ecosystem. ## Combined YAML source View the package source record on GitHub. [combined/cargo-all-features.yml](https://github.com/automic-vault/db/blob/main/combined/cargo-all-features.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph