Torrent / Usenet / NZB container stack with VPN (ProtonVPN) to be run by Docker Compose
C-Rank Grade: B (Solid) - 62/100
External PR Merge Rate: 70%
Response Time: <1h
First Timer Success: 100%
ivan-pinatti/docker-torrent-box-with-vpn 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 ivan-pinatti/docker-torrent-box-with-vpn respond to incoming external pull requests in approximately 0.6 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 62.2 places ivan-pinatti/docker-torrent-box-with-vpn in the B tier.
The external contributor pull request merge rate for ivan-pinatti/docker-torrent-box-with-vpn is 70.0%, based on public PR activity from non-core contributors.
ivan-pinatti/docker-torrent-box-with-vpn currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Python project in ivan-pinatti/docker-torrent-box-with-vpn 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/ivan-pinatti/docker-torrent-box-with-vpn?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
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.
pi-stomp is a DIY high definition, multi-effects stompbox platform for guitar, bass and keyboards
A standard format for offline reinforcement learning datasets, with popular reference datasets and related utilities
Metapackage of Scikit-HEP project data analysis packages for Particle Physics.
What this is A reusable workflow in linuxserver/github-workflows appears to be broken for every fork pull request across their organisation, not only for ours. It is worth reporting where the workflow lives, because nothing in a contributor's branch can fix it. The diagnosis Their init-svc-executable-permissions.yml@v1 runs actions/[email protected] with ref: github.event.pull_request.head.sha from a pull_request_target caller. Checkout 7.0.1 refuses a fork checkout in that context unless allow-unsafe-pr-checkout: true is set. The job therefore dies before reading a single file. It is not evaluating permissions and failing; it never gets far enough to look. How it surfaced A pull request submitted to linuxserver/docker-sabnzbd shows red because of it. The file that pull request touches is already mode 100755, so the check passes as soon as it can actually run. The red is entirely the checkout step. Because the cause is the caller's checkout configuration rather than anything in the contr
The problem CodeRabbit does not automatically review pull requests opened by renovate[bot] or dependabot[bot]. Measured across #53 to #76: a CodeRabbit status appeared on 8 of 8 human pull requests and 1 of 16 bot ones. The single exception was #56, where a review was asked for by hand with @coderabbitai review and arrived in under three minutes. Two explanations were ruled out before raising it: Not rate limiting. Four of the human statuses read Review rate limited, so a throttled review still posts a status. The bot pull requests post nothing at all. Not configuration. reviews.auto_review.ignore_usernames is at its empty default, and the published schema has no other setting that suppresses a review. Why it matters here Bot pull requests are exactly where a reading matters most. They merge unattended, and the intent was for CodeRabbit to act as a quality and security gate on them: to catch a bot pull request that modifies something other than a version pin, such as an injected chan
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 ivan-pinatti/docker-torrent-box-with-vpn, 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 ivan-pinatti/docker-torrent-box-with-vpn acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.0% were successfully merged into the primary branch.
ivan-pinatti/docker-torrent-box-with-vpn 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 ~<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 62.2 places ivan-pinatti/docker-torrent-box-with-vpn in the Solid tier.
The external pull request merge rate is 70.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ivan-pinatti/docker-torrent-box-with-vpn 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 ivan-pinatti/docker-torrent-box-with-vpn 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.