# Install cargo-deny with Homebrew

Cargo plugin for linting your dependencies. Version 0.20.2 via Homebrew; verified 2026-07-09.

## Install

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

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install cargo-deny
```

  Evidence: provider-native install command

## Package facts

- **Package key:** brew:cargo-deny
- **Package manager:** Homebrew
- **Version:** 0.20.2
- **Source summary:** Cargo plugin for linting your dependencies
- **Homepage:** <https://github.com/EmbarkStudios/cargo-deny>
- **Repository:** <https://github.com/EmbarkStudios/cargo-deny>
- **Last updated:** 2026-07-09T22:03:47Z
- **Generated:** 2026-08-03T00:40:33+00:00

## Executables

- cargo-deny (alias)

## Install behavior

- Bottle: not available

## Freshness

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

cargo-deny is an Embark Studios Cargo plugin for linting Rust dependency graphs. It checks advisories, license policy, banned crates, duplicate versions, and allowed package sources from a project-level deny.toml file.

### Project history

Embark Studios created the repository and published the crate in May 2019. The README frames cargo-deny as an open-source release of a tool Embark uses internally, with a dedicated book for in-depth documentation.

The project grew into one of the standard Rust dependency-policy tools, with docs organized around checks for licenses, bans, advisories, and sources. Its repository topics and README both present it as a Cargo subcommand for dependency linting.

### Adoption history

cargo-deny has broad adoption for Rust CI because it covers policy decisions that Cargo itself intentionally does not enforce: which licenses are acceptable, whether multiple versions are allowed, whether vulnerable advisories should fail builds, and which registries or git sources are trusted.

The tool is packaged in apk, Homebrew, dnf, Nix, and pacman, and crates.io metadata shows more than four million downloads by June 2026. The README also points to cargo-deny-action for GitHub Actions use.

### How it is used

The quickstart is `cargo install --locked cargo-deny && cargo deny init && cargo deny check`. The init command creates a deny.toml template in the current working directory unless a path is supplied.

Users commonly run `cargo deny check` in CI, or run targeted checks such as `cargo deny check licenses`, `cargo deny check bans`, `cargo deny check advisories`, and `cargo deny check sources`.

### Why package nerds care

cargo-deny is package-nerd infrastructure because it makes dependency policy executable. Instead of tracking license allowlists, source restrictions, duplicate-version rules, and advisories in prose, teams can encode them in deny.toml and fail builds consistently.

It is also an example of Cargo's external-tool model handling ecosystem governance concerns without bloating Cargo itself.

### Timeline

- 2019: GitHub repository created and first crates.io publication recorded.
- 2019-2020: Early 0.6.x tags show rapid iteration on dependency linting.
- 2024-2026: Release stream continues through 0.19.x.
- 2026: crates.io metadata shows more than four million downloads and version 0.19.9 current in the sampled registry data.

### Related projects

- cargo-deny-action packages cargo-deny for GitHub Actions workflows.
- RustSec advisory data is part of the broader ecosystem behind advisory checking.
- SPDX license identifiers and license lists are central to the licenses check documented by cargo-deny.

### Sources

- <https://api.github.com/repos/EmbarkStudios/cargo-deny>
- <https://crates.io/api/v1/crates/cargo-deny>
- <https://embarkstudios.github.io/cargo-deny>
- <https://github.com/EmbarkStudios/cargo-deny#readme>
- <https://github.com/EmbarkStudios/cargo-deny/blob/main/docs/src/cli/init.md>


## Security Notes

No matching local secret-handling manifest was found for cargo-deny. Nucleus package metadata is still published here so future coverage has a stable package URL.



## 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: <cwd>/deny.toml

## Combined YAML source

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


## Sources

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