Open-source cloud native platform that automates and simplifies the deployment of virtualization, Kubernetes, and OpenStack infrastructure.
C-Rank Grade: S (Elite) - 72/100
External PR Merge Rate: 76%
Response Time: 15h
First Timer Success: 71%
bigstack-oss/cubecos has a recorded first-timer success rate of 71.4%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in bigstack-oss/cubecos respond to incoming external pull requests in approximately 15.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 71.9 places bigstack-oss/cubecos in the S tier.
The external contributor pull request merge rate for bigstack-oss/cubecos is 75.8%, based on public PR activity from non-core contributors.
bigstack-oss/cubecos currently has 12 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in bigstack-oss/cubecos. 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/bigstack-oss/cubecos?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~10 hours (95% approval). Large PRs (>500 lines) take ~72 hours (34% approval). Keep your diff compact for rapid review.
Part of #963 (edge-k3s profile) — and #960. Work Measure the edge-k3s profile on the target device: idle RAM, disk usage, boot time, running-process count, and CVE/attack surface Compare against stock K3s / RKE2 in a simple table Acceptance Baseline footprint numbers recorded and compared to stock — this is the primary go/no-go gate for the edge-k3s profile Why this is a good first issue Self-contained measurement + reporting: run standard tools, record numbers, fill a table. No deep CubeCOS internals required.
Part of #962 (ARM-based build) — and #960. Work Script skopeo/docker manifest inspect across the pinned image tags Flag images with no arm64 manifest; bump old pins (e.g. rancher/k3s:v1.19.5, rancher/kubectl:v1.20.2) Acceptance The k3s/Fleet/edge image subset all have arm64 manifests
Part of #962 (ARM-based build) — and #960. Work Swap x86_64/amd64 → aarch64 in the ~12 component .mk download refs (telegraf/grafana/etcd/mongodb/kapacitor/...) aarch64 availability already verified for all sources; switch RabbitMQ off the CentOS SIG to its arm64-capable repo Acceptance Every component package resolves an aarch64 build
Context Drive platform scope from the actual running services (not from which benchmarks exist). Enumerate every service, classify it, and record coverage - the integrity artifact that keeps the SCG (#944) honest. Part of #946. Work Inventory running services per release (ss -tulnp + systemctl) Classify each: CIS benchmark / Baseline Rubric (#935 pinned comment) / scoped-out internal-only (with evidence) Maintain the register table + scoped-out: internal-only convention Output (machine-consumable) Produce docs/compliance/coverage-register/report.md per the Compliance Artifact Contract (#935). Validated by #948, aggregated by #944. Acceptance Every running service appears in the register with a coverage basis and status report.md passes #948 validation Why this is a good first issue Mostly ss/systemctl + classification against a documented rubric. No deep platform internals needed. Starter artifact - docs/compliance/coverage-register/report.md --- layer: coverage-register benchma
Context Part of #946 — split from #940 (container/orchestration). Work Assess kubernetes against the CIS Kubernetes Benchmark (Level 1) Document config-driven exceptions (managed by CubeCOS config/build) Output (machine-consumable) Produce docs/compliance/kubernetes/report.md per the Compliance Artifact Contract in #935. Worked example: #945. Validated by CI (#948). Why this is a good first issue Self-contained: run one tool, fill one report.md from the skeleton using the contract + example. No deep platform knowledge required. Starter skeleton — docs/compliance/kubernetes/report.md --- layer: kubernetes benchmark: CIS Kubernetes Benchmark version: 1.10.0 (k3s/RKE2) profile: Level 1 (tailored) tool: kube-bench assessed_on: 2026-06-15 result: { pass: 0, fail: 0, not_applicable: 0, exceptions: 1 } exceptions: - rule: cis-k8s-apiserver-flags title: apiserver/kubelet flags managed by k3s reason: k3s/RKE2 set these flags via their own config rather than raw manifests
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 bigstack-oss/cubecos, 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 bigstack-oss/cubecos acknowledge new external contributions in approximately 14 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.8% were successfully merged into the primary branch.
bigstack-oss/cubecos has a recorded first-timer success rate of 71.4%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~14 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 71.9 places bigstack-oss/cubecos in the Elite tier.
The external pull request merge rate is 75.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, bigstack-oss/cubecos currently has 12 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for bigstack-oss/cubecos 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.