Unfortunately no, things are changing too fast, such a review would be outdated after a week.
However I can recommend one thing: don't use other faucet scripts. I've done small code review of them and I could find serious vulnerabilities in all of them. I'm talking about things that allow bypassing timer and in one case also captcha. I've reported most of them, but I wasn't satisfied in how my reports were handled. And I didn't even do a thorough testing, I just spent 5 minutes looking at code of each script. That doesn't include FaucetHUB.io, as they don't have their own script yet, but it does include elbandi's Minifaucet.
I'll give my random thoughts though:
1. I trust ePay.info the most, but that's only because it seems like there's more than one person behind it. It has highest "Bus factor" (https://en.wikipedia.org/wiki/Bus_factor). However I do have many issues with them. They seem to be adding features too fast and without proper testing since FaucetBOX.com announcement. I don't know how it looks now, but historically their support was terrible. From posts in their topic I suspect they're having problems with data consistency. They're here since 2 years (they claim they have 3 years of experience, but FaucetBOX.com is here for only 2 years and I'm pretty sure FaucetBOX.com launched before them) and didn't steal any coins, thats a good sign too.
2. FaucetSystem.com seems to be run by just one person (Bus factor = 1...), which is a problem. They also made many common mistakes when launching, I don't think it's being run by someone with experience in sysops. Just like with ePay.info, I suspect they're having problems with data consistency. They copied some things directly from FaucetBOX.com, which I don't like (the features for owners/users on main page). They're kinda lying about fees (they claim "No system fees for users" but they do have fees for users). They responded best for my vulnerability reports (both in site itself and script) though, which is a plus.
3. FaucetHub.io seems to be run by just one person (Bus factor = 1), which is a problem. However I must say they their launch was pretty professional and it seems their codebase is well tested. I didn't read anything that would suggest data inconsistencies. They require users to register on FaucetHub.io, which may or may not be a problem for you. Personally I would use FaucetHub.io if only mexicantarget's wasn't the only maintainer. EDIT: I've just read about this: https://bitcointalksearch.org/topic/m.17139016 . So it looks like they're pushing it a little bit too fast, just like ePay.info. That said, bugs huppen and they handled this correctly.
So my best advice is: diversify. Create faucets with each service. And as always, keep only as much coins in services as you need. Your coins are safe only if you, and only you, own the private key.