Churn is a count of changes, for example how many commits touched each file. A file that is both changed often and complex is a hotspot. Churn alone says where people work, not that the code is bad.
Code churn
How often a file or function changes over time; a cheap signal for where the work and the bugs gather.