Automic VaultAutomic Vault

brew

cargo-bundle mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install cargo-bundle

local Homebrew formula metadata

Linux

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

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

Überblick

Paketzusammenfassung

Wrap rust executables in OS-specific app bundles

Befehle und Aliase

  • cargo-bundle

Verlauf

Projektgeschichte und Nutzung

cargo-bundle is a Cargo subcommand for wrapping Rust GUI executables into operating-system application bundles and installer formats.

Projektgeschichte

The cargo-bundle repository was created in January 2016 and the first crates.io release followed in March 2016. The README positions it as a tool for generating macOS app bundles, iOS bundles, Debian packages, and experimental Windows MSI installers from Cargo-built executables.

Its design centers on a `[package.metadata.bundle]` section in Cargo.toml. That metadata describes user-facing application attributes such as name, identifier, icon, version, resources, copyright, category, descriptions, Debian dependencies, macOS frameworks, and URL schemes.

Adoptionsgeschichte

cargo-bundle occupies a narrower niche than compiler or profiling Cargo plugins: desktop and GUI Rust applications. Crates.io reports more than 150,000 downloads, and the input records Homebrew and Nix packaging.

The project remained useful because early Rust desktop applications needed a Cargo-native way to bridge from a compiled binary to platform packaging conventions without adopting a full application framework.

Wie es verwendet wird

Users install it with `cargo install cargo-bundle`, add `[package.metadata.bundle]` to Cargo.toml, and run `cargo bundle` from the package directory. The command supports familiar Cargo selectors and build controls such as `--bin`, `--example`, `--release`, `--profile`, `--target`, and feature flags.

The README documents output formats including deb, ios, msi, wxsmsi, osx, rpm, and appimage, while also warning that the project status is early alpha and that the metadata format is not guaranteed stable.

Warum Paket-Nerds sich dafür interessieren

cargo-bundle is historically interesting because it embeds desktop packaging metadata inside Cargo.toml rather than treating app bundling as an entirely external release step. It shows how Rust package metadata became a place for downstream packaging intent, not just dependency resolution.

For package maintainers, it connects Rust crates to platform-native artifacts such as `.app`, `.deb`, and `.msi`, making it a small but useful example of Cargo crossing from language package manager into OS package production.

Zeitleiste

  • 2016-01-10: GitHub repository burtonageo/cargo-bundle was created.
  • 2016-03-22: cargo-bundle 0.0.0 was published on crates.io.
  • 2016 onward: README documented `[package.metadata.bundle]` as the Cargo.toml integration point for bundle metadata.
  • 2026-05-30: Version 0.11.0 was published.

Related projects

  • Cargo provides the build and subcommand interface cargo-bundle extends.
  • Platform packaging formats documented by the project include macOS app bundles, Debian packages, Windows MSI installers, RPM packages, and AppImage.
  • The Rust desktop packaging space overlaps conceptually with later application-packaging frameworks, but cargo-bundle remains a small Cargo-native bundling tool.

Quellen

  • GitHub repository API metadata: https://api.github.com/repos/burtonageo/cargo-bundle
  • Official README: https://github.com/burtonageo/cargo-bundle#readme
  • Package-manager adoption from source_facts.package-manager.
  • crates.io API metadata and versions: https://crates.io/api/v1/crates/cargo-bundle

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Build-Metadaten listen 2 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.toml
Windows
Cargo.toml

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
cargo-bundlecliglobales 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-10
Manager-Version0.11.0
Manager aktualisiert2026-05-31
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.11.0

https://github.com/burtonageo/cargo-bundle

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:cargo-bundle
Version0.11.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/cargo-bundle
Homepagehttps://github.com/burtonageo/cargo-bundle
Repositoryhttps://github.com/burtonageo/cargo-bundle
Upstream-Dokumentationhttps://github.com/burtonageo/cargo-bundle#readme
LizenzApache-2.0 OR MIT
Quellarchivhttps://github.com/burtonageo/cargo-bundle/archive/refs/tags/v0.11.0.tar.gz
Zuletzt aktualisiert2026-05-31T10:36:43Z
Pulseupdated
Build-Abhängigkeitenpkgconf, rust
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-bundle
Version Scheme0
Revision0
Head VersionHEAD
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-bundle

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

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