Scan & Fix Broken Translations
i18n Doctor analyzes any public GitHub repository for translation issues and helps you fix them instantly using Lingo.dev. Never ship broken i18n again.Quick Start
Get scanning in under 2 minutes
View Demo
Try the live application
What You Get
Auto-Detection
Automatically finds locale files in JSON, YAML, or .po formats across common i18n directory patterns
Health Reports
Visual breakdown of coverage per locale with missing, untranslated, and orphan key detection
One-Click Fix
Translate all gaps instantly with Lingo.dev and generate downloadable fixes or GitHub PRs
Key Features
Developers ship apps with broken i18n all the time — new UI strings go untranslated, some locales have 90% coverage while others sit at 40%, and unused keys pile up silently. i18n Doctor solves this.Repository Scanner
Auto-detects translation files in common patterns like
locales/, i18n/, public/locales/Localization Health Dashboard
Per-locale coverage %, visual progress bars, summary cards for total keys, missing, untranslated, orphan
Shareable Report Cards
Every scan generates a unique URL with social-share friendly summary
Lingo.dev Integration
One-click translation of all missing/empty strings via Lingo.dev SDK
Use Cases
Pre-Release Audits
Pre-Release Audits
Scan your repository before shipping to catch missing translations across all locales. Get a comprehensive health report showing exactly which keys need attention.
CI/CD Integration
CI/CD Integration
Run automated scans in your deployment pipeline to prevent broken translations from reaching production. Integrate with GitHub Actions for continuous monitoring.
Localization Health Monitoring
Localization Health Monitoring
Track translation coverage over time across multiple locales. Identify which languages need attention and maintain consistent i18n quality.
Open Source Contributions
Open Source Contributions
Analyze public repositories to find i18n issues and contribute fixes. Perfect for discovering contribution opportunities in open source projects.
How It Works
Auto-Detection
i18n Doctor scans the repository tree and auto-detects translation files in common patterns
Analysis
Compares all target locales against the source locale to identify missing keys, untranslated strings, and orphan keys
Health Report
View a comprehensive dashboard with per-locale coverage stats and expandable issue lists
Supported Translation Formats
JSON
Flat or nested JSON translation files
YAML
YAML format translation files
gettext (.po)
GNU gettext portable object files
Get Started
Quickstart Guide
Run your first scan in 2 minutes
API Reference
Integrate scanning into your workflow
Built for the Lingo.dev Multilingual Hackathon #3 by @lokendratwt