Code Peer Review

You're a developer. And you've spent the last 2 years working with Java sockets in an uninteresting trading app. But you also happen to support anonymity - but have no idea how to get involved. Or you're a security researcher who's spent the last two months understanding the padding oracle backwards and forwards. Wouldn't it be nice to see a personalized RSS feed of cryptography, anonymity, and privacy projects containing the keywords "java.net.Socket" or "CBC Mode"? Then you could skim commits, and if something interesting came up, you may be able to lend your expertise. That's exactly what the Code Audit Feed is for.

Access-Control-Allow-Origin
SO_REUSEADDR
StartTLS
IllegalArgumentException

Record my search What's this?!

When you search, the Code Peer Review system will perform two types of searches: a tag search, and a full-text search. A tag search is very efficient, because it pre-tagged commits with tags overnight, tags like 'SHA1' or 'MD5' - things we predicted people would search for. A Full-Text search however is very, very slow - we're searching every commit's diff for your search terms. When this checkbox is checked, we record the search term in a database table, along with the time, and your IP address. We're going to use this data to find the terms that the most number of (unique) people are interested in, and create tags from them, so the searches will be faster in the future.

Honest to goodness, we're really interesting in using this data to make the service better - and that's not lip service. It's a long-standing bug. We'd appreciate your help.

Hall of Fame | Open Source