config-validation

Cross-platform config file CLI toolchain. Validates syntax, schema compliance, and formatting for across 18 different configuration file types. Written in Go.

Linter for OpenSSH client config files.

Source-aware YAML validation for Go with native schemas, JSON Schema, custom validators, and precise line/column diagnostics.

Stop AI agents from crashing OpenClaw by validating config changes. Auto-backup, schema validation, and auto-rollback.

A web based playground for testing and debugging Renovate configurations in real-time.

A meta-linter that detects stale references in configuration files and linters configuration files

Type-safe environment variables for Node.js — validated at startup, before your app runs.

Source-aware YAML linter for Glance dashboards with compatible include expansion and precise file/line errors.

Lint Cloudflare Pages's _redirects files

🛡️ A powerful yet lightweight tool to catch critical configuration issues before runtime, ensuring your .NET applications run reliably across all environments.

Environment variable validation, security scanning & documentation generator

Config drift detection for Docker Compose. Checks intent, not just syntax.

Deterministic CLI that lints .env files: syncs against .env.example, validates syntax & schema, and detects hardcoded secrets (AWS, Stripe, GitHub, OpenAI, private keys). JSON/Markdown reports, runs locally — secrets never leave your machine.

Validate Hermes agent configuration files with env var expansion and profile isolation

Zero-dependency TypeScript library to validate environment variables at startup - fail fast with clear, structured errors.

A Spring inspired config manager

JetBrains plugin for DataOps authoring: validates Airflow DAG schedules and Kafka Connect configs before deploy.

Validate a whole config tree in one pass, reporting each real mistake once with cascade errors pruned

Catch missing config keys before production — static AST analysis for process.env and config objects

An Envoy config workbench in the browser. Check a config, see what connects to what, and find out where a request actually goes.