Is my sensitive data encrypted by Envault?

Envault stores variables in plaintext within a local SQLite database and relies on system-level filesystem permissions (chmod 600) for security rather than application-level encryption.

How do I avoid sensitive keys appearing in my shell history?

You should use the interactive mode by running 'envault var set KEY_NAME' without providing a value argument; this triggers a secure, hidden input prompt.

Does Envault work outside of Git repositories?

No, Envault requires a Git repository to be initialized (git init) because it uses the repo root to track and organize project-specific variables.

How does Envault identify different projects?

Envault uses the Git repository root directory as a unique identifier for projects, ensuring environment variables are correctly mapped to the right codebase automatically.

Can I use custom environment names like .env.local?

Yes, Envault maps any .env. file to a named environment in its database, where the standard .env file is treated as the 'default' environment.

Envault Manager

Name: Envault Manager
Author: altic-dev

byaltic-dev

•

개발자 도구

Manages environment variables across projects using a centralized SQLite database and bidirectional .env file synchronization.

소개

Envault Manager is a specialized Claude Code Skill designed to simplify and secure the handling of environment variables. By centralizing secrets in a local SQLite database and mapping them to Git repository roots, it allows developers to maintain a single source of truth for their configuration. It features bidirectional syncing between the database and project-specific .env files, supports multiple environments like staging and production, and provides secure interactive prompts to prevent sensitive keys from appearing in shell history. This tool is essential for developers managing complex microservices or multiple project environments who need a structured, AI-friendly way to handle secrets.

주요 기능

Bidirectional synchronization between the database store and local .env files
Automatic mapping of custom .env files to named environments like dev, prod, and staging
Cross-project variable copying to quickly replicate configurations between repositories
Secure interactive entry mode to keep secrets out of shell history and logs
Centralized SQLite storage for all environment variables across multiple projects
2 GitHub stars

사용 사례

Managing multiple environment files (dev/staging/prod) through a unified CLI interface
Importing legacy .env files into a centralized manager for better organization and persistence
Setting up new project secrets by copying existing configurations from related services

소개

주요 기능

Bidirectional synchronization between the database store and local .env files
Automatic mapping of custom .env files to named environments like dev, prod, and staging
Cross-project variable copying to quickly replicate configurations between repositories
Secure interactive entry mode to keep secrets out of shell history and logs
Centralized SQLite storage for all environment variables across multiple projects
2 GitHub stars

사용 사례

Managing multiple environment files (dev/staging/prod) through a unified CLI interface
Importing legacy .env files into a centralized manager for better organization and persistence
Setting up new project secrets by copying existing configurations from related services