Open Source

Start with open source.

Deploy HELM OSS, run one workflow, and verify the release before you trust it.

Open source is the best first step.
Run one workflow before you ask for more.
Public proof stays next to the release.

View on GitHub Read Quickstart

Install

Install and verify.

These are the two commands that matter first.

curl -fsSL https://raw.githubusercontent.com/Mindburn-Labs/helm-oss/main/install.sh | bash

Install the CLI and local runtime from the public source path.

helm verify --release sdk/go/v0.1.1
helm verify --attestation https://github.com/Mindburn-Labs/helm-oss/releases/download/sdk/go/v0.1.1/helm-attestation-sdk-go-v0.1.1.json

Check the release before you rely on it.

Release proof snapshot

Pack ID, hash, and conformance state from the latest public bundle.

Verified

Pack ID

sdk/go/v0.1.1

SHA-256

b4c9e2c71c4c5c2bac2b2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3

Conformance

Verify independently

What you get

Use the public wedge.

HELM OSS is already useful on its own.

Boundary

Fail closed

Block unsafe actions before they run.

Proof

Keep receipts

Each decision leaves a record you can inspect and replay.

Transport

Use one workflow

Point one compatible workflow at HELM before you widen the rollout.

Then choose the next step.

After OSS, most teams need proof or access.

Proof

Check the public proof

Use verifier, explorer, releases, and TITAN without leaving the public site.

Access

Request platform access

Use this only when your team needs a shared control plane.