Automic VaultAutomic Vault

brew

Install argo with Homebrew, scoop

Get stuff done with container-native workflows for Kubernetes. Version 4.0.7 via Homebrew; verified 2026-07-07.

agent safety

Agent safety answer

argo controls Argo workflows and cluster-executed jobs.

Credential access

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

Remote mutation

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

Publish/artifact risk

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

Recommended control

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

Agent-use guidance

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

install

Additional install commands

macOS

Homebrewverified · 100%
brew install argo

local Homebrew formula metadata

Windows

Scoopverified · 92%
scoop install main/argo

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

overview

Package summary

Get stuff done with container-native workflows for Kubernetes

Commands and aliases

  • argo

history

Project history and usage

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.

Project history

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.

Adoption history

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.

How it is used

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.

Why package nerds care

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.

Timeline

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

security posture

Risk level: orange

infrastructure mutation or orchestration signal.

Risk classifier

orange risk · medium confidence · infrastructure

Why

  • infrastructure mutation or orchestration signal

Signals

  • text:container,kubernetes

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Build metadata lists 3 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

CommandKindExposureNote
argocliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version4.0.7
manager updated2026-07-07
local dataok
upstreamnot checked
latest detectednot detected

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

install metadata

Package metadata

Package keybrew:argo
Version4.0.7
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/argo
Homepagehttps://argoproj.io
Repositoryhttps://github.com/argoproj/argo-workflows
Upstream docshttps://argo-workflows.readthedocs.io/
LicenseApache-2.0
Source archivehttps://github.com/argoproj/argo-workflows.git
Last updated2026-07-07T12:10:30Z
Pulseupdated
Build dependenciesgo, node, yarn
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

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 database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Scoop95%

main/argo

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

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • 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