PAGES
← all tools
◆ Secrets Detection & Management

helm-secrets

4.6.0 open-source

helm-secrets is a Helm plugin to decrypt encrypted Helm value files on the fly.

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

all 10 features, with the evidence for each →

Languages

Not documented

Features

10 capabilities · 2 backed by code, an API document or a real run

Built from helm-secrets's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What helm-secrets offers you

  • Command-line interface3
All capabilities 10 capabilities
Helm template secret decryption verified Decrypts and injects secret values into Helm templates at deploy time, with options to evaluate secret expressions, decode base64 secrets, and ignore missing value files. 9 releases · 12 other sources · first seen Apr 2020

Also counts toward: Command-line interface

release 9 total

  • Adds secrets+literal:// downloader syntax to support inline secret references in --set-file 4.1.0 · Sep 2022 · source · release history
  • Adds support for decrypting files defined via --set-file. 4.0.0 · Sep 2022 · source · release history
  • Changes decrypt and encrypt commands to write results to stdout by default; adds -i flag for in-line encryption/decryption. 4.0.0 · Sep 2022 · source · release history
  • The helm secret terraform command is removed; use helm secret decrypt --terraform instead. 4.0.0 · Sep 2022 · source · release history
  • Adds HELM_SECRETS_VALUES_ALLOW_PATH_TRAVERSAL environment variable to control whether dot-dot-slash (path traversal) value file paths are permitted. 3.12.0 · Feb 2022 · source · release history
  • Enables parsing of .netrc for HTTP-based values, overridable via the NETRC environment variable. 3.12.0 · Feb 2022 · source · release history

docs

  • Helm plugin that decrypts encrypted value files on the fly using sops or vals backends.

command line

  • --ignore-missing-values — Ignore missing value files (env: $HELM_SECRETS_IGNORE_MISSING_VALUES) v4.6.2 · Oct 2024 · command-line history
  • --evaluate-templates — Evaluate secret expressions inside helm template (only supported by vals backend) (env: $HELM_SECRETS_EVALUATE_TEMPLATES) v4.6.2 · Oct 2024 · command-line history
  • --evaluate-templates-decode-secrets — If --evaluate-templates is set, decode base64 values from secrets to evaluate them (env: $HELM_SECRETS_EVALUATE_TEMPLATES_DECODE_SECRETS) v4.6.2 · Oct 2024 · command-line history

example 8 total

  • Deploy a Helm chart where one of the encrypted secrets file is optional and might be missing in certain environments. helm-secrets install --values secrets/optional.yaml? mychart/ 4.2.0 · Nov 2022 · source
  • Disable all file-not-found error checks via environment variable for scripting or CI pipelines where missing files are acceptable. HELM_SECRETS_IGNORE_MISSING_VALUES=1 helm-secrets upgrade --values secrets/missing.yaml mychart/ 4.2.0 · Nov 2022 · source
  • Decrypt a file in-line (replacing its contents) using the new -i flag. helm secrets decrypt -i my_secret.yaml 4.0.0 · Sep 2022 · source
  • Encrypt a file and write the result directly to stdout for piping. helm secrets encrypt my_secret.yaml 4.0.0 · Sep 2022 · source
  • Decrypt secrets via plugin command helm secrets upgrade name . -f secrets.yaml
  • Use AWS Secrets Manager as backend helm secrets --backend vals template bitnami/mysql --name-template mysql \
Secret backend architecture shipped Allows secrets to be sourced from backends other than SOPS, enabling integration with various secret management systems. 11 releases · 5 other sources · first seen May 2020

previously: Secret driver architecture

Also counts toward: Command-line interface

