Security News
Input Validation Vulnerabilities Dominate MITRE's 2024 CWE Top 25 List
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
kvault is a CLI for managing HashiCorp Vault Key/Value V2 secret engines from the command line.
npx kvault --help # Or bunx kvault --help
npm install --global kvault
Usage: kvault [options] [command]
Manage your HashiCorp Vault Key/Value v2 secret engines from the command line.
Author: Shahrad Elahi <shahrad@litehex.com> (https://github.com/shahradelahi)
License: GPL-3.0
Options:
-v, --version display the version number
-h, --help display help for command
Commands:
make-profile [options] <name> Create a new vault profile
mount [options] <mount-path> Mount a new KV2 secret engine
pipe [options] <secrets-path> [command...] Pull an environment from Vault and pipe it to a command
push [options] <env-file> <secrets-path> Push an environment to Vault
pull [options] <secrets-path> Pull an environment from Vault
rm [options] <secrets-path> [versions...] Remove a secret from Vault
seal [options] Seal Vault
unmount [options] <mount-path> Unmount a secret engine
unseal [options] [keys...] Unseal Vault
help [command] display help for command
This command will create a profile in your home directory. It will be used to store your Vault's address and token.
Usage: kvault make-profile [options] <name>
Create a new vault profile
Options:
--endpoint-url <endpoint-url> Vault endpoint URL
--token <vault-token> Vault token
--force Overwrite existing profile (default: false)
-h, --help display help for command
# Create a new profile
kvault make-profile my-profile --endpoint-url https://vault.example.com --token my-token
This command will push a secret to your Vault.
Usage: kvault push [options] <env-file> <secrets-path>
Push an environment to Vault
Options:
-P, --profile <name> Name of the profile to use.
--endpoint-url <endpoint-url> Vault endpoint URL
--token <vault-token> Vault token
--cwd <cwd> Current working directory (default: ".")
--force Write to Vault even if the secrets are in conflict (default: false)
-h, --help display help for command
# Push a .env.local file to Vault
kvault push --profile my-profile .env.local secret/my-app
# Use credentials instead of a profile
kvault push --endpoint-url https://vault.example.com --token my-token .env.local secret/my-app
This command will pull a secret from your Vault.
Usage: kvault pull [options] <secrets-path>
Pull an environment from Vault
Options:
-P, --profile <name> Name of the profile to use.
--endpoint-url <endpoint-url> Vault endpoint URL
--token <vault-token> Vault token
-O, --output-file <output-path> Path to write the environment file to
-F, --format <format> Format of the environment file (default: "dotenv")
--cwd <cwd> Current working directory (default: ".")
--force Write environment file even if it exists (default: false)
-h, --help display help for command
# Pull a secret from Vault
kvault pull --profile my-profile secret/my-app
# Pull a secret from Vault and save it to a .env file
kvault pull --profile my-profile secret/my-app --env-path .env
# Pull a secret from Vault and add them to shell environment
kvault pull --profile my-profile secret/my-app --format shell | grep -e '^export' | source /dev/stdin
This command will pull and pipe secrets from your Vault to another command.
Usage: kvault pipe [options] <secrets-path> [command...]
Pull an environment from Vault and pipe it to a command
Arguments:
secrets-path
command Command to pipe to (default: [])
Options:
-P, --profile <name> Name of the profile to use.
--endpoint-url <endpoint-url> Vault endpoint URL
--token <vault-token> Vault token
--cwd <cwd> Current working directory (default: ".")
-h, --help display help for command
# Pull a secret from Vault and pipe it to a command
kvault pipe --profile my-profile secret/my-app env | grep -e '^MY_APP_'
# Pull a secret from Vault and pipe it to a node script
kvault pipe --profile my-profile secret/my-app "node -e 'console.log(process.env.MY_APP_SECRET)'"
This command will remove a path or some versions of a secret.
Usage: kvault rm [options] <secrets-path> [versions...]
Remove a secret from Vault
Arguments:
secrets-path
versions Versions to remove. By default, path will be removed. (default: [])
Options:
-P, --profile <name> Name of the profile to use
--endpoint-url <endpoint-url> Vault endpoint URL
--token <vault-token> Vault token
--force Remove the secret without confirmation (default: false)
-h, --help display help for command
# Remove a path secret from Vault
kvault rm --profile my-profile secret/my-app
# Remove a secret version from Vault
kvault rm --profile my-profile secret/my-app 3 4
Want to contribute? Awesome! To show your support is to star the project, or to raise issues on GitHub.
Thanks again for your support, it is much appreciated!
FAQs
CLI for HashiCorp Vault Key/Value V2 secret engines
We found that kvault demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.