Lockenv
Shares rank 10 of 20 secrets managers by recommenders
Free, simple password-protected vault for storing secrets in git, reasonable for small teams, though access cannot be revoked once its password is known.
Free, simple password-protected vault for storing secrets in git, reasonable for small teams, though access cannot be revoked once its password is known.
8 people gave an opinion
- recommend it
- 8
- criticize it
- 0
- approval share
- 100%
Recommended in 1 of 13 months
- November 2025: not recommended
- December 2025: recommended
- January 2026: not recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 8 people recommend itNeeds 10 or more, not met.
- Nobody criticizes itNeeds 2 to 1 or better, met.
- Recommended in 1 of 13 monthsNeeds 4 or more, not met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
What people warn about
Each mark is one comment
Storing secrets in git feels wrong
“But storing secrets in the same git repository just seems off to me.”
Comment from 8 Dec 2025 in “Show HN: Lockenv – Simple encrypted secrets storage for Git” “Committing the vault to git gives me the heebie-jeebies.”
Comment from 8 Dec 2025 in “Show HN: Lockenv – Simple encrypted secrets storage for Git”
Other secrets managers people recommend
The four most recommended other secrets managers, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| OneCLI | 39 | 8 | 83% | 6 | — | Approved |
| SOPS | 28 | 5 | 85% | 10 | — | Approved |
| HashiCorp Vault | 26 | 10 | 72% | 10 | — | Approved |
| fnox | 20 | 4 | 83% | 9 | — | Approved |
| LockenvThis page | 8 | 0 | 100% | 1 | — | — |
What people said
7 of the 8 comments that mention it, newest first. Each links to the original comment.
“it strikes me as reasonable for 1-10 people teams (well, small businesses)”
“This looks nice, but I think I lean towards fnox”
“But storing secrets in the same git repository just seems off to me.”
“I like the idea of how easy this is. The (admittedly well-known) problem with lockenv is that you can't revoke access once a password is known.”
“Committing the vault to git gives me the heebie-jeebies.”
“A simple password-protected vault committed to git is a reasonable middle ground.”
“That looks amazing, thanks for sharing!”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.