🌸Publish faster with an edge-native blog powered by Cloudflare Workers, D1, and R2
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 64%
Response Time: -
First Timer Success: 100%
openRin/Rin has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in openRin/Rin 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 60.2 places openRin/Rin in the A tier.
The external contributor pull request merge rate for openRin/Rin is 63.6%, based on public PR activity from non-core contributors.
openRin/Rin currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
🌸Publish faster with an edge-native blog powered by Cloudflare Workers, D1, and R2
Active TypeScript repository in openRin/Rin with ongoing community development and issue triage.
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/openRin/Rin?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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (80% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
问题描述 想讓朋友也登入來玩玩看, 不曉得是不是可以加入其他user? ADMIN_USERNAME2 ? 謝謝 复现步骤 N/A 期望行为 N/A 截图 No response 额外信息 No response
问题描述 有大佬知道吗？今天用豆包指导弄了好久，没成功403了。 复现步骤 cf不绑卡用不了s3 期望行为 谁能知道下，实现不了我也死心了 截图 No response 额外信息 No response
一切功能正常，没有设置R2、S3，至依托D1，大家可以去看看。 大家可以去看看我写的建站过程！
描述你遇到的问题 *问题如上，望指教 https://blog.776789.xyz
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 openRin/Rin, 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 openRin/Rin acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 63.6% were successfully merged into the primary branch.
openRin/Rin has a recorded first-timer success rate of 100.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 60.2 places openRin/Rin in the Welcoming tier.
The external pull request merge rate is 63.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, openRin/Rin currently has 6 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for openRin/Rin 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.