# flowrs mit Homebrew installieren

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

## Installation

```sh
sudo av install brew:flowrs
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install flowrs
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:flowrs
- **Paketmanager:** Homebrew
- **Version:** 0.13.3
- **Quellzusammenfassung:** TUI application for Apache Airflow
- **Homepage:** <https://github.com/jvanbuel/flowrs>
- **Repository:** <https://github.com/jvanbuel/flowrs>
- **Zuletzt aktualisiert:** 2026-07-28T13:24:40Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- flowrs (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 0.13.3
## Projektgeschichte und Nutzung

Flowrs is a Rust terminal user interface for monitoring, inspecting, and managing Apache Airflow DAGs from the command line.

### Projektgeschichte

The official README describes Flowrs as a TUI for Apache Airflow built with Ratatui. Its changelog records a first public release in November 2024 and a steady sequence of early 0.1.x releases through 2025.

The package is published as the flowrs binary from the flowrs-tui crate, with installation paths documented for Homebrew, GitHub release binaries, and cargo install.

### Adoptionsgeschichte

Flowrs targets Airflow users who want terminal-native monitoring rather than a browser-only workflow. Its README documents support for managed Airflow services including Conveyor, Amazon MWAA, Google Cloud Composer, and Astronomer, as well as custom self-hosted Airflow instances.

### Wie es verwendet wird

Users can run flowrs config enable -m <service> for managed Airflow services or flowrs config add for a custom Airflow instance. The tool writes configuration to the XDG config path by default and can authenticate with HTTP Basic Auth or bearer tokens.

The TUI supports switching between configured Airflow servers, inspecting DAGs and task instances, and opening endpoints from the terminal.

### Warum Paket-Nerds sich dafür interessieren

Flowrs is package-interesting as part of the modern Rust TUI wave: it combines a cargo-published crate, a Homebrew formula, GitHub release installers, XDG config behavior, and a Ratatui-based terminal interface for a large orchestration system.

### Zeitleiste

- 2024: Flowrs 0.1.1 changelog marks the first release.
- 2024: Flowrs 0.1.3 changes the Homebrew formula name to flowrs.
- 2025: Flowrs 0.1.5 adds browser opening, theme and UI refinements, and config commands.
- 2025: Flowrs 0.1.15 refactors around a Conveyor client and tenant switching.
- 2026: Cargo metadata shows flowrs-tui continuing as a Rust 2021 package with a flowrs binary.

### Related projects

- Official sources connect Flowrs to Apache Airflow, Ratatui, Conveyor, Amazon MWAA, Google Cloud Composer, Astronomer, and Catppuccin themes.

### Quellen

- <https://github.com/jvanbuel/flowrs>
- <https://raw.githubusercontent.com/jvanbuel/flowrs/main/CHANGELOG.md>
- <https://raw.githubusercontent.com/jvanbuel/flowrs/main/Cargo.toml>
- <https://raw.githubusercontent.com/jvanbuel/flowrs/main/README.md>


## Sicherheitshinweise

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



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

- Unix: $XDG_CONFIG_HOME/flowrs/config.toml, ~/.config/flowrs/config.toml, ~/.flowrs

## Credential files

- Unix: $XDG_CONFIG_HOME/flowrs/config.toml, ~/.config/flowrs/config.toml, ~/.flowrs

## Combined YAML source

View the package source record on GitHub. [combined/flowrs.yml](https://github.com/mxcl/pkgdb/blob/main/combined/flowrs.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph
