A system daemon to allow session software to update firmware
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 71%
Response Time: 2h
First Timer Success: 64%
fwupd/fwupd has a recorded first-timer success rate of 63.6%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in fwupd/fwupd respond to incoming external pull requests in approximately 2.4 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 68.5 places fwupd/fwupd in the A tier.
The external contributor pull request merge rate for fwupd/fwupd is 70.6%, based on public PR activity from non-core contributors.
fwupd/fwupd currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in fwupd/fwupd 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/fwupd/fwupd?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (88% approval). Large PRs (>500 lines) take ~12 hours (32% approval). Keep your diff compact for rapid review.
Is your feature request related to a problem? Please describe. We're using fwupdmgr install --allow-reinstall to reinstall the firmware as a test for fwupd and LVFS support on a given firmware version. fwupdmgr can't work on QubesOS due to no direct internet connection in dom0. The qubes-fwupdmgr wrapper can be used to perform LVFS fwupd updates in QubesOS, but the wrapper does not implement the install subcommand, only update and donwgrade, which makes more difficult to test the firmware and requires a manual downgrade to do so. Describe the solution you'd like Implement the install subcommand with flags like --allow-older, --allow-reinstall and --force. It should allow to perform the fwupd update using a cabinet file from LVFS even if the newest available version is already used. Describe alternatives you've considered Downgrading the firmware beforehand Additional context Add any other context or screenshots about the feature request here.
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 fwupd/fwupd, 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 fwupd/fwupd acknowledge new external contributions in approximately 2 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.6% were successfully merged into the primary branch.
fwupd/fwupd has a recorded first-timer success rate of 63.6%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 68.5 places fwupd/fwupd in the Welcoming tier.
The external pull request merge rate is 70.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, fwupd/fwupd 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 fwupd/fwupd 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.