Automic VaultAutomic Vault

brew

Installer argo avec Homebrew, scoop

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de argo pour les workflows d'agents IA.

sécurité des agents

Réponse sur la sécurité des agents

argo controls Argo workflows and cluster-executed jobs.

Accès aux identifiants

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

Modification distante

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

Risque de publication ou d'artéfact

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

Contrôle recommandé

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

Conseils d'utilisation par les agents

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

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install argo

local Homebrew formula metadata

Windows

Scoopvérifié · 92%
scoop install main/argo

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

aperçu

Résumé du paquet

Get stuff done with container-native workflows for Kubernetes

historique

Historique du projet et usages

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.

Historique du projet

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.

Historique d'adoption

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.

Modes d'utilisation

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.

Pourquoi les passionnés de paquets s'y intéressent

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.

Chronologie

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

posture de sécurité

Niveau de risque : orange

infrastructure mutation or orchestration signal.

Classificateur de risque

risque orange · confiance moyen · infrastructure

Pourquoi

  • infrastructure mutation or orchestration signal

Signaux

  • text:container,kubernetes

Comportement d'installation

  • Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
  • Les métadonnées de bottle Homebrew sont disponibles pour 6 plateformes.
  • Les métadonnées de compilation listent 3 dépendances de compilation.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

exécutables

Exécutables installés

CommandeTypeExpositionNote
argocliexécutable global

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-07-25
version du gestionnaire4.0.8
gestionnaire mis à jour2026-07-22
données localesOK
amontnot checked
dernière version détectéenon détecté

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

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:argo
Version4.0.8
Gestionnaire de paquetsHomebrew
Page du gestionnaire de paquetshttps://formulae.brew.sh/formula/argo
Page d'accueilhttps://argoproj.io
Dépôthttps://github.com/argoproj/argo-workflows
Docs amonthttps://argo-workflows.readthedocs.io/
LicenceApache-2.0
Archive sourcehttps://github.com/argoproj/argo-workflows.git
Dernière mise à jour2026-07-22T12:03:14Z
Pulseupdated
Dépendances de compilationgo, node, yarn
Bouteilledisponible (sur arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
post-install Homebrewnon défini
Serviceaucun déclaré

faits du registre

Détails de la base source

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

correspondances dans les bases sources

Autres enregistrements de gestionnaires de paquets

Les correspondances proviennent d’index externes de gestionnaires de paquets et restent séparées des liens de paquets Automic Vault locaux.

Scoop95%

main/argo

scoop install main/argo
  • normalized package name match
  • Correspondance par : 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

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Sources utilisées

  • 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