This is a bit different: I once wrote a static analyser in Java, that took apart another Java binary (yay for the ASM framework!), to build a call dependency tree and detect unreferenced methods (nothing statically calls them), then instrument those methods, so that we could catch sneaky code using reflection to run things...needless to say this was in a security context! Target Java binaries were typically 10-100MB JARs.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.