Ah! I looked for such a thing in the the Orchard repo and it wasn’t there…
I guess this would solve the direct problem, but it also creates yet more centralization: putting ECC in a position that’s privileged not just with respect to its own code, but also with respect to others’ contributed code. It’s explicitly ECC that’s named in the Contributor License Agreement…