Is this fixed?
It's in the article (and the comments here) -- yes, it was remediated within 3 hours of being reported back in January by GitHub.