Community maintained packages for OpenWrt. Documentation for submitting pull requests is in CONTRIBUTING.md
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 56%
Response Time: -
First Timer Success: 44%
openwrt/packages has a recorded first-timer success rate of 44.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in openwrt/packages 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 66.5 places openwrt/packages in the A tier.
The external contributor pull request merge rate for openwrt/packages is 56.2%, based on public PR activity from non-core contributors.
openwrt/packages currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Community maintained packages for OpenWrt. Documentation for submitting pull requests is in CONTRIBUTING.md
Strict review standards in openwrt/packages. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in openwrt/packages 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/openwrt/packages?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 Monday - Wednesday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (70% approval). Large PRs (>500 lines) take ~115 hours (25% approval). Keep your diff compact for rapid review.
Package Name flashprog Maintainer none OpenWrt Version ANY OpenWrt Target/Subtarget ANY Steps to Reproduce The last time the flashrom package got updated in OpenWrt was the beginning of the year 2023. Since then there was a important change in the flashrom ecosystem. There was a split at the core developers. Now there are two independent projects out there each containing different functionality. Sometimes you need flashrom, sometimes you need flashrprog. It is important to have both packages in OpenWrt to have the full functionality for flashing related workloads. https://flashprog.org Actual Behaviour Currently only flashrom is part of the OpenWrt packages. Just updating it #29590 , wont add all the functions that have been added since 2023 to the flashing functionality toolset. Confirmation Checklist The package is maintained in this repository. I understand that issues related to the base OpenWrt repository or LuCI repository will be closed. I am reporting an issue for OpenWrt,
Package Name smartdns Maintainer Nick Peng [email protected] OpenWrt Version 25.12.2 OpenWrt Target/Subtarget mediatek/filogic Steps to Reproduce Install OpenWRT package smartdns 46.1. Observe /etc/init.d/smartdns set_main_dns() behavior: adds LAN IP with CIDR to dhcp_option causing DHCP/DNS issues. Compare with upstream smartdns 47.1, where CIDR is removed and uci batch used. Actual Behaviour On modern OpenWRT (DSA), network.lan.ipaddr contains CIDR notation: 192.168.1.1/24 Causes broken DHCP DNS assignment (6,192.168.1.1/24) → clients receive invalid DNS entries. Bug traced to /etc/init.d/smartdns in OpenWRT package. Upstream smartdns 47.1 has corrected this (sed 's/\/.*//g') and uses uci batch. Confirmation Checklist The package is maintained in this repository. I understand that issues related to the base OpenWrt repository or LuCI repository will be closed. I am reporting an issue for OpenWrt, not an unsupported fork.
Package Name watchcat Maintainer @roger- OpenWrt Version 25.12.0-rc5 OpenWrt Target/Subtarget ipq40xx/generic Steps to Reproduce Watchcat is not recognizing ping responses if the ping transverses through a mesh network. Using the diagnostic tool on the same router, ping responses are coming in normally. When Watchcat pings the same address, Watchcat sees no response. This issue was not present with 25.10.X and prior. Actual Behaviour Diagnostic Ping response from 192.168.1.1 to 192.168.1.12 over a mesh: 64 bytes from 192.168.1.12: seq=2 ttl=64 time=1.353 ms Watchcat Ping response missing from 192.168.1.1 to 192.168.1.12 over a mesh:: watchcat[4123]: Could not reach 192.168.1.12 for 1500. Rebooting after reaching 3600 Confirmation Checklist The package is maintained in this repository. I understand that issues related to the base OpenWrt repository or LuCI repository will be closed. I am reporting an issue for OpenWrt, not an unsupported fork.
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 openwrt/packages, 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 openwrt/packages acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 56.2% were successfully merged into the primary branch.
openwrt/packages has a recorded first-timer success rate of 44.4%. Repositories ranked Welcoming 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 66.5 places openwrt/packages in the Welcoming tier.
The external pull request merge rate is 56.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, openwrt/packages 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 openwrt/packages 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.