In reply to Paul Lempke.

@Paul

Maybe should explain to your class that ~ with 40,000+ plugins, and who knows how many themes ~ however you slice and dice them, you're still only going to be able to trawl through a tiny fraction of what's available in the directories.

This kind of automatic retirement is essential.

As it turns out I am working on project which does the very thing you have suggested, and I hope to be able to announce it very shortly.

But its a complex issue requiring sensitivity of both the developer's plus end-users' rights and wishes, workflow and technical issues involved in cross-platform development, and an on-going dialogue and involvement with the people who give up their free time to manage the directories.

But don't forget, even with all that in place, it also requires the development of a very simple way for the average end-user to be able to update from abandoned plugin/theme A, to adopted plugin/theme B.

And as far as I know, even with 40,000+ plugins in the directory, that's never been tried before.