DEVELOPER TOOLS / ANALYTICS / CASE STUDY
GitHub Analyser.
A clearer view of repositories, contributions, and the patterns behind a developer profile.

01 / The problem
Repository totals tell only part of a developer’s story. Contributions, languages, and comparisons need different views and data sources.
02 / Architecture
The React UI receives profile and repository data through Vercel serverless functions. REST supplies profiles and repositories; GraphQL supplies contributions.
03 / Engineering decisions
Use the API best suited to each view, with serverless functions between the browser and the integrations.
04 / My contribution
- Built repository statistics, language breakdowns, and a 12-month contribution heatmap in React.
- Used Vercel serverless functions with GitHub REST and GraphQL APIs.
- Built side-by-side developer comparisons across contribution and repository activity.
05 / Outcomes & status
A developer analytics dashboard with profile, repository, contribution, and comparison views.
06 / Scope & limitations
API access, rate limits, and upstream availability can affect the live demo. These metrics are context, not a complete measure of engineering ability.
Fnatics↗