Downloads
helm-viz v1.2.0
Current release · 26 October 2026
Two archives per platform: a helm plugin, which puts the whole thing behind helm helmviz, and a standalone binary, which is one directory holding the binary, its LICENSE and its README. Both contain the same program — the UI is embedded in it, so there is nothing else to fetch.
Archives
What is in the release, and the checksum each file was published with. The files themselves come from a link on the download page, for a registration key or an email address. Every file here is named in SHA256SUMS for this version; a published version's files never change.
| Platform | Helm plugin helm plugin install <url> | Standalone binary, LICENSE, README |
|---|---|---|
| macOS · Apple silicon | helm-viz-plugin_1.2.0_darwin_arm64.tar.gz 5.9 MB · signature f90acb2393a2596b087b35bfccacc6ec3b4b4e2d57ee52172696256403089fe7 | helm-viz_1.2.0_darwin_arm64.tar.gz 5.9 MB 0f96cf17920abe5d4ade50338f5ed0e0b8a2268fca9e528ed6e040fb9779b88c |
| macOS · Intel | helm-viz-plugin_1.2.0_darwin_amd64.tar.gz 6.3 MB · signature 8a0e2f2867c123321fc864f8ceebdf9a1017cccb8422e94a891722db5cba0a56 | helm-viz_1.2.0_darwin_amd64.tar.gz 6.3 MB be21644e5008779a76b2a3989318ab21922a1b1c871925e3701b7ee23c0660a2 |
| Linux · x86_64 | helm-viz-plugin_1.2.0_linux_amd64.tar.gz 6.2 MB · signature f33cb5898d975440848b0c961fe9b3daae4baa5c143d330072a5aed6c135b2b9 | helm-viz_1.2.0_linux_amd64.tar.gz 6.2 MB 61f22fb68da4e026bc3ddf6aeaa40bd1c1209c97a7b63be8e139512f3d2bb990 |
| Linux · arm64 | helm-viz-plugin_1.2.0_linux_arm64.tar.gz 5.7 MB · signature 2dfd5f24b02ee3350328fa767ee333a47649cd5a5216a80028a14c8e2cd46c35 | helm-viz_1.2.0_linux_arm64.tar.gz 5.7 MB 1cbeaf5f87f35a9cb9317a7cbfcbd000955dc9cfe3471710e9f9292ce7904afa |
| Windows · x86_64 | None. The manifest's command is a unix path — take the standalone archive. | helm-viz_1.2.0_windows_amd64.zip 6.2 MB e0f7d87858ffbeaae481d8c7268a6a8080894cd7a886d7b59ba8fd29c2a0c01f |
Only the plugin archives carry a .prov: it is helm's own provenance format, and helm 4 is what checks it — at plugin-install time, against your keyring. Nothing would ever verify one beside a standalone tarball, so none is published. SHA256SUMS covers every file on this page. The archives themselves come from a link on the download page, with a registration key or an emailed link.
What changed in v1.2.0
Straight from the tag: every change that reached the product since v1.1.0, in the words it was committed under.
New
- New licence terms: free under 250 staff and A$15M revenue
2 commits since v1.1.0.
Check what you downloaded
A checksum for every archive, and a signature on the ones helm installs for you.
# with the archive from /helm-viz/download in this directory:$ curl -sSL https://jcrstack.com/dl/helm-viz/v1.2.0/SHA256SUMS | sha256sum -c --ignore-missing ./helm-viz_1.2.0_linux_amd64.tar.gz: OK # --ignore-missing, because SHA256SUMS covers every platform# and you downloaded one. shasum -a 256 -c on macOS.$ curl -sSL https://jcrstack.com/dl/helm-viz/jcrstack-release.asc | gpg --import$ gpg --export > ~/.gnupg/pubring.gpg # only needed for `helm plugin install` on helm 4, which# verifies the .prov before it installs. the second line is# not redundant: helm reads keyrings with Go’s OpenPGP, which# cannot parse the keybox format GnuPG has used since 2.1.Every release
Each one keeps its own directory, and the files in a published version never change. If you are pinning helm-viz in a pipeline, ask the download API for a specific version rather than the newest your key covers, so an upgrade is a commit. The pipeline example does.