Sucrose is a versatile wallpaper engine that brings life to your desktop with a wide range of interactive wallpapers.
C-Rank Grade: B (Solid) - 53/100
External PR Merge Rate: 100%
Response Time: 4d
First Timer Success: 100%
Taiizor/Sucrose has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Taiizor/Sucrose respond to incoming external pull requests in approximately 104.8 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 52.8 places Taiizor/Sucrose in the B tier.
The external contributor pull request merge rate for Taiizor/Sucrose is 100.0%, based on public PR activity from non-core contributors.
Taiizor/Sucrose currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in Taiizor/Sucrose 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/Taiizor/Sucrose?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~68 hours (96% approval). Large PRs (>500 lines) take ~503 hours (45% approval). Keep your diff compact for rapid review.
Bug Description A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: Go to '...' Click on '....' Scroll down to '....' See error Expected Behavior A clear and concise description of what you expected to happen. Screenshots/Video If applicable, add screenshots/video to help explain your problem. Desktop (please complete the following information): OS: [e.g. Windows 11 1909] Which wallpaper was running at the time if any. Additional Context Add any other context about the problem here. Log File (Important) Share the diagnostic files by: Right click on the system tray icon -> Report Issue -> Create Log File or Open Sucrose settings (Gear icon) top-right -> System -> Log Files -> Create or Navigate to the Appdata folder C:\Users\<UserName>\AppData\Roaming\Sucrose\Log
there isnt the selection of the two monitor it sees only one monitor
Bug Description Until this morning the "Expand Across Screens" was working fine, after the update it is not working anymore. Wallpaper are only visible in one of my two displays, even when both are working as usual with windows To Reproduce Steps to reproduce the behavior: Go to 'Display preferences' Click on 'Placement Mode' Scroll down and select 'Expand Acress Screens' Switch between that and "Selected Screen Only" and nothig changes Expected Behavior Wallpaper visible and responsive on both screens Screenshots/Video If applicable, add screenshots/video to help explain your problem. Desktop (please complete the following information): OS: Windows 11 Pro 26H2 26300.9550 Which wallpaper was running at the time if any: Dream Line, Fizzy Sparks, The Silent Valley.... any wallpaper Additional Context Add any other context about the problem here. Log File (Important) Share the diagnostic files by: Right click on the system tray icon -> Report Issue -> Create Log File sucrose_log_20260
Please add a 10-second interval between cycles, because the minimum interval is currently 1 minute, which is too much. If you can add it, or tell me how to do it, I would be grateful.
Hello, I am using a dual monitor setup with one vertical screen and one horizontal screen. I want to set different wallpapers for each screen, but I am unable to configure them independently. Could you please add support for setting independent wallpapers for monitors with different orientations?
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 Taiizor/Sucrose, 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 Taiizor/Sucrose acknowledge new external contributions in approximately 4 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
Taiizor/Sucrose has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~4 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 52.8 places Taiizor/Sucrose in the Solid tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Taiizor/Sucrose currently has 6 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for Taiizor/Sucrose 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.