A cross-platform CLI tool written in Go that validates syntax and schema for JSON, YAML, TOML, XML, and other configuration files.
Config File Validator is a cross-platform command-line tool written in Go that validates the syntax and schema of configuration files. It helps catch errors in files like JSON, YAML, TOML, XML, and INI before they are deployed, reducing runtime failures and misconfigurations in applications and infrastructure.
Developers, DevOps engineers, and SREs who manage configuration files across projects and need a reliable way to ensure their correctness in CI/CD pipelines or local development.
It provides a single, lightweight binary that supports a wide range of configuration formats out of the box, with flexible reporting and integration options, making it easier to automate validation in diverse environments.
Cross-platform CLI tool to validate configuration files across 16 formats. Syntax and schema validation with JSON Schema, XSD, and SchemaStore integration. Written in Go.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports syntax validation for over a dozen formats including JSON, YAML, TOML, XML, HCL, and ENV, as listed in the README, making it a one-stop tool for mixed-configuration projects.
Allows recursive directory scanning with configurable depth, exclusion of specific directories or file types, and glob patterns for targeted validation, demonstrated in the examples with flags like --exclude-dirs and --globbing.
Outputs results in standard console, JSON, JUnit, or SARIF formats, with grouping options by file type, directory, or pass-fail status, enabling easy integration into CI/CD pipelines.
All major options can be set via environment variables (e.g., CFV_DEPTH), and it provides a statically compiled binary for consistent cross-platform use, as highlighted in the Philosophy section.
Includes a CLI package for integration into Go applications, with code examples showing custom finders and reporters for tailored validation workflows.
Only supports schema validation for SARIF files currently, as admitted in the README with the note 'Only SARIF files are supported,' leaving other formats without schema-based checks.
Lacks a graphical user interface or IDE plugin, making it less suitable for interactive, real-time validation during editing compared to tools with live feedback.
The programmatic API is specific to Go, so integrating it into applications written in other languages requires shelling out to the CLI, adding complexity for non-Go ecosystems.
Compared to established format-specific validators like jq or yamllint, it has a smaller community and fewer third-party plugins or custom rule sets for advanced validation.