Metadata-Version: 2.4
Name: envwarden
Version: 0.2.0
Summary: Compare .env against .env.example and find missing or undocumented variables
License-Expression: MIT
Project-URL: Homepage, https://github.com/Gnomecromancer/envcheck
Project-URL: Repository, https://github.com/Gnomecromancer/envcheck
Keywords: dotenv,env,environment,config,ci,developer-tools
Classifier: Development Status :: 3 - Alpha
Classifier: Environment :: Console
Classifier: Intended Audience :: Developers
Classifier: Programming Language :: Python :: 3
Classifier: Topic :: Software Development
Classifier: Topic :: Utilities
Requires-Python: >=3.10
Description-Content-Type: text/markdown
Requires-Dist: click>=8.0.0

# envwarden

Compare `.env` against `.env.example` and find missing or undocumented variables — great for CI and onboarding.

## Install

```bash
pip install envwarden
```

## Usage

```bash
# Auto-detect .env and .env.example in current directory
envwarden

# Scan a specific project directory
envwarden /path/to/project

# Ignore undocumented keys (don't flag .env-only vars)
envwarden --allow-extra

# Don't warn about empty values
envwarden --no-warn-empty

# CI-friendly: only print issues, exit 0/1
envwarden --quiet
```

## Example output

```
env:     .env
example: .env.example

✗ Missing (2) — required by .env.example but not in .env:
    DATABASE_URL
    REDIS_URL

⚠ Undocumented (1) — in .env but not in .env.example:
    MY_LOCAL_DEBUG_FLAG

⚠ Empty (1) — keys with no value set:
    SECRET_KEY
```

Exits with code `1` when missing or extra keys are found, `0` when all clear.

## Supported example file names

- `.env.example`
- `.env.sample`
- `.env.template`

## CI integration

```yaml
- name: Verify .env matches .env.example
  run: envwarden --quiet
```

## License

MIT
