Affordable WiFi hacking platform for testing and learning
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
SpacehuhnTech/esp8266_deauther 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 SpacehuhnTech/esp8266_deauther 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 SpacehuhnTech/esp8266_deauther in the D tier.
The external contributor pull request merge rate for SpacehuhnTech/esp8266_deauther is 0.0%, based on public PR activity from non-core contributors.
SpacehuhnTech/esp8266_deauther currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in SpacehuhnTech/esp8266_deauther. Reviews community pull requests with focus on project quality.
Discussions in SpacehuhnTech/esp8266_deauther 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/SpacehuhnTech/esp8266_deauther?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
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Have you searched for existing (open and closed) issues describing the same problem? Yes Describe the error After accidentally flashing an incompatible firmware (ESP32 Marauder esp32c5devkitc1), the display of my DSTIKE Deauther Watch 32 C5 only shows a white backlight with no content. I tried restoring the original Deauther32 firmware using esptool, but the display remains blank. I believe the bootloader.bin provided at docs.spacehuhn.com is not compatible with the specific display hardware of the DstikeWatch32c5. esptool v5.3.0 Connected to ESP32-C5 on COM3 Chip type: ESP32-C5 (revision v1.0) Wrote 21568 bytes at 0x00002000 - Hash of data verified. Wrote 3072 bytes at 0x00008000 - Hash of data verified. Wrote 1687616 bytes at 0x00010000 - Hash of data verified. Hard resetting via RTS pin... To Reproduce Flash incompatible firmware (Marauder esp32c5devkitc1) onto DstikeWatch32c5 Try to restore using bootloader.bin + partition-table.bin + deauther32_v0.1.0_DstikeWatch32c5.bin from docs
Have you searched for existing (open and closed) issues describing the same problem? Yes/No Describe the error A clear and concise description of what the problem is. What do you think causes it? Error/Compile/Output Log 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 If applicable, add screenshots to help explain your problem. Environment (please complete the following information): OS: [e.g. iOS] Browser [e.g. chrome, safari] Version [e.g. 1.0] Hardware [e.g. DSTIKE, DIY] Attempts What have you already tried and didn't work out. Additional context Provide as much information as possible, better too much than too little! If you don't use this template, your issue might be closed and tagged invalid!
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 SpacehuhnTech/esp8266_deauther, 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 SpacehuhnTech/esp8266_deauther 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.
SpacehuhnTech/esp8266_deauther 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 SpacehuhnTech/esp8266_deauther 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, SpacehuhnTech/esp8266_deauther 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 SpacehuhnTech/esp8266_deauther 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.