search

k3integrations / hibp_check

Check passwords against API of compromised passwords
MIT License
0 stars 0 forks source link

Name consistency #3

Open TylerRick opened 5 years ago

TylerRick commented 5 years ago

Maybe call the gem pwnedpasswords to reflect that it's a client for api.pwnedpasswords.com?

More generally speaking, it would be nice to be consistent with whether we say the password has been "pwned" (as used in the upstream API, "used" (password_used), "breached", or "compromised". Which nomenclature is better, and why?