[FEAT] Add public leaderboard page — top contributors by streak and commits

[Priyanshu-byte-coder]

Summary

Issue #79 tracks a follower leaderboard. This issue expands it to a global public leaderboard of DevTrack users who have opted in to public visibility.

Expected Behaviour

A /leaderboard page (no auth required) showing:

• Top 50 users by current streak
• Top 50 users by total commits (this month)
• Tabs: 'Streak' | 'Commits' | 'PRs'
• Each row: avatar, username, score, link to public profile

Implementation Notes

• Query Supabase: users with is_public = true, join with cached metrics
• Cache leaderboard data server-side, refresh every hour
• Add leaderboard_opt_in boolean to user_settings (default false, explicit opt-in)
• Rate limit the page to prevent scraping

GSSoC Info

• Difficulty: Advanced — 55 pts
• Area: Feature / Social

[srinidhi-2006-bit]

Hi @Priyanshu-byte-coder

I’m contributing under GSSoC’26 and I would like to work on this issue.

I understand that the feature involves building a public leaderboard page with ranking tabs for streaks, commits, and PRs, along with public profile visibility controls, optimized Supabase queries, caching, and basic rate limiting for scalability and protection against scraping.

I’ll ensure the implementation is clean, responsive, and aligned with the existing project architecture while maintaining performance and proper data handling.

Looking forward to contributing to DevTrack

[Subhra-Nandi]

Hi @Priyanshu-byte-coder ,

I am participating in GSSoC '26 and would love to work on this issue!

My Background: I have been actively participating in Open Source and have strong hands-on experience building scalable applications using React, Next.js, TypeScript, Node.js, PostgreSQL, Tailwind CSS, and integrating the GitHub API.

Here is my execution process to perfectly implement this feature:

Proposed Execution Plan:
First, I will update the PostgreSQL/Supabase schema for the user_settings table to include the leaderboard_opt_in boolean (defaulting to false). I will then write an optimized Supabase query to fetch users where both is_public and leaderboard_opt_in are true. This query will join the users with their cached metrics, accurately sort them to get the top 50 for streaks, total commits (filtered for the current month), and PRs.

Next, I will build a Next.js API route (/api/leaderboard) to serve this data securely without requiring authentication. To optimize performance and prevent scraping, I will apply server-side caching to refresh the data strictly every hour and implement IP-based rate limiting on the endpoint.

Finally, I will develop the /leaderboard frontend using React and Tailwind CSS. The page will feature a responsive, tabbed interface to easily switch between 'Streak', 'Commits', and 'PRs'. Each row will display the user's avatar, username, score, and a direct link to their public profile, all fully typed with TypeScript for maximum reliability and clean loading states.

Please let me know if I can be assigned to this!

[palakjaiswal16]

Hi @Priyanshu-byte-coder,

I’d like to work on this issue under GSSoC’26.

I understand the feature requires a public /leaderboard page with tabs for Streak, Commits, and PRs, showing only users who have explicitly opted in through public visibility settings. I can help implement the Supabase schema update, optimized leaderboard queries, server-side caching, rate limiting, and a responsive frontend table with avatar, username, score, and public profile links.

I noticed there is already a linked PR (#300), so I’d be happy to contribute if further work, review fixes, or follow-up improvements are needed.

Thanks!

[tech-dipesh]

/assign gssoc 2026

[MansiPawar-art]

Hi @Priyanshu-byte-coder ,

I would like to work on this issue under GSSoC'26.

My approach:

• Create a public /leaderboard page with tabs for Streaks, Commits, and PRs
• Fetch only users who opted into public visibility using the leaderboard_opt_in / is_public setting
• Query and sort the top 50 users from Supabase based on the selected category
• Add server-side caching to refresh leaderboard data periodically and reduce database load
• Build a responsive UI showing avatar, username, score, and public profile link
• Add basic rate limiting and proper loading/error handling for better performance and security

I’d love to contribute to this feature. Please assign this issue to me. Thank you!

[saurabhhhcodes]

Hi @Priyanshu-byte-coder, I’d like to take this up under GSSoC. I can build the public leaderboard with cached contributor metrics, server-side pagination/search, and defensive empty/error states so it does not add unnecessary GitHub API load. I’ll keep it aligned with the existing dashboard components and add focused validation. Could you please assign this to me?