Low-Latency Accelerated Web Remote Desktop Streaming Platform for Self-Hosting, Containers, Kubernetes, or Cloud/HPC
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 67%
Response Time: -
First Timer Success: 67%
selkies-project/selkies has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in selkies-project/selkies 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 63.4 places selkies-project/selkies in the A tier.
The external contributor pull request merge rate for selkies-project/selkies is 66.7%, based on public PR activity from non-core contributors.
selkies-project/selkies currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly encouraging & supportive maintainers (100% positive review sentiment). Active code reviews with constructive guidance for new contributors in selkies-project/selkies.
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/selkies-project/selkies?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (83% approval). Large PRs (>500 lines) take ~115 hours (30% approval). Keep your diff compact for rapid review.
You may support this task by providing a 20x Claude or Codex plan or equivalent AI access, or opening a pull request after building the feature inside a Selkies container or VM instead of on your desktop directly. The PR for this issue needs to be AI-verified because agents are more accurate than people for large codebases and can validate empirical findings in much higher throughput than people. Can be AI-driven: Yes, as long as all cases are tested carefully in real life by people as well as with automated tests. However, guidance is required due to working with GPU hardware intrinsics. Expected to be workable with: Opus 5.5 + Fable 5.1, GPT-6 Astra + Sol, or equivalent (max thinking and requires adjustments along the way; do not work on this with Opus 5 or older models as they regress the codebase). Vulkan video encoding or decoding is now supported in recent versions of Intel, AMD, and NVIDIA GPU drivers, as well as being a widely anticipated supporter of Video4Linux2 (V4L2) encode
You may support this task by providing a 20x Claude or Codex plan or equivalent AI access, or opening a pull request after building the feature inside a Selkies container or VM instead of on your desktop directly. The PR for this issue needs to be AI-verified because agents are more accurate than people for large codebases and can validate empirical findings in much higher throughput than people. Can be AI-driven: Yes, as long as all cases are tested carefully in real life by people as well as with automated tests. However, guidance is required due to working with OS intrinsics, including input. Expected to be workable with: preferably Fable 5.5, otherwise Opus 5.5 + Fable 5.1, GPT-6 Astra + Sol, or equivalent (max thinking and requires adjustments along the way; do not work on this with Opus 5 or older models as they regress the codebase). The descriptions and comments/reviews below essentially serve as prompts. I don't see a lot of performance issues with the Python components becaus
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 selkies-project/selkies, 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 selkies-project/selkies acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.7% were successfully merged into the primary branch.
selkies-project/selkies has a recorded first-timer success rate of 66.7%. 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 63.4 places selkies-project/selkies in the Welcoming tier.
The external pull request merge rate is 66.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, selkies-project/selkies currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for selkies-project/selkies 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.