`envtrap check`

Validates the envtrap.json configuration file in the current working directory.

envtrap check

Output Examples

Valid Configuration

If the configuration passes all schema rules, envtrap exits with code 0:

✅ Configuration is valid.

No Configuration Found

If no envtrap.json is present in the current working directory, envtrap notifies that default settings are in effect:

No envtrap.json found. Using default settings.

Validation Failure

If any field contains an invalid type or unrecognized mode, envtrap prints JSONPath errors and exits with code 1:

Configuration Validation Failed:
  - [channels.network] Expected 'block', 'warn', or 'off', received 'reject'
  - [entropy.threshold] Expected number, received 'high'

CI/CD Pre-Commit Hook

Use envtrap check in pre-commit hooks or CI test scripts to catch configuration mistakes before merging:

package.json

{
  "scripts": {
    "lint:config": "envtrap check"
  }
}

Getting Started

Core Architecture

Monitoring Channels

Configuration

Threat Model & Security

CLI Reference

Releases

Contributing

envtrap check

`envtrap check`

Output Examples

Valid Configuration

No Configuration Found

Validation Failure

CI/CD Pre-Commit Hook

​envtrap check

​Output Examples

​Valid Configuration

​No Configuration Found

​Validation Failure

​CI/CD Pre-Commit Hook

`envtrap check`

Output Examples

Valid Configuration

No Configuration Found

Validation Failure

CI/CD Pre-Commit Hook