Automic VaultAutomic Vault

brew

使用 Homebrew, Nix 安装 cargo-bundle

查看 cargo-bundle 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install cargo-bundle

local Homebrew formula metadata

Linux

Nix已验证 · 92%
nix profile install nixpkgs#cargo-bundle

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

概览

软件包摘要

Wrap rust executables in OS-specific app bundles

命令和别名

  • cargo-bundle

历史

项目历史与用法

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

项目历史

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.

采用历史

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.

使用方式

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.

为什么软件包爱好者会关心

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.

时间线

  • 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.

来源

  • 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

安全态势

风险级别:绿色

narrow executable package without higher-risk signals.

风险分类器

绿色 风险 · 低 置信度 · appliance

原因

  • narrow executable package without higher-risk signals

信号

  • metadata:no-higher-risk-signals

安装行为

  • formula 元数据中未记录 Homebrew post-install 钩子。
  • Homebrew bottle 元数据适用于 6 个平台目标。
  • 构建元数据列出 2 个构建依赖。

建议审查

在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。

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

可执行文件

已安装的可执行文件

命令类型暴露范围备注
cargo-bundlecli全局可执行文件

新鲜度

版本和新鲜度

这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时,才会提示版本落后。

页面生成时间2026-07-10
管理器版本0.11.0
管理器更新时间2026-05-31
本地数据OK
上游当前
检测到的最新版本v0.11.0

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

  • OK没有生成新鲜度警告。

安装元数据

软件包元数据

软件包键brew:cargo-bundle
版本0.11.0
软件包管理器Homebrew
软件包管理器页面https://formulae.brew.sh/formula/cargo-bundle
主页https://github.com/burtonageo/cargo-bundle
仓库https://github.com/burtonageo/cargo-bundle
上游文档https://github.com/burtonageo/cargo-bundle#readme
许可证Apache-2.0 OR MIT
源码归档https://github.com/burtonageo/cargo-bundle/archive/refs/tags/v0.11.0.tar.gz
最后更新2026-05-31T10:36:43Z
Pulseupdated
构建依赖pkgconf, rust
Bottle可用 (于 arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install未定义
服务未声明

注册表事实

源数据库详情

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

源数据库匹配

其他软件包管理器记录

匹配项来自外部软件包管理器索引,并与本地 Automic Vault 软件包链接分开显示。

Nix95%

cargo-bundle

nix profile install nixpkgs#cargo-bundle
  • normalized package name match
  • 匹配方式: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

来源线索

由仓库数据生成

此页面由 av-webscripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。

使用的来源

  • 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