# Install config-file-validator with Homebrew, MacPorts, scoop, winget CLI tool to validate different configuration file types. Version 2.3.0 via Homebrew; verified 2026-06-24. ## Install ```sh sudo av install brew:config-file-validator ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install config-file-validator ``` Evidence: local Homebrew formula metadata - MacPorts (94%): ```sh sudo port install config-file-validator ``` Evidence: MacPorts ports tree: sysutils/config-file-validator/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ### Windows - Scoop (92%): ```sh scoop install main/config-file-validator ``` Evidence: Scoop official bucket manifest trees: bucket/config-file-validator.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 - winget (92%): ```sh winget install --id Boeing.config-file-validator -e ``` Evidence: Windows Package Manager source index: Boeing.config-file-validator from https://cdn.winget.microsoft.com/cache/source.msix ## Package facts - **Package key:** brew:config-file-validator - **Package manager:** Homebrew - **Package manager page:** - **Version:** 2.3.0 - **Source summary:** CLI tool to validate different configuration file types - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** Apache-2.0 - **Source archive:** - **Last updated:** 2026-06-24T23:45:20Z - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - validator (cli) - validator (alias) ## Build dependencies - go ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 2.3.0 - Package-manager updated: 2026-06-24 - Local data: ok - Upstream repository: https://github.com/Boeing/config-file-validator - Upstream latest detected: v2.3.0 (current) ## Project history and usage Config File Validator is a Boeing-published CLI for validating configuration files across many formats. It recursively searches directories, detects formats by extension or known filename, and reports syntax, schema, and CI-friendly output. ### Project history The project is maintained as an Apache-2.0 Go command and library. Its README describes support for 18 formats, schema validation through JSON Schema, XSD, and SchemaStore, and integration surfaces such as GitHub Actions, pre-commit, SARIF, JUnit, JSON output, and a Go library API. The 2.x changelog records a shift from simple syntax/format checking into a broader configuration-validation platform: schema maps, SchemaStore lookup, SARIF output, JSONC, stdin support, exit-code granularity, and project-level .cfv.toml configuration. ### Adoption history Official installation instructions list Homebrew, Winget, MacPorts, Scoop, Go install, and binary releases for macOS, Linux, and Windows. That breadth makes the tool unusually package-manager-visible for a validator whose main use is inside repositories and CI jobs. ### How it is used Common usage is to run validator against a repository or directory tree, optionally constrained by file types, schema maps, ignore files, and reporter output. The .cfv.toml file lets projects commit validation defaults instead of repeating CLI flags in CI. ### Why package nerds care For package and tooling curators, Config File Validator is notable because it treats configuration files themselves as the package surface: it knows common filenames through GitHub Linguist data, validates extensionless files, and emits outputs that package CI systems can consume directly. ### Timeline - 2025: v1.9.0 added a changelog, JSON formatting checks, and TOON validation. - 2026: v2.0.0 added schema validation for JSON, YAML, TOML, and TOON, XML schema support, type maps, schema maps, SchemaStore, SARIF, and no-schema mode. - 2026: v2.2.0 added .cfv.toml discovery, JSONC support, pre-commit support, embedded SchemaStore catalog support, and zero-setup remote schema fetching. - 2026: later 2.x work added a documentation website, GitHub reporter output, ignore-file support, and automatic known-file detection from GitHub Linguist. ### Related projects - Official documentation and README connect the tool to JSON Schema, XSD, SchemaStore, GitHub Actions, pre-commit, SARIF, GitHub Linguist, and Go. ### Sources - - - - - - ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - narrow executable package without higher-risk signals ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: ./.cfv.toml ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** config-file-validator - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Other Package-Manager Records - MacPorts - config-file-validator: normalized package name match | MacPorts ports tree: sysutils/config-file-validator/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 - Scoop - main/config-file-validator: normalized package name match | Scoop official bucket manifest trees: bucket/config-file-validator.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 - winget - Boeing.config-file-validator: normalized package name match | Windows Package Manager source index: Boeing.config-file-validator from https://cdn.winget.microsoft.com/cache/source.msix ## Related links - [Source-control packages](https://www.automicvault.com/pkg/source-control-tools/) - Belongs to a source-control command family. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [Developer build packages](https://www.automicvault.com/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata. - [go](https://www.automicvault.com/pkg/brew/go/) - Build dependency declared by Homebrew. - [dhall-json](https://www.automicvault.com/pkg/brew/dhall-json/) - Shares av.db curated category or tags: cli, configuration, developer-tools, json, yaml. - [butane](https://www.automicvault.com/pkg/brew/butane/) - Shares av.db curated category or tags: cli, configuration, developer-tools, yaml. - [json2hcl](https://www.automicvault.com/pkg/brew/json2hcl/) - Shares av.db curated category or tags: cli, configuration, developer-tools, json. - [ytt](https://www.automicvault.com/pkg/brew/ytt/) - Shares av.db curated category or tags: cli, configuration, developer-tools, yaml. - [dasel](https://www.automicvault.com/pkg/brew/dasel/) - Shares av.db curated category or tags: cli, developer-tools, json, toml, yaml. - [dhall-bash](https://www.automicvault.com/pkg/brew/dhall-bash/) - Shares av.db curated category or tags: cli, configuration, developer-tools. - [dyff](https://www.automicvault.com/pkg/brew/dyff/) - Shares av.db curated category or tags: cli, configuration, developer-tools, json, yaml. - [dynaconf](https://www.automicvault.com/pkg/brew/dynaconf/) - Shares av.db curated category or tags: cli, configuration, developer-tools. - [action-validator](https://www.automicvault.com/pkg/brew/action-validator/) - Both packages work with overlapping file formats or content types. Shared terms: cli, developer, developer-tools, validate, validation. ## Combined YAML source View the package source record on GitHub. [combined/config-file-validator.yml](https://github.com/automic-vault/db/blob/main/combined/config-file-validator.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph