Python packaging made simple. Recommendations & guidance curated by the pyOpenSci community
C-Rank Grade: S (Elite) - 72/100
External PR Merge Rate: 87%
Response Time: 3h
First Timer Success: 100%
pyOpenSci/python-package-guide has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in pyOpenSci/python-package-guide respond to incoming external pull requests in approximately 2.5 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 71.7 places pyOpenSci/python-package-guide in the S tier.
The external contributor pull request merge rate for pyOpenSci/python-package-guide is 86.8%, based on public PR activity from non-core contributors.
pyOpenSci/python-package-guide currently has 50 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in pyOpenSci/python-package-guide. 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/pyOpenSci/python-package-guide?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 19:00 UTC (19:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 17:00 to 21:00 UTC (17:00 - 21: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 ~4 hours (96% approval). Large PRs (>500 lines) take ~12 hours (39% 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 Python.
Ultralytics YOLOv5 in PyTorch for object detection, instance segmentation, classification, training, and export.
Get AI to teach and answer questions for you - just by typing!
CISO Assistant is a one-stop-shop GRC platform for Risk Management, AppSec, Compliance & Audit, TPRM, BIA, Privacy, and Reporting. It supports 150+ global frameworks with automatic control mapping, including ISO 27001, NIST CSF, SOC 2, CIS, PCI DSS, NIS2, DORA, GDPR, HIPAA, CMMC, and more.
This issue is created automatically and should not be edited directly. This issue is for translating package-structure-code.po into Italian. It is one part of the larger effort tracked in the main issue: #717. Start there if you want the full picture and the setup steps. Thank you for helping! If this is your first open source contribution, you are in the right place. If you are working in one of our development sprints at a conference, someone from the pyOpenSci team will be available to help you get set up. Claim your lines To keep our work from overlapping, claim a range of lines before you start: Read the comments below to see which lines are already taken. Add a comment with the lines you will translate. You can copy this: I'm working on lines 1–100. When your part is ready, open a Pull Request and link back to this issue. You can see line numbers when you open the file on GitHub. If you are not sure how much you can take on, start with a small range. You can always claim
This issue is created automatically and should not be edited directly. This issue is for translating documentation.po into Italian. It is one part of the larger effort tracked in the main issue: #717. Start there if you want the full picture and the setup steps. Thank you for helping! If this is your first open source contribution, you are in the right place. If you are working in one of our development sprints at a conference, someone from the pyOpenSci team will be available to help you get set up. Claim your lines To keep our work from overlapping, claim a range of lines before you start: Read the comments below to see which lines are already taken. Add a comment with the lines you will translate. You can copy this: I'm working on lines 1–100. When your part is ready, open a Pull Request and link back to this issue. You can see line numbers when you open the file on GitHub. If you are not sure how much you can take on, start with a small range. You can always claim more late
This issue is created automatically and should not be edited directly. This issue is for translating maintain-automate.po into Italian. It is one part of the larger effort tracked in the main issue: #717. Start there if you want the full picture and the setup steps. Thank you for helping! If this is your first open source contribution, you are in the right place. If you are working in one of our development sprints at a conference, someone from the pyOpenSci team will be available to help you get set up. Claim your lines To keep our work from overlapping, claim a range of lines before you start: Read the comments below to see which lines are already taken. Add a comment with the lines you will translate. You can copy this: I'm working on lines 1–100. When your part is ready, open a Pull Request and link back to this issue. You can see line numbers when you open the file on GitHub. If you are not sure how much you can take on, start with a small range. You can always claim more
This issue is created automatically and should not be edited directly. This issue is for translating tests.po into Italian. It is one part of the larger effort tracked in the main issue: #717. Start there if you want the full picture and the setup steps. Thank you for helping! If this is your first open source contribution, you are in the right place. If you are working in one of our development sprints at a conference, someone from the pyOpenSci team will be available to help you get set up. Claim your lines To keep our work from overlapping, claim a range of lines before you start: Read the comments below to see which lines are already taken. Add a comment with the lines you will translate. You can copy this: I'm working on lines 1–100. When your part is ready, open a Pull Request and link back to this issue. You can see line numbers when you open the file on GitHub. If you are not sure how much you can take on, start with a small range. You can always claim more later. When
This issue is created automatically and should not be edited directly. This issue is for translating TRANSLATING.po into Italian. It is one part of the larger effort tracked in the main issue: #717. Start there if you want the full picture and the setup steps. Thank you for helping! If this is your first open source contribution, you are in the right place. If you are working in one of our development sprints at a conference, someone from the pyOpenSci team will be available to help you get set up. Claim your lines To keep our work from overlapping, claim a range of lines before you start: Read the comments below to see which lines are already taken. Add a comment with the lines you will translate. You can copy this: I'm working on lines 1–100. When your part is ready, open a Pull Request and link back to this issue. You can see line numbers when you open the file on GitHub. If you are not sure how much you can take on, start with a small range. You can always claim more later.
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 pyOpenSci/python-package-guide, 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 pyOpenSci/python-package-guide acknowledge new external contributions in approximately 2 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 86.8% were successfully merged into the primary branch.
pyOpenSci/python-package-guide has a recorded first-timer success rate of 100.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 71.7 places pyOpenSci/python-package-guide in the Elite tier.
The external pull request merge rate is 86.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, pyOpenSci/python-package-guide currently has 50 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for pyOpenSci/python-package-guide 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.