pass vs eWallet

As it has both Git support and encrypts passwords to GPG-encrypted text files, it is really simple to access everywhere. You can either use a self-hosted or a personal cloud hosted Git repository. It is automatically being kept up-to-date. Clients for pretty much everything and a really active community. Even if you can't run a client you will still be able to access the password by decrypting them from the Git store.

And is basically just a bunch of GPG-encrypted files stored in a folder.

You are not forced to rely on any other service provider than yourself. Like saving them on a remote server as in the case of LastPass. You don't have to extend your trust (to LastPass or any other provider).

It has a Qt-based GUI, an Android and iOS app, a Firefox plugin, a Golang GUI app, an interactive CUI, a dmenu script, OS X integration, and also an Emacs package.

It doesn't use a database like, for example, KeePass and thus doesn't open all passwords at once. Just one at a time.

You can version-control the encrypted files using Git, which allows you to track all changes done.

Does one thing and does it well.

As GPG and Git are widely used, it relies on thoroughly tested and secure functionality.

You and your team can share a repo and different subtrees can be encrypted for different sets of GPG ids.

For example the plugin "pass-extension-tail" makes it possible to only display the non-password parts of a password file, like the username or the name of the service the password is needed for, and without showing the password.

It's very easy to understand what the program does, why it's doing it, and how it's secure.

It can sync the passwords between all used devices via DropBox.

Runs on Mac, Windows, iPhone and Android.

It can store the password safe on the local computer (not in the cloud).

Syncing from laptop/desktop to phone and tablet (without using the cloud features).