Interesting topic. However, let’s look at the flip-side of the coin. Those open source projects with one sole developer carry inherent risks in the sense that same sole developer may suffer burnout, dwindling enthusiasm, boredom, or a lack of desire to continue without some form of incentive - usually financial, or sponsorship from a larger entity. In this sense, adopting open source for long term usage based on these principles can be dangerous, and leave you “high and dry” without solutions to any issues that arise.
However, the possibilities here are distinct in the sense that you can fork the project yourself, and assume the role of maintainer, or fork and bring in other resources to contribute / assist in future development. The overall point here is that organisations who may rely on open source software and are then faced with the project being abandoned, or worse still, no resources to assume responsibility could find themselves in a difficult situation.