Open source Dropbox-like file sharing with full client encryption !
C-Rank Grade: S (Elite) - 75/100
External PR Merge Rate: 89%
Response Time: 20h
First Timer Success: 100%
Scille/parsec-cloud has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Scille/parsec-cloud respond to incoming external pull requests in approximately 20.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 75.2 places Scille/parsec-cloud in the S tier.
The external contributor pull request merge rate for Scille/parsec-cloud is 89.4%, based on public PR activity from non-core contributors.
Scille/parsec-cloud currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in Scille/parsec-cloud. Prompt code reviews with positive guidance for new contributors.
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/Scille/parsec-cloud?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~13 hours (96% approval). Large PRs (>500 lines) take ~96 hours (40% approval). Keep your diff compact for rapid review.
Dependabot's docker-compose updates are not working. This is because the file is named parsec-server.docker.yaml, but the dependabot requires the file to be named something like docker-compose*.yml (see docker/lib/dependabot/docker_compose/file_fetcher.rb#L9). There are requests for relaxing the regex, but it seems that the (docker-)compose prefix would still be kept. So, the easiest fix would be to rename the file something like: docker-compose.parsec-server.yaml /!\ There are many references to this file in the docs. Once changed, you can check if dependabot config is working from the following link: https://github.com/Scille/parsec-cloud/network/updates
Currently when an admin-sys want to expired an organization, it need to set is_expired in the datamodel to true but _expired_on is not updated. We should instead only rely on _expired_on since we can achieve the same behavior as with is_expired. This does not need to break the existing API has we can easily set _expired_on to now() when patching is_expired is true. And similarly, we can return is_expired if the date is due.
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 Scille/parsec-cloud, 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 Scille/parsec-cloud acknowledge new external contributions in approximately 20 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 89.4% were successfully merged into the primary branch.
Scille/parsec-cloud has a recorded first-timer success rate of 100.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~20 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 75.2 places Scille/parsec-cloud in the Elite tier.
The external pull request merge rate is 89.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Scille/parsec-cloud 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 Scille/parsec-cloud 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.