Distros contain contrib modules and distro maintainers often have testing and other procedures they must work through before releasing a new distro version. When a security update for a dependent module is released they may have to rush that process and risk making a mistake. Knowing of an impending security release will for better planning.
Let distribution maintainers see count of s.d.o issues for modules and statuses for modules in their distro so that they can plan better for new releases of their distro.
This would be exposed only for modules in a distro and to the maintainer(s) of that distro.
This would show only issue counts, not the issue title or other details of the issues. Perhaps issue status and perhaps followup date.
To mitigate against someone creating a distro of every Drupal module this could be enabled per s.d.o account (perhaps with a role) so that only "trusted" distro maintainers have access to this.
Possible tasks:
Closed: outdated
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I feel like the initial motivation for this concept has fallen away.
The most sustainable thing at this point is that maintainers of distributions (or recipes) that are successful should become co-maintainer of the modules in their distribution/recipe.