Open-source project health analytics

The brief

A software company depends on hundreds of open-source libraries and wants early warning when a project is going quiet or becoming risky. Build a pipeline that turns public GitHub events into health signals (activity, maintainer spread, issue response times) and predicts which projects are at risk of being abandoned. Good looks like: a reproducible data pipeline, a validated risk score, and a dashboard a team lead can use to review their dependencies.

What you will build

1. Pull and store a sample of GitHub event data
2. Define health metrics and a label for abandoned projects
3. Build features and train a risk model
4. Validate the score against projects that really went quiet
5. Ship a dashboard to look up a project or a list of dependencies
6. Document the pipeline so it can run every week

Free, open data to build it with

• GH Archive: public GitHub event data ↗ GH Archive
• Stack Overflow Developer Survey ↗ Stack Overflow

Check each dataset's licence before you publish your work. Your mentor gives your team its own version of the brief (data, scope or region), so every team's project is its own.