Fast TUI for searching, inspecting, and queueing pacman/AUR packages.
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 100%
Response Time: <1h
First Timer Success: 100%
Firstp1ck/Pacsea 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 Firstp1ck/Pacsea 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 61.8 places Firstp1ck/Pacsea in the A tier.
The external contributor pull request merge rate for Firstp1ck/Pacsea is 100.0%, based on public PR activity from non-core contributors.
Firstp1ck/Pacsea currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in Firstp1ck/Pacsea welcoming community pull requests and bug fixes.
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/Firstp1ck/Pacsea?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Monday - Friday from 00:00 to 04:00 UTC (00:00 - 04: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 (45% approval). Keep your diff compact for rapid review.
Summary Some tracked files in this repo currently have executable mode (100755) even though they are not executed directly in our workflow. We run Bash/Fish scripts via ./..., so executable bits on *.sh / *.fish are intentional. Python scripts are run via uv or python ..., so +x is unnecessary for those files. Affected files dev/scripts/check_translation_keys.py dev/scripts/update_version_announcement.py Why this matters Reduces noisy permission-only diffs and review comments. Keeps file modes aligned with actual execution patterns. Improves repo consistency. Proposed fix Change both files from executable (100755) to regular (100644) and commit the mode change only. Acceptance criteria Both Python files are 100644 in git. No content changes, only permission/mode changes. Bash/Fish scripts remain executable where needed.
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 Firstp1ck/Pacsea, 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 Firstp1ck/Pacsea acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
Firstp1ck/Pacsea 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 61.8 places Firstp1ck/Pacsea in the Welcoming tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Firstp1ck/Pacsea 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 Firstp1ck/Pacsea 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.