A simple, extensible LLM client for Emacs
C-Rank Grade: D (Risky) - 17/100
External PR Merge Rate: -
Response Time: 2d
First Timer Success: -
karthink/gptel has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in karthink/gptel respond to incoming external pull requests in approximately 36.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 17.3 places karthink/gptel in the D tier.
The external contributor pull request merge rate for karthink/gptel is 0.0%, based on public PR activity from non-core contributors.
karthink/gptel currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in karthink/gptel. Prompt code reviews with positive guidance for new contributors.
Discussions in karthink/gptel 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/karthink/gptel?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 Wednesday - Friday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~24 hours (81% approval). Large PRs (>500 lines) take ~175 hours (29% approval). Keep your diff compact for rapid review.
gptel/gptel-openai.el Lines 240 to 243 in e505a9d (when gptel-max-tokens ;; HACK: The OpenAI API has deprecated max_tokens, but we still need it ;; for OpenAI-compatible APIs like GPT4All (#485) (plist-put prompts-plist :max_tokens gptel-max-tokens)) This causes errors with self-hosted GPT-5 when combined with gptel-agent: https://github.com/karthink/gptel-agent/blob/b90d59531783ed18fd91da0c14d053bc3e0e8df7/gptel-agent.el#L515 Really not sure which repo this belongs in, but this seems more like a gptel issue to me.
If you use the Bedrock backend, I need your help. Please try editing a tool call and let me know if it works. Here's how to do it. Procure and enable some gptel-tool(s). Any tools. (setq gptel-confirm-tool-calls t) and (setq gptel-include-tool-results t). Make an LLM request in a buffer that generates a tool call. The tool confirmation UI will show up. Press C-c C-i or C-c TAB (same thing) to edit the tool call. Edit the tool call arguments and confirm the tool call. (You can also edit the tool name, changing the tool call entirely, but the rest of the call will have to be consistent.) Check the result in the buffer to see if the tool was called with the modified arguments.
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 karthink/gptel, 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 karthink/gptel acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
karthink/gptel has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 17.3 places karthink/gptel in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, karthink/gptel 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 karthink/gptel 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.