PAGES
← all tools
◆ Secrets Detection & Management

SOPS

v3.13.3 open-source

Encrypted file editor supporting YAML, JSON, ENV, INI, and BINARY formats with AWS KMSAWS KMSAWS Key Management Service, Amazon's hosted service for creating and controlling cryptographic keys, giving cyber tools a durable, audited place to encrypt data without managing raw key material themselves., GCP KMSKMSA managed service that creates, stores, rotates and controls access to encryption keys, usually backed by HSMs. Applications ask it to encrypt or decrypt rather than holding keys themselves., Azure Key Vault, age, and PGP.

Summary

SOPS is an open-source command-line editor for encrypted files, free to use under the Mozilla Public License, that reads and writes YAML, JSON, ENV, INI and binary formats while encrypting values with AWS KMS, GCP KMS, Azure Key Vault, HuaweiCloud KMS, age or PGP. It is aimed at platform engineers and application developers who need secrets committed alongside config in git without storing them in plaintext, fitting naturally 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. workflows where encrypted files are decrypted at deploy time. Rather than compare itself to a named alternative, its README frames it as the successor to years of managing PGP-encrypted files by hand. Started at Mozilla in 2015 and now a CNCF Sandbox project, it has 216 contributors, over 250 commits and dozens of releases in the past year, with its latest release 29 days ago.

Encrypted file editor supporting YAML, JSON, ENV, INI, and BINARY formats with AWS KMS, GCP KMS, Azure Key Vault, age, and PGP.

How SOPS helps

Which secrets in this file are still plaintext and need encrypting before I commit?

reads the document's structure and encrypts only the values, leaving keys and structure intact so a diff against the last commit shows exactly what changed

Can more than one teammate decrypt this file without sharing a single private key?

encrypts each value's data key separately against every recipient's KMS or PGP/age key listed for the file, so any one of them can decrypt with their own key

Who is actually able to read this secret if the repo leaks?

lists the recipients configured for a given path, since each file only decrypts for the AWS KMS, GCP KMS, Azure Key Vault, HuaweiCloud KMS, age or PGP identities it was encrypted against

Did someone edit the decrypted values in this file, or just reformat it?

recomputes and checks a MAC over the values at decrypt time, so edits made outside the tool or tampering with content show up as a verification failure

How do I rotate keys after someone leaves the team without re-encrypting every secret by hand?

re-wraps the existing data key for the new set of recipients across a whole file or directory tree in one pass, without touching the encrypted values themselves

all 32 features, with the evidence for each →

Languages

Not documented

Features

32 capabilities · 1 backed by code, an API document or a real run

Built from SOPS'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 SOPS offers you

  • Command-line interface12
  • Offline mode1
  • Plugin API support1
  • Plugin system1
  • S3 export1
  • User-defined detection rules1
All capabilities 32 capabilities
HuaweiCloud KMS encryption key management verified Allows users to specify, add, and remove HuaweiCloud KMS keys (identified by region and UUID) as master keys for encrypting and managing access to files. 27 releases · 8 other sources · first seen Apr 2019

Also counts toward: Command-line interface

release 27 total

  • Allows multiple space-separated Age private keys in the SOPS_AGE_KEY environment variable, enabling multi-key Age workflows without key files. v3.13.0 · May 2026 · source · release history
  • Preserves YAML inline comments through encrypt/edit roundtrips, preventing comment loss on re-encryption. v3.13.0 · May 2026 · source · release history
  • Adds allowlist support for acceptable HashiCorp Vault URLs, restricting which Vault instances SOPS will contact. v3.13.0 · May 2026 · source · release history
  • Adds SOPS_GCP_KMS_ENDPOINT and SOPS_GCP_KMS_UNIVERSE_DOMAIN environment variables for pointing SOPS at custom or sovereign GCP KMS endpoints. v3.13.0 · May 2026 · source · release history
  • The --indent global flag value is now correctly propagated to store configs, giving consistent indentation across output formats. v3.13.0 · May 2026 · source · release history
  • Adds --value-stdin option to sops set to supply a replacement value from standard input. v3.11.0 · Sep 2025 · source · release history

command line

  • --hckms — comma separated list of HuaweiCloud KMS key IDs (format: region:key-uuid) v3.12.0 · Feb 2026 · command-line history
  • --add-hckms — add the provided comma-separated list of HuaweiCloud KMS key IDs (format: region:key-uuid) to the list of master keys on the given file v3.12.0 · Feb 2026 · command-line history
  • --rm-hckms — remove the provided comma-separated list of HuaweiCloud KMS key IDs (format: region:key-uuid) from the list of master keys on the given file v3.12.0 · Feb 2026 · command-line history

