Metadata-Version: 2.4
Name: env-diff-cli
Version: 0.1.0
Summary: Compare two .env files — show added, removed, and changed keys without leaking values
Author-email: Aaron Levin <awlevin@comcast.net>
License-Expression: MIT
License-File: LICENSE
Keywords: cli,devtools,diff,dotenv,env
Classifier: Development Status :: 4 - Beta
Classifier: Environment :: Console
Classifier: License :: OSI Approved :: MIT License
Classifier: Topic :: Software Development :: Build Tools
Requires-Python: >=3.9
Description-Content-Type: text/markdown

# env-diff

Compare two `.env` files — see what's added, removed, or changed **without leaking secret values**.

## Install

```bash
pip install env-diff
```

## Usage

```bash
env-diff .env.example .env.local
```

```
Added (2)
  + NEW_API_KEY
  + FEATURE_FLAG

Removed (1)
  - OLD_SECRET

Changed (1)
  ~ DATABASE_URL

3 difference(s) found
```

### Options

| Flag | Description |
|------|-------------|
| `--show-values` | Show masked values for changed keys (e.g. `sk****yz`) |
| `--no-color` | Disable colored output |
| `-q, --quiet` | Exit code only: `0` = identical, `1` = different |

## Exit Codes

- `0` — files are identical
- `1` — differences found
- `2` — file not found or error

## Why?

Every dev has done `diff .env.example .env` and accidentally pasted the output somewhere public. `env-diff` shows you **what changed** without showing **the actual secrets**.

Perfect for:
- PR reviews ("which env vars changed?")
- Deployment checklists
- Onboarding ("what do I need to add to my .env?")
- CI checks (compare `.env.example` against required vars)

## License

MIT
