Auditing and relabeling cross-distribution Linux wheels.
C-Rank Grade: B (Solid) - 43/100
External PR Merge Rate: 50%
Response Time: <1h
First Timer Success: -
pypa/auditwheel has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in pypa/auditwheel respond to incoming external pull requests in approximately 0.0 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 43.0 places pypa/auditwheel in the B tier.
The external contributor pull request merge rate for pypa/auditwheel is 50.0%, based on public PR activity from non-core contributors.
pypa/auditwheel currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in pypa/auditwheel 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/pypa/auditwheel?utm_source=github&utm_medium=badge)
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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 14:00 to 18:00 UTC (14:00 - 18: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 (62% approval). Large PRs (>500 lines) take ~0 hours (22% 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.
SVG (vector) files for all Magic the Gathering set, watermark, and miscellaneous symbols.
Type hints → Web UI. Turn Python functions into web apps — standalone or mounted inside yours.
STELLA: Self-Evolving LLM Agent for Biomedical Research
Hi there! I'm opening this for consideration. For better or worse, some people like to manually patch their wheels after they're built by a normal, well-behaved build backend. Sometimes this means that they modify their wheel tags without updating the corresponds Tag: fields in .dist-info/WHEEL, or update those fields incorrectly (e.g. by doing Tag: <compressed-tag> instead of one Tag: per expanded compatibility tag. It'd be great if auditwheel could detail these (and repair them, where possible) 🙂 For reference, I've made some misshapen wheels that exhibit these behaviors: futzed_dist_info_wheel_tag_invalid-0.1.0-py3-none-any.whl demonstrates a tag inconsistency/invalidity (valid tags in the filename, but the Tag: in the WHEEL file is junk) futzed_dist_info_wheel_tag_missing-0.1.0-py3-none-any.whl demonstrates the Tag: being missing entirely from the WHEEL file (More broadly, these and others are all detected by a consistency check between the wheel filename's expanded tags and t
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/auditwheel, 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/auditwheel acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 50.0% were successfully merged into the primary branch.
pypa/auditwheel has a recorded first-timer success rate of 0.0%. Repositories ranked Solid 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 43.0 places pypa/auditwheel in the Solid tier.
The external pull request merge rate is 50.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, pypa/auditwheel 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 pypa/auditwheel 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.