I guess you and I define "actual churn" differently.
I can rarely get a 6-month-old JavaScript web project to compile and run this easily. Churn in node versions, npm/yarn versions, dependencies being abandoned, superseded, dropping backwards compatibility.
I agree that the churn is constant.
Pinned package versions in npm solves this.
If you want to use the latest dependencies then yes there is ongoing management required. There are tools to help with this.