From a user:

I’m not aware of any tool that would check
all source files in the code base and fail the build if licensing
information doesn’t comply with the requirements and isn’t aligned
with the LICENSE.txt file in the root of the repository."

It would a nice thing to allow more complex policies that can handle these cases. The devils is in the details of course, as the core code should be under the same license as root, top level license, but at the same time, it may be commonly OK to have secondary licenses diverges for non core code, like build scripts or test files.