helm-secrets
4.6.0 open-sourceThe section your link pointed to isn't on helm-secrets's page any more, so we've brought you to the top.
helm-secrets is a Helm plugin to decrypt encrypted Helm value files on the fly.
# Copy the provided example to your project directory cp path/to/helm-secrets/examples/backends/onepassword.sh /usr/local/bin/ # Use it in your helm values file with the 'pass' plugin type pointing to the new backend # vault: # secretManager: onepassword helm-secrets install --evaluate-templates ./my-chart export HELM_SECRETS_ALLOWED_BACKENDS='sops,vault' helm-secrets install --values secrets/optional.yaml? mychart/ HELM_SECRETS_IGNORE_MISSING_VALUES=1 helm-secrets upgrade --values secrets/missing.yaml mychart/ helm secrets upgrade --install myapp ./chart --set-file auth.rootPassword=secrets+literal://ref+vault://secret/mysql#/rootPassword helm secrets encrypt my_secret.yaml helm secrets decrypt -i my_secret.yaml export SOPS_GPG_EXEC=/c/Program Files (x86)/GNU/GnuPG/pub/gpg.exe helm secrets decrypt values.yaml.enc helm secrets patch windows helm secrets decrypt values.yaml.enc helm-secrets --output-decrypt-file-path deploy/secrets.yml # or export HELM_SECRETS_OUTPUT_DECRYPTED_FILE_PATH=1 dec_path=$(helm-secrets decrypt deploy/secrets.yml) echo "Decrypted to: $dec_path" helm-secrets --version helm secrets install --driver-args '--env=AWS_REGION=us-east-1' my-release ./my-chart
Summary
helm-secrets is an open-source Helm plugin that decrypts encrypted Helm value files on the fly, using sops or a vals secret backend to pull from a cloud secret manager like AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault. It runs as a command-line plugin invoked alongside helm itself, either through its protocol handler or as a direct plugin command, which is how it fits into GitOpsGitOpsA practice where Git repositories serve as the single source of truth for infrastructure and application state, with automated systems continuously reconciling live environments to match what is declared in version control. operators such as ArgoCDArgoCDA Kubernetes-native continuous delivery controller, maintained by the CNCF, that syncs live cluster state to declarative config stored in Git, giving cyber tools automated, auditable deployment pipelines.. It is aimed at platform and DevOps engineers who keep Helm value files in git and need secrets encrypted at rest rather than committed in plaintext. First committed in 2017, it now has 92 contributors and 365 commits in the past year, indicating active maintenance.
helm-secrets is a Helm plugin to decrypt encrypted Helm value files on the fly.
How helm-secrets helps
How do I keep secrets encrypted in git without committing plaintext values?
encrypts value files at rest with sops, so what sits in the repository is ciphertext, and decryption only happens when the plugin is invoked alongside a helm command
How do I get a value file's secrets into a helm release without a manual decrypt-then-delete step?
decrypts the file on the fly through a protocol handler or plugin command, feeding helm plaintext in memory for that run only
How do I keep a GitOps operator like ArgoCD deploying charts that reference encrypted values?
works through the same protocol handler ArgoCD calls, so the operator decrypts values as part of its normal sync instead of needing a separate pipeline step
How do I pull a secret from AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault straight into a chart's values or templates?
reads secret references through a vals backend and substitutes the live value from the configured cloud secret manager at render time
Can I confirm what a template will actually render before it reaches a cluster, including the secret values inside it?
evaluates the secret expressions inside the template and can decode base64 secret values so the rendered output can be checked directly
Which value files in a chart directory are missing without failing the whole run?
can be told to ignore missing value files rather than aborting, so a run across many charts reports what is absent instead of stopping
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for helm-secrets, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail helm-secrets puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
15 entries
No entries match these filters.
- March 20241
- February 20231
- November 20221
- September 20222
- June 20221
- February 20221
- November 20211
- October 20211
- June 20211
- March 20211
- February 20211
- May 20201
- April 20202
Project health
Issue, contributor and maintainer activity in jkroepke/helm-secrets, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 8 ±0 vs prior 12 months
- Maintainers 1 +0 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 95% of issues opened, last 12 months
- Median time to close < 1 day first maintainer reply 2.7 hours
- Open backlog 1 of 207 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 1
- Contributors / month 1
- Commits / month 4
- Stars 2,029
- bugs 71%
- features 24%
- other 5%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.