fair point, sorry for the implied impugn. no, I don't have any examples, but then, it's not likely we're going to hear of any - anyone affected is probably una

fair point, sorry for the implied impugn. no, I don't have any examples, but then, it's not likely we're going to hear of any - anyone affected is probably unaware (until now, maybe). I guess some might come out of the woodwork now. But again, Rubygems should have data on who downloaded this version of this gem, and so should be able to warn them, and even publish that data so we know not to visit their sites until they acknowledge and fix.