install

Additional install commands

macOS

Homebrewverified · 100%

brew install config-file-validator

local Homebrew formula metadata

MacPortsverified · 94%

sudo port install config-file-validator

MacPorts ports tree · sysutils/config-file-validator/Portfile · source: api.github.com

Windows

Scoopverified · 92%

scoop install main/config-file-validator

Scoop official bucket manifest trees · bucket/config-file-validator.json · source: api.github.com

Windows Package Managerverified · 92%

winget install --id Boeing.config-file-validator -e

Windows Package Manager source index · Boeing.config-file-validator · source: cdn.winget.microsoft.com

overview

Package summary

CLI tool to validate different configuration file types

Project links

Commands and aliases

validator

history

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 posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

narrow executable package without higher-risk signals

Signals

metadata:no-higher-risk-signals

Install behavior

No Homebrew post-install hook is recorded in formula metadata.
Homebrew bottle metadata is available for 6 platform targets.
Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

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

Config paths the tool may read or write during local use.

Unix: ./.cfv.toml

executables

Installed executables

Command	Kind	Exposure	Note
`validator`	cli	global executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08

manager version2.3.0

manager updated2026-06-24

local dataok

upstreamcurrent

latest detectedv2.3.0

https://github.com/Boeing/config-file-validator

okNo freshness warnings were generated.

install metadata

Package metadata

Package key	brew:config-file-validator
Version	2.3.0
Package manager	Homebrew
Package manager page	https://formulae.brew.sh/formula/config-file-validator
Homepage	https://boeing.github.io/config-file-validator/
Repository	https://github.com/Boeing/config-file-validator
Upstream docs	https://boeing.github.io/config-file-validator
License	Apache-2.0
Source archive	https://github.com/Boeing/config-file-validator/archive/refs/tags/v2.3.0.tar.gz
Last updated	2026-06-24T23:45:20Z
Pulse	updated
Build dependencies	go
Bottle	available (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	not defined
Service	none declared

registry facts

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	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	head stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

MacPorts95%

config-file-validator

sudo port install config-file-validator

normalized package name match
Matched by: Config File Validator

MacPorts ports tree · api.github.com · MacPorts ports tree: sysutils/config-file-validator/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

Scoop95%

main/config-file-validator

scoop install main/config-file-validator

normalized package name match
Matched by: Config File Validator

Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/config-file-validator.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

winget95%

Boeing.config-file-validator

winget install --id Boeing.config-file-validator -e

normalized package name match
Matched by: Config File Validator

Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: Boeing.config-file-validator from https://cdn.winget.microsoft.com/cache/source.msix

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/config-file-validator.yml

Used sources

Geiger risk classifier
Nucleus package database
av.db category and tag curation
cross-ecosystem install command graph
curated configuration and credential file locations
curated package history
external package-manager database matches
package relationship graph
package version freshness
package-page enrichment

Install config-file-validator with Homebrew, MacPorts, scoop, winget