Yet another Yogurt - An AUR Helper written in Go
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 77%
Response Time: 10h
First Timer Success: 60%
Jguer/yay has a recorded first-timer success rate of 60.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Jguer/yay respond to incoming external pull requests in approximately 10.2 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 64.4 places Jguer/yay in the A tier.
The external contributor pull request merge rate for Jguer/yay is 76.7%, based on public PR activity from non-core contributors.
Jguer/yay currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in Jguer/yay. Prompt code reviews with positive guidance for new contributors.
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/Jguer/yay?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~7 hours (96% approval). Large PRs (>500 lines) take ~49 hours (35% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Go.
go library for processing container images and simulating a squash filesystem
Go library for the VMware vSphere API
Fast-track AI innovation with a centralized, trusted, curated registry
Is your feature request related to a problem? Please describe. When using yay -Gp <package>, yay prints the fetched PKGBUILD to stdout as plain text. This is useful for quickly inspecting a package without cloning it, but repeated PKGBUILD inspection is harder than it needs to be because the output is not syntax-highlighted. A one-off flag is not very useful here because users can already write: yay -Gp <package> | bat --language bash --style=plain --paging=never The missing piece is a persistent yay configuration option so users can configure their preferred PKGBUILD viewer once and then simply run: yay -Gp yay and get highlighted output automatically. Describe the solution you would like Add a config option for the command used to display PKGBUILD output from yay -Gp, for example: PkgbuildPager = bat --language bash --style=plain --paging=never or an equivalent JSON/config key if that better matches the current configuration format. When the option is unset, yay -Gp should keep the c
When updating, yay always ask which packages to exclude, and pressing Enter while leaving it empty does not exclude any package. I'd like to have an option in the config file so I can always "not exclude", therefore the prompt doesn't appear and it always updates all AUR packages. Thanks.
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 Jguer/yay, 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 Jguer/yay acknowledge new external contributions in approximately 10 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 76.7% were successfully merged into the primary branch.
Jguer/yay has a recorded first-timer success rate of 60.0%. Repositories ranked Welcoming 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 64.4 places Jguer/yay in the Welcoming tier.
The external pull request merge rate is 76.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Jguer/yay 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 Jguer/yay 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.