Automic VaultAutomic Vault

brew

argo mit Homebrew, scoop installieren

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

Agent-Sicherheit

Antwort zur Agent-Sicherheit

argo controls Argo workflows and cluster-executed jobs.

Credential-Zugriff

Reads kubeconfig, Argo tokens, workflow parameters, and secret references.

Änderungen an Remote-Zustand

Can submit, stop, delete, and retry workflows in clusters.

Publish-/Artefakt-Risiko

Can trigger jobs that build, deploy, or process artifacts.

Empfohlene Kontrolle

Gate submit, delete, retry, and token-backed workflow commands.

Hinweise für Agent-Nutzung

Allow workflow status reads; require approval for submissions and destructive operations.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install argo

local Homebrew formula metadata

Windows

Scoopverifiziert · 92%
scoop install main/argo

Scoop official bucket manifest trees · bucket/argo.json · Quelle: api.github.com

Überblick

Paketzusammenfassung

Get stuff done with container-native workflows for Kubernetes

Verlauf

Projektgeschichte und Nutzung

Argo Workflows is the Argo project's Kubernetes-native workflow engine. The project implements workflows as Kubernetes custom resources, models work as container steps or DAG tasks, and ships the `argo` CLI for submitting, linting, watching, and managing workflow objects.

Projektgeschichte

The argo-workflows GitHub repository was created in August 2017. Over time it became one of the four main Argo subprojects alongside Argo CD, Argo Events, and Argo Rollouts. Its README describes the broader Argo project as a collection of tools for getting work done with Kubernetes and identifies Argo Workflows as the container-native workflow engine.

The project matured from a Kubernetes workflow controller into a CNCF graduated project with documented governance, maintainers, community meetings, release branches, client libraries, and security process. Official releases now span both the 3.x maintenance line and the 4.x line, with Homebrew packaging the `argo` binary from argoproj/argo-workflows tags.

Adoptionsgeschichte

Argo Workflows' own README calls it the most popular workflow execution engine for Kubernetes and says about 200+ organizations officially use it. The official USERS.md list includes large technology, finance, cloud, media, and AI/data companies, and the Argo repository points each subproject to its adopter list. Its use cases page and README emphasize machine-learning pipelines, data and batch processing, infrastructure automation, CI/CD, and other Kubernetes jobs.

The ecosystem around it is broad: the README names Argo Events, Hera, Katib, Kedro, Kubeflow Pipelines, Netflix Metaflow, Seldon, SQLFlow, and others as projects that use or rely on Argo Workflows. That adoption pattern made the CLI useful not only for direct workflow authors, but also for platform teams building higher-level ML, data, and batch-compute systems on Kubernetes.

Wie es verwendet wird

Users define Workflows or CronWorkflows as Kubernetes YAML and use the `argo` CLI to lint, submit, list, watch, retry, resubmit, suspend, resume, terminate, and inspect them. The workflow controller then schedules each step as a container, supports artifacts and parameters, handles DAG or step sequencing, and integrates with Kubernetes-native scheduling, service accounts, volumes, and secrets.

The Homebrew formula builds the CLI from source and tests `argo version` plus `argo lint --kubeconfig`, reflecting the package-manager view of Argo as a local Kubernetes client tool. In actual clusters, the CLI is paired with the controller, CRDs, optional UI/server, archives, metrics, and SSO features documented by the project.

Warum Paket-Nerds sich dafür interessieren

Argo Workflows is significant because it turned Kubernetes CRDs into a mainstream packaging and operations surface for workflow engines. A package install gives you a local `argo` binary, but the real artifact is a contract with cluster-side CRDs, controllers, Helm charts, and YAML manifests, making it a canonical example of cloud-native CLI packaging.

For package maintainers, it also illustrates a common modern split: the Homebrew formula builds one CLI executable, while the upstream project simultaneously publishes controller images, manifests, docs, examples, SDKs, and a larger CNCF-governed ecosystem.

Zeitleiste

  • 2017: argo-workflows GitHub repository created.
  • 2020: Argo Workflows user survey summary published by the Argo project.
  • 2021: Argo Workflows user survey results published by the Argo project.
  • 2022: v3.3.6 is the earliest GitHub release visible through the releases API snapshot used for this enrichment.
  • 2023: Argo Workflows and Events user survey results published.
  • 2026: v4.0.x and v3.7.x release lines are both active in GitHub releases.

Related projects

  • The official Argo project groups Argo Workflows with Argo CD, Argo Events, and Argo Rollouts. The README also points to client libraries including Go, Java, Hera for Python, and Juno for TypeScript.

Sicherheitslage

Risikostufe: orange

infrastructure mutation or orchestration signal.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

  • infrastructure mutation or orchestration signal

Signale

  • text:container,kubernetes

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Build-Metadaten listen 3 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
argocliglobales 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-Version4.0.8
Manager aktualisiert2026-07-22
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/argoproj/argo-workflows

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:argo
Version4.0.8
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/argo
Homepagehttps://argoproj.io
Repositoryhttps://github.com/argoproj/argo-workflows
Upstream-Dokumentationhttps://argo-workflows.readthedocs.io/
LizenzApache-2.0
Quellarchivhttps://github.com/argoproj/argo-workflows.git
Zuletzt aktualisiert2026-07-22T12:03:14Z
Pulseupdated
Build-Abhängigkeitengo, node, yarn
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 Nameargo
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.

Scoop95%

main/argo

scoop install main/argo
  • normalized package name match
  • Abgeglichen nach: Argo
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/argo.json from https://api.github.com/repos/ScoopInstaller/Main/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 agent safety answer
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment