Control WS2812B and many more types of digital RGB LEDs with an ESP32 over WiFi!
C-Rank Grade: A (Welcoming) - 58/100
External PR Merge Rate: 43%
Response Time: 1d
First Timer Success: 43%
wled/WLED has a recorded first-timer success rate of 42.9%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in wled/WLED respond to incoming external pull requests in approximately 25.2 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 58.4 places wled/WLED in the A tier.
The external contributor pull request merge rate for wled/WLED is 42.6%, based on public PR activity from non-core contributors.
wled/WLED currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in wled/WLED. Maintains strict focus on technical quality and test standards.
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/wled/WLED?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 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (53% approval). Large PRs (>500 lines) take ~121 hours (19% approval). Keep your diff compact for rapid review.
WLED/wled00/const.h Line 113 in 439d4a0 #define WLED_MAX_BUTTONS 32 C3 has at most 22 possible pins, similar for the upcoming -C5 (max 29 gpio) and -C6 (max 29 gpio). Some of these are not available because they are reserved for RAM, PSRAM, or Not connected (NC). Classic esp32 has 39 possible gpio, but 11 of them are not usable => max 28 buttons if you don't connect any LEDs. Is it intended to allow more buttons than physically possible on the board? MAX_NUM_PINS is passed to the UI directly, meaning that more buttons can be defined than physicially availeable? WLED/wled00/xml.cpp Lines 326 to 338 in 439d4a0 settingsScript.printf_P(PSTR("bLimits(%d,%d,%d,%d,%d,%d,%d,%d,%d,%d);"), WLED_PLATFORM_ID, // TODO: replace with a info json lookup
What happened? I recently upgraded to a Hue Pro Bridge, and when attempting to sync WLED to a Hue light I get a "Hue Status: Inactive" message. To Reproduce Bug In sync settings, add the bridge pro IP address, light number, etc. press the touchlink button and click "save". Expected Behavior Syncing between WLED and a given hue bulb Install Method Binary from WLED.me What version of WLED? WLED 15.3 Which microcontroller/board are you seeing the problem on? ESP32 Relevant log/trace output Anything else? No response Code of Conduct I agree to follow this project's Code of Conduct
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 wled/WLED, 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 wled/WLED acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 42.6% were successfully merged into the primary branch.
wled/WLED has a recorded first-timer success rate of 42.9%. Repositories ranked Welcoming 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 58.4 places wled/WLED in the Welcoming tier.
The external pull request merge rate is 42.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, wled/WLED 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 wled/WLED 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.