An open-source multi-provider AI assisted CLI development tool. Use whatever LLM you want to code in your terminal.
C-Rank Grade: S (Elite) - 74/100
External PR Merge Rate: 96%
Response Time: 12h
First Timer Success: 75%
vybestack/llxprt-code has a recorded first-timer success rate of 75.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in vybestack/llxprt-code respond to incoming external pull requests in approximately 11.8 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 74.0 places vybestack/llxprt-code in the S tier.
The external contributor pull request merge rate for vybestack/llxprt-code is 96.0%, based on public PR activity from non-core contributors.
vybestack/llxprt-code currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
An open-source multi-provider AI assisted CLI development tool. Use whatever LLM you want to code in your terminal.
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/vybestack/llxprt-code?utm_source=github&utm_medium=badge)
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
What would you like to be added? Make a mode for LLxprt like the ! mode maybe we make it < mode. IN this mode you can only use the tool calls as if you were the agent. A few "niceties" are added so you don't have to hand-format JSON, but if you want to list a directory, you have to use the tool call, and what you see is what the LLM sees. Additionally what shows in the scroll area is the LLM context. If it compresses, that's waht you see the compressed version. you can scroll up and down to the whole context but...that's what you see. No more, no less. Why is this needed? The goal is to understand how the model sees things and tune our tools as needed. This is largely a development and diagnostic tool. However, you can't really empathize with that @!#!$@ model unless you see why it had a hard time. Additional context No response
What would you like to be added? A way to automatically preserve prior file states when core editing tools modify files, so users can restore a previous version if an edit goes wrong. Why is this needed? Edits can easily introduce syntax errors or unwanted changes, and relying on git commits for every attempt is heavy. Having automatic snapshots improves safety and confidence when using editing tools. Additional context No response
What would you like to be added? JetBrains IDEs (e.g. PHPStorm) support Why is this needed? it is one of the most widely used IDE family Additional context No response
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 vybestack/llxprt-code, 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 vybestack/llxprt-code acknowledge new external contributions in approximately 11 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 96.0% were successfully merged into the primary branch.
vybestack/llxprt-code has a recorded first-timer success rate of 75.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~11 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 74.0 places vybestack/llxprt-code in the Elite tier.
The external pull request merge rate is 96.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, vybestack/llxprt-code 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 vybestack/llxprt-code 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.