Backup and migrate Kubernetes applications and their persistent volumes
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 65%
Response Time: 1d
First Timer Success: 48%
velero-io/velero has a recorded first-timer success rate of 48.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in velero-io/velero respond to incoming external pull requests in approximately 28.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 63.9 places velero-io/velero in the A tier.
The external contributor pull request merge rate for velero-io/velero is 64.6%, based on public PR activity from non-core contributors.
velero-io/velero currently has 9 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (77% critical review signals). Ensure PRs strictly follow guidelines before requesting review in velero-io/velero.
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/velero-io/velero?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 07:00 UTC (07: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 ~18 hours (81% approval). Large PRs (>500 lines) take ~135 hours (29% approval). Keep your diff compact for rapid review.
Environment velero-plugin-for-aws: v1.14.3 (docker.io image, initContainer) velero server: v1.18.2 (Helm chart velero 12.2.0) Object storage: Backblaze B2, S3-compatible endpoint (s3.<region>.backblazeb2.com), s3ForcePathStyle: true BackupStorageLocation.spec.config does not set tagging (left unset/empty) What happened Every scheduled backup (daily + weekly, defaultVolumesToFsBackup: true, kopia uploader) failed at the final metadata-upload step, over multiple days, while running velero-plugin-for-aws:v1.14.3: error putting object velero/backups/<backup-name>/velero-backup.json: operation error S3: PutObject, https response error StatusCode: 400, api error InvalidArgument: Unsupported header 'x-amz-tagging' received for this API call. The per-volume PodVolumeBackup data itself uploaded successfully each time (confirmed via PodVolumeBackup.status.phase: Completed with correct sizes, and later via a direct kopia snapshot restore against the repository). Only the final PutObject for ve
What steps did you take and what happened: Run a structured-output describe command that resolves to multiple items, for example multiple backups or restores, with -o json. The existing backup describe implementation does not produce structured output for a multi-item describe. PR #9983 mirrors that behavior for restores: structured output is used only when exactly one restore is selected, while a multi-item request falls back to plaintext output despite the requested output format. What did you expect to happen: velero backup describe and velero restore describe should handle multi-item structured output consistently and return valid machine-readable output in the requested format. The output should represent every selected item without silently falling back to plaintext and should avoid excessive memory use. The following information will help us better understand what's going on: If you are using velero v1.7.0+: Please use velero debug --backup <backupname> --restore <restorename>
Describe the problem/challenge you have Following up on the discussion in #10194: several well-known Kubernetes label strings are hardcoded across the codebase instead of using the constants already exported by k8s.io/api/core/v1 (well_known_labels.go), which Velero already imports. A couple of spots even define their own local const that duplicates the upstream value. Unlike the external-snapshotter finalizer cleanup in #10194 (blocked on an upstream module change), this one is unblocked since the constants are already available in an imported module. Pure mechanical replacement, no functional change. Constant mapping: Hardcoded string k8s.io/api/core/v1 constant "kubernetes.io/hostname" corev1.LabelHostname "kubernetes.io/os" corev1.LabelOSStable "topology.kubernetes.io/zone" corev1.LabelTopologyZone Describe the solution you'd like Replace the hardcoded strings with the corev1 constants, and collapse the local duplicate consts (NodeOSLabel, zoneLabel) onto the upstream
What steps did you take and what happened: config.S3Url = https://<Netapp storageGrid>:443 Reliably returns SignatureDoesNotMatch with signature payload as host:<hostname>:443 Then generated presigned URLs using aws s3 presign--endpoint-url <StorageGrid>[:443] which storageGrid handled correctly both ways. Note the value of the host attribute is the SAME (not port number) in both invocations of the AWS CLI X-Amz-Algorithm=AWS4-HMAC-SHA256& ... Date=<now>&X-Amz-Expires= ... host:<storageGrid hostname> StorageGrid version = v11.9.0.5 Removed the port spec from config.S3Url and works flawlessly. What did you expect to happen: (edit, this part is wrong, see comment below) The URL parser is smart enough to know that the 'authority' section of a URL is made up of [userinfo @] host [:port] and that port is not a component of the host. The mechanism of network path (eg. port number, protocol scheme) do not belong in the signature. (end edit) Maybe the S3 spec is unclear on that matter and var
There's a lot of context TODO prior to this pr that in future pr we should eliminate for proper cancellations handling. Not for this pr. I think there's Linter setting for this. Exception for test code. Originally posted by @kaovilai in #9697
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 velero-io/velero, 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 velero-io/velero acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 64.6% were successfully merged into the primary branch.
velero-io/velero has a recorded first-timer success rate of 48.3%. 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 63.9 places velero-io/velero in the Welcoming tier.
The external pull request merge rate is 64.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, velero-io/velero currently has 9 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for velero-io/velero 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.