Lack of update can be explained many ways -- hens have produced eggs in the same form for a bit more than the decade since Dr. Perin published CodeRead...and Perin himself has had other fish to fry (take a gander at his CV: the notion of 'publish or perish' comes to mind). However, the 1998-2001 CodeRead discussion on his UNC pages identifies some shortcomings ("not working very well" to throw out a PM bete noir) which suggest that if he was using it last year, he's also likely to have improved it.

his CV, http://perrin.socsci.unc.edu/cv.pdf strongly suggests that CodeRead was originally developed while he was a candidate for his PhD. His "computer tips" page suggests that he produced some interesting Perl s/w within the past few years... and provides an email address.

The academic world being what it is, an inquiry directed to him might be fruitful.