Automic VaultAutomic Vault

brew

cargo-dist mit Homebrew, Nix, pacman, apt, winget installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install cargo-dist

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#cargo-dist

nixpkgs package indexes · pkgs/by-name/ca/cargo-dist/package.nix · Quelle: api.github.com

Arch Linux pacmanverifiziert · 92%
sudo pacman -S cargo-dist

Arch Linux sync databases · cargo-dist · Quelle: geo.mirror.pkgbuild.com

Debian aptverifiziert · 92%
sudo apt install dist

Debian stable package indexes · dist · Quelle: deb.debian.org

Windows

Windows Package Managerverifiziert · 92%
winget install --id axodotdev.dist -e

Windows Package Manager source index · axodotdev.dist · Quelle: cdn.winget.microsoft.com

Überblick

Paketzusammenfassung

Tool for building final distributable artifacts and uploading them to an archive

Verlauf

Projektgeschichte und Nutzung

cargo-dist, now branded in its README as `dist`, is a release and binary-distribution tool from Axo that generates shippable artifacts, installers, release manifests, and CI workflows for Rust and other projects. It occupies the packaging layer between `cargo build` and public distribution channels such as GitHub Releases and package managers.

Projektgeschichte

The cargo-dist crate appeared on crates.io in September 2022, and the GitHub repository was created in October 2022. Its early identity was tightly Rust-centered, but the official README now labels the project `dist (formerly known as cargo-dist)`, reflecting its wider release-engineering ambitions.

The README describes the project as a tool that plans, builds, hosts, publishes, and announces releases. A defining design choice is generated CI: `dist init` can generate release workflows that wait for version tags, build artifacts on multiple platforms, create or edit GitHub Releases, and attach generated release notes and artifacts.

The project also documents self-hosting: dist's own releases are produced through dist-generated release machinery, with cargo-release used for version and changelog mechanics.

Adoptionsgeschichte

cargo-dist grew as Rust CLI authors wanted repeatable binary releases without maintaining bespoke GitHub Actions matrices and installer scripts. The supplied package-manager facts show packaging across Homebrew, Debian/Ubuntu as `dist`, Nix, Arch Linux, and winget, indicating adoption beyond the Rust-only install path.

crates.io records more than one hundred thousand downloads, while the GitHub repository has thousands of stars. That combination of registry use, cross-platform package-manager presence, and generated CI support makes it one of the more visible Rust-origin release automation tools.

Wie es verwendet wird

A typical user initializes configuration with `dist init`, commits the generated configuration and CI workflow, then publishes by pushing a version tag. dist plans the release, builds archives and installers, produces a machine-readable manifest, and can host artifacts on a GitHub Release.

Configuration can live in Cargo.toml, package.json, dist-workspace.toml, or dist.toml, which matches the project's move from a Cargo-only helper toward a general binary distribution tool.

Warum Paket-Nerds sich dafür interessieren

cargo-dist matters to package nerds because it treats release artifacts as first-class package metadata: archives, installers, checksums, changelogs, manifests, hosting locations, and package-manager publishing become a repeatable graph instead of ad hoc release notes.

It also captures a common Rust ecosystem pattern: a tool starts as a Cargo subcommand, then expands into broader developer tooling while keeping Cargo workspace integration as a core path.

Zeitleiste

  • 2022: cargo-dist crate first published on crates.io.
  • 2022: axodotdev/cargo-dist GitHub repository created.
  • 2024: README documents generated CI workflows, installers, release manifests, package publishing, and self-hosted releases.
  • 2026: crates.io metadata shows active updates and the 0.32.x release line.

Related projects

  • oranda is referenced by the README as a companion for generated project websites.
  • cargo-release is documented in the repository's release workflow for version, changelog, and tag mechanics.
  • GitHub Releases and GitHub Actions are central hosting and CI targets in the official documentation.

Sicherheitslage

Risikostufe: blue

broad file, network, media, or database tool signal.

Risikoklassifikator

blue Risiko · mittel Konfidenz · tool

Warum

  • broad file, network, media, or database tool signal

Signale

  • text:upload,archive

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

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

Config paths the tool may read or write during local use.

Unix
Cargo.tomlpackage.jsondist-workspace.tomldist.toml

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
distcliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25
Manager-Version0.32.0
Manager aktualisiert2026-05-22
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.32.0

https://github.com/axodotdev/cargo-dist

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:cargo-dist
Version0.32.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/cargo-dist
Homepagehttps://axodotdev.github.io/cargo-dist/
Repositoryhttps://github.com/axodotdev/cargo-dist
Upstream-Dokumentationhttps://axodotdev.github.io/cargo-dist/book
LizenzApache-2.0 OR MIT
Quellarchivhttps://github.com/axodotdev/cargo-dist/archive/refs/tags/v0.32.0.tar.gz
Zuletzt aktualisiert2026-05-22T09:34:54Z
Pulseupdated
Build-Abhängigkeitenrust
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namecargo-dist
Version Scheme0
Revision0
Head VersionHEAD
Conflicts With
  • nmh
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

cargo-dist

nix profile install nixpkgs#cargo-dist
  • normalized package name match
  • Abgeglichen nach: Cargo Dist
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/ca/cargo-dist/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
pacman95%

cargo-dist 0.32.0-1

Shippable application packaging for Rust

https://github.com/axodotdev/cargo-dist

sudo pacman -S cargo-dist
  • License: Apache-2.0 AND MIT
  • Architecture: x86_64
  • 3 Abhängigkeiten
  • normalized package name match
  • Abgeglichen nach: Cargo Dist
Arch Linux sync databases · geo.mirror.pkgbuild.com · Arch Linux sync databases: cargo-dist from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz
Debian apt92%

dist 1:3.5-236-1.1

Tools for developing, maintaining and distributing software

sudo apt install dist
  • Section: devel
  • Architecture: all
  • 4 Abhängigkeiten
  • installed executable or alias match
  • Abgeglichen nach: Dist
Debian stable package indexes · deb.debian.org · Debian stable package indexes: dist from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz
Ubuntu apt92%

dist 1:3.5-236-1

Tools for developing, maintaining and distributing software

sudo apt install dist
  • Section: universe/devel
  • Architecture: all
  • 4 Abhängigkeiten
  • installed executable or alias match
  • Abgeglichen nach: Dist
Ubuntu 24.04 LTS package indexes · archive.ubuntu.com · Ubuntu 24.04 LTS package indexes: dist from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz
winget92%

axodotdev.dist

winget install --id axodotdev.dist -e
  • installed executable or alias match
  • Abgeglichen nach: Dist
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: axodotdev.dist from https://cdn.winget.microsoft.com/cache/source.msix

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment