Automic VaultAutomic Vault

brew

cargo-component mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install cargo-component

local Homebrew formula metadata

Linux

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

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

Überblick

Paketzusammenfassung

Create WebAssembly components based on the component model proposal

Befehle und Aliase

  • cargo-component

Verlauf

Projektgeschichte und Nutzung

cargo-component is a Bytecode Alliance Cargo subcommand for creating WebAssembly components from Rust projects. It exists to bridge Cargo workflows with the WebAssembly component model, WIT interfaces, generated bindings, and component dependencies.

Projektgeschichte

The repository was created in 2022 under the Bytecode Alliance. Its README describes cargo-component as an experimental attempt to imagine what first-class Rust support for WebAssembly components might look like before Cargo itself has native component-model support.

The project grew alongside Bytecode Alliance work on the WebAssembly component model, wit-bindgen, Wasmtime, and WASI Preview 2. It uses Cargo.toml metadata and generates Rust bindings so component interfaces can be used in a Cargo-like development loop.

Adoptionsgeschichte

Adoption has followed the WebAssembly component-model community rather than general Rust CLI usage. crates.io metadata shows hundreds of thousands of downloads by June 2026, and Homebrew and Nix packaging make it easier to install for component-model experiments and CI builds.

The README notes that Rust's upstream wasm32-wasip2 target now produces components for some WASI use cases, leaving cargo-component most relevant where projects need non-WASI WIT interfaces, component dependencies, or features not yet covered by plain Cargo.

Wie es verwendet wird

The documented flow starts with `cargo component new --lib <name>` or a command component, creates a `wit/world.wit` interface, implements generated bindings in Rust, and builds with `cargo component build`.

The tool can also add and update component interface dependencies through Cargo.toml, and it supports adapter configuration in `[package.metadata.component]` for WASI Preview 1 to Preview 2 adaptation.

Warum Paket-Nerds sich dafür interessieren

cargo-component is significant because it treats WebAssembly components as packageable dependencies inside Cargo projects. For package ecosystem watchers, it is a live example of how Rust's package manager might evolve when language packages and portable component interfaces meet.

It also marks a transitional period: component-model tooling is moving quickly, and the README explicitly frames cargo-component as useful until more support lands in the Rust compiler and Cargo.

Zeitleiste

  • 2021: crates.io records an initial cargo-component publication.
  • 2022: GitHub repository created under bytecodealliance/cargo-component.
  • 2024: README references Rust 1.82 adding the upstream wasm32-wasip2 target.
  • 2025: GitHub releases show the 0.21.x series.

Related projects

  • The WebAssembly component model defines the component format cargo-component targets.
  • wit-bindgen generates bindings for WIT interfaces and is closely related to cargo-component's generated Rust bindings.
  • Wasmtime supplies WASI adapter work referenced by the README.
  • Rust's wasm32-wasip2 target is an upstream alternative for some WASI-only component builds.

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 8 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.toml.vscode/settings.json

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
cargo-componentcliglobales 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.21.1
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.21.1

https://github.com/bytecodealliance/cargo-component

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:cargo-component
Version0.21.1
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/cargo-component
Homepagehttps://github.com/bytecodealliance/cargo-component
Repositoryhttps://github.com/bytecodealliance/cargo-component
Upstream-Dokumentationhttps://github.com/bytecodealliance/cargo-component#readme
LizenzApache-2.0
Quellarchivhttps://github.com/bytecodealliance/cargo-component/archive/refs/tags/v0.21.1.tar.gz
Build-Abhängigkeitenrust
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namecargo-component
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-component

nix profile install nixpkgs#cargo-component
  • normalized package name match
  • Abgeglichen nach: Cargo Component
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/ca/cargo-component/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