Linux virtual machines, with a focus on running containers
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 61%
Response Time: -
First Timer Success: 57%
lima-vm/lima has a recorded first-timer success rate of 57.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in lima-vm/lima respond to incoming external pull requests in approximately 0.0 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 68.0 places lima-vm/lima in the A tier.
The external contributor pull request merge rate for lima-vm/lima is 61.3%, based on public PR activity from non-core contributors.
lima-vm/lima currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in lima-vm/lima. Reviews community pull requests with focus on project quality.
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/lima-vm/lima?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 23:00 to 03:00 UTC (23:00 - 03:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (77% approval). Large PRs (>500 lines) take ~115 hours (28% approval). Keep your diff compact for rapid review.
lima/cmd/limactl-menu/main.go Lines 185 to 187 in f6158fe if in.Protected { prot = " " + tview.Escape("[LOCKED]") } [LOCKED] sounds like as if it were flock-ed. Should be shown as [PROTECTED] or maybe 🔒
limactl menu should return to the menu after invoking an action ("Shell", "Delete", etc.). Currently it just exits.
╔ Lima Instances ══════════════════════════════════════════════════════════════════════════════════╗ ║ ║ ║ ● default Running aarch64 4CPU/4.3GB 127.0.0.1:58684 ║ ║ ║ ║ ● agent Stopped aarch64 4CPU/4.3GB 127.0.0.1:49847 ║ ║ ║ ║ ● docker-rootful Stopped aarch64 4CPU/4.3GB 127.0.0.1:58382 ║ ║
Help wanted to work on the following items, but these ones should NOT be considered as "good first issues". Non-trivial contribution experience is expected. Relatively easy: #5285 #5295 #5160 Medium: #4766 #368 #5312 Difficult: #4371 #5495 #4326 #3033 Contributors: if you are interested in working on these items, please show your interest with detailed design proposal in the corresponding issue ticket (NOT in this umbrella ticket) Maintainers: feel free to edit the list
$ git grep -n '^type .* = ' | grep -v '.pb.go' pkg/downloader/downloader.go:41:type Status = string pkg/guestagent/sockets/sockets.go:10:type Kind = string pkg/guestagent/sockets/sockets.go:20:type State = byte pkg/instance/start.go:391:type watchHostAgentEventsTimeoutKey = struct{} pkg/instance/start.go:399:type launchingShellKey = struct{} pkg/limatype/lima_instance.go:15:type Status = string pkg/limatype/lima_yaml.go:77:type CPUType = map[Arch]string pkg/limatype/lima_yaml.go:171:type SFTPDriver = string pkg/limatype/lima_yaml.go:232:type ProvisionMode = string pkg/limatype/lima_yaml.go:271:type ProbeMode = string pkg/limatype/lima_yaml.go:285:type Proto = string pkg/networks/usernet/config.go:18:type SockType = string pkg/sshutil/format.go:15:type FormatT = string type Foo = string should be changed to type Foo string so that type checking can be enforced on compilation
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 lima-vm/lima, 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 lima-vm/lima acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 61.3% were successfully merged into the primary branch.
lima-vm/lima has a recorded first-timer success rate of 57.1%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 68.0 places lima-vm/lima in the Welcoming tier.
The external pull request merge rate is 61.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, lima-vm/lima 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 lima-vm/lima 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.