The AI Compute Platform for frontier teams. SkyPilot turns fragmented AI compute into one AI supercomputer, so frontier AI teams build custom intelligence faster.
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 62%
Response Time: 1d
First Timer Success: 48%
skypilot-org/skypilot has a recorded first-timer success rate of 48.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in skypilot-org/skypilot respond to incoming external pull requests in approximately 28.3 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 66.7 places skypilot-org/skypilot in the A tier.
The external contributor pull request merge rate for skypilot-org/skypilot is 62.1%, based on public PR activity from non-core contributors.
skypilot-org/skypilot currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in skypilot-org/skypilot. 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/skypilot-org/skypilot?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 23:00 to 03:00 UTC (23:00 - 03:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~18 hours (78% approval). Large PRs (>500 lines) take ~136 hours (28% approval). Keep your diff compact for rapid review.
Summary enable_docker: {mode: BUILD} runs the BuildKit sidecar from moby/buildkit:v0.28.0-rootless: skypilot/sky/provision/kubernetes/utils.py Lines 4252 to 4265 in f616a2f DOCKER_SIDECAR_DEFAULTS: Dict[DockerMode, DockerSidecarDefaults] = { DockerMode.ALL: DockerSidecarDefaults( image='docker:29.3-dind', cli_image='docker:29.3-cli', cache_vol_name='dind-storage', cache_mount='/var/lib/docker', ), DockerMode.BUILD: DockerSidecarDefaults( image='moby/buildkit:v0.28.0-rootless',
Description For the S3-compatible object stores CoreWeave, Nebius, R2, and VastData, the awscli-install guard checks for aws on PATH, but the generated sync command invokes awscli at the runtime-venv path {SKY_REMOTE_PYTHON_ENV}/bin/aws. When the cluster's container image already ships aws on PATH (e.g. NGC images such as nvcr.io/nvidia/nemo:24.05, which bundle aws-cli), the guard passes, the venv install is skipped, and the sync fails: /opt/skypilot-runtime/bin/aws: No such file or directory Root cause The install guard resolves aws via PATH, but the sync command invokes the venv aws — so on an image with a system aws the install is skipped and the invoked binary is missing. Affected stores (guard line vs. invocation line): CoreWeave — guard cloud_stores.py#L619 → invocation #L659 (file variant #L676) Nebius — guard #L559 → invocation #L592 / #L605 R2 — guard #L368 → invocation #L404 / #L421 VastData — guard #L693 → invocation #L722 / #L741 S3CloudStorage is not a
Background PR #9774 pins azure-mgmt-storage<25.0.0 to unblock CI/usage, but only mitigates the symptom. This issue tracks the proper fix. Problem sky/data/storage.py:_create_storage_account passes a hand-built dict with a top-level encryption key to storage_accounts.begin_create: self.storage_client.storage_accounts.begin_create( resource_group_name, storage_account_name, { 'sku': {'name': 'Standard_GRS'}, 'kind': 'StorageV2', 'location': self.region, 'encryption': { # <-- top-level 'services': {'blob': {'key_type': 'Account', 'enabled': True}}, 'key_source': 'Microsoft.Storage' }, }).result() On the wire, encryption belongs under properties (properties.encryption). Whether the malformed top-level key is corrected depends on the SDK version: azure-mgmt-storage <= 24.x (msrest): the serializer remaps the dict via _attribute_map (encryption → properties.encryption), so the body is correct an
On a K8s cluster where sky show-gpus --infra k8s shows only H100: sky launch --gpus H100-MEGA succeeds (should it?) sky launch --gpus 'NVIDIA:40GB+' shows H100-NVLINK, H100-SXM, H100-MEGA, H100-NVL as separate options, all resolving to the same physical H100 K8s prefix-based fuzzy matching in _accelerator_name_matches() accepts any name where H100 is a prefix (e.g., H100-MEGA, H100-SXM). The optimizer should filter against what's actually available on the cluster.
We can just mark a row to be deleted, but not actually deleting it from the table
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 skypilot-org/skypilot, 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 skypilot-org/skypilot acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 62.1% were successfully merged into the primary branch.
skypilot-org/skypilot has a recorded first-timer success rate of 48.1%. 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 66.7 places skypilot-org/skypilot in the Welcoming tier.
The external pull request merge rate is 62.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, skypilot-org/skypilot currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for skypilot-org/skypilot 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.