OpenWrt Notification Plugin – Send Alerts to WeChat or Telegram
C-Rank Grade: D (Risky) - 12/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
tty228/luci-app-wechatpush 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 tty228/luci-app-wechatpush 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 12.0 places tty228/luci-app-wechatpush in the D tier.
The external contributor pull request merge rate for tty228/luci-app-wechatpush is 0.0%, based on public PR activity from non-core contributors.
tty228/luci-app-wechatpush currently has 8 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in tty228/luci-app-wechatpush. Reviews community pull requests with focus on project quality.
Discussions in tty228/luci-app-wechatpush 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/tty228/luci-app-wechatpush?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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
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.
默认的那个路径，保留配置升级固件会丢失变成缺省值
搜索打开和关闭的 GitHub 问题 请在提交问题之前回答这些问题，谢谢。 | Please answer these questions before submitting them. Thank you. 你使用了哪个版本？ | Which version did you use? openwrt 25.12 预期行为 | Expected behavior 希望解决25.12版本下的ipv4无法推送的问题 实际行为 | Actual behavior 原因分析（如果可以） | Cause analysis (if possible) 问题重现步骤 | Steps to reproduce the problem [ImmortalWrt ~]# /usr/share/wechatpush/wechatpush getip /usr/share/wechatpush/wechatpush: line 1089: [: : integer expected /usr/share/wechatpush/wechatpush: line 1087: [: : integer expected IPv4: 59.65.119.32地址： 中国 接口： 网络接口IPv6: 地址： 美国 加州 聖荷西接口： 网络接口 [ImmortalWrt ~]#
搜索打开和关闭的 GitHub 问题 请在提交问题之前回答这些问题，谢谢。 | Please answer these questions before submitting them. Thank you. 你使用了哪个版本？ | Which version did you use? [v3.6.12]，原来固件，内置了微信推送，但是不知道版本号 预期行为 | Expected behavior 这是老固件，内置的微信推送，在删除wrtbwmon流量统计插件以后，定时推送的数据，不显示【总流量】 实际行为 | Actual behavior 昨天安装的3.6.12版微信推送，我删除流量统计插件wrtbwmon以后，还有【总流量】字段 原因分析（如果可以） | Cause analysis (if possible) 问题重现步骤 | Steps to reproduce the problem
搜索打开和关闭的 GitHub 问题 请在提交问题之前回答这些问题，谢谢。 | Please answer these questions before submitting them. Thank you. 你使用了哪个版本？ | Which version did you use? 基于OpenWrt的固件内置，不知道具体是什么版本，没找到地方查看 预期行为 | Expected behavior 正常显示，比较美观 实际行为 | Actual behavior 显示不正常，不够美观 原因分析（如果可以） | Cause analysis (if possible) 问题重现步骤 | Steps to reproduce the problem 运行一段时间后，会出现，重启客户端，有时候会正常，有时候还是不正常。 这种情况是固件原因，还是软件原因？ 谢谢
📋 背景 感谢 @tty228 开发了 luci-app-wechatpush 这个强大的路由器推送插件！我一直在使用它来监控路由器状态和设备上下线。 在使用「自定义推送」功能时，我尝试对接了一个开源的微信消息桥接服务 WeChat Bridge，发现效果非常好，这里分享一下完整的对接方案，供其他用户参考，作者也可以考虑将此方案补充到文档中。 实际效果截图 微信收到的路由器通知效果： ✨ WeChat Bridge 简介 WeChat Bridge 是一个基于腾讯 iLink Bot API 的超轻量微信消息桥接服务： 🐳 Docker 一键部署，开箱即用 🌐 标准 RESTful API，支持 JSON 格式推送 🔔 支持 Webhook 反向推送 🤖 内置 AI 助手（OpenAI / Gemini / Claude / DeepSeek） ⏰ 24h 保活守护，主动提醒防断联 📱 自带 Web 管理面板，扫码登录即可 🔧 对接 luci-app-wechatpush 的配置方法 1. 部署 WeChat Bridge（Docker） mkdir -p wechat-bridge && cd wech
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 tty228/luci-app-wechatpush, 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 tty228/luci-app-wechatpush 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.
tty228/luci-app-wechatpush 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 12.0 places tty228/luci-app-wechatpush 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, tty228/luci-app-wechatpush currently has 8 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for tty228/luci-app-wechatpush 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.