Looks good. Hopefully someone will write something to automagically search for unintentionally exposed sensitive files and notify the repo owner - when the "human" version of Code Search came out, a lot of private keys and other such things were discovered.
Re:Code Search API
by eli on Sunday July 21, 2013 @02:32PM
(#6079719)
I'm sure malicious bots do try to mass message repository owners through Github. It's called spam and every platform over a certain size experiences it. I expect Github already has measures in place to block it.
Re:Code Search API
by eli on Friday July 19, 2013 @01:44PM
(#6071691)
When I searched Github it seemed like most of the supposedly leaked passwords were actually examples or placeholders and not a problem.
It would be one thing if Github ran (or at least sanctioned) a feature that warned you of possible security problems, but I don't think I'd like potentially multiple, poorly-coded bots going around messaging repo owners.
Re:Code Search API
by bowmessage on Friday July 19, 2013 @12:53PM
(#6071319)
I suppose there are already templating abilities written into the popular code editors, but something that maybe takes the first two or three lines of what you've written (maybe a common JDBC connection style block) and identifies it as such. I'm not sure if it would be incredibly useful but it would be interesting to see what came of it.
Re:Code Search API
by archivator on Friday July 19, 2013 @01:57PM
(#6071767)
To me, Github search is kinda useless. When I search for anything Android related (i.e. usage search for some framework type), I get a billion copies of the main Android source. The signal to noise ratio is almost 0..
It would be one thing if Github ran (or at least sanctioned) a feature that warned you of possible security problems, but I don't think I'd like potentially multiple, poorly-coded bots going around messaging repo owners.
There are already really good ways to do that which don't involve making connections to remote servers.
My biggest issue with github search is it still has issues with searches like $i++ as it will not match something like for(i=0;i++;i<100) which is occasionally frustrating. For reference a comparison http://searchcode.com/?q=i%2B%2B vs https://github.com/search?q=i%2B%2B&type=Code&ref=searchresu...