Remove version checks, add version-test.php
Update readme information on version compatibility
Fixed typo
Merge pull request #16 from pborreli/patch-1

Fixed typo
Add travis config file
Add travis hook
Fix travis version info
Update lib/password.php

Might as well check if the file exists and is readable instead of just checking if it exists and then suppressing errors trying to read it.
Merge pull request #19 from multiwebinc/patch-1

Update lib/password.php
Phalanger Fix

While mcrypt_create_iv and MCRYPT_DEV_URANDOM are both available in
Phalanger, when used it will generate a warning stating that the file
(/dev/urandom) cannot be read from.

The !$buffer_valid check would catch this, however there would still be
a warning generated every time a password was hashed.

In my opinion it is best to check if Phalanger is being used, and
prevent this path from executing in the first place.
Merge pull request #20 from leight/phalanger_fix

Phalanger Fix
White space changes
update version info in composer.json
Increase amount of randomness generated, to account for under-production with the base64 serialization identified by #11
Merge branch 'master' into v1.0
Increment version number
Reset raw length used as per #11
Update README.md

Update version information
Rely on checking for PASSWORD_DEFAULT, which should ALWAYS be available.

Since this is supposed to be forward compatible.  What happens if BCRYPT is pulled one day for any reason?  This would break forward compatibility, but relying on PASSWORD_DEFAULT should be safe.

I think another option would be:

if ( ! function_exists('password_hash') ) {
}
Merge pull request #26 from johncongdon/master

Fix for potential forward compatibility break.