Automic VaultAutomic Vault

brew

astro mit Homebrew, winget installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install astro

local Homebrew formula metadata

Windows

Windows Package Managerverifiziert · 92%
winget install --id Astronomer.Astro -e

Windows Package Manager source index · Astronomer.Astro · Quelle: cdn.winget.microsoft.com

Überblick

Paketzusammenfassung

To build and run Airflow DAGs locally and interact with the Astronomer API

Verlauf

Projektgeschichte und Nutzung

Astro CLI is Astronomer's command-line interface for developing Apache Airflow projects locally and deploying them to Astronomer products. In package-manager terms it is the small Go binary that turns a directory of DAGs, requirements, Dockerfile, and Astro project metadata into a repeatable local Airflow environment and a deployable unit.

Projektgeschichte

The CLI grew out of Astronomer's Airflow platform tooling and was distributed publicly as the astro-cli repository. Its README describes it as a command-line interface for data orchestration that works with Astronomer products, and its release notes mark all releases before 1.0.0 as beta. Version 1.0.0 was published in May 2022 as the converged Astro CLI release, while Astronomer's own CLI release notes document the transition from older astrocloud command names to the standardized astro login, astro logout, astro dev init, and deployment commands.

The tool's center of gravity is local developer experience for Airflow: astro dev init creates a project skeleton, astro dev start runs the Airflow stack locally in containers, and deployment/workspace commands talk to Astronomer APIs. Later releases added Windows package-manager support, organization and context switching, richer config commands, and deployment inspection/logging features.

Adoptionsgeschichte

Homebrew packages the CLI as astro and the upstream README documents brew install astro for macOS, winget install -e --id Astronomer.Astro for Windows, and an install.astronomer.io shell installer for Linux. That multi-channel distribution matters because Airflow teams often need the same CLI in laptops, CI, and enterprise Windows workstations.

Adoption is tied to Astronomer's hosted Astro and Astronomer Software/Private Cloud products rather than being a general Airflow replacement. The CLI became the user-facing packaging point for Astronomer's Airflow workflow: initialize a project, run it locally, test DAGs, and deploy to a managed Deployment.

Wie es verwendet wird

Typical package usage starts with brew install astro, then astro dev init in an empty project directory and astro dev start to build and run local Airflow containers. The generated project includes dags, tests, Dockerfile, requirements.txt, packages.txt, plugins, include, and an .astro/config.yaml file for project settings.

Astro CLI stores project settings in .astro/config.yaml and global settings in a user-level Astro config file. Astronomer documentation notes project-level settings such as webserver and Postgres ports and says global configuration is stored centrally with the executable, for example under ~/.astro/config.yaml on Unix-like systems. Login-related context and cached identity state also live in the user-level config.

Warum Paket-Nerds sich dafür interessieren

For package nerds, astro is a good example of a cloud-product CLI that still earns a normal package-manager slot because its heavy dependencies are external services and container runtimes, not vendored platform SDKs. The package is mostly a single command surface, but it orchestrates Docker/Podman, generated project files, Airflow commands, and authenticated API calls.

The formula is also notable because it has to track a fast-moving SaaS CLI while preserving enough compatibility for CI images and developer laptops. Astronomer's docs warn that backward compatibility is guaranteed only between matching minor versions of the platform and CLI, which makes package version selection operationally important.

Zeitleiste

  • 2021: Public beta-era Astro CLI releases were already being published from the astronomer/astro-cli repository.
  • 2022-05-27: Astro CLI v1.0.0 was published as the converged v1 release.
  • 2022-06-28: Astronomer documented Astro CLI 1.2.0 and the standardized astro command names.
  • 2022-10-27: Astro CLI v1.6.0 added documented winget installation support for Windows.
  • 2026: Astronomer documentation continues to position Astro CLI as the command reference and local development tool for Astro projects.

Related projects

  • Apache Airflow is the workflow engine Astro CLI packages around for local and managed development.
  • Docker or Podman provide the local container runtime used by astro dev commands.
  • Astronomer Astro and Astronomer Software/Private Cloud are the platform targets for deployment and context commands.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für astro wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 5 Plattformziele verfügbar.
  • Installiert mit 1 Laufzeitabhängigkeiten.
  • 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
.astro/config.yaml~/.astro/config.yaml
Windows
.astro/config.yaml%USERPROFILE%\.astro\config.yaml

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
~/.astro/config.yaml
Windows
%USERPROFILE%\.astro\config.yaml

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
astrocliglobales 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-Version1.43.1
Manager aktualisiert2026-07-02
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv1.43.1

https://github.com/astronomer/astro-cli

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:astro
Version1.43.1
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/astro
Homepagehttps://www.astronomer.io/
Repositoryhttps://github.com/astronomer/astro-cli
Upstream-Dokumentationhttps://www.astronomer.io/docs/astro/cli/configure-cli
LizenzApache-2.0
Quellarchivhttps://github.com/astronomer/astro-cli/archive/refs/tags/v1.43.1.tar.gz
Zuletzt aktualisiert2026-07-02T16:40:03Z
Pulseupdated
Abhängigkeitenpodman
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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

winget95%

Astronomer.Astro

winget install --id Astronomer.Astro -e
  • normalized package name match
  • Abgeglichen nach: Astro
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: Astronomer.Astro from https://cdn.winget.microsoft.com/cache/source.msix

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