CI/CD Integration
Inject encrypted vault secrets into your pipelines. No .env files in your repo.
GitHub Actions
Use the official meowrithm/meowpass-action@v1 to pull secrets into your workflow.
1. Create an API key
2. Add GitHub secrets
In your repo Settings → Secrets and variables → Actions, add:
| Secret name | Value |
|---|---|
| MEOWPASS_VAULT_ID | Your vault ID |
| MEOWPASS_TOKEN | API key (mp_...) |
| MEOWPASS_MASTER_KEY | Pre-derived master key (hex) |
| MEOWPASS_SALT | Key salt (base64) |
3. Add to your workflow
Write .env file instead
Use mode: env to write a .env file:
Vercel
Sync vault secrets to Vercel project environment variables with one command. Auto-maps MeowPass environments to Vercel targets.
1. Create a Vercel token
Go to vercel.com/account/tokens and create a token. Add it as a GitHub secret or export it locally.
2. Sync secrets
3. GitHub Actions + Vercel deploy
Env mapping: production → production, staging → preview, default → development. See full Vercel docs for all options.
Any CI/CD (CLI)
For GitLab CI, CircleCI, Jenkins, or any pipeline — use mp run or mp pull directly.
Drift Detection in CI
Use mp diff --exit-on-drift to fail builds when local .env is out of sync with the vault.
Git Hooks
Catch drift before it reaches CI. Install a pre-commit hook: