Slint is an open-source declarative GUI toolkit to build native user interfaces for Rust, C++, JavaScript, or Python apps.
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 83%
Response Time: 2d
First Timer Success: 54%
slint-ui/slint has a recorded first-timer success rate of 53.6%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in slint-ui/slint respond to incoming external pull requests in approximately 51.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 65.0 places slint-ui/slint in the A tier.
The external contributor pull request merge rate for slint-ui/slint is 83.1%, based on public PR activity from non-core contributors.
slint-ui/slint currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in slint-ui/slint. Ensure PR scope matches issue requirements closely before requesting review.
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/slint-ui/slint?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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~33 hours (96% approval). Large PRs (>500 lines) take ~245 hours (37% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Rust.
Protocol and libraries for sending and receiving OpenTelemetry data using Apache Arrow
tui/cli tool for fetch everythin' in internet
A security-focused library OS supporting kernel- and user-mode execution
Feature Description Currently OpenGL backend explicitly disabled for Femtovg WGPU renderer: i_slint_core::graphics::wgpu_29::init_instance_adapter_device_queue_surface( surface_target, requested_graphics_api, /* rendering artifacts :( */ wgpu::Backends::GL, )?; So I made a fork, where enable OpenGL backend for Femtovg WGPU and tested it for the next examples gallery memory slide_puzzle system-tray dnd-kanban imagefilter runtime_key_bindings speedometer carousel todo todo-mvc virtual_keyboard 7guis wgpu_texture I tested both on Windows and Linux, have not seen any artifacts or any other kind of bug Linux env: Intel (iGPU, native Mesa) Mesa Intel(R) Graphics (RPL-S) OpenGL 4.6 (Core/Compat) Mesa 26.1.2, OpenGL ES 3.2 Mesa 26.1.2 NVIDIA (RTX 4070, via zink) │ zink Vulkan 1.4(NVIDIA GeForce RTX 4070 Laptop GPU (NVIDIA_PROPRIETARY)) Tested on both chips Windows env: AMD Radeon(TM) 610M from ATI Tec
Feature Description If you transform-scale an svg it starts to get blocky and you can tell it was pre-rendered as a fixed size image. However text will continue to scale up smoothly regardless of size. Product Impact No response
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 slint-ui/slint, 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 slint-ui/slint acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.1% were successfully merged into the primary branch.
slint-ui/slint has a recorded first-timer success rate of 53.6%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 days+. 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 65.0 places slint-ui/slint in the Welcoming tier.
The external pull request merge rate is 83.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, slint-ui/slint 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 slint-ui/slint 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.