I've studied software metrics for quite sometime and they are widely despised by developers, because they are
a) not useful for developers
b) never put effort into context that can be discussed, vetted and refined.
What I'm trying to do is fix the stigma associated with software metrics, by focusing on how they can be used by developers. For example, code churn metrics can be used in a positive way for developers as the following example shows:
Without looking a single line of code, you can estimate the impact each commit will have, which can be useful for domain experts, team leaders, etc.
I'm hoping to have a version of the product that people can install via docker or on bare metal linux by the end of this month.