example

  • Point SOPS at a private or sovereign GCP KMS endpoint (e.g., a VPC-SC-restricted or gov-cloud endpoint) without modifying your .sops.yaml. export SOPS_GCP_KMS_ENDPOINT=https://cloudkms.myorg.example.com export SOPS_GCP_KMS_UNIVERSE_DOMAIN=myorg.example.com sops --encrypt --gcp-kms… v3.13.0 · May 2026 · source
  • Supply multiple Age identities in a single env var for environments where you can't use a key file (e.g., CI with several recipient keys). export SOPS_AGE_KEY="AGE-SECRET-KEY-1ABC... AGE-SECRET-KEY-1DEF..." sops --decrypt secrets.enc.yaml v3.13.0 · May 2026 · source
  • Pipe a secret value into sops set from another command, avoiding shell history exposure. vault kv get -field=password secret/db | sops set secrets.yaml '["database"]["password"]' --value-stdin v3.11.0 · Sep 2025 · source
  • Retrieve the age private key from a secrets manager at runtime instead of storing it on disk. SOPS_AGE_KEY_CMD='aws secretsmanager get-secret-value --secret-id my-age-key --query SecretString --output text' sops --decrypt secrets.enc.yaml v3.10.0 · Mar 2025 · source
  • Provide an age key directly via environment variable instead of using a sops-age-key file. SOPS_AGE_KEY='age1...' sops encrypt --age <public_key> myfile.yaml v3.7.2 · Mar 2022 · source
Age plugin integration shipped Adds support for age plugins, enabling external age key management plugins and runtime retrieval of keys from secrets managers. 2 releases · 3 other sources · first seen Oct 2017

Also counts toward: Plugin API support, Plugin system

release

  • Adds age plugin support, enabling external age key management plugins v3.10.0 · Mar 2025 · source · release history
  • Adds support for age as a key management service (KMS), enabling encryption/decryption with age public keys alongside existing providers v3.7.0 · Mar 2021 · source · release history

example

  • Retrieve the age private key from a secrets manager at runtime instead of storing it on disk. SOPS_AGE_KEY_CMD='aws secretsmanager get-secret-value --secret-id my-age-key --query SecretString --output text' sops --decrypt secrets.enc.yaml v3.10.0 · Mar 2025 · source
  • Encrypt a secrets file using an age public key instead of GPG or AWS KMS. sops --age age1ql3z7hjy54pw3hyww5ayyfg7zqg67ek58rpd3ysw56lklxt9hwsqf30v8p --encrypt config.yaml > config.enc.yaml v3.7.0 · Mar 2021 · source
  • Run the keyservice daemon to allow other SOPS instances to access your local GPG agent via a socket. sops keyservice /tmp/sops-keys.sock 3.0.0 · Oct 2017 · source
exec-file local path enforcement shipped Hardens the `sops exec-file` subcommand by rejecting non-local paths in `--filename`, preventing path traversal misuse. 3 releases · 1 other source · first seen Oct 2017

Also counts toward: Command-line interface

release

  • The sops exec-file subcommand now rejects non-local paths in --filename, hardening against path traversal misuse. v3.13.0 · May 2026 · source · release history
  • Adds the sops exec-file command to write SOPS secrets to a temporary file and execute a command v3.5.0 · Nov 2019 · source · release history
  • Adds sops keyservice subcommand to forward access to a local master key over a socket 3.0.0 · Oct 2017 · source · release history

example

  • Write decrypted secrets to a temporary file and execute a program that reads from that path. sops exec-file 'path/to/secrets.yaml' 'myapp --config /tmp/sops-xxxxx.json' v3.5.0 · Nov 2019 · source
Configuration auditing shipped Provides capabilities to scan the current directory for potential issues with SOPS configuration files. 3 releases · 1 other source · first seen May 2018

Also counts toward: Command-line interface, Offline mode

release

  • Adds --disable-version-check to allow offline --version checks 3.8.0 · Sep 2023 · source · release history
  • Switches --version network requests from public DNS to GitHub endpoints 3.8.0 · Sep 2023 · source · release history
  • Adds initial SOPS workspace auditing support (WIP) 3.0.5 · May 2018 · source · release history

example

  • Check version in an air-gapped environment without triggering network calls. sops --disable-version-check --version 3.8.0 · Sep 2023 · source
exec-file subcommand shipped Writes decrypted secrets to a temporary file and executes a user-specified program, allowing applications to read secrets from disk. 3 releases · 1 other source · first seen Nov 2019

Also counts toward: Command-line interface

