Automic VaultAutomic Vault

brew

cargo-chef mit Homebrew, apk, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install cargo-chef

local Homebrew formula metadata

Linux

Alpine Linux apkverifiziert · 92%
sudo apk add cargo-chef

Alpine Linux edge package indexes · cargo-chef · Quelle: dl-cdn.alpinelinux.org

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

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

Überblick

Paketzusammenfassung

Cargo subcommand to speed up Rust Docker builds using Docker layer caching

Befehle und Aliase

  • cargo-chef

Verlauf

Projektgeschichte und Nutzung

cargo-chef is a Cargo subcommand for making Rust container builds friendlier to Docker layer caching. It analyzes a project into a dependency recipe, builds that recipe in an earlier image layer, and lets later source-code-only changes reuse the expensive dependency build.

Projektgeschichte

The project was created by Luca Palmieri in 2020 and its README says it was initially developed for the deployment chapter of Zero to Production in Rust. The upstream repository describes the command as a way to speed up Rust Docker builds using Docker layer caching.

Its design codified a pattern Rust teams were already hand-rolling in Dockerfiles: copy manifests first, build dependencies, then copy application sources. cargo-chef made that approach workspace-aware and less fragile by generating a recipe from Cargo.toml and Cargo.lock inputs.

Adoptionsgeschichte

cargo-chef spread through Rust backend and CI workflows because Docker build cache misses are especially painful for projects with large dependency graphs. The project publishes a prebuilt Docker image, and the crate has accumulated millions of crates.io downloads, showing adoption beyond a one-off example tool.

Packaging in Homebrew, apk, and Nix reflects its use by developers who want the subcommand available outside pure cargo-install workflows.

Wie es verwendet wird

A typical workflow runs `cargo chef prepare --recipe-path recipe.json` after copying the source tree in a planner stage, then `cargo chef cook --release --recipe-path recipe.json` in a builder stage before copying the full application code.

The README emphasizes that the tool is mainly intended for container builds, not normal local development, because it writes the project skeleton needed to cache dependencies.

Warum Paket-Nerds sich dafür interessieren

For package managers, cargo-chef is interesting because it turns Cargo metadata into a build-cache artifact. It is a small CLI, but it sits directly at the intersection of Cargo workspaces, lockfiles, reproducible images, and CI build economics.

It is also a recognizable Rust ecosystem answer to the `requirements.txt`-style dependency layer used in other language containers.

Zeitleiste

  • 2020: GitHub repository created and first crates.io release published.
  • 2020: README documents its origin in Zero to Production in Rust.
  • 2025-2026: Release stream continues through the 0.1.x series, with crates.io showing more than three million downloads by June 2026.

Related projects

  • Cargo is the package manager and build tool that cargo-chef extends.
  • Docker and the official Rust container images are the primary environment targeted by the documented workflow.
  • Zero to Production in Rust is the book project that originally motivated the tool.

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

Executables

Installierte Executables

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

https://github.com/LukeMathWalker/cargo-chef

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

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:cargo-chef
Version0.1.77
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/cargo-chef
Homepagehttps://github.com/LukeMathWalker/cargo-chef
Repositoryhttps://github.com/LukeMathWalker/cargo-chef
Upstream-Dokumentationhttps://github.com/LukeMathWalker/cargo-chef#readme
LizenzApache-2.0 OR MIT
Quellarchivhttps://github.com/LukeMathWalker/cargo-chef/archive/refs/tags/v0.1.77.tar.gz
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-chef
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

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

Nix95%

cargo-chef

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

cargo-chef 0.1.77-r0

A cargo sub-command to build project dependencies for optimal Docker layer caching.

https://github.com/LukeMathWalker/cargo-chef

sudo apk add cargo-chef
  • License: MIT OR Apache-2.0
  • Architecture: x86_64
  • Source Package: cargo-chef
  • 1 Abhängigkeiten
  • 1 stellt bereit
  • normalized package name match
  • Abgeglichen nach: Cargo Chef
Alpine Linux edge package indexes · dl-cdn.alpinelinux.org · Alpine Linux edge package indexes: cargo-chef from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
apk95%

cargo-chef-doc 0.1.77-r0

A cargo sub-command to build project dependencies for optimal Docker layer caching. (documentation)

https://github.com/LukeMathWalker/cargo-chef

sudo apk add cargo-chef-doc
  • License: MIT OR Apache-2.0
  • Architecture: x86_64
  • Source Package: cargo-chef
  • normalized package name match
  • Abgeglichen nach: Cargo Chef
Alpine Linux edge package indexes · dl-cdn.alpinelinux.org · Alpine Linux edge package indexes: cargo-chef-doc from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz

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 package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment