Modern, extensible Python project management
C-Rank Grade: B (Solid) - 54/100
External PR Merge Rate: 16%
Response Time: 2h
First Timer Success: 50%
pypa/hatch has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in pypa/hatch respond to incoming external pull requests in approximately 1.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 54.5 places pypa/hatch in the B tier.
The external contributor pull request merge rate for pypa/hatch is 16.0%, based on public PR activity from non-core contributors.
pypa/hatch currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in pypa/hatch. Reviews community pull requests with focus on project quality.
Discussions in pypa/hatch focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/pypa/hatch?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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (20% approval). Large PRs (>500 lines) take ~9 hours (15% approval). Keep your diff compact for rapid review.
Description refresh of #1775 Could we add support for an environment variable to override some hard coded url's in Hatch? (from https://docs.astral.sh/uv/configuration/environment/) ? This could help with #1596 The use case is within #1596 , where Python distributed binaries are pulled from 'https://github.com/indygreg/python-build-standalone/releases/download/' . I would like to override this URL for one relevant to my environment. Note: this is an old request and perhaps something got changed since the initial request. Use case/motivation No response Related issues No response Are you willing to submit a PR? Yes I am willing to submit a PR! Code of Conduct I agree to follow the Python Software Foundation's Code of Conduct
Description When creating a new project with hatch new, create a default .gitignore file. A very minimal .gitignore can be: __pycache__/ dist/ Use case/motivation A well-prepared standard .gitignore that helps a hatch user getting start quicker with Python development with Git. More can be added manually by the user to fits their needs, but at least the .gitignore is there to edit. Related issues This isssue is a reopen of #667 Are you willing to submit a PR? Yes I am willing to submit a PR! Code of Conduct I agree to follow the Python Software Foundation's Code of Conduct
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 pypa/hatch, 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 pypa/hatch acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 16.0% were successfully merged into the primary branch.
pypa/hatch has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 54.5 places pypa/hatch in the Solid tier.
The external pull request merge rate is 16.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, pypa/hatch 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 pypa/hatch 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.