"also" is a strong word for a project this young. It was started in October 2025, does not have any issues (at all) and is completely vibe coded. Not starting a discussion about security & vibe coding now, but I wouldn't blindly recommend such a nascent project if compared to something mature like SOPS.
patabyte 3 days ago [-]
SOPS with Age is simple, and simple is good. I strongly recommend this approach.
sam_lowry_ 3 days ago [-]
SOPS is simple? You are kidding me. Pass from https://www.passwordstore.org/ fame is simple. SOPS is ultra-complicated for a security tool.
sevg 3 days ago [-]
I dunno, it seems mostly simple to me.
You have a .sops.yaml with some Age public keys, and then you run “sops secrets.yml” to create an encrypted file.
jmholla 3 days ago [-]
Can you explain what you find complicated about sops? I've used it with ease for the last two years, both personally and professionally.
ComputerGuru 3 days ago [-]
Possibly of interest to readers (but not directly competing) is securestore, our open-source, open-protocol, cross-language framework (cli tool + libraries) for securely storing secrets and programmatically retrieving them in production: https://neosmart.net/blog/securestore-open-secrets-format/
Looks like every other CLI manager I've ever seen. It says not ready for production use. What's different for this than the others?
Arrowmaster 2 days ago [-]
The latest release was June 2022 and the last non dependabot commit was March 2023, until new activity 4 days ago using AI. Why should anyone use this?
https://github.com/getsops/sops
You have a .sops.yaml with some Age public keys, and then you run “sops secrets.yml” to create an encrypted file.
donet version: https://github.com/neosmart/SecureStore
rust version: https://github.com/neosmart/securestore-rs
(This one is production ready)