Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%

brew install config-file-validator

local Homebrew formula metadata

MacPortsverifiziert · 94%

sudo port install config-file-validator

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

Windows

Scoopverifiziert · 92%

scoop install main/config-file-validator

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

Windows Package Managerverifiziert · 92%

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

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

Überblick

Paketzusammenfassung

CLI tool to validate different configuration file types

Projektlinks

Befehle und Aliase

validator

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

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.

Quellen

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

narrow executable package without higher-risk signals

Signale

metadata:no-higher-risk-signals

Installationsverhalten

In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

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

Installierte Executables

Befehl	Art	Sichtbarkeit	Hinweis
`validator`	cli	globales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25

Manager-Version2.3.0

Manager aktualisiert2026-06-24

lokale DatenOK

Upstreamaktuell

neueste erkannte Versionv2.3.0

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

OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüssel	brew:config-file-validator
Version	2.3.0
Paketmanager	Homebrew
Paketmanager-Seite	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-Dokumentation	https://boeing.github.io/config-file-validator
Lizenz	Apache-2.0
Quellarchiv	https://github.com/Boeing/config-file-validator/archive/refs/tags/v2.3.0.tar.gz
Zuletzt aktualisiert	2026-06-24T23:45:20Z
Pulse	updated
Build-Abhängigkeiten	go
Bottle	verfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	nicht definiert
Dienst	keiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

MacPorts95%

config-file-validator

sudo port install config-file-validator

normalized package name match
Abgeglichen nach: 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
Abgeglichen nach: 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
Abgeglichen nach: 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

Paketgraph

Links stammen aus dem lokalen Paketbeziehungsgraph, Ergänzungen, Abhängigkeitskanten, Ecosystem-Matches und Paket-Hub-Mitgliedschaft.

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Combined YAML source

View the package source record on GitHub.

combined/config-file-validator.yml

Verwendete Quellen

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

config-file-validator mit Homebrew, MacPorts, scoop, winget installieren