L Harness — self-hosted LINE Official Account CRM: step messaging, broadcasts, forms and reservations, with MCP and TypeScript SDK. By Shudesu (野田修一).
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 57%
Response Time: -
First Timer Success: 25%
Shudesu/line-harness-oss has a recorded first-timer success rate of 25.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Shudesu/line-harness-oss 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 61.3 places Shudesu/line-harness-oss in the A tier.
The external contributor pull request merge rate for Shudesu/line-harness-oss is 57.3%, based on public PR activity from non-core contributors.
Shudesu/line-harness-oss currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
L Harness — self-hosted LINE Official Account CRM: step messaging, broadcasts, forms and reservations, with MCP and TypeScript SDK. By Shudesu (野田修一).
Balanced & professional review environment in Shudesu/line-harness-oss. Maintains strict focus on technical quality and test standards.
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/Shudesu/line-harness-oss?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 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (72% approval). Large PRs (>500 lines) take ~115 hours (26% approval). Keep your diff compact for rapid review.
いつもありがとうございます。 オープンソースで非常に強力なツールを公開・メンテしてくださっていること、本当に助かっています。 その上で、一つ機能要望としてご検討いただけたら嬉しい点があり、共有させてください。 ユースケース 本番リリース前のリハーサルテストや、新規導線・シナリオ動作確認の際に、 特定の友だちレコードを「初期状態」に戻して再検証したい場面があります。 現在は管理画面・MCP のどちらにも友だち削除手段がなく、 Cloudflare D1 を直接 SQL で触る以外に方法がない状態です。 参考までに、競合の LINE マーケティングツール（エルメ系）では 友だちリストから個別に削除できる UI があり、テスト工程で重宝していました。 ご検討いただきたい機能 優先度の高い順に： 管理画面の友だち詳細画面に「
Problem In the operator chat list, there is no way to tell which chats have received new messages since you last viewed them. The status badge (未読/対応中/解決済) is a manual operator status, not an automatic new-message indicator There is no unread count, "NEW" badge, or visual highlight for chats with new incoming messages Opening a chat does not automatically mark it as read — the operator must manually change the status Expected behavior Chats with new incoming messages should show a visual indicator (e.g., bold text, dot badge, or unread count) Viewing a chat should automatically transition status from "未読" to "対応中" File apps/web/src/app/chats/page.tsx — chat list rendering (L455-486)
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 Shudesu/line-harness-oss, 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 Shudesu/line-harness-oss acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 57.3% were successfully merged into the primary branch.
Shudesu/line-harness-oss has a recorded first-timer success rate of 25.0%. 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 61.3 places Shudesu/line-harness-oss in the Welcoming tier.
The external pull request merge rate is 57.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Shudesu/line-harness-oss currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for Shudesu/line-harness-oss 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.