macOS
Homebrew Caskverifiziert · 100%
brew install --cask aws-vault-binaryprovider-native install command
cask / Rang 290
aws-vault-binary mit Homebrew Cask installieren
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für aws-vault-binary in AI-Agent-Workflows.
Installation
Weitere Installationsbefehle
Überblick
Paketzusammenfassung
Securely stores and accesses AWS credentials in a development environment
Projektlinks
Befehle und Aliase
- aws-vault
Verlauf
Projektgeschichte und Nutzung
The `aws-vault-binary` cask packages the original 99designs AWS Vault macOS binary distribution. AWS Vault stores long-term AWS IAM credentials in an operating-system secure store and exposes short-lived STS credentials to commands, shells, browser sessions, or local metadata-style endpoints.
Projektgeschichte
The original `99designs/aws-vault` repository was created in August 2015, with GitHub releases beginning at v1.0.0 in September 2015. The upstream README links to a 99designs announcement post and describes the tool as complementary to the AWS CLI, aware of profiles in `~/.aws/config`.
By 2026 the original README marked the project abandoned and pointed users to the active `ByteNess/aws-vault` fork. The cask, however, still references the 99designs repository and v7.2.0 macOS DMG artifact, so this record reflects the legacy binary distribution rather than the newer Homebrew formula.
Adoptionsgeschichte
AWS Vault became one of the canonical AWS credential helpers in the macOS and Unix developer tooling ecosystem. The original README listed installation through direct releases, Homebrew, MacPorts, Chocolatey, Scoop, Arch, Gentoo, FreeBSD, OpenSUSE, Nix, and asdf, which is unusually broad for a single-purpose credential CLI.
The 99designs repository metadata showed thousands of stars and hundreds of forks in June 2026, and the v7.2.0 release assets had large download counts, especially for Linux and Apple Silicon macOS binaries. Homebrew cask analytics still showed active installs for the binary cask even after the original project became legacy.
Wie es verwendet wird
The classic workflow is `aws-vault add profile` to store long-term credentials in the platform vault, then `aws-vault exec profile -- command` or `aws-vault login profile` to obtain temporary AWS credentials or console access. The usage guide also documents credential_process use, MFA session caching, SSO caching, and metadata server modes.
Because secrets live in the OS keychain or equivalent backend, `~/.aws/credentials` is not the primary storage location for this package's secrets.
Warum Paket-Nerds sich dafür interessieren
This cask is historically significant because it preserves the old signed macOS binary channel after the main formula moved on. It also illustrates a common packaging split: the same tool can exist as a source-built formula and as a binary cask, with different upstreams and maintenance status over time.
Zeitleiste
- 2015-08: Original 99designs/aws-vault repository created.
- 2015-09: v1.0.0 GitHub release published.
- 2023-03: v7.2.0 published by the 99designs repository.
- 2025-05: ByteNess active fork created.
- 2026-06: Original README marked 99designs/aws-vault abandoned and pointed to ByteNess/aws-vault.
Related projects
- `ByteNess/aws-vault` is the maintained fork named by the original upstream README.
- `aws-sso-cli` uses similar secure keyring ideas but focuses on IAM Identity Center rather than long-term IAM access keys.
Quellen
Sicherheitslage
Noch keine Protected-Tool-Abdeckung gefunden
Für aws-vault-binary wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.
Installationsverhalten
- Es wurden keine Homebrew-Bottle-Metadaten erfasst.
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
~/.aws/config- Windows
%USERPROFILE%\.aws\config
Executables
Installierte Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
aws-vault | Binärdatei | Homebrew-Cask-Binärdatei | aws-vault |
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-08-03
Manager-Version7.2.0
Manager aktualisiert
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
- OKEs wurden keine Aktualitätswarnungen generiert.
Installationsmetadaten
Paketmetadaten
| Paketschlüssel | cask:aws-vault-binary |
|---|---|
| Version | 7.2.0 |
| Paketmanager | Homebrew Cask |
| Homepage | https://github.com/99designs/aws-vault |
| SHA-256 | 9887eb8f6c2bd431e814b32b9ec8a6bd394dbeb0c60822d76ed9be3c84ca1cc5 |
| Download-URL | https://github.com/99designs/aws-vault/releases/download/v7.2.0/aws-vault-darwin-arm64.dmg |
| Bottle | nicht erfasst |
| Dienst | keiner deklariert |
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.
Combined YAML source
View the package source record on GitHub.
Verwendete Quellen
- Nucleus package database
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation