A backup application for the Android Open Source Project.
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 76%
Response Time: 2d
First Timer Success: 60%
seedvault-app/seedvault has a recorded first-timer success rate of 60.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in seedvault-app/seedvault respond to incoming external pull requests in approximately 46.3 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 60.3 places seedvault-app/seedvault in the A tier.
The external contributor pull request merge rate for seedvault-app/seedvault is 76.0%, based on public PR activity from non-core contributors.
seedvault-app/seedvault currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in seedvault-app/seedvault. 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/seedvault-app/seedvault?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 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~30 hours (95% approval). Large PRs (>500 lines) take ~222 hours (34% approval). Keep your diff compact for rapid review.
Prefacing with the fact that backing up my phone to my Nextcloud instance with WebDAV has been sturdy and solid for a while, I have the annoyance that Seedvault sends a lot of files to the trash bin when cleaning up backups. This clogs up the trash bin with files that aren't in my retention policy anymore, making it difficult to browse the bin normally. I don't want to completely disable trash bin retention, I still want that option for my user files. Nextcloud now supports WebDAV DELETEs without trashbin with a X-NC-Skip-Trashbin header. Issue PR It would be awesome to have Seedvault pass this custom header on DELETEs, at least as an opt-in. An expert setting for "custom WebDAV headers" would also work.
I am currently restoring a backup when lineageos 22 is first booted on a factory reset device. I noticed that the installing of apps does not progress once the screen turns off. I have to turn on the screen such that it moves forward. The screen goes off after a few seconds and the install phase is long, it takes probably 30 minutes or more. Also the screen turn off time at this stage of lineageos provisioning is hard coded, no way to increase it before running the seedvault restore. It would be nice if seedvault could restore apps without user interaction. As seedvault is a system app it should not be a problem to run even if the screen is off. I know that there was a bug in android in the past sometimes not fireing the 'app is installed' event resp. listeners were not notified. I don't know if seedvault has some polling mechanism additionally running to circumvent this. Maybe this polling mechanism is not executing when the screen is off, or the 'app is installed' event is not fired
I would really like to be able to use Seedvault, but I gave up on it years ago because it doesn't support any backends I'm able (or willing) to provide. And I see a whole bunch of requests for this or that backend, with most of them being things that probably have SAF providers available. The ones I would like to use definitely do. My understanding is that Seedvault actually works with many, most, or all SAF providers, but there's a hardcoded list of the ones it's willing to use. I've seen hints at three reasons for this: Worry that a backend won't be available when it's time to do a full restore. I don't think this is a good reason. Full restores are rare. It may be inconvenient, but it's not unreasonable to copy a backup repository to a USB stick if you need to restore it. It is unreasonable to have to use a USB stick for every incremental backup. And it's sometimes possible to provide a read-only view of a repository in a backend where it would be impossible to provide a read-write
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 seedvault-app/seedvault, 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 seedvault-app/seedvault acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 76.0% were successfully merged into the primary branch.
seedvault-app/seedvault has a recorded first-timer success rate of 60.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 60.3 places seedvault-app/seedvault in the Welcoming tier.
The external pull request merge rate is 76.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, seedvault-app/seedvault currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for seedvault-app/seedvault 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.