OpenXRay/xray-16 - Open Source PR Review Scorecard

Improved version of the X-Ray Engine, the game engine used in the world-famous S.T.A.L.K.E.R. game series by GSC Game World. Join OpenXRay! ;)

C-Rank Grade: B (Solid) - 49/100

External PR Merge Rate: 18%

Response Time: 17h

First Timer Success: -

Frequently Asked Questions

Is OpenXRay/xray-16 welcoming to first-time open-source contributors?

OpenXRay/xray-16 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.

How fast can I expect code review feedback on my pull request?

Maintainers in OpenXRay/xray-16 respond to incoming external pull requests in approximately 17.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 49.2 C-Rank™ score (B Tier) represent?

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 49.2 places OpenXRay/xray-16 in the B tier.

What is the external contributor pull request merge rate for OpenXRay/xray-16?

The external contributor pull request merge rate for OpenXRay/xray-16 is 18.2%, based on public PR activity from non-core contributors.

Are there Good First Issues available in OpenXRay/xray-16?

OpenXRay/xray-16 currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

OpenXRay
OpenXRay/xray-16B•Solid3.6k
GitHub
Back to Explorer
OpenXRay

OpenXRay/xray-16

3,574
Active (30d)B•Solid(49/100)Low Sample (<20 PRs)C++

Improved version of the X-Ray Engine, the game engine used in the world-famous S.T.A.L.K.E.R. game series by GSC Game World. Join OpenXRay! ;)

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.5/10
Patience Score
8.2/10
Nitpick Rate
20%

Collaborative maintainer environment in OpenXRay/xray-16. Reviews community pull requests with focus on project quality.

What Contributors Actually Say

Discussions in OpenXRay/xray-16 focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • •1) Keep PR scope strictly aligned with the linked issue.
  • •2) Ensure local linters pass before opening a review.
  • •3) Maintain full test coverage for modified logic.

Top PR Submission Do's

  • •Call out API, migration, or compatibility impact clearly
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not hide breaking changes in implementation details
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
17 hours
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
18.2%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
0.0%
No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
6 core
Highly collaborative maintainer core
Diagnostic Health HUD
18.2%
Merge Gauge
0.0%
1st-Timer
Community Vibe24/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for OpenXRay/xray-16
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/OpenXRay/xray-16)](https://getmerged.abhishekco.de/OpenXRay/xray-16?utm_source=github&utm_medium=badge)

Active Good First Issues (3)

View on GitHub

Describe the bug UI in the PDA tabs looks weird (see screenshots under the spoiler). To Reproduce Steps to reproduce the behavior: Install clean CoC 1.4.22 Start a new game Open PDA Tap on the PDA tabs See the UI Expected behavior UI of PDA looks weird. Screenshots, videos Spoiler BugTrap error report No crash here. But add the log - openxray_denie.log Desktop (please complete the following information): OS: Windows 10 OpenXRay build version - 6505 Additional context No

📅 Opened Sep 27, 2026💬 1 comment
Quality: 90/100Contribute

Describe the bug When talking to Uncle Yar at Yanov station to get Kopachy mission there is duplicated text in possible answers before and after the mission. To Reproduce Steps to reproduce the behavior: Go to Yanov station Talk to Uncle Yar See duplicated text in sentaces for answers Screenshots, videos BugTrap error report no crash Desktop (please complete the following information): OpenXRay Release build 9898, Mar 15 2026 (Windows 64-bit, shared) GitHub Actions build 6322 (23118509982) from commit[3526a63] branch[dev] (built by OpenXRay/xray-16) Additional context Someone needs to confirm that this is vanilla bug since I havent tested without Open Xray

📅 Opened Mar 17, 2026💬 1 comment
Quality: 45/100Contribute

Is your feature request related to a problem? Please describe. It would be very useful to add option to turn off auto targeting rectangles in game engine options. Describe the solution you'd like All that has to be done is to change value to vis_frame_speed = 0 in w_binoc.ltx. The option could be added under main menu\options\game under draw crosshair option. It could be named auto targeting rectangle. Describe alternatives you've considered Removing option completely from *.ltx breaks the engine but speed set from 4 to 0 works so far

📅 Opened Feb 25, 2026💬 2 comments
Quality: 70/100Contribute
Looking for more C++ beginner tasks?Explore C++ GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for OpenXRay/xray-16

When evaluating whether to contribute to OpenXRay/xray-16, 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 OpenXRay/xray-16 acknowledge new external contributions in approximately 17 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 18.2% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to OpenXRay/xray-16

01

Is OpenXRay/xray-16 welcoming to first-time open-source contributors?

OpenXRay/xray-16 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.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~17 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 49.2 C-Rank™ score represent?

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 49.2 places OpenXRay/xray-16 in the Solid tier.

04

What is the external contributor pull request merge rate for OpenXRay/xray-16?

The external pull request merge rate is 18.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in OpenXRay/xray-16?

Yes, OpenXRay/xray-16 currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for OpenXRay/xray-16 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.