Multipass orchestrates virtual Ubuntu instances
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 52%
Response Time: 2d
First Timer Success: 50%
canonical/multipass has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in canonical/multipass respond to incoming external pull requests in approximately 38.7 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 59.2 places canonical/multipass in the A tier.
The external contributor pull request merge rate for canonical/multipass is 51.5%, based on public PR activity from non-core contributors.
canonical/multipass currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in canonical/multipass. 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/canonical/multipass?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~25 hours (64% approval). Large PRs (>500 lines) take ~186 hours (23% approval). Keep your diff compact for rapid review.
Describe the bug When I type multipass launch --name my_vm -- and then Tab/Tab, I'd expect the --zone option to be proposed. Also, when I invoke autocompletion after typing multipass, I'd expect zones, enable-zones and disable-zones to be proposed. To Reproduce How, and what happened? In a shell, type multipass launch --name my_vm -- Then use Tab/Tab to get autocomplete options. => --zone is not listed in the available ones. Expected behavior What did you expect to happen? To get the --zone option listed, and ideally, after typing in --zone, I'd also expect the autocompletion to provide the available zones. Additional info OS: Ubuntu 26.04 CPU architecture or model: x64 multipass version multipass 1.17.0-dev.pr5289+g4754a402 multipassd 1.17.0-dev.pr5289+g4754a402
Describe the bug Cannot start a Multipass instance that previously used a native mount, if the directory is not available in the host machine anymore, after being unmounted. To Reproduce multipass launch 26.04 --name example-instance --cpus 1 --memory 8G --disk 8G multipass stop example-instance mkdir ~/example-mount multipass mount ~/example-mount example-instance:example-mount -t native multipass start example-instance multipass info example-instance // The directory appears mounted, as expected multipass stop example-instance multipass unmount example-instance:example-mount multipass info example-instance // The mount is gone, as expected rmdir ~/example-mount Reboot the host machine multipass start example-instance Expected behavior example-instance should start Actual behavior multipass start example-instance fails and outputs: start failed: The following errors occurred: qemu-system-x86_64: -virtfs local,security_model=passthrough,uid_map=1000:1000,gid_map=1000:1000,path=/home/
Describe the bug The mount options are silently dropped on timeout To Reproduce How, and what happened? multipass launch -n a --timeout 5 --mount ~/dir:/mnt/dir Error does not mention the missed mounts, even if the instance eventually reaches the running state. Expected behavior Multipass should clarify to the user that the mount flags are dropped if the mount initialization part is not reached. Additional info OS: Ubuntu 24.04 CPU architecture or model: amd64 multipass version: 1.17.0-dev
Describe the bug When deleting a snapshot from a running VM, Multipass will attempt the process without checking whether the VM is in a state that allows the process. └─[λ] multipass delete a.snapshot1 --purge delete failed: Cannot list snapshots from the image: qemu-img failed (Process returned exit code: 1) with output: qemu-img: Could not open '/var/snap/multipass/common/data/multipassd/vault/instances/a/ubuntu-24.04-server-cloudimg-amd64.img': Failed to get shared "write" lock Is another process using the image [/var/snap/multipass/common/data/multipassd/vault/instances/a/ubuntu-24.04-server-cloudimg-amd64.img]? └─[2] multipass delete a.snapshot1 Snapshots can only be purged (after deletion, they cannot be recovered). Are you sure you want to continue? (Yes/no): Yes delete failed: Cannot list snapshots from the image: qemu-img failed (Process returned exit code: 1) with output: qemu-img: Could not open '/var/snap/multipass/common/data/m
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 canonical/multipass, 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 canonical/multipass acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 51.5% were successfully merged into the primary branch.
canonical/multipass has a recorded first-timer success rate of 50.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 59.2 places canonical/multipass in the Welcoming tier.
The external pull request merge rate is 51.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, canonical/multipass currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for canonical/multipass 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.