Some further ideas: - Make the periodic maintainership reminders optional. Every developer would be able to choose if (s)he wishes to receive them or not. I believe many would choose to receive them. - Maintain the last date the maintainership has been verified - either by an upload of a new version or by explicitly by the author (like by answering a reminder). This way, visitors would have a clear indication what could they expect, regardless of the reminders. - Add some estimate based on the packages that depend on this one. For example, take the maximum of these dates for all packages depending on this one maintained by the same author. It's very likely that if the same person actively develops something that is based on a package, (s)he will care about the package too, even if it hasn't been updated for a while. This would solve "perfect stable" packages like deepseq. - Alternatively, reminders could be human-triggered, instead of being sent automatically. If the date is older than some bound (like those 3 months), there could be a button like "query maintainership". If a visitor presses it, Hackage would send the reminder to the author (if it hasn't sent one recently, of course). This way, the reminder would be sent only for packages that somebody is actually interested in.