Package manager source
Homebrew metadata was not linked in local data.
brew package intelligence
Automic Vault tracks hashicorp/tap/vagrant because plain text vagrant cloud token matters when AI agents run command-line tools on macOS.
install
brew install hashicorp/tap/vagrant
Homebrew metadata was not linked in local data.
overview
This package is present in local Automic Vault package data. The page is generated so package-specific security metadata has a stable URL.
Not present in the local metadata.
No executable aliases were found in the local package database.
radioisotope
Vagrant stores its Vagrant Cloud login token in ~/.vagrant.d/data/vagrant_login_token. Our isotope stores that token in the macOS keychain and injects it as VAGRANT_CLOUD_TOKEN only while `vagrant` runs.
Local README excerpt
Vagrant stores its Vagrant Cloud login token in ~/.vagrant.d/data/vagrant_login_token. The CLI also honors VAGRANT_CLOUD_TOKEN, which is a clean wrapper boundary for runtime credential injection.
This radioisotope migrates the saved login token into the macOS keychain, removes the plaintext token file, and wraps vagrant so the token is present only while the command runs.
VAGRANT_HOME are not migrated.Source: data/radioisotopes/vagrant/README.md
https://github.com/hashicorp/homebrew-tap/blob/HEAD/Formula/vagrant.rb
executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
| No executable data was present. | |||
install metadata
| Package key | brew:hashicorp/tap/vagrant |
|---|---|
| Package manager | Homebrew |
source trail
This page is regenerated by scripts/generate-pkg-pages.py. Deployments refuse to publish if www/pkg/ is stale relative to local package data.