An AI Assistant that’s easy to setup, does your work 24/7, knows your preferences and gets better over time.
C-Rank Grade: S (Elite) - 80/100
External PR Merge Rate: 92%
Response Time: 11h
First Timer Success: 79%
vellum-ai/vellum-assistant has a recorded first-timer success rate of 78.8%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in vellum-ai/vellum-assistant respond to incoming external pull requests in approximately 10.7 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 80.0 places vellum-ai/vellum-assistant in the S tier.
The external contributor pull request merge rate for vellum-ai/vellum-assistant is 92.5%, based on public PR activity from non-core contributors.
vellum-ai/vellum-assistant currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
An AI Assistant that’s easy to setup, does your work 24/7, knows your preferences and gets better over time.
Strict review standards in vellum-ai/vellum-assistant. 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/vellum-ai/vellum-assistant?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 19:00 UTC (19:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~7 hours (96% approval). Large PRs (>500 lines) take ~51 hours (42% approval). Keep your diff compact for rapid review.
Problem or use case Feature request: please add Cartesia as a supported TTS provider. Context: we're setting up phone calling (Twilio ConversationRelay) and have been evaluating TTS options for real-time voice. Cartesia is purpose-built for low-latency synthesis and is widely considered the benchmark for real-time voice applications — sub-100ms TTFB, optimized for conversational back-and-forth. It's a natural fit for the phone calling use case. Current supported providers (ElevenLabs, Fish Audio, Deepgram, xAI) are solid but Cartesia specifically targets the latency requirements that matter most for phone calls. Proposed solution No response Alternatives considered No response Additional context No response
Update Jun 30, 2026: The Swift paths referenced below are stale. The macOS UI moved off SwiftUI onto an Electron shell rendering the React web app, so IntegrationDetailModal.swift / SettingsStore.swift / startManagedOAuthConnect no longer exist. The daemon + IPC plumbing this issue suggested (steps 2-3 below) is already done; only the web UI picker remains. See this comment for the updated file map. The body below is kept for context. Goal Let guardians explicitly choose OAuth scopes from the Integrations UI before clicking Connect, instead of always falling back to the provider's defaults. Today ✅ The assistant can negotiate scopes conversationally at connection time. ✅ After a connection is made, the Integrations UI displays the scopes that were actually granted. ❌ The Connect button in the Integrations modal always uses the provider's default scopes — there is no UI to pick scopes ahead of time. What we want A scope-picker section in the Integrations connection modal that
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 vellum-ai/vellum-assistant, 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 vellum-ai/vellum-assistant acknowledge new external contributions in approximately 10 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 92.5% were successfully merged into the primary branch.
vellum-ai/vellum-assistant has a recorded first-timer success rate of 78.8%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~10 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 80.0 places vellum-ai/vellum-assistant in the Elite tier.
The external pull request merge rate is 92.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, vellum-ai/vellum-assistant 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 vellum-ai/vellum-assistant 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.