Code metrics and insights for Git projects.

Churn or file churn is the number of times a file has changed in a given time range, calculated by counting the number of commits this file appears on.

It will tell you which files are the ones that are constantly changing, thus the ones more likely to be hotspots of bugs or related to features with constant requirement changes.

File coupling is a potential code smell that occurs when you have an implicit temporal relationship between two or more files in a project.

If files A and B are constantly changed together, in the same commit, they are probably coupled or tighly related to each other.