An open source utility that provides fast incremental file transfer. It also has useful features for backup and restore operations among many other use cases.
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 71%
Response Time: 2h
First Timer Success: 100%
RsyncProject/rsync has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in RsyncProject/rsync respond to incoming external pull requests in approximately 2.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 67.6 places RsyncProject/rsync in the A tier.
The external contributor pull request merge rate for RsyncProject/rsync is 71.0%, based on public PR activity from non-core contributors.
RsyncProject/rsync does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Active maintainer team in RsyncProject/rsync 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/RsyncProject/rsync?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (89% approval). Large PRs (>500 lines) take ~10 hours (32% approval). Keep your diff compact for rapid review.
Motivation Rsync's existing transfer statistics report the amount of data transferred, but that alone does not describe the logical write footprint of a delta update. For workloads such as large database files, VM images, or other files where relatively small changes are scattered across a large file, the number of bytes changed and the number of storage-sized regions touched can be quite different. For example, a transfer might modify only 1 MiB of data while requiring writes spread across hundreds of separate 4 KiB regions. Reporting only the number of bytes transferred does not make that distinction visible. Proposed feature Add a statistic to --stats reporting the number of unique 4 KiB logical file blocks touched by rsync's own write operations. For example: Literal data written: 1.0 MiB 4 KiB logical blocks touched: 256 The statistic would count each 4 KiB logical block at most once for a given file, even if rsync writes to that block multiple times during the operation.
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 RsyncProject/rsync, 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 RsyncProject/rsync acknowledge new external contributions in approximately 2 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 71.0% were successfully merged into the primary branch.
RsyncProject/rsync has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming 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 67.6 places RsyncProject/rsync in the Welcoming tier.
The external pull request merge rate is 71.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
RsyncProject/rsync does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for RsyncProject/rsync 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.