Integrate multiple LLM API providers into VS Code's GitHub Copilot Chat using the Language Model API. One-click use of your Claude Code, Gemini CLI, Antigravity, Github Copilot, OpenAI Codex (ChatGPT Plus/Pro), xAI Grok (SuperGrok / X Premium+) account quotas.
C-Rank Grade: A (Welcoming) - 55/100
External PR Merge Rate: 50%
Response Time: -
First Timer Success: -
smallmain/vscode-unify-chat-provider has a recorded first-timer success rate of 0.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in smallmain/vscode-unify-chat-provider 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 54.8 places smallmain/vscode-unify-chat-provider in the A tier.
The external contributor pull request merge rate for smallmain/vscode-unify-chat-provider is 50.0%, based on public PR activity from non-core contributors.
smallmain/vscode-unify-chat-provider currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Integrate multiple LLM API providers into VS Code's GitHub Copilot Chat using the Language Model API. One-click use of your Claude Code, Gemini CLI, Antigravity, Github Copilot, OpenAI Codex (ChatGPT Plus/Pro), xAI Grok (SuperGrok / X Premium+) account quotas.
Collaborative maintainer environment in smallmain/vscode-unify-chat-provider. Reviews community pull requests with focus on project quality.
Discussions in smallmain/vscode-unify-chat-provider focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/smallmain/vscode-unify-chat-provider?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (62% approval). Large PRs (>500 lines) take ~115 hours (22% approval). Keep your diff compact for rapid review.
如题，老黄的api是由rpm限制的，其实有些api也有rpm限制的，能不能多一个写rpm上限的网络控制选项，稍微调整一下避免很容易触发429
目前插件的功能主要集中在供应商的适配和接入, 只能通过输出面板查看请求的数据, 而且是以请求为单位的, 比如: Usage: {"input_tokens":26034,"input_tokens_details":{"cached_tokens":64},"output_tokens":131,"output_tokens_details":{"reasoning_tokens":0},"total_tokens":26165,"num_sources_used":0,"num_server_side_tools_used":0,"cost_in_usd_ticks":527388000} 是否考虑添加token相关的数据可视化展示呢? 缓存命中情况, 会话/天/周/月等不同周期的统计情况.
当前项目非常实用，简洁方便的配置管理，是我必装的插件之一了，也给很多朋友推荐。想提一个需求，即ACP协议的支持，目前我也有看见一些Demo可以参考，如：https://github.com/gayanper/vscode-acp-provider
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 smallmain/vscode-unify-chat-provider, 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 smallmain/vscode-unify-chat-provider acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 50.0% were successfully merged into the primary branch.
smallmain/vscode-unify-chat-provider has a recorded first-timer success rate of 0.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 54.8 places smallmain/vscode-unify-chat-provider in the Welcoming tier.
The external pull request merge rate is 50.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, smallmain/vscode-unify-chat-provider 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 smallmain/vscode-unify-chat-provider 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.