Open-source AI CLI and local MCP server connecting 25 clients—Claude Code, Cursor, Codex, ChatGPT, Hermes, and OpenClaw—to 2,000+ models/APIs, with OAuth and rollback.
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 98%
Response Time: <1h
First Timer Success: 100%
sandbaseai/cli 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 sandbaseai/cli respond to incoming external pull requests in approximately 0.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 65.4 places sandbaseai/cli in the A tier.
The external contributor pull request merge rate for sandbaseai/cli is 97.9%, based on public PR activity from non-core contributors.
sandbaseai/cli currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Open-source AI CLI and local MCP server connecting 25 clients—Claude Code, Cursor, Codex, ChatGPT, Hermes, and OpenClaw—to 2,000+ models/APIs, with OAuth and rollback.
Collaborative maintainer environment in sandbaseai/cli. Reviews community pull requests with focus on project quality.
Discussions in sandbaseai/cli 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/sandbaseai/cli?utm_source=github&utm_medium=badge)
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 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~1 hours (44% approval). Keep your diff compact for rapid review.
Goal Verify whether a clean Cline installation can configure and use the SandBase CLI v0.1.17 local MCP server using only the repository's README.md and/or llms-install.md. This evidence is required before SandBase can truthfully request inclusion in Cline's official MCP Marketplace. Test source Use the immutable GitHub Release artifact, not npm latest (which is still v0.1.14): npx -y https://github.com/sandbaseai/cli/releases/download/v0.1.17/sandbaseai-cli-0.1.17.tgz catalog --json Release: https://github.com/sandbaseai/cli/releases/tag/v0.1.17 Acceptance criteria Start from a clean or newly created Cline MCP configuration. Give Cline only README.md and/or llms-install.md as setup guidance. Record the exact Cline version and operating system. Confirm Cline can start the stdio MCP server and enumerate all six tools. Complete browser OAuth without placing credentials in an Issue, terminal transcript, screenshot, URL, or CLI argument. Successfully run a non-destructive discovery
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 sandbaseai/cli, 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 sandbaseai/cli acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 97.9% were successfully merged into the primary branch.
sandbaseai/cli 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 ~<1 hour. 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 65.4 places sandbaseai/cli in the Welcoming tier.
The external pull request merge rate is 97.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, sandbaseai/cli currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for sandbaseai/cli 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.