release

  • Passes the filename to exec-file commands via the SOPS_FILEPATH environment variable, allowing dynamic configuration based on target file v3.7.0 · Mar 2021 · source · release history
  • Support --input-type for exec-file to specify the input format. v3.6.1 · Sep 2020 · source · release history
  • Adds the sops exec-file command to write SOPS secrets to a temporary file and execute a command v3.5.0 · Nov 2019 · source · release history

example

  • Write decrypted secrets to a temporary file and execute a program that reads from that path. sops exec-file 'path/to/secrets.yaml' 'myapp --config /tmp/sops-xxxxx.json' v3.5.0 · Nov 2019 · source
GCP KMS sovereign/custom endpoint support shipped Allows pointing the cyber tool at private, custom, or sovereign GCP KMS endpoints (such as VPC-SC-restricted or gov-cloud endpoints) via environment variables. 2 releases · 1 other source · first seen Oct 2017

release

  • Adds SOPS_GCP_KMS_ENDPOINT and SOPS_GCP_KMS_UNIVERSE_DOMAIN environment variables for pointing SOPS at custom or sovereign GCP KMS endpoints. v3.13.0 · May 2026 · source · release history
  • Adds Google Compute Platform KMS as a supported encryption provider 3.0.0 · Oct 2017 · source · release history

example

  • Point SOPS at a private or sovereign GCP KMS endpoint (e.g., a VPC-SC-restricted or gov-cloud endpoint) without modifying your .sops.yaml. export SOPS_GCP_KMS_ENDPOINT=https://cloudkms.myorg.example.com export SOPS_GCP_KMS_UNIVERSE_DOMAIN=myorg.example.com sops --encrypt --gcp-kms… v3.13.0 · May 2026 · source
HashiCorp Vault allowlist support shipped Restricts which HashiCorp Vault URLs the cyber tooling will contact, allowing operators to whitelist only specific or trusted Vault instances. 2 releases · 1 other source · first seen Apr 2019

release

  • Adds allowlist support for acceptable HashiCorp Vault URLs, restricting which Vault instances SOPS will contact. v3.13.0 · May 2026 · source · release history
  • Added a way to specify the GPG key server to use through the SOPS_GPG_KEYSERVER environment variable 3.3.0 · Apr 2019 · source · release history

example

  • Specify the GPG key server via environment variable for signing/decrypting SOPS_GPG_KEYSERVER=keyserver.ubuntu.com sops -d secrets.yaml.gpg 3.3.0 · Apr 2019 · source
Native list key configuration shipped Allows configuring keys directly using native list syntax in the `.sops.yaml` configuration file, replacing previous complex nested structures. 2 releases · 1 other source · first seen Sep 2023

Also counts toward: Command-line interface

release

  • Supports native list syntax for configuring keys in .sops.yaml. v3.11.0 · Sep 2025 · source · release history
  • Adds --input-type flag to the updatekeys subcommand 3.8.0 · Sep 2023 · source · release history

example

  • Force the input format when updating keys for a non-default file type like JSON. sops --input-type json updatekeys sops.json 3.8.0 · Sep 2023 · source
GCP Oauth access token authentication shipped Supports `GOOGLE_OAUTH_ACCESS_TOKEN` for Google Cloud Platform authentication, allowing use of pre-obtained OAuth tokens. 2 releases · 1 other source · first seen Apr 2019

release

  • Supports GOOGLE_OAUTH_ACCESS_TOKEN for Google Cloud Platform authentication v3.10.0 · Mar 2025 · source · release history
  • Added a way to specify the GPG key server to use through the SOPS_GPG_KEYSERVER environment variable 3.3.0 · Apr 2019 · source · release history

example

  • Specify the GPG key server via environment variable for signing/decrypting SOPS_GPG_KEYSERVER=keyserver.ubuntu.com sops -d secrets.yaml.gpg 3.3.0 · Apr 2019 · source
Secrets publishing to remote storage shipped Pushes encrypted secrets to external storage services like S3, GCS, or Hashicorp Vault. 3 releases · first seen Sep 2019

Also counts toward: Command-line interface, S3 export

release

  • sops publish now supports --omit-extensions flag for omitting the extension in the destination path v3.6.0 · Jul 2020 · source · release history
  • sops publish now supports --recursive flag for publishing all files in a directory v3.6.0 · Jul 2020 · source · release history
  • Adds the sops publish subcommand to push encrypted secrets to S3, GCS, or Hashicorp Vault 3.4.0 · Sep 2019 · source · release history
INI file support shipped Enables the cyber tool to process and encrypt/decrypt files in the INI format. 2 releases · first seen Apr 2019

