Open source re-implementation of Tomb Raider I, Tomb Raider II and Tomb Raider III, along with additional enhancements and bugfixes
C-Rank Grade: A (Welcoming) - 58/100
External PR Merge Rate: 20%
Response Time: 9h
First Timer Success: -
LostArtefacts/TRX has a recorded first-timer success rate of 0.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in LostArtefacts/TRX respond to incoming external pull requests in approximately 8.7 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 57.7 places LostArtefacts/TRX in the A tier.
The external contributor pull request merge rate for LostArtefacts/TRX is 20.0%, based on public PR activity from non-core contributors.
LostArtefacts/TRX currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in LostArtefacts/TRX. Prompt code reviews with positive guidance for new contributors.
Discussions in LostArtefacts/TRX 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/LostArtefacts/TRX?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~6 hours (25% approval). Large PRs (>500 lines) take ~42 hours (15% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in C.
Apache NuttX is a mature, real-time embedded operating system (RTOS)
Create mobile applications with PHP
Hardware Security Module (HSM) for Raspberry Pico and ESP32
What would you like to see? I don't know if this is possible, but I would like that Lara would not be visible in her own sunglasses reflection while in photo mode. (I don't know if it happens because of the game implementation of the photo mode camera or if it's the game trying to render her reflection as if it where any kind of mirror, but it makes the photo unrealistic) What problem would this solve? Trying to get an angle where her own reflection would not appear in her glasses. Extra context No response
Hello, I'm experiencing a very big performance hit in the Return to Egypt level. This seems very strange, since it's the only official TR1 level where I get such performance. In every other level the game is very smooth (didn't actually measure it but feels like 60 fps to me). Is this hardware not enough? CPU: Intel i5-8265U RAM: 16GB DDR4 Storage: 256GB NVMe SSD OS: Arch Linux Thanks
Hi there, in case you're not familiar with Flatpak, it's a distro-agnostic package manager that allows running a program on virtually any Linux distro (Ubuntu, Arch, Fedora etc...). Flatpak is rapidly growing and evolving, passing four million users and over two billion downloads in 2024, with currently nearing four billion downloads. On top of offering many security benefits, Flatpak makes the installation of an app trivial. Therefore I'd like to request a Flatpak for your app. Ideally you'd have it verified, thereby adding another layer of trust to your app. Thanks in advance and best regards!
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 LostArtefacts/TRX, 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 LostArtefacts/TRX acknowledge new external contributions in approximately 8 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 20.0% were successfully merged into the primary branch.
LostArtefacts/TRX has a recorded first-timer success rate of 0.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~8 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 57.7 places LostArtefacts/TRX in the Welcoming tier.
The external pull request merge rate is 20.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, LostArtefacts/TRX currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for LostArtefacts/TRX 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.