Earlier quoted context omitted.
> Wow! Building this in 7 weeks is an incredible feat. Here is an analysis of Tooljet development in the last 90 days https://public-001.gitsense.com/insights/github/repos?q=wind... I also did one for budibase as well https://public-001.gitsense.com/insights/github/repos?q=wind... Disclaimer: I'm the creator of GitSense
Why no LoC included, it seems most useful metric. Also bugs filed/fixed would be helpful too. Thank you for your effort!
LoC invokes PTSD for many developers and I honestly want to do it right, which will take a bit effort and thinking on my part. For example, when providing LoC, I want to be able to break it down into useful information like (isolated code, used here and there) and so forth.
I want LoC to help us understand the significance of going from one revision to another, so that LoC can be used to help us drive actionable insights.
Edit: Just realized I never addressed your other points which is I do want to index and provide insights into everything in the software development lifecycle, it's just that I'm bound by resource constraints right now.