Back to projects
dataProductionDATA SCIENCE

What Makes GitHub Repositories Go Viral?

Analysis of 215,000+ Repositories

Deep-dive statistical analysis of 215,000+ GitHub repositories to identify patterns driving open-source popularity. Discovered critical insights including forks as superior predictor (75%+ correlation), extreme data skewness (88.33), multicollinearity traps, programming language impact, and the dominance of open licenses. Comprehensive exploratory data analysis combined with correlation studies and machine learning modeling to reveal hidden patterns in open-source success.

GitHub Live Post
Case study snapshot
Role
Data science analyst
Audience
Open-source builders, data science reviewers, and portfolio visitors
Timeline
2025-02
Role
Data science analyst
Audience
Open-source builders, data science reviewers, and portfolio visitors
Date
2025-02
Problem

Why it mattered

Open-source popularity advice is often anecdotal; builders need data-backed patterns behind stars, forks, licenses, and languages.

Solution

What shipped

A statistical analysis of 215,000+ repositories that identifies correlations, skew, feature traps, and signals connected to popularity.

Impact

Proof signal

215,000+ repositories analyzed; Forks identified as 75%+ predictor; Extreme skewness (88.33) uncovered; Multicollinearity patterns discovered

< architecture />

System flow

Large repository data is cleaned, explored, statistically profiled, visualized, and converted into insight narratives for public sharing.

Data Collection
EDA & Skewness Detection
Feature Engineering
Correlation Analysis
Multicollinearity Testing
Model Building
Visual architecture
01
Data Collection
02
EDA & Skewness Detection
03
Feature Engineering
04
Correlation Analysis
05
Multicollinearity Testing
06
Model Building
quality score

Honest maturity snapshot

Code Quality9/10
UI / UX6/10
Scalability8/10
Production Ready9/10
Before

Raw datasets, disconnected metrics, and hard-to-scan findings.

After

A structured analysis or dashboard with clear KPIs, visual patterns, and decision-ready insights.

capabilities

Features

  • 215,000+ repository analysis.
  • Correlation and multicollinearity checks.
  • Skewness and outlier analysis.
  • Programming-language and license comparisons.
  • Public-facing findings written for non-data audiences.
tradeoffs

Engineering challenges

  • Avoiding misleading conclusions from heavily skewed open-source data.
  • Separating correlation from causal claims.
  • Turning complex EDA into useful public insight.
proof

Results

  • Identified forks as a stronger popularity signal than many surface metrics.
  • Created a foundation for the repository popularity predictor.
  • Demonstrated end-to-end data storytelling.
reflection

What I learned

  • Tradeoff learned: Avoiding misleading conclusions from heavily skewed open-source data.
  • Proof learned: Identified forks as a stronger popularity signal than many surface metrics.
  • Next iteration: Refresh the dataset on a schedule.
< stack />
PythonPandasScikit-learnMatplotlibSeabornStatistical Analysis
< next iteration />

Future improvements

Refresh the dataset on a schedule.
Add interactive charts and reproducible dashboards.
Segment findings by repository age and domain.
GitHub Repository Popularity PredictorDocument Q&A RAG System