# Install cargo-update with Homebrew

Cargo subcommand for checking and applying updates to installed executables. Version 22.1.1 via Homebrew; verified 2026-07-28.

## Install

```sh
sudo av install brew:cargo-update
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install cargo-update
```

  Evidence: provider-native install command

## Package facts

- **Package key:** brew:cargo-update
- **Package manager:** Homebrew
- **Version:** 22.1.1
- **Source summary:** Cargo subcommand for checking and applying updates to installed executables
- **Homepage:** <https://github.com/nabijaczleweli/cargo-update>
- **Repository:** <https://github.com/nabijaczleweli/cargo-update>
- **Last updated:** 2026-07-28T04:45:39Z
- **Generated:** 2026-08-03T00:40:33+00:00

## Executables

- cargo-install-update (alias)
- cargo-install-update-config (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 22.1.1
## Project history and usage

cargo-update provides Cargo subcommands for checking and applying updates to executables installed with `cargo install`.

### Project history

The official manual says cargo-update was built from frustration with periodically checking cargo-installed executables for updates. The README presents `cargo install-update` and `cargo install-update-config` as the two user-facing commands.

### Adoption history

GitHub records the repository as created in October 2016, and crates.io records the first cargo-update release the same month. The input package facts list Alpine, Homebrew, Nix, and Arch packages.

### How it is used

The manual documents updating all installed packages with `cargo install-update -a`, updating selected packages, listing without updating, using cargo-binstall when appropriate, and configuring per-package build options with `cargo install-update-config`.

### Why package nerds care

cargo-update fills a long-standing package-manager gap for Cargo-installed CLI tools: it gives users a repeatable way to discover and apply crate executable updates while preserving per-package install options.

### Timeline

- 2016: GitHub repository created and first crates.io release recorded.
- 2026: crates.io records max_version 20.0.2.

### Related projects

- The manual documents optional cargo-binstall integration and relies on Cargo registry metadata and Cargo install state.

### Sources

- <https://api.github.com/repos/nabijaczleweli/cargo-update>
- <https://github.com/nabijaczleweli/cargo-update>
- <https://docs.rs/cargo-update>
- <https://github.com/nabijaczleweli/cargo-update#readme>
- <https://rawcdn.githack.com/nabijaczleweli/cargo-update/man/cargo-install-update-config.1.html>
- <https://rawcdn.githack.com/nabijaczleweli/cargo-update/man/cargo-install-update.1.html>
- <https://crates.io/api/v1/crates/cargo-update>
- <https://formulae.brew.sh/api/formula/cargo-update.json>


## 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_HOME/.install_config.toml, ~/.cargo/.install_config.toml

## Credential files

- Unix: $CARGO_HOME/credentials, $CARGO_HOME/credentials.toml, ~/.cargo/credentials, ~/.cargo/credentials.toml

## Combined YAML source

View the package source record on GitHub. [combined/cargo-update.yml](https://github.com/automic-vault/db/blob/main/combined/cargo-update.yml)


## Sources

- Nucleus package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation