Build smaller, faster, and more secure desktop and mobile applications with a web frontend.
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 51%
Response Time: -
First Timer Success: 34%
tauri-apps/tauri has a recorded first-timer success rate of 34.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in tauri-apps/tauri respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 63.1 places tauri-apps/tauri in the A tier.
The external contributor pull request merge rate for tauri-apps/tauri is 51.3%, based on public PR activity from non-core contributors.
tauri-apps/tauri currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (66% critical review signals). Ensure PRs strictly follow guidelines before requesting review in tauri-apps/tauri.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/tauri-apps/tauri?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~11 hours (64% approval). Large PRs (>500 lines) take ~85 hours (23% approval). Keep your diff compact for rapid review.
Describe the bug A Windows WebView2 custom protocol request can call Tauri's custom protocol handler from a non-main thread. If the handler path looks up and clones a Webview, this can clone tauri_runtime_wry::DispatcherMainThreadContext off the main thread and trip the unsafe Rc precondition inside tao::EventLoopWindowTarget. In our app this was observed as an unsafe precondition violation around Rc::inc_strong / strong_count == 0 while cloning a Tauri webview during custom protocol handling. The suspected chain is: text Tauri::Webview::clone -> DetachedWebview::clone -> WryWebviewDispatcher::clone -> Context::clone -> DispatcherMainThreadContext::clone -> EventLoopWindowTarget::clone -> Rc<EventLoopRunner>::clone DispatcherMainThreadContext has unsafe Send / Sync impls with the safety comment saying the type is only used on the main thread, but the derived Clone can still be reached from non-main-thread custom protocol callbacks. Source locations checked This is still present in the
Describe the bug When typing Arabic or Hebrew text (RTL languages) in a contenteditable element or rich text editor (TipTap), the page scroll jumps on every keystroke when the text contains spaces (triggering word wrap). This issue only occurs in the Tauri desktop app (macOS WebView), not in standard web browsers (Chrome, Safari, Firefox). The scroll jump makes the app completely unusable for Arabic/Hebrew-speaking users as the page jumps unpredictably while typing. The issue specifically occurs when: ✅ Text is RTL (Arabic/Hebrew characters) ✅ AND text contains spaces (triggers word wrap) ✅ AND running in Tauri desktop app (WebView) Does NOT occur when: ❌ Typing English text (LTR) ❌ Typing Arabic text WITHOUT spaces (no word wrap) ❌ Running the same code in regular web browsers Reproduction Steps: Create a Tauri app with a scrollable page container Add a TipTap editor (or any contenteditable element) to the page Scroll the page down so there's scroll offset Focus the e
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to tauri-apps/tauri, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of tauri-apps/tauri acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 51.3% were successfully merged into the primary branch.
tauri-apps/tauri has a recorded first-timer success rate of 34.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 63.1 places tauri-apps/tauri in the Welcoming tier.
The external pull request merge rate is 51.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, tauri-apps/tauri currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for tauri-apps/tauri are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.