# Install cargo-outdated with Homebrew

Cargo subcommand for displaying when Rust dependencies are out of date. Version 0.19.0 via Homebrew; verified 2026-06-22.

## Install

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

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install cargo-outdated
```

  Evidence: provider-native install command

## Package facts

- **Package key:** brew:cargo-outdated
- **Package manager:** Homebrew
- **Version:** 0.19.0
- **Source summary:** Cargo subcommand for displaying when Rust dependencies are out of date
- **Homepage:** <https://github.com/kbknapp/cargo-outdated>
- **Repository:** <https://github.com/kbknapp/cargo-outdated>
- **Last updated:** 2026-06-22T14:02:58-07:00
- **Generated:** 2026-08-03T00:40:33+00:00

## Executables

- cargo-outdated (alias)

## Install behavior

- Bottle: not available

## Freshness

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

cargo-outdated is a Cargo subcommand that reports when Rust project dependencies have newer compatible or latest versions available.

### Project history

The project was created on GitHub in August 2015 and first published to crates.io as version 0.1.1 in November 2015. Its README describes the core approach as creating a temporary workspace, running Cargo's built-in cargo update machinery, and comparing dependency trees.

### Adoption history

The crate is distributed through crates.io and has also been packaged by multiple operating-system package managers, including Homebrew, Debian, Ubuntu, Alpine, Arch, and Nix according to the batch source facts. crates.io metadata lists it under development-tools and cargo-plugin categories.

### How it is used

Users install it as cargo-outdated and run cargo outdated from a project directory. The README documents list and JSON output, workspace checking, dependency ignore and exclusion options, manifest-path support, and an exit-code option for automation.

### Why package nerds care

It is one of the older Rust ecosystem tools for auditing dependency freshness without immediately changing the project lockfile, making it useful to maintainers who want npm-outdated-style visibility in Cargo workflows.

### Timeline

- 2015: GitHub repository created and first crates.io release published.
- 2024: v0.15.0 release published on GitHub.
- 2026: crates.io reported v0.19.0 as the latest release.

### Related projects

- Cargo's cargo update command is central to cargo-outdated's implementation.
- cargo-binstall is documented by the README as a way to install prebuilt versions.

### Sources

- <https://api.github.com/repos/kbknapp/cargo-outdated>
- <https://github.com/kbknapp/cargo-outdated>
- <https://github.com/kbknapp/cargo-outdated#readme>
- <https://crates.io/api/v1/crates/cargo-outdated>
- <https://formulae.brew.sh/api/formula/cargo-outdated.json>


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## Combined YAML source

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


## Sources

- Nucleus package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation