Source code of the recurrent donations platform Liberapay
C-Rank Grade: B (Solid) - 42/100
External PR Merge Rate: 15%
Response Time: 23d
First Timer Success: -
liberapay/liberapay.com 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 liberapay/liberapay.com respond to incoming external pull requests in approximately 553.1 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 42.3 places liberapay/liberapay.com in the B tier.
The external contributor pull request merge rate for liberapay/liberapay.com is 15.4%, based on public PR activity from non-core contributors.
liberapay/liberapay.com currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active Python repository in liberapay/liberapay.com with ongoing community development and issue triage.
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/liberapay/liberapay.com?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 13:00 to 17:00 UTC (13:00 - 17: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 ~359 hours (19% approval). Large PRs (>500 lines) take ~2655 hours (15% 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.
Access large language models from the command-line
A command line VNC client and python library
An open source model gateway that provides one control plane across closed, open-source, local, and custom models.
This was already noted in #688, but I forgot to do it in #2511. Bearer tokens should be easy to recognize so that machines can detect them and thus be able to prevent or remediate leaks. Liberapay should probably start using the generic RFC 8959 prefix secret-token: followed by the brand prefix lp_. To avoid breaking existing sessions, the new prefix should only be required for newly generated secrets. To avoid wasting space, the secrets should continue to be stored without the prefix in the database. It looks like GitHub's secret scanning partner program isn't open source, so Liberapay probably shouldn't join it. The list of patterns should be a common that everyone can use, contribute to and fork, not a private database belonging to Microsoft.
The liberapay/payin/paypal.py file should be modified so that API requests are retried automatically once or twice before giving up and raising an exception. This would prevent some payments from failing when a transient network or hardware failure occurs. (The stripe module already retries requests automatically.)
Liberapay supports automatic conversion between Traditional and Simplified Chinese texts thanks to OpenCC. Sadly, that library is unsafe. Ideally it would be rewritten in a safe programming language, but in the meantime Liberapay should be modified to only use it in sandboxed sub-processes.
We've been pinged on Mastodon about a relatively new standard I wasn't aware of: https://fundingjson.org/ The possible use of it I can think of right now is the automatic verification that a Liberapay account and a repository or website are controlled by the same person. Relevant issues: #661, #943 and #2425 for repositories, #1034 for websites.
Hello, my problem is that the markdown logo is a bit to aggressive. See this example which is generated via this markdown code: [](https://liberapay.com/buhtz/donate) It is like a command: "Donate!" (or die). It is not polite. I would prefer to delete the "Donate" string and add something like Liberapay Support Support me on Liberapay (or something else) The Ko-fi button in the screenshot is a good example I think. There still might be some other svg files on your server. But I am not allowed to list the content of https://liberapay.com/assets/widgets/. And your logo page does not list that files.
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 liberapay/liberapay.com, 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 liberapay/liberapay.com acknowledge new external contributions in approximately 23 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 15.4% were successfully merged into the primary branch.
liberapay/liberapay.com 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 ~23 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 42.3 places liberapay/liberapay.com in the Solid tier.
The external pull request merge rate is 15.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, liberapay/liberapay.com currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for liberapay/liberapay.com 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.