No, it was in response to the correct comment but I should elaborate.

> Leaning on a proprietary solution also means you're downstream of any decision the makers of the tool make, including choosing to nuke your (and/or your business's) use case.

My understanding is that OP is advocating free/libre software protects a business from changes in software that could affect the business' use case.

This risk is present in both proprietary and free/libre software. Maintainers may remove features that some users find critical. If a feature is removed and your business requires the feature, you now need to maintain a fork of the software or contribute development time upstream.

You're right, by trusting any outside source for a dependency, you're still dependent. But as you noted, there's the option of adopting the software yourself and injecting it as vendored or something similar. Proprietary doesn't even have that.

Depending on the project, it may move slow enough for the dependency to be slow to update and it be fine. Depends on what you're doing.

At least in the case you mentioned, I can revert to an older version and freeze it there until my business can sort out the way forward.

Ideally, one chooses dependencies that are easy to replace and reasonable to maintain for a bit, if needed. Or if you're lucky, no dependencies at all!