Inspect a Helm Chart.yaml for a non-SemVer version, dependencies a v1 chart will ignore, an unquoted appVersion read as a number, and keys Helm skips.
Waiting for a Chart.yaml
Templates are not rendered and no Helm command is run.
The findings appear here
A version that is not SemVer, a v1 chart whose dependencies Helm will ignore, an unquoted appVersion read as a number, and keys Helm does not recognise.
This reads Chart.yaml as YAML. It does not render templates, resolve dependencies from their repositories, or run `helm lint` — all of which check things that are invisible here.
Chart.yaml Inspector runs entirely on your device — no Helm command is run and nothing is uploaded.
You’re on the Free plan. Compare plans
Helm ignores an unrecognised key in Chart.yaml rather than complaining. So `appversion` with a lowercase v is simply absent, `maintiners` is simply not there, and nothing tells you — `helm list` shows a blank column that nobody notices for months. Those keys get collected and reported here, because nothing else is going to.
The finding worth more than all the others is a `v1` chart that declares dependencies in Chart.yaml. Helm 3 installs a v1 chart quite happily, and reads its dependencies from requirements.yaml instead — so the dependencies block is ignored entirely and the subcharts are silently not installed. The release succeeds. The database it needed is not there.
`version` and `appVersion` are different things and the distinction catches people out. `version` is the chart's own and Helm requires SemVer 2, with no leading `v` — a chart versioned `v1.0.0` is rejected outright. `appVersion` is the application's, need not be SemVer, and should be quoted, because unquoted `1.10` is the number 1.1 under YAML's rules. This shows you that happening rather than describing it.
Dependencies are listed with their version constraint, their alias and their condition. A dependency with no repository is resolved from the `charts/` directory as a vendored subchart, which works and means the dependency is whatever happens to be on disk — worth knowing rather than worth avoiding.
Nothing is rendered and no Helm command is run. `helm lint` knows the chart schema and will catch things this cannot; this reads YAML.
If the chart is `apiVersion: v1`, Helm reads dependencies from requirements.yaml and ignores the `dependencies` block in Chart.yaml completely. The install succeeds and the subcharts are absent. Changing to `apiVersion: v2` is the fix, and this reports it as an error.
`version` is the chart's own version and must be SemVer 2 with no leading v — Helm rejects anything else. `appVersion` is the version of the application the chart deploys, need not be SemVer, and is what `helm list` shows. They move independently: a chart fix bumps version and leaves appVersion alone.
Because unquoted, YAML reads it as a number and a trailing zero on a decimal is not significant. Quote it — `appVersion: "1.10"` — and this tool shows you the unquoted value being misread so you can see it rather than take it on trust.