# cargo-about mit Homebrew, Nix, pacman installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für cargo-about in AI-Agent-Workflows.

## Installation

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

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install cargo-about
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#cargo-about
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/ca/cargo-about/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

- pacman (92%):

```sh
sudo pacman -S cargo-about
```

  Evidenz: Arch Linux sync databases: cargo-about from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

## Paketfakten

- **Paketschlüssel:** brew:cargo-about
- **Paketmanager:** Homebrew
- **Version:** 0.9.1
- **Quellzusammenfassung:** Cargo plugin to generate list of all licenses for a crate
- **Homepage:** <https://github.com/EmbarkStudios/cargo-about>
- **Repository:** <https://github.com/EmbarkStudios/cargo-about>
- **Zuletzt aktualisiert:** 2026-06-30T12:38:26Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- cargo-about (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 0.9.1
## Projektgeschichte und Nutzung

cargo-about is an Embark Studios Cargo plugin for generating license listings for the full dependency graph of a Rust crate. It sits at the intersection of Cargo metadata, SPDX license data, and release compliance work.

### Projektgeschichte

Embark Studios created the public cargo-about repository in November 2019 and released it as one of its open-source Rust tools. The README states that Embark uses and likes the tool internally, while warning that it is not legal advice.

The project provides both a command-line Cargo subcommand and an mdBook manual. Its normal workflow is to initialize an about.toml and template, then generate a license output such as an HTML notice file from dependency metadata.

### Adoptionsgeschichte

cargo-about's adoption follows Rust projects that need repeatable license disclosure for dependency-heavy applications. The supplied package-manager facts list Homebrew, Nix, and Arch Linux packages, and the upstream README documents installation from crates.io and Arch Linux.

The project also benefited from Embark's wider open-source Rust toolchain presence. Its repository topics include SPDX, license-checking, Cargo plugin, and Rust, which describe the niche it occupies among Cargo subcommands.

### Wie es verwendet wird

The documented starting workflow is `cargo about init`, which creates about.toml and about.hbs in a Cargo project, followed by `cargo about generate about.hbs` to produce license information.

The official book documents commands and configuration for generating, clarifying, and working around license metadata issues, making cargo-about more of a compliance-report generator than a general dependency-audit scanner.

### Warum Paket-Nerds sich dafür interessieren

cargo-about matters because open-source license obligations are one of the least glamorous but most important parts of shipping packaged software. Rust's transitive dependency graphs can be large, and cargo-about turns that graph into a reproducible artifact for release notes, installers, game bundles, and product distributions.

For package nerds, its importance is also cultural: it is a Cargo subcommand that treats package metadata as operational data, using Cargo manifests and SPDX license identifiers to make dependency compliance automatable.

### Zeitleiste

- 2019: cargo-about repository created on GitHub.
- 2019: GitHub releases show an initial 0.0.1 release in November.
- 2026: Repository metadata shows continued maintenance, Rust implementation, and licensing/SPDX topics.

### Related projects

- cargo-about is related to Cargo itself, SPDX license data, crates.io package metadata, and docs.rs API documentation.
- It overlaps culturally with cargo-deny and cargo-audit: all three turn Cargo dependency metadata into release or security decisions, but cargo-about focuses on license listings rather than vulnerability or policy enforcement.

### Quellen

- <https://api.github.com/repos/EmbarkStudios/cargo-about>
- <https://embarkstudios.github.io/cargo-about/>
- <https://github.com/EmbarkStudios/cargo-about>
- <https://raw.githubusercontent.com/EmbarkStudios/cargo-about/main/README.md>
- source_facts.package-manager


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- 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: <manifest_root>/about.toml
## Andere Paketmanager-Einträge

- Nix - cargo-about: normalized package name match | nixpkgs package indexes: pkgs/by-name/ca/cargo-about/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- pacman - cargo-about - 0.8.4-2: normalized package name match | Arch Linux sync databases: cargo-about from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Cargo plugin to generate list of all licenses for a crate | https://github.com/EmbarkStudios/cargo-about


## Combined YAML source

View the package source record on GitHub. [combined/cargo-about.yml](https://github.com/mxcl/pkgdb/blob/main/combined/cargo-about.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph