Find a way to detect unmaintained modules
We could find a way to calculate a score based on some factors to know if a module is actively maintained or not.
Ex:
- GitHub issues without answer from a maintainer
Any feedback welcome
Sounds like an interesting project. . .
I agree unanswered issues are a great indicator of maintenance.
Perhaps a proactive approach may, as well, be in order. For example,
As part of the listing application process, the maintainer is required to register to a site and agree to a "pulse check" in which they will receive an automated email, both periodically ( every 6 months maybe ) and if indicators determine the module may be abandoned. The email could have a magic link that allows the maintainer to land on the site and submit a form with the status.
On this site, the maintainer will see the status of the listing application. Once/if accepted, they will see the status of maintenance. The maintainer can login and submit the "Maintenance Status Form" whenever their status changes.
Admins receive automated emails / slack notification if the status a module changes to unmaintained.
If either the maintainer indicates abandonment or the email goes unanswered, then depending on the popularity / importance of the module, steps could be taken to seek new maintainers or whatever.
This could be a small, standalone app. I'd be happy to build something. Sounds like a good YT video.
I'm thinking Nuxt Pulse.

Thoughts?
Hey @rohrig and thank you for your proposal!
I do like the idea of asking directly the maintainer about this, but not sure if the email is necessary when it can be done by directly creating an issue on GitHub for instance?
I think at first I would like to get more stats for each package, potentially use the OSS Insights API?
Hi @Atinux, valid points. When I wrote this I was still pumped about my nuxt-mailer module 😆 . Opening an issue makes way more sense. Cool thing OSS Insights API, I'd never heard of it. I'd like to help out. I'll see what I can put together using OSS Insights.