Config and env validators

Catch broken CI YAML, duplicate env keys, and obvious secrets before they hit a pipeline. These are shallow linters: GitHub/GitLab structure, not actionlint; .env lines, not a full dotenv parser.

Docker Compose and Kubernetes checks look at YAML shape, not cluster admission. nginx.conf and .htaccess tools are bracket/section heuristics. CSP Analyzer belongs with HTTP security; it is listed here because it is a header-as-config paste tool. Prefer one .env page — Env File Validator is the canonical API.

CI/CD(1)

Env files & secrets(2)

Infra configs(5)

App manifests & lockfiles(6)

FAQ

Why did my GitHub workflow pass but fail in Actions?
This linter checks YAML plus a few required keys (on, jobs, runs-on/steps). It does not evaluate expressions, reusable workflows, or marketplace actions. Run actionlint or the GitHub UI for the rest.
Env File vs .env Syntax Checker?
/env-syntax-checker permanently redirects to Env File Validator. Same API, one page.

Other validator groups