A lightweight Gradio WebUI for stable-diffusion.cpp.
C-Rank Grade: D (Risky) - 17/100
External PR Merge Rate: -
Response Time: 2d
First Timer Success: -
daniandtheweb/sd.cpp-webui 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 daniandtheweb/sd.cpp-webui respond to incoming external pull requests in approximately 42.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 17.0 places daniandtheweb/sd.cpp-webui in the D tier.
The external contributor pull request merge rate for daniandtheweb/sd.cpp-webui is 0.0%, based on public PR activity from non-core contributors.
daniandtheweb/sd.cpp-webui currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in daniandtheweb/sd.cpp-webui. Reviews community pull requests with focus on project quality.
Discussions in daniandtheweb/sd.cpp-webui focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/daniandtheweb/sd.cpp-webui?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Monday - Friday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~27 hours (81% approval). Large PRs (>500 lines) take ~201 hours (29% approval). Keep your diff compact for rapid review.
The new option of stream layers in the performance menu in the new version that replaced offload to cpu, causes me to get OOM when i didn't before, before i ran sdxl on q8 on 4gb of vram completely fine, now i always get OOM, i had to revert to the previous version to use sdxl again I have a old rx 560 4gb vram gpu and im running sd.cpp compiled with vulkan, yes i now it is a bad gpu for this, but for simple models like sd1.5 in fp16 i didn't even needed any offload, and with offload to cpu, sdxl models and other that use the same architecture like pony and illustrious, they all work in q8, even with loras, or at least, they worked with the previous offload to cpu option sdxl, with flash attention enabled, because it halved the generation speed for me, and without cfg scale/with cfg scale at 1, i could run 512x at 4-5s per step and 1024x at 11-14s per step varying on how many and which loras i was using, i say with cfg at 1 because i was running with loras like dmd2 for images on low s
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 daniandtheweb/sd.cpp-webui, 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 daniandtheweb/sd.cpp-webui acknowledge new external contributions in approximately 1 days+. 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.
daniandtheweb/sd.cpp-webui 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 ~1 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 17.0 places daniandtheweb/sd.cpp-webui 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, daniandtheweb/sd.cpp-webui 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 daniandtheweb/sd.cpp-webui 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.