No. The helm verify command confirms that a chart archive has not changed since it was packaged and that it was signed by the holder of a particular key. It does not review the templates, the images they pull or the permissions they request. Treat it as an integrity check, then inspect the contents.
What helm verify actually checks
When a chart is packaged with signing, Helm writes a provenance file next to the archive, named like the chart with a .prov suffix. According to the Helm docs, that file holds the contents of Chart.yaml, the SHA-256 digest of the archive, and a PGP signature over the whole thing.
Running helm verify mychart-0.1.0.tgz recomputes the digest and checks the signature. Running helm install --verify does the same before anything is rendered, and aborts the install if the check fails. If the digest does not match you get an error along the lines of "sha256 sum does not match".
What it proves and what it does not
| Question | Does helm verify answer it? |
|---|---|
| Is the archive byte for byte what the signer packaged? | Yes |
| Was it signed by the holder of a specific key? | Yes |
| Do I have reason to trust that key's owner? | No, you decide that |
| Are the templates free of risky settings? | No |
| Do the container images it references have vulnerabilities? | No |
| Will it ask for cluster-admin through RBAC objects? | No |
The Helm docs are direct about the trust gap: Helm does not act as a certificate authority, so establishing trust in a signer's public key is up to you. A signature from a key you never vetted only tells you that someone signed it.
A sensible order of checks
- Obtain the publisher's public key through a channel other than the chart repository itself.
- Run
helm verifyor install with--verifyand a--keyringpointing at that key. - Render the chart with
helm templateand read the output, especially ClusterRole, ClusterRoleBinding, hooks and anything with privileged settings. - List every image the rendered manifests reference and scan them.
- Pin the chart version, and for OCI charts pin the digest.
Step 3 is where most real review happens. A verified chart can still ship a privileged DaemonSet, because the publisher meant it to.
Try it yourself
Try it yourself
Click through it at your own pace, or open it full screen. Scan an image and look at how findings are grouped, since a signed chart still pulls images that need their own review.
Safeguard can scan the images and dependencies a chart pulls in, and a free scan is available at https://gold.safeguard.sh/scan. For a deeper walk through chart review, see how to scan a Helm chart for misconfigurations.
Quick check
Does helm verify work for charts stored in an OCI registry?
The Helm registry docs say a provenance file next to the chart is uploaded on push, but they do not give a helm verify command for OCI charts. They point to the helm-sigstore plugin as an alternative. Check your Helm version before depending on it.
Is a signed chart the same as a reviewed chart?
No. A signature shows origin and integrity. Review is a separate step that you perform on the rendered manifests.
Sources
Last reviewed: 19 October 2026.
