Automic Vault

brew package intelligence

hashicorp/tap/vault

Automic Vault tracks hashicorp/tap/vault because plain text vault token matters when AI agents run command-line tools on macOS.

Read docs Run scanner

overview

What Automic Vault knows about hashicorp/tap/vault

This package is present in local Automic Vault package data. The page is generated so package-specific security metadata has a stable URL.

Homepage

Not present in the local metadata.

Commands and aliases

No executable aliases were found in the local package database.

radioisotope

Plain Text Vault Token

The Vault CLI stores its default token in ~/.vault-token when using the internal token helper. Our isotope stores that token in the macOS keychain and injects it as VAULT_TOKEN only while `vault` runs.

Local README excerpt

Vault Radioisotope

The Vault CLI stores its default token in ~/.vault-token through its internal token helper. The CLI also honors VAULT_TOKEN, which is a clean wrapper boundary for runtime credential injection.

This radioisotope migrates ~/.vault-token into the macOS keychain, removes the plaintext token file, and wraps vault so the token is present only while the command runs.

Caveats

  • We currently migrate the internal token-helper file only.
  • Custom external token helpers are not migrated.
  • Direct execution of the original binary will not receive credentials.

Source: data/radioisotopes/vault/README.md

Caveats

  • We currently migrate the internal token-helper file only.
  • Custom external token helpers are not migrated.
  • Direct execution of the original binary will not receive credentials.

install metadata

Resolver facts

Package keybrew:hashicorp/tap/vault

source trail

Generated from repository data

This page is regenerated by scripts/generate-pkg-pages.py. Deployments refuse to publish if www/pkg/ is stale relative to local package data.

Used sources

  • local isotope README
  • radioisotope security manifest