Skip to main content
The Leaderboard provides a public benchmark dataset comparing translation coverage across popular open source repositories, helping you understand where your project stands in the ecosystem.

​
Accessing the Leaderboard

The Leaderboard is publicly accessible at: 
https://i18n.doctor/leaderboard
No authentication required. The Leaderboard shows all scanned repositories, aggregated by unique owner/repo combination.

​
What It Shows

The Leaderboard displays:

Repository Rankings

Repositories sorted by average coverage percentage (highest first)

Coverage Metrics

Visual progress bars and percentage badges for each repository

Key Statistics

Total keys, locale count, and summary data per repository

​
Leaderboard Table

Each entry shows:
ColumnDescription
#Ranking position (sorted by coverage descending)
Repositoryowner/repo format, linked to full report
KeysTotal source keys in the repository
LocalesNumber of target locales detected
CoverageProgress bar + badge showing average coverage %

​
Color Coding

Coverage badges use the same color scheme as health reports:
  • 🟢 Green (≥90%) - Excellent coverage
  • 🟠 Orange (60-89%) - Needs attention
  • 🔴 Red (<60%) - Critical issues

​
Benchmark Repositories

The Leaderboard seeds with these popular open source projects:

calcom/cal.com

Open source Calendly alternative

outline/outline

Team knowledge base and wiki

RocketChat/Rocket.Chat

Open source team chat platform

element-hq/element-web

Matrix protocol web client

appwrite/appwrite

Backend as a service platform

formbricks/formbricks

Open source survey platform

twentyhq/twenty

Open source CRM

documenso/documenso

Open source DocuSign alternative
Click any benchmark repository link to scan it immediately and add it to the leaderboard if not already present.

​
How Rankings Work

The Leaderboard uses this algorithm:
1

Fetch all reports

Query the reports table for all scanned repositories
2

Deduplicate

Group by repo_owner/repo_name (case-insensitive) and keep only the most recent scan for each unique repository
3

Sort by coverage

Order repositories by avgCoverage descending (highest coverage first)
4

Assign rank

Display ranking numbers starting from #1

​
Adding Your Repository

To add your repository to the Leaderboard:
  1. Navigate to i18n.doctor
  2. Enter your repository URL in the scan form
  3. Wait for the scan to complete
  4. Your repository will automatically appear on the Leaderboard
The Leaderboard shows the most recent scan for each repository. Re-scanning a repository updates its ranking if the coverage changes.

​
Empty State

When no repositories have been scanned yet, the Leaderboard displays:
  • A message indicating the leaderboard is empty
  • Quick-scan links for all benchmark repositories
  • Instructions to scan repos to populate the board
Click any benchmark repository name to instantly navigate to its scan page: 
https://i18n.doctor/owner/repo
These links use the short URL format that automatically triggers a scan.

​
Technical Implementation

The Leaderboard is a client-side React component that:
  • Fetches all reports from Supabase reports table
  • Performs client-side deduplication by repository
  • Sorts results by coverage percentage
  • Displays a loading spinner while fetching data
  • Shows real-time rankings based on the latest scans

​
Data Source

interface LeaderboardEntry {
  repo_owner: string
  repo_name: string
  repo_url: string
  report: {
    totalSourceKeys: number
    summary: {
      avgCoverage: number
      totalLocales: number
      totalMissing: number
    }
  }
  created_at: string
}
The component queries: 
SELECT repo_owner, repo_name, repo_url, report, created_at
FROM reports
ORDER BY created_at DESC
Then deduplicates in-memory by creating a Set of owner/repo combinations (case-insensitive).

​
Use Cases

Compare your repository’s i18n coverage against similar projects in your domain (e.g., CRM tools, chat platforms).
Study high-ranking repositories to understand patterns and strategies for maintaining excellent translation coverage.
Identify repositories with low coverage that might benefit from translation contributions.
Use the leaderboard as a proxy metric for i18n maturity when evaluating open source projects for adoption.

​
Privacy Considerations

All scanned repositories appear on the public Leaderboard. Only scan public repositories you’re comfortable exposing.
Private repositories:
  • Require GitHub OAuth authentication
  • Are not added to the public Leaderboard
  • Only visible in your personal Dashboard

​
Future Enhancements

Planned features for the Leaderboard include filters, search, historical trends, and category groupings. These will be available in a future release.

​
Next Steps

Dashboard

Track your personal scan history across multiple repositories

Understanding Reports

Learn how to interpret coverage metrics and prioritize fixes

Build docs developers (and LLMs) love

Get started for freeTalk to us