This is a small proof-of-concept where I explored how github activity can be used to estimate the health of OWASP projects. The idea is simple - if a project has regular commits , active contributors , and issues getting resolved it is likely to be healthy. This dashboard tries to represent that in a simple way.
- Fetches data from Github (commits, contributors, issues , PRs)
- Processes that data into basic metrics
- Calculates a Pulse Score as a rough indicator of project activity
- Displays everything in a simple dashboard
The pulse score is based on a few activity signals:
Pulse score= commit activity+ contributor activity+ issue resolution+ PR activity
Right now, this is what hits my mind it's a simplifies model just to explore the idea. The goal is not accuracy yet , but understanding what signals matter.
While contributing to OWASP Nest, I got interested in how we can understand this project better. Instead of just raw numbers , I wanted to see if we can combine them into something more meaningful and easier to understand. This PoC is my first step in exploring the idea.
This project is built using a simple modern web stack.
- Next.js (React framework)
- React (UI)
- TypeScript
app/→ Next.js App Router (pages and routing)components/→ UI components (like ProjectCard, charts)lib/→ core logic (e.g. Pulse Score calculation)api/→ server-side routes (GitHub data fetching)types/→ TypeScript types
- Tailwind CSS
- Global styles using
globals.css
- GitHub data is fetched through a backend API route
- Pulse Score is calculated using simple activity metrics
- Runs on Node.js (via Next.js)
- Rendered in the browser (client + server rendering)
- The scoring logic is basic and not weighted properly yet
- It does not consider things like issue complexity or contributor quality
- Data is fetched in a simple way and not optimized for scale