Immutable Linux OS to run Incus
C-Rank Grade: S (Elite) - 74/100
External PR Merge Rate: 95%
Response Time: 2d
First Timer Success: 83%
lxc/incus-os has a recorded first-timer success rate of 83.3%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in lxc/incus-os respond to incoming external pull requests in approximately 59.6 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 73.8 places lxc/incus-os in the S tier.
The external contributor pull request merge rate for lxc/incus-os is 94.8%, based on public PR activity from non-core contributors.
lxc/incus-os 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 lxc/incus-os. 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/lxc/incus-os?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 Wednesday - Friday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~39 hours (96% approval). Large PRs (>500 lines) take ~286 hours (43% approval). Keep your diff compact for rapid review.
Its currently difficult without reading logs to determine when the last successful sync was. Would it be possible to add the last openfga-sync successful sync time to to the openfga application state? I assume this might need an issue opened with openfga-sync to write the last sync time somewhere it can be read from.
Summary IncusOS has no way to issue TRIM/discard to the SSDs backing its ZFS pools, and no way for an operator to arrange one. scrub_schedule has no trim counterpart, and the design (correctly) leaves no shell to run zpool trim from. I'd like to propose a trim_schedule field alongside scrub_schedule, and optionally a trim-pool action mirroring scrub-pool. Why there is currently no path As far as I can tell from the source, nothing in the stack ever trims: CreateZpool passes ashift=12, mountpoint=none and the encryption options — no autotrim. Incus itself sets autotrim=on, but only in its pool creation path. A pool created by incus-osd and then adopted by Incus via source= never goes through that path, which is the normal IncusOS arrangement. SystemStorageConfig exposes pools, scrub_schedule and allow_mixed_dev_sizes; pools expose name, type, devices, cache/log/special. There is no field for autotrim or any other zpool property. The storage actions are scrub-pool, delete-pool, wipe-d
It would be useful to show a different status message like "Wiping target driver, this may take a while" so that folks don't think we're stuck when dealing with a very slow blkdiscard operation.
As we're planning to move to the FuturFusion server kernel and new x86_64_v3 baseline, it would be useful to get details on existing systems. I think the endpoint should give us: Kernel version detail System CPU information (including x86_64 baseline if possible) dmesg output Module list including their dependencies
General idea would be to POST /1.0/debug/network-dump with arguments as part of a JSON struct, then depending on options, you either get a streaming pcap file as output or you get streaming text file. Interrupting the connection then interrupts the command on the IncusOS side.
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 lxc/incus-os, 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 lxc/incus-os acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 94.8% were successfully merged into the primary branch.
lxc/incus-os has a recorded first-timer success rate of 83.3%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 73.8 places lxc/incus-os in the Elite tier.
The external pull request merge rate is 94.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, lxc/incus-os 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 lxc/incus-os 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.