A container runtime written in Rust
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 58%
Response Time: 12h
First Timer Success: 58%
youki-dev/youki has a recorded first-timer success rate of 57.9%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in youki-dev/youki respond to incoming external pull requests in approximately 12.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 60.3 places youki-dev/youki in the A tier.
The external contributor pull request merge rate for youki-dev/youki is 58.2%, based on public PR activity from non-core contributors.
youki-dev/youki currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in youki-dev/youki. 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/youki-dev/youki?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 Monday - Wednesday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~8 hours (73% approval). Large PRs (>500 lines) take ~59 hours (26% approval). Keep your diff compact for rapid review.
Background The ContainerLifecycle test group is designed to test OCI container state transitions (create → start → kill → state → delete). However, it currently contains several checkpoint-related methods that test CRIU features rather than the container lifecycle itself: checkpoint_leave_running checkpoint_leave_running_work_path_tmp checkpoint_manage_cgroups_mode_ignore checkpoint_manage_cgroups_mode_soft checkpoint_link_remap checkpoint_with_external_namespaces checkpoint_tcp_skip_in_flight These tests are conceptually closer to the checkpoint_restore test group. However, they cannot simply be moved there because checkpoint_restore skips all tests when running with youki (!is_runtime_youki()), whereas the above tests should run with youki. Proposed Solution Introduce a new checkpoint test group for checkpoint-only tests (no restore required), and move all checkpoint-related methods out of ContainerLifecycle: ContainerLifecycle → create, start, kill, state, delete, exec
Currently, the integration tests are not run on aarch64 in CI #3530 (review)
Background In the Checkpoint/Restore test suite (tests/contest/contest/src/tests/checkpoint_restore/mod.rs), we heavily rely on the OCI terminal: true requirement to test persistent IPC file descriptors (FIFOs). Because terminal: true requires an active console socket, the C/R tests use a specialized CrTestContext::start method. This method concurrently spawns the container in detached mode (run -d --console-socket), accepts the socket connection, and hands it off to handle_console_socket(stream). Currently, this -d spawn and concurrent socket-handling logic is encapsulated exclusively within the C/R test context. Feature Request During the review of PR #3493, see link to PR comment, it was pointed out that this logic could be highly useful for other test suites that might need to test console sockets or detached runs in the future. We agreed to extract this out of CrTestContext and into tests/contest/contest/src/utils/test_utils.rs as a global helper, but deferred it to this separate
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 youki-dev/youki, 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 youki-dev/youki acknowledge new external contributions in approximately 12 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 58.2% were successfully merged into the primary branch.
youki-dev/youki has a recorded first-timer success rate of 57.9%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~12 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 60.3 places youki-dev/youki in the Welcoming tier.
The external pull request merge rate is 58.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, youki-dev/youki currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for youki-dev/youki 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.