Most static code analysis looks for bugs or just too complex functions.

The novelty of Change Impact is it looks at the context of the complexity. Adding complexity to something already complex should be flagged for review.

I've not come across any static code analysis so far that has provided this.

And in my own research of architectures, I came to this formula.