dev-vault offers a local-first approach to securely managing sensitive credentials like API keys and passwords. With strong encryption, easy integration into version control, and a user-friendly CLI, this tool helps developers prevent accidental exposure of secrets while streamlining team collaboration.
dev-vault is a secure and efficient local-first secrets manager designed specifically for development environments. By enabling developers to manage sensitive information such as API keys and database passwords on a per-project basis, dev-vault significantly reduces the risk of accidental exposure while enhancing team collaboration.
Key Features
- Local-First: Secrets are stored locally in an encrypted vault file, ensuring that sensitive data remains under the user’s control.
- Encrypted Storage: All secrets are protected with strong encryption, providing peace of mind that credentials are safe at rest.
- Git-Friendly Design: The encrypted vault file (
secrets.vault) can be safely committed to version control without compromising security. The decryption key (.dev-vault.key) is automatically added to.gitignoreto prevent accidental exposure. - Language Agnostic: Compatible with any programming language or framework,
dev-vaultinjects secrets as environment variables, enabling seamless integration into diverse development workflows. - Command-Line Interface: Offers a straightforward CLI for managing secrets, making it accessible for developers.
Usage Example
To initialize a new vault and manage secrets:
cd my-project
# Initialize a new vault
dev-vault init
# Set secrets
dev-vault set DATABASE_URL "postgres://user:pass@host/db"
dev-vault set API_KEY "your_super_secret_api_key"
# Retrieve a secret
dev-vault get DATABASE_URL
# List all secrets
dev-vault list
# Remove a secret
dev-vault rm API_KEY
# Execute commands with secrets as environment variables
dev-vault exec -- npm start
By adopting dev-vault, developers can enhance the security and management of sensitive credentials, streamline collaboration, and integrate seamlessly into their existing workflows.
Any chance you would want to include ZOSCII encoding as an option - it is 100% secure, quantum computer proof given infinite time. The data is not stored in the encoded file. The ZOSCII repo has a similar project to this but why should it be the only solution?
Sign in to comment.