Automic VaultAutomic Vault

brew

ahoy mit Homebrew, Nix, scoop, winget installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install ahoy

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#ahoy

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

Windows

Scoopverifiziert · 92%
scoop install main/ahoy

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

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

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

Überblick

Paketzusammenfassung

Creates self documenting CLI programs from commands in YAML files

Verlauf

Projektgeschichte und Nutzung

Ahoy is a project-local task runner that turns commands written in a YAML file into a self-documenting CLI. Its purpose is to let each repository expose its own small command surface without requiring contributors to learn a bespoke shell script layout or install a language-specific task runner.

Projektgeschichte

The GitHub repository was created in October 2015, and the earliest listed GitHub release is 1.0.0 from the next day. The older Read the Docs site documents the original framing: a zero-code, dependency-free way to give projects their own CLI, particularly for running interactive commands inside Docker containers.

The current README keeps the same core idea while expanding the implementation details: commands live in .ahoy.yml, run relative to that file, can be invoked from subdirectories, and can import multiple config files. The project later moved under the ahoy-cli organization and added newer command-alias, environment-file, and completion features.

Adoptionsgeschichte

Ahoy's adoption is strongest in teams that want Makefile-like ergonomics but richer command help and project-local behavior. The README's Docker and database examples reflect its origin in development-environment workflows, especially wrapping docker-compose, shell, database, test, and deployment commands.

The supplied package facts list Homebrew, Nix, Scoop, and winget packages, showing that Ahoy crossed from a macOS/Linux developer convenience into cross-platform package-manager distribution.

Wie es verwendet wird

A project adds a .ahoy.yml file declaring commands, descriptions, aliases, imports, environment files, and an entrypoint. Running ahoy lists commands and per-command help; running ahoy <command> executes the configured shell command relative to the config file.

Official examples include replacing long docker exec invocations with short project commands, initializing an example .ahoy.yml, and using environment files for global or command-specific variables.

Warum Paket-Nerds sich dafür interessieren

Ahoy sits in the small but beloved category of developer workflow shims: lighter than a build system, more discoverable than a pile of shell scripts, and easy to package as a single CLI binary. For package maintainers, its value is that the runtime surface is simple while the user-facing workflow can standardize a repository's command vocabulary.

Zeitleiste

  • 2015: GitHub repository created and release 1.0.0 published.
  • 2015: Release 1.1.0 published and documented by the older Read the Docs site.
  • 2016-2017: Version 2 alpha and beta releases appeared.
  • 2026: Official repository metadata shows continued activity under ahoy-cli/ahoy.

Related projects

  • Ahoy overlaps with Make, npm scripts, just, Task, and docker-compose wrapper scripts, but focuses on project-specific command discovery and help.
  • The README points to ahoy-cli/zsh-ahoy for dedicated Zsh completion support.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 8 Plattformziele verfügbar.
  • 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
.ahoy.yml

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
ahoycliglobales 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-Version2.5.0
Manager aktualisiert2026-07-21
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv2.5.0

https://github.com/ahoy-cli/ahoy

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:ahoy
Version2.5.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/ahoy
Homepagehttps://github.com/ahoy-cli/ahoy/
Repositoryhttps://github.com/ahoy-cli/ahoy
Upstream-Dokumentationhttps://ahoy-cli.readthedocs.io/en/latest
LizenzMIT
Quellarchivhttps://github.com/ahoy-cli/ahoy/archive/refs/tags/v2.5.0.tar.gz
Zuletzt aktualisiert2026-07-21T17:14:18-04:00
Pulseupdated
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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

Nix95%

ahoy

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

main/ahoy

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

Ahoy.Ahoy

winget install --id Ahoy.Ahoy -e
  • normalized package name match
  • Abgeglichen nach: Ahoy
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: Ahoy.Ahoy 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