It would be extraordinarily useful to include code churn metrics from source control. This would be an extremely helpful metric to help decide what parts of the codebase a team should look to start cutting down complexity, dependencies, and other issues.

I use code churn when it's available to help identify modules, classes, or methods that we should focus on. Items with high churn indicate they're getting touched a lot, which often indicates brittle sections of the codebase.

Since this is totally dependent on each particular source control system, it would make sense to start with only one or two of the most widely used SC systems in the .NET ecosystem. Maybe VSS? (KIDDING!)