Open Container Initiative-based implementation of Kubernetes Container Runtime Interface
C-Rank Grade: A (Welcoming) - 56/100
External PR Merge Rate: 56%
Response Time: 2d
First Timer Success: 74%
cri-o/cri-o has a recorded first-timer success rate of 73.9%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in cri-o/cri-o respond to incoming external pull requests in approximately 45.2 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 56.4 places cri-o/cri-o in the A tier.
The external contributor pull request merge rate for cri-o/cri-o is 56.5%, based on public PR activity from non-core contributors.
cri-o/cri-o currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in cri-o/cri-o. Maintains strict focus on technical quality and test standards.
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/cri-o/cri-o?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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~39 hours (73% approval). Large PRs (>500 lines) take ~286 hours (26% approval). Keep your diff compact for rapid review.
Problem Integration tests can hang indefinitely when a test gets stuck. This was observed in the ci-fedora-kata Prow job for PR #10054: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/cri-o_cri-o/10054/pull-ci-cri-o-cri-o-main-ci-fedora-kata/2070422031282737152 test/test_runner.sh sets BATS_TEST_RETRIES=1 but does not set BATS_TEST_TIMEOUT. If a single test hangs, the entire CI job blocks until the platform kills it. Proposal Add BATS_TEST_TIMEOUT=600 (10 minutes) in test/test_runner.sh to enforce a per-test time limit: export BATS_TEST_TIMEOUT=600 This would abort any individual test that exceeds 10 minutes, making it easy to identify which test hung instead of waiting for the entire job to time out. Tests that intentionally sleep (e.g. test/timeout.bats) may need a per-file override. References bats-core BATS_TEST_TIMEOUT docs bats-core/bats-core#1020 — known issue where run subprocesses may not be killed on timeout
Problem The CI environment setup is currently duplicated between two separate mechanisms: GitHub Actions: Shell scripts scripts/github-actions-packages and scripts/github-actions-setup (Ubuntu/apt-based, hardcoded package lists and component installs) Prow jobs: Ansible playbooks under contrib/test/ci/ (RHEL/CentOS/Fedora-oriented, modular task includes) Both install largely the same set of dependencies — conmon, conmon-rs, cri-tools, runc, crun, bats, CNI plugins, buildah, libpathrs, ginkgo — but they diverge in versions, install methods, and system configuration. When a new dependency is added or a version is bumped, both paths must be updated independently, which leads to drift and hard-to-debug CI failures. Proposal Consolidate the GitHub Actions shell scripts into the existing Ansible playbook framework so that a single set of playbooks drives environment setup for both Prow and GitHub Actions: Extend the Ansible playbooks to support Ubuntu (apt) in addition to the existing
PR #9929 bumped 30 Go module dependencies but had to hold back several due to breaking API changes. These need dedicated follow-up work: containerd/containerd/api v1.10.0 -> v1.11.0 v1.11.0 renames all ttrpc-generated service types (TaskService -> TTRPCTaskService, NewTaskClient -> NewTTRPCTaskClient, EventsService -> TTRPCEventsService, etc.). Affects internal/oci/runtime_vm.go and vendored containerd/containerd/pkg/ttrpcutil/client.go. containerd v1.7.x only requires API v1.8.0; the v1.11.0 types come from the 2.x line. go.podman.io/common v0.66.2 -> v0.67.0 Removes ArtifactStore, ArtifactReference, ArtifactStoreReference types and their constructors from pkg/libartifact. Removes Artifact.Digest field (replaced with GetDigest() method). Requires rewriting internal/ociartifact/ (store.go, artifact.go, libartifact_store.go). go.podman.io/storage v1.61.1 -> v1.62.0 Uses securejoin.OpenInRoot and securejoin.Reopen at the top-level import, but these were removed in filepath-securejoin v0.
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 cri-o/cri-o, 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 cri-o/cri-o acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 56.5% were successfully merged into the primary branch.
cri-o/cri-o has a recorded first-timer success rate of 73.9%. 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 56.4 places cri-o/cri-o in the Welcoming tier.
The external pull request merge rate is 56.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, cri-o/cri-o 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 cri-o/cri-o 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.