Many software projects impose targets on themselves for things like 'software quality' that involves even stable code being checked and changed. For example, m

Many software projects impose targets on themselves for things like 'software quality' that involves even stable code being checked and changed. For example, maybe they've received reports the code has bugs, but nobody thinks fixing is a good use of maintainers' time - or with such an old format, maybe no-one even knows what the correct behaviour should be. Maybe they have decided all file loading and network-interaction code should be fuzz-tested for security bugs. Or that every such module should have at least x% unit test coverage. Perhaps the the code uses deprecated methods and needs to be modernised. Or maybe they simply feel every file ought to have an owner, and nobody trusted has stepped up.