I published a tiny script that makes mass grabbing of files from Github easy (<a href="https:&#x2F;&#x2F;github.com&#x2F;cortesi&#x2F;ghrabber" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;cortesi&#x2F;ghrabber</a>),  and wrote about some of the interesting things one could find with it. For example, there are hundreds of complete browser profiles on Github, including cookies, browsing history, etc:<p><a href="http:&#x2F;&#x2F;corte.si&#x2F;posts&#x2F;hacks&#x2F;github-browserstate" rel="nofollow">http:&#x2F;&#x2F;corte.si&#x2F;posts&#x2F;hacks&#x2F;github-browserstate</a><p>I&#x27;ve also written about some less security critical things, like shell history (<a href="http:&#x2F;&#x2F;corte.si&#x2F;posts&#x2F;hacks&#x2F;github-shhistory" rel="nofollow">http:&#x2F;&#x2F;corte.si&#x2F;posts&#x2F;hacks&#x2F;github-shhistory</a>) custom aspell dictionaries (<a href="http:&#x2F;&#x2F;corte.si&#x2F;posts&#x2F;hacks&#x2F;github-spellingdicts" rel="nofollow">http:&#x2F;&#x2F;corte.si&#x2F;posts&#x2F;hacks&#x2F;github-spellingdicts</a>), and seeing if one could come up with ideas for command-line tools by looking at common pipe chains from shell histories (<a href="http:&#x2F;&#x2F;corte.si&#x2F;posts&#x2F;hacks&#x2F;github-pipechains" rel="nofollow">http:&#x2F;&#x2F;corte.si&#x2F;posts&#x2F;hacks&#x2F;github-pipechains</a>).<p>I&#x27;ve held back on some of the more damaging leaks that are easy to exploit en-masse with a tool like this (some are discussed in the linked post, but there are many more), because there&#x27;s just no way to counteract this effectively without co-operation from Github. I&#x27;ve reported this to Github with concrete suggestions for improving things, but have never received a response.