Inspect a Helm values.yaml for committed credentials, a latest image tag and a missing resources block, and generate the values table for its README.
Waiting for a values.yaml
Nothing is rendered and no Helm command is run.
The findings appear here
A credential with a default that ships inside the chart, an image tag of latest, a missing resources block, and the replicaCount that an HPA will fight with.
Values at a credential-shaped path are masked here and written as (set at install) in the generated documentation, because a generated README is the document most likely to end up committed. Beyond that: which of these values a template actually uses is invisible without rendering, and nothing here renders anything — so a value with no finding may still be unused, or required and absent.
values.yaml Inspector runs entirely on your device — credential-shaped values are masked rather than read, and nothing is uploaded.
You’re on the Free plan. Compare plans
Values are masked by key name, never by value. A pasted values.yaml routinely contains a real password, and a tool that echoes it into a table has published it to whatever screen is being shared. So anything at a path ending in password, secret, token, apiKey and the rest is shown as dots.
In the generated documentation it becomes "(set at install)" rather than the value, because a generated README is the document most likely to be committed, and a password committed into a README is a password published.
A credential with a default in values.yaml gets a warning in its own right. It ships inside the packaged chart, and it ends up in the release's stored values where anyone with `helm get values` can read it back — which is a quieter exposure than a committed file and a wider one.
The null distinction is worth knowing. A `null` default in values.yaml is Helm's idiom for "the user must set this", and reads as absent in a template. But a `null` in an override file deletes the key rather than setting it to null. Same literal, opposite meanings depending on which file it is in.
What this cannot know is which of these values a template actually uses. That needs rendering, and nothing here renders anything — so a value with no finding may still be dead, or required and missing.
Nothing leaves your browser, and beyond that the inspector masks anything at a credential-shaped path before displaying it — and writes "(set at install)" rather than the value in generated documentation. So a password cannot reach the screen or the README even by accident.
Because it travels further than the repository. It ships inside the packaged chart, and Helm stores the release's values in the cluster where `helm get values` reads them back. Leaving it empty and requiring it at install keeps it in one place.
Because charts conventionally fall back to `.Chart.AppVersion` when the tag is empty, which keeps the deployed image and the chart's declared app version in step automatically. A hardcoded tag has to be remembered separately on every release.
No, and it says so. Finding that needs the templates rendered, which means executing Go templates — this does not. A value with no finding here may still be entirely unused.