<commit_before>Awesome-Password-PHP
====================

Github home of Awesome Password Hashing Utility for PHP

![Y U NO HASH PASSWORD?](http://i.imgur.com/mucsL.jpg)<commit_msg>Updating documentation<commit_after># Awesome Password

## A Password Hashing Utility for PHP

I constantly read stories about X or Y site's users tables getting hacked and the passwords being stored in plain text.

![Y U NO HASH PASSWORD?](http://i.imgur.com/mucsL.jpg)

Perhaps you're using unsalted MD5 or SHA1, but it's practically the same depending on the password. For example, take the password of "awesome" or "password": 

MD5(awesome): [be121740bf988b2225a313fa1f107ca1](http://www.md5-lookup.com/index.php?q=be121740bf988b2225a313fa1f107ca1)
SHA1(awesome): [03d67c263c27a453ef65b29e30334727333ccbcd](http://www.sha1-lookup.com/index.php?q=03d67c263c27a453ef65b29e30334727333ccbcd)

MD5(password): [<PASSWORD>](http://www.md5-lookup.com/index.php?q=5f4dcc3b5aa765d61d8327deb882cf99)
SHA1(password): [<PASSWORD>](http://www.sha1-lookup.com/index.php?q=5baa61e4c9b93f3f0682250b6cf8331b7ee68fd8)

Still think that your "hashed" passwords are safe?


{'fraction_non_alphanumeric': 0.1265377855887522, 'fraction_numerical': 0.13005272407732865, 'mean_word_length': 6.644295302013423, 'pattern_counts': {'":': 1, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 4, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3326648', 'n_tokens_mistral': 519, 'n_tokens_neox': 423, 'n_words': 91}