Thanks, glad you like it. We're putting this out there to figure out what kinds of info developers would like about how tools are actually used by others. Let u

Thanks, glad you like it. We're putting this out there to figure out what kinds of info developers would like about how tools are actually used by others. Let us know via the Contact tab there if you have some questions or think you have some problems data like this could solve. Binary code is difficult to analyze. Typically, it's taken a skilled person with a disassembler and knowledge of the software in use to figure out the kinds of things we're showing here. We've built a custom similarity engine that does this on a large scale. It takes each binary apart into snippets, then looks up snippets that are close to those representative features, and finally combines the results to return a list of what code was found in that binary. Attach that to a firehose that is delivering thousands of apps per day, and you've got SourceDNA. It was extremely challenging to develop, and we're proud of what we've built. We've found that most developers are interested in finding out what others are doing, best practices, etc. I personally find it more enjoyable to apply machine learning to track code instead of users, which is the more common place big data is applied.