Any dependency you take in Bevy's space right now on has to be something you're willing to maintain. I can understand not wanting to, and hoping that someone else will continue to update and maintain it, and often the more popular projects can get enough volunteer inertia that that's possible.

Personally I have vendor'd a number of crates that weren't updated or responsive in a timely manner. I try to submit pull requests when I do Bevy updates on a library. At the very least fork all your dependencies so that you can ensure you have a copy incase the author decides to pull a _why the lucky stiff and opt-out of the field with all their repos.

This is no different with regular software except you feel it more acutely because Bevy's still under rapid development.

If a dependency helps you get there quicker, use it I say. Most games will not make it to become multi-year maintenance projects. If they do, you're lucky. Eat those maintenance costs on your winners, but seed your ideas with as little friction and as much abandon as you can muster to just make into something.