EnvMark

Name: EnvMark
Author: Grazulex

Git-Based .env File Management.
One Repo • One Branch Per Environment • Zero Server

Get Started View on GitHub

Install with npm

npm install -g @grazulex/envmark

terminal

$ envmark pull dev

📦 Pull from development

──────────────────────────────────────

Project: my-app

Environment: dev (branch: development)

✔ Syncing repository...

✔ Fetched .env file

📄 .env pulled from development

Saved to: .env

Lines: 24

How It Works

envmark-secrets (Single Git Repository) ├── branch: development │ ├── project-alpha/.env │ ├── project-beta/.env │ └── api-gateway/.env ├── branch: staging │ ├── project-alpha/.env │ └── ... ├── branch: qa │ └── ... └── branch: main (production) ├── project-alpha/.env └── ...

One repo for all projects. One branch = One environment. Git handles versioning, diffing, and access control.

Why EnvMark?

🔄

Git-Native Storage

Your .env files live in a Git repository. Full version history, diffs, branching, and pull requests for free.

🌳

Branch = Environment

Development, staging, production - each environment is a Git branch. Simple, intuitive, powerful.

🏢

Multi-Project Support

All your projects in one repository. Each project has its own folder within each environment branch.

🔐

Optional Encryption

AES-256-GCM client-side encryption. Your secrets stay secret, even in shared repositories.

🚫

Zero Server

No hosted service, no API, no subscription. Just Git. Works with GitHub, GitLab, Bitbucket, or self-hosted.

🎨

Beautiful CLI

Colorful output, spinners, interactive prompts. Environment management that feels modern.

Environment Aliases

Alias	Git Branch
`dev`, `development`	development
`staging`	staging
`qa`	qa
`prod`, `production`	main

Ready to simplify your .env management?

Get started in under a minute with a single command.

Quick Start Guide View Commands