The issue is resolved now, the repo is available again.<p>We have not received any response to the support case that we opened, but we assume that it was a false positive of some automatic algorithm.<p>As a consequence of this we're going to set up a mirror outside Github so that the work didn't stop if something like that happens again.<p>UPD: We received the official response explaining that this was a mistake. I must admit the whole situation was resolved really quickly, good job.
I see adblockers as another casualty of the end of the ZIRP era. Big Tech was benevolent when the money was free, but now that they have to tighten the waistband all the nice open-sourced add-ons (like 3rd party readers, ad-blockers, etc.) are all getting killed off (or at least they're trying to)
For those that haven't bothered clicking the link, they add:<p>> Github was struggling with "malware" comment spam lately and we added several filter rules that block this stuff. Maybe this is what triggered disabling the repo?<p>The comments so far immediately jumping to conspiracy speculation is depressing.<p>It's already back up.
And its because of situations like this, that I push to multiple foundries at the same time. Consolidation of resources is makes it only as secure as your control of maintaining them.