Dingtalk channel plugin for OpenClaw
C-Rank Grade: B (Solid) - 50/100
External PR Merge Rate: 70%
Response Time: 3d
First Timer Success: 75%
soimy/openclaw-channel-dingtalk has a recorded first-timer success rate of 75.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in soimy/openclaw-channel-dingtalk respond to incoming external pull requests in approximately 82.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 50.0 places soimy/openclaw-channel-dingtalk in the B tier.
The external contributor pull request merge rate for soimy/openclaw-channel-dingtalk is 70.3%, based on public PR activity from non-core contributors.
soimy/openclaw-channel-dingtalk currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Dingtalk channel plugin for OpenClaw
Responsive & active maintainer team in soimy/openclaw-channel-dingtalk. Reviews pull requests with focus on project architectural goals.
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/soimy/openclaw-channel-dingtalk?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 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~54 hours (88% approval). Large PRs (>500 lines) take ~396 hours (32% approval). Keep your diff compact for rapid review.
Bug 描述 调用 DingTalk channel 的 gateway method 时，所有请求都报错： pluginSdk.readStringParam is not a function 环境 OpenClaw 版本：2026.4.8（主程序） DingTalk 插件版本：@soimy/[email protected] 插件内嵌 openclaw SDK 版本：2026.3.13 根本原因 readStringParam 定义在 openclaw/agents/tools/common.js，在 SDK 2026.4.x 中有导出，但插件内嵌的 SDK 是 2026.3.13，缺少该 API。 插件代码（index.ts）调用： const accountId = pluginSdk.readStringParam(params, "accountId");
背景与问题概述 在钉钉群里发送doc，docx引用和支付都获取， Excel可以正常下载。 复现步骤 1.在钉钉群里发送doc，docx文档 2.使用引用@机器人人 3.日志看到"[引用了一个文件，但无法获取内容] 期望行为 机器人能够正常下载doc，docx文档 实际行为 [引用了一个文件，但无法获取内容] 发生范围 单聊和群聊都会发生 环境信息 3.5.1版本 相关日志、截图或补充信息 No response 提交前确认 我已搜索现有 Issue，暂未发现可直接合并的问题报告 我已对日志、截图、payload 中的敏感信息做过脱敏 我已阅读仓库中的 CONTRIBUTING 文档，并尽量补齐了定位所需信息
目前在钉钉中的引用消息只会传递id，是否能够支持获取引用消息内容？ 在钉钉中引用消息 对应消息在WebUI中的展示
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 soimy/openclaw-channel-dingtalk, 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 soimy/openclaw-channel-dingtalk acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.3% were successfully merged into the primary branch.
soimy/openclaw-channel-dingtalk has a recorded first-timer success rate of 75.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 days+. 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 50.0 places soimy/openclaw-channel-dingtalk in the Solid tier.
The external pull request merge rate is 70.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, soimy/openclaw-channel-dingtalk 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 soimy/openclaw-channel-dingtalk 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.