
Security News
vlt Launches "reproduce": A New Tool Challenging the Limits of Package Provenance
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
@litehex/vault-cli
Advanced tools
A minimal CLI to access your HashiCorp's Vault secrets from the command line.
npx @litehex/vault-cli --help
# Or use `bunx`:
bunx @litehex/vault-cli --help
npm i -g @litehex/vault-cli
This command will create a profile in your home directory. It will be used to store your Vault's address and token.
Usage: vault 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
vault make-profile my-profile --endpoint-url https://vault.example.com --token my-token
This command will push a secret to your Vault.
Usage: vault 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
vault push --profile my-profile .env.local secret/data/my-app
# Use credentials instead of a profile
vault push --endpoint-url https://vault.example.com --token my-token .env.local secret/data/my-app
This command will pull a secret from your Vault.
Usage: vault 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
-E, --env-path <env-path> Path to the environment file
-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
vault pull --profile my-profile secret/data/my-app
# Pull a secret from Vault and save it to a .env file
vault pull --profile my-profile secret/data/my-app --env-path .env
This project is licensed under the GPL-3.0 License - see the LICENSE file for details
FAQs
CLI for HashiCorp's Vault KV2 engine
The npm package @litehex/vault-cli receives a total of 0 weekly downloads. As such, @litehex/vault-cli popularity was classified as not popular.
We found that @litehex/vault-cli demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer 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
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
Research
Security News
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
Research
The Socket Research Team discovered a malicious npm package, '@ton-wallet/create', stealing cryptocurrency wallet keys from developers and users in the TON ecosystem.