release

Multi-key Age environment variable support shipped Allows multiple space-separated Age private keys in the `SOPS_AGE_KEY` environment variable, enabling multi-key Age workflows without key files. 1 release · 1 other source · first seen May 2026

release

  • Allows multiple space-separated Age private keys in the SOPS_AGE_KEY environment variable, enabling multi-key Age workflows without key files. v3.13.0 · May 2026 · source · release history

example

  • Supply multiple Age identities in a single env var for environments where you can't use a key file (e.g., CI with several recipient keys). export SOPS_AGE_KEY="AGE-SECRET-KEY-1ABC... AGE-SECRET-KEY-1DEF..." sops --decrypt secrets.enc.yaml v3.13.0 · May 2026 · source
YAML inline comment preservation shipped Preserves YAML inline comments through encrypt and edit roundtrips, preventing comment loss when re-encrypting files. 2 releases · first seen Apr 2019

release

  • Preserves YAML inline comments through encrypt/edit roundtrips, preventing comment loss on re-encryption. v3.13.0 · May 2026 · source · release history
  • Adds multi-document support for YAML files 3.3.0 · Apr 2019 · source · release history
sops set stdin value input shipped Adds a `--value-stdin` option to the `sops set` subcommand to supply a replacement value from standard input, avoiding shell history exposure. 1 release · 1 other source · first seen Sep 2025

Also counts toward: Command-line interface

release

  • Adds --value-stdin option to sops set to supply a replacement value from standard input. v3.11.0 · Sep 2025 · source · release history

example

  • Pipe a secret value into sops set from another command, avoiding shell history exposure. vault kv get -field=password secret/db | sops set secrets.yaml '["database"]["password"]' --value-stdin v3.11.0 · Sep 2025 · source
Age identity passphrase support shipped Enables the use of age identities protected with a passphrase, expanding compatibility with various key storage formats. 2 releases · first seen Oct 2017

release

  • Adds support for age identities protected with a passphrase v3.10.0 · Mar 2025 · source · release history
  • Versions in SOPS 1.X files are re-encoded as strings, breaking backward compatibility with older SOPS versions 3.0.0 · Oct 2017 · source · release history
INI duplicate section support shipped Adds the ability to handle and encrypt/decrypt files with duplicate sections in the INI format store. 2 releases · first seen Apr 2019

release

SSH key support for age encryption shipped Adds the ability to use SSH keys as identities for age encryption. 2 releases · first seen Apr 2019

