# config-file-validator mit Homebrew, MacPorts, scoop, winget installieren
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für config-file-validator in AI-Agent-Workflows.
## Installation
```sh
sudo av install brew:config-file-validator
```
Weitere Installationsbefehle:
### macOS
- Homebrew (100%):
```sh
brew install config-file-validator
```
Evidenz: local Homebrew formula metadata
- MacPorts (94%):
```sh
sudo port install config-file-validator
```
Evidenz: 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
```
Evidenz: 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
```
Evidenz: Windows Package Manager source index: Boeing.config-file-validator from https://cdn.winget.microsoft.com/cache/source.msix
## Paketfakten
- **Paketschlüssel:** brew:config-file-validator
- **Paketmanager:** Homebrew
- **Version:** 2.3.0
- **Quellzusammenfassung:** CLI tool to validate different configuration file types
- **Homepage:**
- **Repository:**
- **Zuletzt aktualisiert:** 2026-07-27T22:04:03+02:00
- **Generiert:** 2026-08-03T19:37:03+00:00
## Executables
- validator (Alias)
## Installationsverhalten
- Bottle: nicht verfügbar
## Version und Aktualität
- Seite generiert: 2026-08-03
- Manager-Version: 2.3.0
## 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
-
-
-
-
-
-
## Sicherheitshinweise
narrow executable package without higher-risk signals.
- **Geiger-Risiko:** grün / niedrig
- 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
## Andere Paketmanager-Einträge
- 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
## Combined YAML source
View the package source record on GitHub. [combined/config-file-validator.yml](https://github.com/mxcl/pkgdb/blob/main/combined/config-file-validator.yml)
## Quellen
- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph