Package manager source
Homebrew metadata was not linked in local data.
brew package intelligence
Automic Vault tracks runpod/runpod/runpodctl because plain text runpod api key matters when AI agents run command-line tools on macOS.
install
brew install runpod/runpod/runpodctl
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
runpodctl stores the RunPod API key in ~/.runpod/config.toml. Older installs can also have ~/.runpod.yaml, which current runpodctl versions still read and migrate. Our isotope stores those package-owned config files in the macOS keychain and exposes them through a temporary HOME only while `runpodctl` runs.
Local README excerpt
The runpodctl CLI stores the RunPod API key in its local config, usually ~/.runpod/config.toml. Older installs can also have ~/.runpod.yaml, which current runpodctl versions still read and migrate.
Automic Vault migrates those package-owned config files into the macOS keychain and injects them through a temporary HOME only while runpodctl runs.
This keeps local RunPod API keys out of plaintext home-directory config without changing runpodctl's command-line interface.
~/.runpod/config.toml and legacy ~/.runpod.yamlfiles only.
Source: data/radioisotopes/runpodctl/README.md
https://github.com/runpod/homebrew-runpod/blob/HEAD/runpodctl.rb
executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
| No executable data was present. | |||
install metadata
| Package key | brew:runpod/runpod/runpodctl |
|---|---|
| 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.