OCI registry client - managing content like artifacts, images, packages
C-Rank Grade: B (Solid) - 52/100
External PR Merge Rate: 57%
Response Time: 10h
First Timer Success: -
oras-project/oras has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in oras-project/oras respond to incoming external pull requests in approximately 9.9 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 51.7 places oras-project/oras in the B tier.
The external contributor pull request merge rate for oras-project/oras is 57.1%, based on public PR activity from non-core contributors.
oras-project/oras does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in oras-project/oras.
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/oras-project/oras?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~6 hours (71% approval). Large PRs (>500 lines) take ~47 hours (26% approval). Keep your diff compact for rapid review.
Now that #1913 has merged, e2e tests run twice on every push and pull request: build (.github/workflows/build.yml) runs make teste2e / make teste2e-covdata, which starts the three registries as plain Docker containers on the runner via test/e2e/scripts/e2e.sh. e2e-k8s (.github/workflows/e2e-k8s.yml) runs the same Ginkgo suite inside a KinD cluster. The Docker-on-the-runner path is now redundant. It should be removed so there is a single e2e entry point. Proposed changes .github/workflows/build.yml: drop the Run E2E Tests step and its ORAS_PATH env. build keeps build + unit tests + version check. Makefile: remove the teste2e and teste2e-covdata targets. test/e2e/scripts/: remove e2e.sh, prepare.sh, and common.sh (only used by the removed targets). build-image.sh, deploy.sh, status.sh, run-tests.sh, run-interactive.sh, teardown.sh, and generate-cache-db.sh stay. test/e2e/README.md / CONTRIBUTING.md: make sure nothing still points at make teste2e as the local workflow. test/e2e/testda
What is the version of your ORAS CLI v1.3.4 What would you like to be added? This should work: docker pull ghcr.io/oras-project/oras:latest https://github.com/orgs/community/discussions/23606 The latest tag isn’t automatic, you need to push it like any other tag. Having these options work would also be nice: docker pull ghcr.io/oras-project/oras:v1.3 docker pull ghcr.io/oras-project/oras:v1 Why is this needed for ORAS? Convenience for users and CI pipelines. Are you willing to submit PRs to contribute to this feature? Yes, I am willing to implement it.
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 oras-project/oras, 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 oras-project/oras acknowledge new external contributions in approximately 9 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 57.1% were successfully merged into the primary branch.
oras-project/oras has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~9 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 51.7 places oras-project/oras in the Solid tier.
The external pull request merge rate is 57.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
oras-project/oras 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 oras-project/oras 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.