A · leads
sops
95.8
23,737 stars · MPL-2.0
DevOps
sops leads by 1.6 · narrow
A · leads
95.8
23,737 stars · MPL-2.0
B
94.2
17,154 stars · MPL-2.0
sops versus wtf is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Go. The composite score is 95.8 for sops and 94.2 for wtf.
sops has 23,737 GitHub stars to wtf's 17,154, a gap of 6,583 (1.38×). Forks are 1,119 for sops and 866 for wtf. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 100 versus 96.
Push history: sops was last pushed on 16 November 2026 (1 day ago), and wtf was last pushed on 14 November 2026 (3 days ago). Open issues stand at 473 for sops (0.020 per star) and 107 for wtf (0.006 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Both sops and wtf are listed as MPL-2.0. A weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. The license score is therefore level at 78 versus 78, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In DevOps, both sops (23,737 stars) and wtf (17,154 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: sops is open source, wtf is open source.
sops is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 4 points (100 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
sops finishes ahead at 95.8 against wtf at 94.2, a 1.6 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | sops | wtf |
|---|---|---|
| GitHub stars | 23,737 | 17,154 |
| Forks | 1,119 | 866 |
| Open issues | 473 | 107 |
| Adoption | 100 | 97 |
| Activity | 100 | 100 |
| Community | 100 | 96 |
| Issue health | 84 | 84 |
| License | 78 | 78 |
| Self-hosting | 100 | 100 |
| Composite | 95.8 | 94.2 |
Simple and flexible tool for managing secrets
The personal information dashboard for your terminal
sops has more GitHub stars: 23,737 versus 17,154 for wtf. The gap is 6,583 stars.
sops was pushed more recently: 16 November 2026 versus 14 November 2026 for wtf. That is 2 days apart.
Yes. This catalog marks both sops and wtf as self-hostable. Confirm each project's deploy docs before you plan a migration.
sops is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. wtf is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
sops scores 95.8 and wtf scores 94.2. This page calls that a narrow lead for sops.