Official upstream for the cloud-init: cloud instance initialization
C-Rank Grade: D (Risky) - 30/100
External PR Merge Rate: -
Response Time: 11h
First Timer Success: -
canonical/cloud-init has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in canonical/cloud-init respond to incoming external pull requests in approximately 10.9 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 29.9 places canonical/cloud-init in the D tier.
The external contributor pull request merge rate for canonical/cloud-init is 0.0%, based on public PR activity from non-core contributors.
canonical/cloud-init currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in canonical/cloud-init. Prompt code reviews with positive guidance for new contributors.
Discussions in canonical/cloud-init focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/cloud-init?utm_source=github&utm_medium=badge)
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 Monday - Wednesday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~7 hours (81% approval). Large PRs (>500 lines) take ~52 hours (29% approval). Keep your diff compact for rapid review.
Bug report On an amd64 systems with i386 architecture enabled, cloud-init will not install packages only available in i386 Steps to reproduce the problem Enable i386 arch in early boot before apt update: bootcmd: - [ cloud-init-per, once, dpkgi386, dpkg, --add-architecture, i386] Add package available to apt in i386 packages: - steamcmd cloud-init will not find the package to install. Package will install successfully from command line: apt install steamcmd Cause: cloud-init searches for packages using apt-cache pkgnames before attempting to install, which only lists packages for the primary architecture. Adding the --all-names flag to the call in apt.py does include packages for i386, but also includes virtual packages unavailable for installation. Environment details Cloud-init version: 25.1.4 Operating System Distribution: Debian 13 Trixie Cloud provider, platform or installer type: vultr cloud-init logs 2026-09-07 17:24:37,859 - apt.py[DEBUG]: The following packages were not fou
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/cloud-init, 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/cloud-init acknowledge new external contributions in approximately 10 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
canonical/cloud-init has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~10 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 29.9 places canonical/cloud-init in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, canonical/cloud-init 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 canonical/cloud-init 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.