// the find
Boeing/config-file-validator
Cross-platform CLI tool to validate configuration files across 18 formats. Syntax and schema validation with JSON Schema, XSD, and SchemaStore integration. Written in Go.
A single-binary CLI from Boeing that validates config files across 18 formats — JSON, YAML, TOML, HCL, XML, INI, and more — with optional schema validation via JSON Schema, XSD, or automatic SchemaStore lookup. It recursively scans directories, auto-detects formats by extension or known filename, and outputs results in formats CI pipelines can consume (JUnit, SARIF, JSON). For teams that have sprawling config files across a monorepo, this replaces a collection of format-specific linters.
93% test coverage and txtar-based integration tests for every CLI flag combination — the test suite is genuinely thorough, not just a coverage number. SARIF and JUnit output means you get inline PR annotations in GitHub Actions without writing glue code. The SchemaStore integration is the useful feature here: it auto-fetches schemas for known files like `.github/workflows/*.yml` or `package.json` so you get semantic validation, not just syntax checking. Usable as a Go library, so you can embed it if you need config validation inside another tool rather than shelling out.
510 stars for a tool that solves a genuinely common problem suggests it hasn't broken through — partly because most teams already have format-specific validators baked into their editors and CI, so the pitch of 'one tool for all formats' has to clear a high bar to displace them. Schema validation requires you to either supply a schema path or rely on SchemaStore's catalog, which covers common files but misses anything proprietary or internal. The Justfile validator ships a hand-rolled parser and lexer inside the repo, which means it will lag behind `just`'s own grammar changes and is a maintenance burden the maintainers will eventually regret. No watch mode — you're running it on-demand or in CI, not getting live feedback during editing.