It used some pretty interesting strategies around creating Git statistics such as the concept of seperating "new code" vs "churn". They defined churn as "modifying a line that had been previously modified in the last month" (I forgot if it was month or some other timeline).

It would chart if an engineer made a large number of "churn" diffs vs new code vs "legacy/refactoring" which was modifying code that was last touched a long time ago.

I did a trial in 2018 and liked the product a lot. There were some simple metrics like "does a developer commit code every business day" and "how long do your PRs sit waiting for review". Other more complex things they produced from the git log were statistics about churn (how often you touch the same code), and new code vs. refactoring vs. bug fixing.

Overall, I thought they handled the "you can't make metrics for developers" type objections fairly well. To get everyone on the dev team engaged and thinking about their metrics seemed like too big of a hurdle given the cost per seat of GitPrime.