A Shadcn-inspired component registry for Rust. Build cross-platform apps for Web, Desktop, iOS and Android.
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
rust-ui/ui has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in rust-ui/ui 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 7.5 places rust-ui/ui in the D tier.
The external contributor pull request merge rate for rust-ui/ui is 0.0%, based on public PR activity from non-core contributors.
rust-ui/ui currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in rust-ui/ui welcoming community pull requests and bug fixes.
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/rust-ui/ui?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 10:00 UTC (10:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 17:00 to 21:00 UTC (17:00 - 21:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~14 hours (94% approval). Large PRs (>500 lines) take ~106 hours (34% approval). Keep your diff compact for rapid review.
Implement rich text editor support for dioxus-ui. Original request: #43 Living feature plan: https://github.com/rust-ui/ui/blob/main/plans/PLAN_MINIMAL_EDITOR_FEATURES.md Plan priorities may evolve during implementation. Contributors should follow the current plan rather than treating the feature table as fixed scope. Current direction: native contenteditable Rust/WASM DOM bridge no Tiptap/ProseMirror dependency demo-first validation on /test-page Refs #43
Context The current Sonner integration relies on three JS/CSS files loaded globally: File Size Role public/components/sonner.js ~35KB Third-party Sonner library — renders toasts into [data-sonner-toaster] public/components/sonner.min.js ~14KB Minified version public/components/sonner.css ~8.6KB Sonner styles public/components/lazy_load_sonner.js ~4KB Lazy loader — defers loading sonner.js until SonnerTrigger or SonnerList appears in DOM The Leptos side (app_crates/registry/src/ui/sonner.rs) provides: SonnerTrigger — a button with data-toast-title, data-toast-description, data-toast-position, data-variant attributes. Sonner.js reads these on click and renders a toast. SonnerList / SonnerContainer / SonnerToaster — the DOM container where Sonner.js injects toast elements. The JS library owns all toast state: creation, stacking, animation, auto-dismiss timers, and swipe-to-dismiss. Leptos has no visibility into this state. What needs to happen Replace the entire
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 rust-ui/ui, 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 rust-ui/ui acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
rust-ui/ui has a recorded first-timer success rate of 0.0%. Repositories ranked Risky 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 7.5 places rust-ui/ui in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, rust-ui/ui currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for rust-ui/ui 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.