Project 'Health Check' metrics, with auto 'Get involved' engagment

What's your idea?

To put a block/pane on every project page on D.org that provides an at-a-glance summary of how 'healthy' the project is. This would replace/extend the 'Statistics' block presently implemented and provide a clear, colourful overview of how 'healthy' -- in terms of bugs, issue activity, maintainers and installs -- the project is.

Ideally, to have the 'at-a-glance' properties, these would be clearly rendered to be 'good', 'ok' or 'bad' somehow, and compared to a standard/good practice set of metrics.

Further extensions could include engagement features so that when a metric is low, a 'Get involved' section appears, with buttons linking to pages on how to help the project... E.g. When 'Installs per open issue' is low, the following is shown:

This project could use YOUR help!
Please consider helping out with the Issues

EXAMPLE: this block would provide such metrics as:

• Commits per day/week/month/year
• Issue comments per day/week/month/year
• Installs per open issue
• Installs per active maintainer
• Open issues per active maintainer
• Installs per active maintainer
• etc
• OVERALL SCORE

What are the benefits?

Current/potential users/developers of the project can look at the block and see quickly if it's worth them installing the project, OR getting involved if the project use help.

Once implemented, this allows a report for all projects to be built that helps show people the best place to get involved. It also allows (later) a chance for financial support/bounty/sponsorship to be focused where it's needed.

Additionally:

• Maintainers might get more help
• Project users and maintainers will (hopefully) want to maximise their score, so they'd aim to clean up their projects, or be compelled to clearly ASK for help with things. (sometimes it's lonely being a maintainer!)
• Drupal's projects start to either get better, or be left to die (as all projects do eventually).

What are the risks?

• We'd need split up health checks for each supported major version of Drupal -- or for each branch of the project -- to avoid skewed data thanks for forgotten D5 versions or buggy & cutting edge D8/9 branches. The user should be able to pick
• Obviously the metrics would need to be chosen and calculated so their score makes sense, false positives/negatives will erode trust.
• A 'overall score' risks marking down an otherwise excellent project with a single shortcoming -- but then this is the point: to gain support or help bring quality up.

How can we measure the impact of this idea? (metrics)

• Tracking clicks on the 'help this project' buttons
• Comparing modules health over time
• Occasional maintainers questionnaires
• other Analytics & feedback

Who directly benefits from / will use this improvement? (target audiences)

Project users, potential project users, maintainers, Drupal as a whole.

Are additional resources available for discovery/implementation? (volunteer effort, financial backing, etc.)

TBC, but I'd help out...