Manage your Nerves device fleet, including firmware updates, health reports, and interactive device consoles.
C-Rank Grade: S (Elite) - 74/100
External PR Merge Rate: 87%
Response Time: 23h
First Timer Success: 88%
nerves-hub/nerves_hub_web has a recorded first-timer success rate of 87.5%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in nerves-hub/nerves_hub_web respond to incoming external pull requests in approximately 22.6 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 74.3 places nerves-hub/nerves_hub_web in the S tier.
The external contributor pull request merge rate for nerves-hub/nerves_hub_web is 86.9%, based on public PR activity from non-core contributors.
nerves-hub/nerves_hub_web currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in nerves-hub/nerves_hub_web. Prompt code reviews with positive guidance for new contributors.
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/nerves-hub/nerves_hub_web?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 ~15 hours (96% approval). Large PRs (>500 lines) take ~109 hours (39% 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 Elixir.
Library that fixes problem of losing state on LiveView reconnects
A self-hostable, distributed, S3-compatible object store that runs on the BEAM.
Use Commanded to build Elixir CQRS/ES applications
Support scripts has no way to tell whether it was recently modified and what was modified, making it a little more difficult to debug issues. When a script results in an error, it sometimes leads to an investigation of whether the support script was changed/broken or if a device's firmware changed. But It would be nice to have: A section for "last edited at: " or something similar. A way to see previous versions of the support script, so rollbacks can be easy.
When writing support scripts, I am unsure if the script has errors until I actually try running it. To combat this, I tend to write the code on an IDE with a LSP/linter first, and then paste it in. It would be nice if I can get feedback in the app without having to leave it and open an IDE. This would make support scripts faster to write, and reduce the risk of a bad script reaching the device.
Describe the bug If you are uploading firmware in one tab, then open another tab and start a new upload, the upload in the other tab is canceled. This is a big pain when you have 4-5 firmware images you'd like to upload at once. To Reproduce Steps to reproduce the behavior: Try to upload two firmwares at the same time in different browser tabs (I assume this is an issue with tabs sharing a live view session, so using different browsers or private browsing mode probably won't display this behavior) Expected behavior I should be able to have parallel firmware uploads. Ideally, it would be possible to select multiple .fw files at once and have them all upload, rather than having to open multiple tabs.
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 nerves-hub/nerves_hub_web, 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 nerves-hub/nerves_hub_web acknowledge new external contributions in approximately 22 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 86.9% were successfully merged into the primary branch.
nerves-hub/nerves_hub_web has a recorded first-timer success rate of 87.5%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~22 hours. 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 74.3 places nerves-hub/nerves_hub_web in the Elite tier.
The external pull request merge rate is 86.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, nerves-hub/nerves_hub_web currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for nerves-hub/nerves_hub_web 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.