Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | SOPS | zoxide | Bruno |
|---|---|---|---|
| Platforms | Universal | Universal | Universal |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MPL-2.0 | MIT | MIT |
| Stars | 23593 | 40431 | 48002 |
| Last activity | October 27, 2026 | October 24, 2026 | October 30, 2026 |
| Install complexity | MODERATE | — | EASY |
| Category | Security, DevOps | Workflow | Testing, Git |
| Best use | Ideal for a developer or small platform team that wants encrypted configuration beside code with readable Git diffs. Use it for YAML, JSON, ENV and INI files and tightly scoped CI or runtime access. It is not a replacement for dynamic secret issuance or source-system credential rotation. | For developers switching among many directories in an interactive terminal. It learns from visited paths and helps you return; use explicit paths for scripts and deployments that require a fixed destination. | Ideal for a solo developer or small team that wants API collections and tests beside the code with Git review. Use it for repeatable REST, GraphQL, gRPC, and WebSocket checks—not live cloud collaboration or load testing. |