Bleeping Computer reports that executable files (.exe, .msi, etc.) were showing safe browsing errors in Google Chrome and Firefox for around 8 hours yesterday (25 January, 2017).

Although this only affected a small number of users, it would be pretty significant for the commercial and open source projects hosted there who use executable downloads.

Neither the Bleeping Computer article nor the GitHub blog explains what happened or how it was fixed. Since this had to be caused by something GitHub changed (and subsequently fixed) without requiring changes to the browser, explaining what happened would be helpful not only to impacted projects to assess how they handle downloads and their GitHub accounts in the future, but also others who might avoid similar issues. It would also help those considering hosting projects on GitHub decide how to proceed.

What do you think?  Comment here.