feat(web): add contributor leaderboard page

[Harxhit]

Summary

Adds a Contributor Leaderboard to the web app (apps/web) as a new /leaderboard route and references it from the README Contributors section.

The leaderboard is now generated automatically via a GitHub Actions workflow and served as a static JSON file, eliminating GitHub API rate-limit issues in the client.

The page displays:

• Contributor avatar image and GitHub username
• Issues created
• Merged PRs
• Open PRs
• Ranking by merged PRs → issues → open PRs

Maintainer accounts (@ShantKhatri, @Harxhit, @blankirigaya) and bot accounts are excluded from the leaderboard.

Changes

• apps/web/src/pages/LeaderboardPage.tsx

  • Added leaderboard page
  • Switched from direct GitHub API requests to consuming generated leaderboard data from /leaderboard.json

• apps/web/src/App.tsx

  • Added /leaderboard route

• apps/web/public/leaderboard.json

  • Generated leaderboard data consumed by the frontend

• .github/workflows/update-leaderboard.yml

  • New workflow to regenerate leaderboard data on a schedule and on demand

• .github/scripts/generateLeaderboard.js

  • Aggregates contributor statistics and writes leaderboard data

• README.md

  • Added leaderboard reference in the Contributors section

Notes

• Leaderboard data is generated by GitHub Actions instead of being fetched from the GitHub API in the browser.
• This removes GitHub Search API rate-limit issues and reduces page load time.
• The workflow can be triggered manually using workflow_dispatch and also runs automatically on a schedule.

Testing

Local

1. Create or generate:

   apps/web/public/leaderboard.json

[
  {
    "login": "Harxhit",
    "avatarUrl": "https://github.com/Harxhit.png",
    "profileUrl": "https://github.com/Harxhit",
    "mergedPrs": 42,
    "openPrs": 3,
    "issues": 12
  },
  {
    "login": "octocat",
    "avatarUrl": "https://github.com/octocat.png",
    "profileUrl": "https://github.com/octocat",
    "mergedPrs": 10,
    "openPrs": 2,
    "issues": 5
  }
]

2. Start the web app:

   npm dev

3. Verify:

   http://localhost:5173/leaderboard.json

   returns valid JSON.

4. Verify:

   http://localhost:5173/leaderboard

   renders the leaderboard correctly.

GitHub Actions

1. Open the Actions tab.
2. Run Update Leaderboard manually.
3. Confirm the workflow completes successfully.
4. Verify apps/web/public/leaderboard.json is updated and committed.
5. Verify the deployed leaderboard reflects the updated data.

---

Proof

Note:

This is not an actual representation(fake data).

[vercel]

@Harxhit is attempting to deploy a commit to the Prashantkumar Khatri's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Hi @Harxhit,

Thanks for opening this pull request.

This PR has been automatically classified based on the files modified.

Applied Labels

• gssoc:approved
• web

Primary Review Area

• web

Reviewer

@ShantKhatri has been identified as the primary reviewer for this pull request.

If you have any questions regarding the affected area or implementation details, feel free to reach out to the assigned reviewer.

Thank you for your contribution!

[github-actions]

CI — All Checks Passed

Backend — SKIP

Check	Result
Lint	-
Test	-
Typecheck	-

Mobile — SKIP

Check	Result
Lint	-
Test	-

Web — PASS

Check	Result
Build	PASS

---

Last updated: Mon, 22 Jun 2026 04:16:01 GMT

[ShantKhatri]

Hi @Harxhit , the API is not rate limiting most of the time:

Changes are already addressed.