The idea being that new features should be fully tested and clearly documented before being merged - ideally with a minimum of overhead. Because if you defer either, it likely won't get done.
Until then it’s possible that taking contributions is more work that the author doing it themselves.
In any case, extensive test coverage is a the only way I think you can take contributions for even a medium size project.
I have a o(10k) loc project that takes contributions. The contributions are more for community building than anything else. I evaluate pull requests based on code quality and if the tests pass - I don’t ever manually test it.
It’s a lot of work to do even just that when the project falls off my priority list.
Taking contributions has long-term cost.
It's perfectly fine for authors to decide they don't want to follow this route and simply disallow most contributions (instead of investing into the test infrastructure required to enable them).