🐉 Vue Component Framework
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 42%
Response Time: 13h
First Timer Success: 44%
vuetifyjs/vuetify has a recorded first-timer success rate of 44.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in vuetifyjs/vuetify respond to incoming external pull requests in approximately 12.9 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 59.8 places vuetifyjs/vuetify in the A tier.
The external contributor pull request merge rate for vuetifyjs/vuetify is 42.0%, based on public PR activity from non-core contributors.
vuetifyjs/vuetify currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (75% critical review signals). Ensure PRs strictly follow guidelines before requesting review in vuetifyjs/vuetify.
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/vuetifyjs/vuetify?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~8 hours (53% approval). Large PRs (>500 lines) take ~62 hours (19% approval). Keep your diff compact for rapid review.
Problem to solve Currently, users can navigate the v-carousel using touch swipe gestures, navigation arrows, or pagination dots. However, desktop users frequently rely on their mouse wheel or trackpad scroll to navigate through horizontal galleries or sliding content. When a desktop user hovers over a large carousel and instinctively scrolls their mouse wheel, nothing happens (or the whole page scrolls, depending on the layout). This breaks the expected user experience, especially in full-screen image galleries, presentations, or horizontal content sliders where mouse-wheel navigation is an industry standard. While touch devices are well-supported, desktop interaction feels incomplete without wheel support. Proposed solution I propose adding a native wheel event listener to the v-carousel (or the underlying v-window component) to allow users to scroll through items.
Environment Vuetify Version: 3.11.7 Vue Version: 3.5.27 OS: macOS 10.15.7 (current) Steps to reproduce Use VoiceOver with Safari Open VMenu Navigate to menu item Expected Behavior VoiceOver reads out the labels, e.g. "Click Me, menu item" Actual Behavior VoiceOver only reads out "menu item" without the labels. (For Testing) Remove aria-owns form the DOM, then labels are there. Reproduction Link https://play.vuetifyjs.com/#... Other comments It seems like this commit 975a18c introduced the bug to Safari. In Chrome everything works. Vuetify 3.10.7 is the last working version for Safari.
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 vuetifyjs/vuetify, 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 vuetifyjs/vuetify acknowledge new external contributions in approximately 12 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 42.0% were successfully merged into the primary branch.
vuetifyjs/vuetify has a recorded first-timer success rate of 44.4%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~12 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 59.8 places vuetifyjs/vuetify in the Welcoming tier.
The external pull request merge rate is 42.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, vuetifyjs/vuetify 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 vuetifyjs/vuetify 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.