getsops/sops

Simple and flexible tool for managing secrets

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 32 minutes ago
Added to GitGenius on September 2nd, 2026
Created on August 13th, 2015
Open Issues & Pull Requests: 445 (+0)
GitHub issues: Enabled
Number of forks: 1,075
Total Stargazers: 23,048 (+0)
Total Subscribers: 122 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 18.6 hours
Mean response time: 110.0 days
90th percentile: 254.9 days
Tracked items: 285

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 5% of issues opened in the past year have been closed. Three people close 73% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 143
New in 7 days: 1
Closed in 7 days: 2
Avg open age: 1,114 days
Stale 30+ days: 127
Stale 90+ days: 108

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 4
Events in 7 days: 10

Top labels

  • area/keyservice (51)
  • enhancement (48)
  • bug (25)
  • keyservice/awskms (25)
  • area/CLI (18)
  • area/stores (9)
  • keyservice/age (9)
  • help wanted (8)

Detailed Description

SOPS is a command-line tool for managing encrypted secrets in configuration files. It encrypts and decrypts files in YAML, JSON, ENV, INI, and binary formats using cloud key management services or local encryption methods including AWS KMS, GCP KMS, Azure Key Vault, HuaweiCloud KMS, age, and PGP.

The tool solves the problem of storing sensitive data safely within version control systems and configuration repositories. Rather than requiring separate secret stores or manual encryption workflows, SOPS acts as an editor that transparently encrypts file contents while keeping the file structure readable. Users can edit encrypted files directly, and the tool handles encryption and decryption automatically. This approach allows secrets to live alongside configuration while remaining protected, and supports multiple encryption backends so teams can use their existing cloud infrastructure or local key management.

Teams managing infrastructure-as-code, Kubernetes deployments, or other configuration-heavy environments should consider SOPS when they need secrets integrated into their existing file-based workflows. It suits projects already using cloud key management services, as it integrates directly with those systems without requiring additional infrastructure. The tool is particularly valuable for teams that want encrypted secrets in version control without adopting a separate secrets management platform.

The project transitioned from Mozilla stewardship to a new group of maintainers under Cloud Native Computing Foundation sponsorship. Development shows active engagement with security practices, including a dedicated security advisory process for vulnerability reporting. The tool maintains broad compatibility across multiple encryption backends and file formats, indicating sustained effort to support diverse infrastructure environments and user preferences.