The way pass is built on top of gpg encrypted files in git is at the core of its robustness and simplicity. Creating an encrypted, version controlled store from scratch would be a not insignificant engineering effort, though something similar could be accomplished, for example, by putting the password store inside encfs.
If the mere existence of a credential is considered confidential information, a simple measure to bypass this flaw is to give it a meaningless randomly generated name such as "faithful_iceberg".
I hope this matures enough to compete with `pass`
History (undo/redo) is planned on passpie, probably using git as well.
Some ideas are: passpie history --list passpie history --undo XYZ passpie history --redo ABC passpie history --backend git --redo 123 passpie history --sync
You may like pass you may like passpie you may like both. :)
http://copr-fe.cloud.fedoraproject.org/coprs/rkuska/passpie/
