If you're hit by a bus tomorrow, at what point do folks know to migrate off your never-to-be-maintained-again image?

Don't get me wrong -- I'm not trying to discourage you from sharing configs and artifacts that work for you. They're valuable information to publish.

I just get terrified when I see folks regularly deploying images maintained by individuals rather than organizations.

Sure, that’s a valid concern. I think there are some other aspects of projects to consider than only the the org vs individual distinction though.

For example, I first wrote about nginx-proxy and docker-gen 4 years ago (http://jasonwilder.com/blog/2014/03/25/automated-nginx-rever...). Since then, both projects have gone through continued releases with bug fixes, updates and new features. Between the two projects, there are about 110 different contributors and I am no longer the top contributor on one of them.

The projects are MIT licensed and free to be forked or maintained independently if neeeded.

There’s a large community of users that write blogs, help with issues, and even create derivative works inspired or derived from the project.

Finally, I’d add that a lot of orgs behind projects are really just an individual that wants to make a useful closed source project open for others. The org or company name attached doesn’t necessarily mean a company is going to support it any better than a dedicated individual or community that cares about it.