短信转发器——监控Android手机短信、来电、APP通知，并根据指定规则转发到其他手机：钉钉群自定义机器人、钉钉企业内机器人、企业微信群机器人、飞书机器人、企业微信应用消息、邮箱、bark、webhook、Telegram机器人、Server酱、PushPlus、手机短信等。包括主动控制服务端与客户端，让你轻松远程发短信、查短信、查通话、查话簿、查电量等。（V3.0 新增）PS.这个APK主要是学习与自用，如有BUG请提ISSUE，同时欢迎大家提PR指正
C-Rank Grade: B (Solid) - 49/100
External PR Merge Rate: 17%
Response Time: -
First Timer Success: -
pppscn/SmsForwarder has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in pppscn/SmsForwarder 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 49.3 places pppscn/SmsForwarder in the B tier.
The external contributor pull request merge rate for pppscn/SmsForwarder is 16.7%, based on public PR activity from non-core contributors.
pppscn/SmsForwarder currently has 8 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
短信转发器——监控Android手机短信、来电、APP通知，并根据指定规则转发到其他手机：钉钉群自定义机器人、钉钉企业内机器人、企业微信群机器人、飞书机器人、企业微信应用消息、邮箱、bark、webhook、Telegram机器人、Server酱、PushPlus、手机短信等。包括主动控制服务端与客户端，让你轻松远程发短信、查短信、查通话、查话簿、查电量等。（V3.0 新增）PS.这个APK主要是学习与自用，如有BUG请提ISSUE，同时欢迎大家提PR指正
Established Kotlin ecosystem in pppscn/SmsForwarder. Maintains structured code review standards for external 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/pppscn/SmsForwarder?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 03:00 to 07:00 UTC (03:00 - 07:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (21% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
是否有人曾提过类似的问题？ 否（No） 你觉得APP有什么不足之处？ 转发通道不支持拖动排序,对强迫症不是很友好,一个设备的多个通道想排在一起 你觉得该怎么去完善会比较好？【非必答】 转发通道允许拖动排序
是否有人曾提过类似的问题？ 否（No） 你觉得APP有什么不足之处？ "开发者模式关闭权限监控"我找了很久，都没有在ColorOS16的开发者模式中找到，为什么要找这个，我把电池管理、后台自启等等所有的权限都打开了，在锁屏状态下都没办法转发短信 你觉得该怎么去完善会比较好？【非必答】 还是希望作者大大能够针对性优化一下，我翻看教程看到作者大大用的Ace5应该也是ColorOS16了吧
是否有人曾提过类似的问题？ 否（No） 你觉得APP有什么不足之处？ [Suggestion]: 小米手机无人值守支持 问题描述 希望增加对小米手机（HyperOS / 澎湃OS）无人值守运行的支持。 目前在小米设备开启锁屏密码后，设备重启第一次未解锁时，应用无法正常自动启动。 具体表现： 使用 Magisk service.d 脚本尝试检测并拉起应用； 无锁屏密码时可以正常工作； 开启 PIN/密码锁屏后，重启设备，在首次输入密码之前： cmd package resolve-activity 无法正常解析应用 Activity； am start -n 包名/Activity 返回 Error type 3； 应用无法自动恢复运行。 原因推测： 小米系统使用文件加密（FBE）机制，在首次解锁前用户数据分区未完全解锁，导致部分应用组件不可访问。 期望改进 希望增加针对小米设备的无人值守适配，例如： 支持检测 Android 用户首次解锁状态后再执行自动启
是否有人曾提过类似的问题？ 否（No） 你觉得APP有什么不足之处？ 想要一个可以针对接收到短信时，通过设置手机号或者内容进行语音播报的功能。经常把车停路边，如果有交警挪车的短信过来，可以语音我让我赶紧过去挪车 你觉得该怎么去完善会比较好？【非必答】 No response
是否有人曾提过类似的问题？ 否（No） 你觉得APP有什么不足之处？ 可以考虑增加对Matrix协议的支持，并且支持Matrix的原生e2ee功能（但是开启这个功能需要验证） 官方的介绍：https://matrix.org/ 你觉得该怎么去完善会比较好？【非必答】 No response
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 pppscn/SmsForwarder, 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 pppscn/SmsForwarder acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 16.7% were successfully merged into the primary branch.
pppscn/SmsForwarder has a recorded first-timer success rate of 0.0%. Repositories ranked Solid 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 49.3 places pppscn/SmsForwarder in the Solid tier.
The external pull request merge rate is 16.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, pppscn/SmsForwarder 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 pppscn/SmsForwarder 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.