release 11 total

  • Adds examples/backends/onepassword.sh as a new custom backend reference for the 1Password CLI 4.6.0 · Mar 2024 · source · release history
  • Adds vals support on Windows, enabling encrypted secret management via Vals expressions in Helm charts 3.14.0 · Jun 2022 · source · release history
  • Enables protocol handling on Windows requiring helm secrets patch windows command execution 3.14.0 · Jun 2022 · source · release history
  • Defaults now prefer gpg4win over other GPG installations; use SOPS_GPG_EXEC=gpg to restore previous GPG binary selection behavior 3.14.0 · Jun 2022 · source · release history
  • Adds age encryption support for the downloader plugin syntax 3.10.0 · Nov 2021 · source · release history
  • Adds a [vals](https://github.com/variantdev/vals) driver, enabling access to Vault, AWS SSM, GCP, sops, terraform states, and other file sources via the vals engine. 3.9.0 · Oct 2021 · source · release history

example

  • Permit a custom out-of-tree backend script to be selected via the backend! prefix in value file paths or Argo CD Application specs. export HELM_SECRETS_ALLOWED_BACKENDS=/usr/local/lib/my-backend.sh helm secrets upgrade myapp ./chart -f '/usr/local/lib/my-backend.sh!/path/to/secrets.yaml' v4.7.10 · Oct 2026 · source
  • Implementing a custom secret backend for Helm charts using 1Password CLI # 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… 4.6.0 · Mar 2024 · source
  • Apply Windows-specific protocol patches required for sops integration to work on Windows environments helm secrets patch windows helm secrets decrypt values.yaml.enc 3.14.0 · Jun 2022 · source
  • Configure sops-gpg to use a specific GPG executable when running on Windows export SOPS_GPG_EXEC=/c/Program Files (x86)/GNU/GnuPG/pub/gpg.exe helm secrets decrypt values.yaml.enc 3.14.0 · Jun 2022 · source
  • Pass custom environment variables or flags to the age or sops driver for advanced configuration. helm secrets install --driver-args '--env=AWS_REGION=us-east-1' my-release ./my-chart 3.5.0 · Feb 2021 · source
CLI output control and help verified Provides flags to suppress informational output, display the tool version, and show help text. 3 releases · 4 other sources · first seen Jun 2021

previously: CLI output control

release

  • Allows overriding the secret backend on a per-value-file basis 4.3.0 · Feb 2023 · source · release history
  • Adds HELM_SECRETS_ALLOWED_BACKENDS environment variable to restrict which backends can be used 4.3.0 · Feb 2023 · source · release history
  • Adds --version subcommand to print version information 3.8.0 · Jun 2021 · source · release history

command line

example

  • Check the installed version of helm-secrets in a script. helm-secrets --version 3.8.0 · Jun 2021 · source
Backend restriction via environment variable shipped Restricts which secret backends can be used by setting an allowed list via the HELM_SECRETS_ALLOWED_BACKENDS environment variable. 3 releases · 1 other source · first seen Feb 2023

release

  • Out-of-tree secret backends (file paths) referenced via the backend! prefix in value files, URLs, or literals are now blocked unless the path is listed in HELM_SECRETS_ALLOWED_BACKENDS. v4.7.10 · Oct 2026 · source · release history
  • Restricts out-of-tree secret backends (file paths) loaded via the backend! prefix of value files, URLs, or literals to only those explicitly listed in HELM_SECRETS_ALLOWED_BACKENDS; --backend and HELM_SECRETS_BACKEND are unaffected.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v4.7.10 · Oct 2026 · source · release history
  • Adds HELM_SECRETS_ALLOWED_BACKENDS environment variable to restrict which backends can be used 4.3.0 · Feb 2023 · source · release history

example

  • Restrict helm-secrets to only use sops and vault backends. export HELM_SECRETS_ALLOWED_BACKENDS='sops,vault' 4.3.0 · Feb 2023 · source
Decrypted file path output shipped Allows extraction of the path to decrypted secret files without processing their content, supporting custom naming prefixes and suffixes. 3 releases · 1 other source · first seen Jun 2021

Also counts toward: Command-line interface

release

  • Adds HELM_SECRETS_DEC_PREFIX environment variable for decrypted file naming in addition to existing suffix support 3.8.0 · Jun 2021 · source · release history
  • Adds --output-decrypt-file-path flag and HELM_SECRETS_OUTPUT_DECRYPTED_FILE_PATH environment variable to output only the path of decrypted files 3.8.0 · Jun 2021 · source · release history
  • The default value of HELM_SECRETS_DEC_SUFFIX changed from .yaml.dec to .dec, so files no longer have the .yaml extension stripped before appending the suffix. 3.8.0 · Jun 2021 · source · release history

example

  • Extract the path of a decrypted secrets file for piping into other commands without processing the file content itself. 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" 3.8.0 · Jun 2021 · source
File access control policies shipped Controls whether path traversal, absolute paths, symlinks, and missing files are permitted when loading secret value files. 2 releases · 1 other source · first seen Feb 2022

release

  • Adds HELM_SECRETS_VALUES_ALLOW_PATH_TRAVERSAL environment variable to control whether dot-dot-slash (path traversal) value file paths are permitted. 3.12.0 · Feb 2022 · source · release history
  • Adds HELM_SECRETS_VALUES_ALLOW_ABSOLUTE_PATH environment variable to control whether absolute value file paths are permitted. 3.12.0 · Feb 2022 · source · release history

example

  • Disable all file-not-found error checks via environment variable for scripting or CI pipelines where missing files are acceptable. HELM_SECRETS_IGNORE_MISSING_VALUES=1 helm-secrets upgrade --values secrets/missing.yaml mychart/ 4.2.0 · Nov 2022 · source
Template expression evaluation with vals shipped Evaluates template expressions in values files and Helm templates using the vals backend to resolve secret references. 1 release · 1 other source · first seen Feb 2023

release

  • Adds --evaluate-templates flag to enable evaluating secret references in Helm templates via the vals backend 4.3.0 · Feb 2023 · source · release history

example

  • Evaluate template expressions in values files using the vals backend. helm-secrets install --evaluate-templates ./my-chart 4.3.0 · Feb 2023 · source
Values file downloader extensions shipped Supports additional value file sources and protocols, such as .netrc for HTTP, literal strings for --set-file, and vault path injection. 2 releases · first seen Feb 2022

release

  • Adds secrets+literal:// downloader syntax to support inline secret references in --set-file 4.1.0 · Sep 2022 · source · release history
  • Enables parsing of .netrc for HTTP-based values, overridable via the NETRC environment variable. 3.12.0 · Feb 2022 · source · release history
Shell auto-completion shipped Provides configuration files for shell environments to enable command auto-completion for improved usability. 1 release · first seen Apr 2020

release

Helm command and plugin support shipped Extends functionality to cover all Helm subcommands and plugins, allowing the cyber tool to work with the full range of Helm operations. 1 release · first seen Apr 2020

release

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. 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 →

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…

Explore the full chart →

Releases

Show

15 entries

  1. March 20241
  2. February 20231
  3. November 20221
  4. September 20222
  5. June 20221
  6. February 20221
  7. November 20211
  8. October 20211
  9. June 20211
  10. March 20211
  11. February 20211
  12. May 20201
  13. April 20202
    Show

    15 entries

    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.

    1. Contributors 8 ±0 vs prior 12 months
    2. Maintainers 1 +0 joined · −0 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 95% of issues opened, last 12 months
    5. Median time to close < 1 day first maintainer reply 2.7 hours
    6. Open backlog 1 of 207 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 1
    3. Contributors / month 1
    4. Commits / month 4
    5. Stars 2,029
    Issue themes, last 12 months
    • 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.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →