Self-hosted AI gateway for multi-channel, multi-credential setups — API keys and subscription accounts, scheduling, failover, request logs and usage. 自托管 AI 网关：多渠道多凭据统一接入，含密钥与订阅账号、调度容错、日志与用量。
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 65%
Response Time: 8h
First Timer Success: 50%
tbphp/gpt-load has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in tbphp/gpt-load respond to incoming external pull requests in approximately 8.1 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 68.4 places tbphp/gpt-load in the A tier.
The external contributor pull request merge rate for tbphp/gpt-load is 64.8%, based on public PR activity from non-core contributors.
tbphp/gpt-load currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in tbphp/gpt-load. Ensure PR scope matches issue requirements closely before requesting review.
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/tbphp/gpt-load?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 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~5 hours (81% approval). Large PRs (>500 lines) take ~39 hours (29% approval). Keep your diff compact for rapid review.
例行检查 / Checklist [ x ] 我已确认目前没有类似 issue (I have checked for similar issues) [ x ] 我已确认当前主版本线的最新补丁版本仍无法满足需求 (I have confirmed the latest patch release in my current major line does not meet this need) [ x ] 我已查看对应版本线的 README 和发布说明 (I have read the README and release notes for my release line) [ x ] 我不会在 issue 中提交任何凭据或令牌 (I will not include credentials or tokens in this issue) [ x ] 我理解并愿意跟进此 issue，协助测试和提供反馈 (I am willing to follow up on this issue, assist with testing, and provide feedback) 目标版本线 / Target Release Line 2.x，原生二进制部署。 功能描述 / Feature Description 希望为原生二进制部署增加内置自更新能力，让用户能够通过简单的命令或管理界面完成版本检查和升级，不必每次手动寻找发布文件、下载、替换二进制并处理重启。 这
例行检查 / Checklist [X ] 我已确认目前没有类似 issue (I have checked for similar issues) [X ] 我已确认当前主版本线的最新补丁版本仍无法满足需求 (I have confirmed the latest patch release in my current major line does not meet this need) [X ] 我已查看对应版本线的 README 和发布说明 (I have read the README and release notes for my release line) [ X] 我不会在 issue 中提交任何凭据或令牌 (I will not include credentials or tokens in this issue) [ X] 我理解并愿意跟进此 issue，协助测试和提供反馈 (I am willing to follow up on this issue, assist with testing, and provide feedback) 目标版本线 / Target Release Line 2.0 功能描述 / Feature Description 缺少查看详细请求体功能，1.0的时候我用来做报错纠正网关的，升级后无法查看请求体了 应用场景 / Use Case 使用日志里面应当记录 期望方案 / Desired Behavior 添加开关是否开启 兼容性、数据与
例行检查 / Checklist 我已确认目前没有类似 issue (I have checked for similar issues) 我已确认当前主版本线的最新补丁版本仍无法满足需求 (I have confirmed the latest patch release in my current major line does not meet this need) 我已查看对应版本线的 README 和发布说明 (I have read the README and release notes for my release line) 我不会在 issue 中提交任何凭据或令牌 (I will not include credentials or tokens in this issue) 我理解并愿意跟进此 issue，协助测试和提供反馈 (I am willing to follow up on this issue, assist with testing, and provide feedback) 目标版本线 / Target Release Line 2.x； 功能描述 / Feature Description 希望支持更多类型的计费模式 分时段（峰谷）定价：同一模型在不同时间段使用不同单价或折扣倍率 2.按次 / 按量计费：生图等非 token 计量的模型按“张”或“次”收费 应用场景 / Use Case 使用 DeepSeek 这
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 tbphp/gpt-load, 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 tbphp/gpt-load acknowledge new external contributions in approximately 8 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 64.8% were successfully merged into the primary branch.
tbphp/gpt-load has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~8 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 68.4 places tbphp/gpt-load in the Welcoming tier.
The external pull request merge rate is 64.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, tbphp/gpt-load 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 tbphp/gpt-load 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.