Credential access
Reads manifest files that may include secret references or generated values.
brew / rank 282
Install kubeconform with Homebrew
FAST Kubernetes manifests validator, with support for Custom Resources! Version 0.8.0 via Homebrew; verified 2026-07-27.
agent safety
Agent safety answer
kubeconform validates Kubernetes manifests and may read deployment configuration.
Remote mutation
Validation is local and does not mutate clusters.
Publish/artifact risk
Can validate deployable artifacts before cluster application.
Recommended control
Gate only when scanning secret-bearing files or feeding apply pipelines.
Agent-use guidance
Allow local validation; require approval before passing output into deployment commands.
install
Additional install commands
macOS
Homebrewverified · 100%
brew install kubeconformprovider-native install command
overview
Package summary
FAST Kubernetes manifests validator, with support for Custom Resources!
Project links
Commands and aliases
- kubeconform
history
Project history and usage
Kubeconform is a Kubernetes manifest validator that grew out of the Kubeval lineage: its own documentation says it is inspired by, contains code from, and is designed to stay close to Kubeval while adding higher-throughput validation, configurable schema locations, CRD support, offline validation, and a schema registry fork for recent Kubernetes versions.
Project history
The GitHub repository was created on 2020-05-30. The public documentation feed dates the overview, installation, usage, CRD support, JSON Schema conversion, GitHub Action, and Go-module documentation pages to 2021-07-02, which matches the period when the project presented itself as a standalone replacement for common Kubeval workflows.
Kubeconform kept the Unix-style single-binary validator shape that made Kubeval popular in CI, but its distinguishing evolution was schema flexibility: users can validate against Kubernetes versions, local or remote schema locations, and converted CRD schemas rather than only core Kubernetes resources.
Adoption history
Adoption has been strongest in CI/CD and GitOps-adjacent workflows where teams want to fail manifest changes before applying them to a cluster. The tool's package-manager footprint across Homebrew, Linux distributions, Windows package managers, and Nix reflects a cross-platform CLI audience rather than a cluster-installed controller audience.
The repository metadata observed on 2026-07-01 showed more than 3000 GitHub stars, making it one of the better-known third-party Kubernetes manifest validators outside kubectl itself.
How it is used
Typical use is to pass files, directories, or stdin to `kubeconform`, optionally choosing output such as text, JSON, JUnit, or TAP and enabling summary output for CI logs. For custom resources, users point `-schema-location` at local or HTTP(S) JSON schemas, or convert CRDs to JSON Schema with the project-provided conversion tooling.
The package matters in validation pipelines because it gives maintainers a fast, scriptable check for Kubernetes resource structure without needing live cluster access.
Why package nerds care
For package-manager users, Kubeconform is the kind of small Go CLI that fits neatly into `brew install`, CI images, pre-commit hooks, and reproducible Nix shells. Its significance is not a broad runtime platform but a sharp replacement-class tool for a once-common Kubernetes validation gap.
Timeline
- 2020-05-30: GitHub repository created.
- 2021-07-02: Documentation pages published for overview, installation, usage, CRD support, JSON Schema conversion, GitHub Action usage, and Go-module usage.
- 2024-07-30: Release v0.6.7 published.
- 2025-05-12: Release v0.7.0 published.
- 2026-06-04: Release v0.8.0 published.
Related projects
- Kubeval is the direct predecessor named by the Kubeconform documentation. The kubernetes-json-schema registry is part of the validation ecosystem because Kubeconform uses JSON schemas for Kubernetes resources and supports schema-location overrides for CRDs.
Sources
security posture
Risk level: orange
infrastructure mutation or orchestration signal.
Risk classifier
orange risk · medium confidence · infrastructure
Why
- infrastructure mutation or orchestration signal
Signals
- text:kubernetes
Install behavior
- No Homebrew bottle metadata was recorded.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
kubeconform | executable | indexed executable | Discovered from the local executable index. |
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-08-03
manager version0.8.0
manager updated2026-07-27
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:kubeconform |
|---|---|
| Version | 0.8.0 |
| Package manager | Homebrew |
| Homepage | https://github.com/yannh/kubeconform |
| Repository | https://github.com/yannh/kubeconform |
| Last updated | 2026-07-27T21:58:44+02:00 |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
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.
Used sources
- Geiger risk classifier
- Nucleus package database
- curated agent safety answer
- curated package history
- pkgdb category and tag curation