Automic VaultAutomic Vault

brew

flowpipe mit Homebrew installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install flowpipe

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Cloud scripting engine

Verlauf

Projektgeschichte und Nutzung

Flowpipe is Turbot's open-source cloud scripting and workflow automation engine for defining DevOps pipelines as HCL code.

Projektgeschichte

Flowpipe was introduced in December 2023 as a cloud scripting engine for automation and workflow, with pipelines for DevOps written in HCL. The initial release supported pipeline execution, steps such as container, email, function, HTTP, query, sleep, transform, and pipeline, schedule and HTTP triggers, credential management, and mod composition.

The project reached 1.0.0 in October 2024. That release added a connection resource for credentials, formal connection and notifier variable types, enum validation, defined CLI exit codes, and deprecated earlier credential resources in favor of connection resources.

Adoptionsgeschichte

Flowpipe's adoption path is tied to Turbot's broader CLI and mod ecosystem. Its README points users to Flowpipe Hub library mods and samples for services such as AWS, Azure, GCP, GitHub, Jira, Okta, PagerDuty, SendGrid, Slack, Teams, and Zendesk.

The README also positions Flowpipe alongside Steampipe and Powerpipe in Turbot Pipes, using Steampipe for data access, Powerpipe for visualization, and Flowpipe for workflow automation.

Wie es verwendet wird

Users define pipelines, triggers, variables, locals, and steps in .fp files inside a Flowpipe mod. Config resources such as workspaces and connections are HCL files ending in .fpc and are loaded from the working directory or mod location and the Flowpipe install config directory.

A typical package workflow installs the flowpipe CLI, initializes a mod with flowpipe mod init, writes pipeline definitions in HCL, installs reusable mods from the hub or Git repositories, and runs pipelines from the terminal.

Warum Paket-Nerds sich dafür interessieren

Flowpipe is notable for package metadata because it brings Terraform-like HCL mod conventions to command-line workflow automation. It also has a recognizable family relationship with Turbot's Steampipe, Powerpipe, hub mods, and connection configuration files.

Zeitleiste

  • 2023: Flowpipe 0.1.0 introduces the cloud scripting engine and HCL pipeline model.
  • 2024: Flowpipe 0.2.0 adds query triggers, expanded HTTP triggers, database query support, and more credential types.
  • 2024: Flowpipe 0.3.0 adds human workflow, Slack and email messaging, input steps, and Steampipe credential import.
  • 2024: Flowpipe 0.6.0 adds interactive workflows in the terminal via console integration.
  • 2024: Flowpipe 1.0.0 introduces connection resources and deprecates credential resources.
  • 2026: Flowpipe 1.2.x continues with security and dependency maintenance releases.

Related projects

  • Official sources connect Flowpipe to Flowpipe Hub mods, Turbot Pipes, Steampipe, Powerpipe, and the shared Turbot pipe-fittings codebase.

Sicherheitslage

Risikostufe: orange

infrastructure mutation or orchestration signal.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

  • infrastructure mutation or orchestration signal

Signale

  • text:cloud

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.

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
*.fpmod.fp$PWD/*.fpc~/.flowpipe/config/*.fpc$FLOWPIPE_INSTALL_DIR/config/*.fpc

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
$PWD/*.fpc~/.flowpipe/config/*.fpc$FLOWPIPE_INSTALL_DIR/config/*.fpc

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
flowpipecliglobales 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-08
Manager-Version1.2.2
Manager aktualisiert2026-06-22
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv1.2.2

https://github.com/turbot/flowpipe

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:flowpipe
Version1.2.2
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/flowpipe
Homepagehttps://flowpipe.io
Repositoryhttps://github.com/turbot/flowpipe
Upstream-Dokumentationhttps://flowpipe.io/docs
LizenzAGPL-3.0-only
Quellarchivhttps://github.com/turbot/flowpipe/archive/refs/tags/v1.2.2.tar.gz
Zuletzt aktualisiert2026-06-22T14:03:21-07:00
Pulseupdated
Build-Abhängigkeitencorepack, go, node
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 Nameflowpipe
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

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
  • package relationship graph
  • package version freshness
  • package-page enrichment