Use Omarchy Linux on Windows without any hassle.
C-Rank Grade: S (Elite) - 72/100
External PR Merge Rate: 78%
Response Time: 10h
First Timer Success: 100%
omacom/try-omarchy-windows has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in omacom/try-omarchy-windows respond to incoming external pull requests in approximately 9.6 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 omacom/try-omarchy-windows in the S tier.
The external contributor pull request merge rate for omacom/try-omarchy-windows is 77.6%, based on public PR activity from non-core contributors.
omacom/try-omarchy-windows does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Strict review standards in omacom/try-omarchy-windows. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in omacom/try-omarchy-windows 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/omacom/try-omarchy-windows?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 22:00 UTC (22:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 22:00 to 02:00 UTC (22:00 - 02:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~6 hours (96% approval). Large PRs (>500 lines) take ~46 hours (35% approval). Keep your diff compact for rapid review.
Track the remaining work toward an official v1. Current public baseline: v0.0.18-preview, published September 13. v15–17 were unpublished candidates. The reconciled scope, evidence boundaries and testing instructions merged in #115. Use V1 readiness for detailed acceptance requirements and TESTING.md for reports. Completed baseline Ship Omarchy 4.0.3, browser-theme repair (#89) and an in-place guest runtime update path. Ship resource/disk controls (#87), installation moves, file/folder clipboard and transfer windows, snapshots and recovery controls. Pin the source-built graphics runtime and matching source archive. Record physical AMD Windows 11 acceptance, including storage/recovery, transfers and graphics testing, with individual artifact limits. Publish signed v18 and verify public downloads, versions and update signatures. Evidence: guest upgrades and Windows acceptance. Earlier-runtime tests do not establish every check on the final runtime. Next candidate and v1 gates
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 omacom/try-omarchy-windows, 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 omacom/try-omarchy-windows acknowledge new external contributions in approximately 9 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 77.6% were successfully merged into the primary branch.
omacom/try-omarchy-windows has a recorded first-timer success rate of 100.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~9 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 omacom/try-omarchy-windows in the Elite tier.
The external pull request merge rate is 77.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
omacom/try-omarchy-windows does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for omacom/try-omarchy-windows 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.