I have a feeling that someone may have already mentioned this but I read an article on Salting Passwords.
It may sound like overkill and paranoia, but imagine if the password stored in 1password was **NOT ** the exact and correct password.
Imagine the scenario....
1Password has say 16 salting algorithms. Say algorithm 1 adds a random character at the beginning and end of the password.
(i.e. "P455w0rd" becomes "#P455w0rd$").
This technically means that the password stored is NOT the correct password, and when autofill kicks in it calls upon the corresponding salting algorithm to paste the correct password, or whenever you go to edit it.
Should a cache or database ever be compromised (which should never happen) the password(s) stored are not the exact ones, giving the victim some peace of mind that the resting (stored) password is NOT the actual one.
(I'm sure you can argue that encryption already does this to some degree.)
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided