I dont know if this is the right module for this.
In addition to the recent ci task printing a summary report of all modulesync versions that havent been patched into their corresponding modules yet, we could use a task that allows us to find stale modules / modules which havent had a release in a long time.
A cutoff point could possibly be something like last-released: 2 years ago.
If we have modules that havent had a release in that long time, we may have a stale module (candidate for archiving) or something else is broken/needs fixing (which would be good to know about). Thoughts on this?