Dump the license list of packages installed with pip.
C-Rank Grade: B (Solid) - 59/100
External PR Merge Rate: 100%
Response Time: 19h
First Timer Success: 100%
raimon49/pip-licenses has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in raimon49/pip-licenses respond to incoming external pull requests in approximately 19.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 59.0 places raimon49/pip-licenses in the B tier.
The external contributor pull request merge rate for raimon49/pip-licenses is 100.0%, based on public PR activity from non-core contributors.
raimon49/pip-licenses currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in raimon49/pip-licenses 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/raimon49/pip-licenses?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 03:00 to 07:00 UTC (03:00 - 07:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~13 hours (96% approval). Large PRs (>500 lines) take ~93 hours (45% approval). Keep your diff compact for rapid review.
The Problem & Scope In the README.md (circa v5.5.5): pip-licenses/README.md Lines 122 to 157 in 2a8cfbc By default, this tool finds the license from [Trove Classifiers](https://pypi.org/classifiers/) or package Metadata. Some Python packages declare their license only in Trove Classifiers. (See also): [Set license to MIT in setup.py by alisianoi ・ Pull Request #1058 ・ pypa/setuptools](https://github.com/pypa/setuptools/pull/1058), [PEP 314\#License](https://www.python.org/dev/peps/pep-0314/#license) For example, even if you check with the `pip show` command, the license is displayed as `UNKNOWN`. ```bash
I suggest a single source of truth to document changes. Currently: CHANGELOG.md GitHub Releases page Wouldn't it make sense to avoid duplication? How about keeping GitHub Releases and discarding CHANGELOG.md? This would imply that: the contents of CHANGELOG.md are not appended to README.md any more, removing the need for a dynamic README while building sdist, and on the PyPI project page, changes would only be accessible through the existing Releases link - but that's what "all" projects do. Are repository maintainers able to modify release notes GitHub Releases page after the fact? I am asking because it would allow to align this page with the contents of CHANGELOG.md and then get rid of CHANGELOG.md.
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 raimon49/pip-licenses, 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 raimon49/pip-licenses acknowledge new external contributions in approximately 19 hours. 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.
raimon49/pip-licenses has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~19 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 59.0 places raimon49/pip-licenses in the Solid 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, raimon49/pip-licenses currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for raimon49/pip-licenses 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.