Automic VaultAutomic Vault

brew

flyway mit Homebrew, MacPorts, Nix, scoop installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install flyway

local Homebrew formula metadata

MacPortsverifiziert · 94%
sudo port install flyway

MacPorts ports tree · java/flyway/Portfile · Quelle: api.github.com

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#flyway

nixpkgs package indexes · pkgs/by-name/fl/flyway/package.nix · Quelle: api.github.com

Windows

Scoopverifiziert · 92%
scoop install main/flyway

Scoop official bucket manifest trees · bucket/flyway.json · Quelle: api.github.com

Überblick

Paketzusammenfassung

Database version control to control migrations

Verlauf

Projektgeschichte und Nutzung

Redgate Flyway is a database migration and schema versioning tool for command-line, API, Maven, Gradle, Docker, and desktop workflows. It applies versioned migrations, records them in a schema history table, and is used to bring database change management into application-style CI/CD pipelines.

Projektgeschichte

The open-source repository identifies Flyway as a Redgate project and carries copyright from 2010 through 2026. The README emphasizes a simple, focused migration model and lists support across Windows, macOS, Linux, Docker, Java, Maven, and Gradle.

Redgate documentation presents Flyway as part of a wider product family that includes Flyway Command Line, Flyway Desktop, APIs, build-tool integrations, and Redgate editions. The GitHub README also notes that Flyway is a registered trademark of Boxfuse GmbH owned by Red Gate Software Ltd.

Adoptionsgeschichte

Flyway's adoption is tied to the rise of database DevOps: its own documentation says it extends DevOps to databases, automates database deployments, and is commonly used from the command line in CI/CD systems. The README lists support for 50-plus DBMS products and many community or third-party integrations, including Spring Boot, SBT, Ant, Grails, Play, DropWizard, Grunt, Griffon, and Ninja.

Wie es verwendet wird

The standard workflow is to create ordered SQL, Java, or scripting migrations, run Flyway against a database, and let it create or update the `flyway_schema_history` table as migrations are applied. It can be used directly through the CLI, embedded through the Java API, or driven through Maven and Gradle.

Warum Paket-Nerds sich dafür interessieren

Flyway matters to package ecosystems because it is both a standalone CLI and a Java library/plugin stack. It bridges application release tooling and mutable database state, so packaging has to serve local developer installs, CI runners, containers, build plugins, and enterprise editions without confusing the open-source command-line engine with Redgate's commercial surfaces.

Zeitleiste

  • 2010: The Flyway open-source repository's copyright period begins.
  • 2021: Redgate Flyway documentation was published in its current documentation space.
  • 2022: Redgate published the Flyway Engine release-notes page in the current documentation system.
  • 2024: The GitHub release stream included Flyway 10.x releases.
  • 2026: Redgate documentation listed Flyway 12.10.0 as a current engine release.

Related projects

  • Related official surfaces include Flyway Desktop, Flyway Command Line, Flyway Java API, the Maven and Gradle plugins, flyway-community-db-support, and Redgate's commercial Flyway editions.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für flyway 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 1 Plattformziele verfügbar.
  • Installiert mit 1 Laufzeitabhä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
./flyway.toml./flyway.conf~/flyway.conf<flyway-install-dir>/conf/flyway.conf

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
~/flyway.conf

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
flywaycliglobales 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-Version12.10.0
Manager aktualisiert2026-06-30
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/flyway/flyway

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:flyway
Version12.10.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/flyway
Homepagehttps://www.red-gate.com/products/flyway/community/
Repositoryhttps://github.com/flyway/flyway
Upstream-Dokumentationhttps://documentation.red-gate.com/flyway
LizenzApache-2.0
Quellarchivhttps://github.com/flyway/flyway/releases/download/flyway-12.10.0/flyway-commandline-12.10.0.tar.gz
Zuletzt aktualisiert2026-06-30T12:28:44Z
Pulseupdated
Abhängigkeitenopenjdk
Bottleverfügbar (auf all)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameflyway
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

flyway

nix profile install nixpkgs#flyway
  • normalized package name match
  • Abgeglichen nach: Flyway
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/fl/flyway/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
MacPorts95%

flyway

sudo port install flyway
  • normalized package name match
  • Abgeglichen nach: Flyway
MacPorts ports tree · api.github.com · MacPorts ports tree: java/flyway/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
Scoop95%

main/flyway

scoop install main/flyway
  • normalized package name match
  • Abgeglichen nach: Flyway
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/flyway.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

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