✨☁️📁✨ Cloud Commander file manager for the web with console and editor.
C-Rank Grade: B (Solid) - 44/100
External PR Merge Rate: 67%
Response Time: 2h
First Timer Success: -
coderaiser/cloudcmd has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in coderaiser/cloudcmd respond to incoming external pull requests in approximately 2.4 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 44.3 places coderaiser/cloudcmd in the B tier.
The external contributor pull request merge rate for coderaiser/cloudcmd is 66.7%, based on public PR activity from non-core contributors.
coderaiser/cloudcmd currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
✨☁️📁✨ Cloud Commander file manager for the web with console and editor.
Active maintainer team in coderaiser/cloudcmd welcoming community pull requests and bug fixes.
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/coderaiser/cloudcmd?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 03:00 to 07:00 UTC (03:00 - 07:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (83% approval). Large PRs (>500 lines) take ~11 hours (30% approval). Keep your diff compact for rapid review.
Describe the bug volumes.map is not a function To Reproduce Steps to reproduce the behavior: Install CloudCMD as instructed. Run cloudcmd Expected behavior CloudCMD to pop up. Screenshots If applicable, add screenshots to help explain your problem. Desktop (please complete the following information): Version (cloudcmd -v):v19.19.0 Node Version node -v:v26.2.0 OS (uname -a on Linux):Windows 11 Browser name/version:Firefox Used Command Line Parameters:cloudcmd Changed Config:None Additional context I will mention every time I check in to see if CloudCMD is functioning under Windows, it appears to get worse and worse over time. It's now entirely non-functional on Windows. It might be best to remove the Windows tag from the front page if it's not gonna be fixed by main dev.
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 coderaiser/cloudcmd, 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 coderaiser/cloudcmd acknowledge new external contributions in approximately 2 hours. 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.
coderaiser/cloudcmd has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 44.3 places coderaiser/cloudcmd in the Solid 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, coderaiser/cloudcmd 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 coderaiser/cloudcmd 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.