A Powerful and All-in-One MQTT 5.0 client toolbox for Desktop, CLI and WebSocket.
C-Rank Grade: B (Solid) - 47/100
External PR Merge Rate: 33%
Response Time: 20h
First Timer Success: -
emqx/MQTTX 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 emqx/MQTTX respond to incoming external pull requests in approximately 20.2 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 47.1 places emqx/MQTTX in the B tier.
The external contributor pull request merge rate for emqx/MQTTX is 33.3%, based on public PR activity from non-core contributors.
emqx/MQTTX currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
A Powerful and All-in-One MQTT 5.0 client toolbox for Desktop, CLI and WebSocket.
Active maintainer team in emqx/MQTTX 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/emqx/MQTTX?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 07:00 UTC (07: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 ~13 hours (42% approval). Large PRs (>500 lines) take ~97 hours (15% approval). Keep your diff compact for rapid review.
Describe the problem you Confuse 在 MQTTX 客户端中模拟设备连接 OneNET 云平台时，反复出现 Error: Connection refused: Bad username or password 错误。已多次核对并确认 Client ID、Username 以及使用平台官方工具生成的 Password（Token）完全正确，但仍然无法连接成功。尝试过切换服务器地址、更换端口、调整 SSL/TLS 设置，并严格按照文档重新生成 Token，问题依然存在。困惑的点在于：既然账号密码没有错，为什么还会被拒绝？ More detail MQTT 版本：3.1.1 服务器地址：studio-mqtt.heclouds.com，端口：1883 Client ID 格式：产品ID&设备名称 Username：产品ID Password：通过 OneNET 平台“设备调试”在线工具生成的 Token（method=md5，res=products/.../devices/...，et=1810609920） 已在平台确认设备状态为“已注册”且未被禁用 SSL/TLS 已设置为关闭 生成 Token 时使用的是“设备密钥 (deviceKey)”，已检查所有字段
官网上的https://mqttx.app/downloads 下载地址已经不可用了 https://packages.emqx.io/MQTTX/vv1.13.0/MQTTX-Setup-1.13.0-x64.exe
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 emqx/MQTTX, 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 emqx/MQTTX acknowledge new external contributions in approximately 20 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 33.3% were successfully merged into the primary branch.
emqx/MQTTX 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 ~20 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 47.1 places emqx/MQTTX in the Solid tier.
The external pull request merge rate is 33.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, emqx/MQTTX 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 emqx/MQTTX 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.