release

  • Adds SSH key support for age encryption v3.10.0 · Mar 2025 · source · release history
  • Enables comment lines in .env files (lines starting with #) to be preserved during encryption/decryption 3.3.0 · Apr 2019 · source · release history
Path-based encryption configuration shipped Allows users to define which files to encrypt or skip based on path patterns using encrypted_suffix, unencrypted_suffix, and encrypted_regex rules. 2 releases · first seen Sep 2019

Also counts toward: Command-line interface, User-defined detection rules

release

  • Add support for --unencrypted-regex to exclude secrets from encryption. v3.6.1 · Sep 2020 · source · release history
  • Adds the encrypted_regex option to the sops config file for targeted encryption 3.4.0 · Sep 2019 · source · release history
Binary file format support shipped Enables the cyber tool to process binary files by allowing explicit specification of input and output types via command-line flags. 2 releases · first seen Apr 2018

Also counts toward: Command-line interface

release

  • Adds support for encrypting data through the use of Hashicorp Vault v3.6.0 · Jul 2020 · source · release history
  • Adds flags to force binary input (--input-type=binary) and output (--output-type=binary) formats 3.0.3 · Apr 2018 · source · release history
exec-env subcommand shipped Injects decrypted secrets as environment variables for a single command execution without writing them to disk. 1 release · 1 other source · first seen Nov 2019

Also counts toward: Command-line interface

release

  • Adds the sops exec-env command to inject SOPS secrets as environment variables for a single command execution v3.5.0 · Nov 2019 · source · release history

example

  • Run a command with decrypted secrets available as environment variables without writing them to disk. sops exec-env 'path/to/secrets.yaml' 'echo $MY_SECRET_KEY' v3.5.0 · Nov 2019 · source
AWS KMS alias reference support shipped Allows referencing AWS KMS keys by their alias in addition to raw ARN for encryption and decryption. 1 release · 1 other source · first seen Apr 2019

release

example

  • Use AWS CLI profile prod and KMS alias for encryption instead of raw ARN sops -e --aws-kms-alias 'alias/my-key' --aws-profile prod secrets.json 3.3.0 · Apr 2019 · source
Path-based encryption suffix configuration shipped Allows users to define which files to encrypt or skip based on path patterns using encrypted_suffix and unencrypted_suffix rules in the configuration file. 2 releases · first seen Apr 2018

release

  • Allows specifying unencrypted_suffix and encrypted_suffix rules in .sops.yaml 3.0.3 · Apr 2018 · source · release history
  • New encrypted_suffix option (mirror of existing unencrypted_suffix) 3.0.3 · Apr 2018 · source · release history
Shamir secret sharing support shipped Configures and manages Shamir secret sharing by requiring multiple keys from different providers to decrypt a file. 1 release · 1 other source · first seen Oct 2017

Also counts toward: Command-line interface

release

  • Adds sops groups subcommand to configure Shamir secret sharing using the .sops.yaml config file 3.0.0 · Oct 2017 · source · release history

example

  • Configure a group requiring both a PGP key and an AWS KMS key to decrypt a file using Shamir secret sharing. sops groups --add 'group_name: pgp/0xABC123, aws_kms/arn:aws:kms:us-east-1:123456789012:key/12345678-1234-1234-1234-123456789012' 3.0.0 · Oct 2017 · source
Consistent indentation propagation shipped Correctly propagates the `--indent` global flag value to all store configs, ensuring consistent indentation across different output formats. 1 release · first seen May 2026

release

  • The --indent global flag value is now correctly propagated to store configs, giving consistent indentation across output formats. v3.13.0 · May 2026 · source · release history
Azure Key Vault latest version default shipped Automatically uses the latest key version in Azure Key Vault when no specific version is provided, simplifying key management. 1 release · first seen Sep 2025

release

  • Azure Key Vault: omitting a key version now automatically uses the latest key version. v3.11.0 · Sep 2025 · source · release history
Non-string dotenv/exec-env value support shipped Allows non-complex non-string values (such as integers and booleans) in dotenv and exec-env stores. 1 release · first seen Sep 2025

release

  • Allows non-complex non-string values (integers, booleans, etc.) in dotenv and exec-env stores. v3.11.0 · Sep 2025 · source · release history
sops set file value input shipped Adds a `--value-file` option to the `sops set` subcommand to supply a replacement value from a file instead of inline. 1 release · first seen Sep 2025

Also counts toward: Command-line interface

release

  • Adds --value-file option to sops set to supply a replacement value from a file instead of inline. v3.11.0 · Sep 2025 · source · release history
Time type encryption support shipped Supports encrypting and decrypting `time.Time` objects in YAML and JSON files. 1 release · first seen Mar 2025

release

  • Supports encryption and decryption of time.Time objects in YAML/JSON files v3.10.0 · Mar 2025 · source · release history
Azure Key Vault configuration support shipped Adds the ability to configure Azure Key Vault as a master key provider via the sops config file. 1 release · first seen Sep 2019

release

  • Adds Azure Keyvault configuration support to the sops config file 3.4.0 · Sep 2019 · source · release history
YAML multi-document support shipped Supports processing multiple YAML documents within a single file during encryption and decryption. 1 release · first seen Apr 2019

release

Nested data structure value setting shipped Extends the set functionality to modify values within nested data structures using dot-notation keys. 1 release · first seen Apr 2018

release

  • --set flag now works with nested data structures (e.g., .a.b=c) 3.0.3 · Apr 2018 · source · release history
Comment encryption support shipped Enables the encryption of comments within supported file formats by default. 1 release · first seen Oct 2017

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 SOPS, 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 SOPS 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 →

Website history

getsops.io, every change

Mozilla's home page and 3 more pages as they looked each month from January 2025 to October 2026: 13 renders, 0 changes of tagline or palette. Step through them, play them, or put any two months side by side.

Website history is included with Researcher and Business.

See plans →

Releases

Show

18 entries

  1. July 20261
  2. May 20261
  3. September 20251
  4. March 20251
  5. October 20241
  6. June 20241
  7. September 20231
  8. May 20221
  9. March 20221
  10. March 20211
  11. September 20201
  12. July 20201
  13. November 20191
  14. September 20191
  15. April 20191
  16. May 20181
  17. April 20181
  18. October 20171
    Show

    18 entries

    Project health

    Issue, contributor and maintainer activity in mozilla/sops, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 25 −4 vs prior 12 months
    2. Maintainers 2 +1 joined · −1 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed not measured of issues opened, last 12 months
    5. Median time to close not measured issues closed, last 12 months
    6. Open backlog not measured open issues today
    1. Issues opened / month not measured
    2. Open backlog not measured
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 23,137
    Issue themes, last 12 months not measured

    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 →