⚡ A fast Git hook manager written in Rust, designed as a drop-in alternative to pre-commit, reimagined.
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 86%
Response Time: 3d
First Timer Success: 60%
j178/prek 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 j178/prek respond to incoming external pull requests in approximately 78.3 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 60.1 places j178/prek in the A tier.
The external contributor pull request merge rate for j178/prek is 86.3%, based on public PR activity from non-core contributors.
j178/prek currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
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/j178/prek?utm_source=github&utm_medium=badge)
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Follow-up to #1594, #1596. prek resolves the Python version for hook venvs using: PEP 723 > user config > requires-python from pyproject.toml > default (Any) (i.e. let uv decide). This works when the hook or repo explicitly declares its Python requirement, but doesn't handle transitive constraints — when a hook's deps require a narrower range than what's declared, or nothing is declared at all. Example: hook foo has no requires-python, but its dep bar requires >=3.10. prek can't know this upfront, so uv's default version selection is used when calling uv venv create. Depending on previously installed uv versions, the venv may be created with a Python that's too old and uv pip install fails. uv handles this in uvx/uv tool install via refine_interpreter(): when resolution fails with NoSolution, it extracts a Python bound from the error, recreates the environment, and retries. The retry is cheap since uv's HTTP cache already has all the metadata from the failed attempt. It's heuristic a
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 j178/prek, 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 j178/prek acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 86.3% were successfully merged into the primary branch.
j178/prek 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 ~3 days+. 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 60.1 places j178/prek in the Welcoming tier.
The external pull request merge rate is 86.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, j178/prek 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 j178/prek 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.