Jeff,

I can see your argument on plugin author responsibility particularly when it comes to security issues, but I'm not cleare if we have the full story behind why Michael felt that way.

I've been on the receiving end of a security issue in one of my plugins and I had to pull a feature because of compatibility issues rather than because of security. I wasn't treated in a condescending manner, to be clear.
But, it wasn't ideal as I had many users complaining about a feature that actually speeded things up!
Now, I'm developing it as a add-on I'll host on GitHub and my website and try to deploy updates via Software Licensing which isn't ideal given I need to actually buy the plugin.

Then again, I chose to continue to support the plugin on WP.org and felt it important that users get the updates straight through there.

I'd like to believe that Michael would eventually be back in the directory when he finds the time to make a proper update.