Native navigation primitives for your React Native app.
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 77%
Response Time: 3d
First Timer Success: 53%
software-mansion/react-native-screens has a recorded first-timer success rate of 52.6%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in software-mansion/react-native-screens respond to incoming external pull requests in approximately 81.3 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 62.7 places software-mansion/react-native-screens in the A tier.
The external contributor pull request merge rate for software-mansion/react-native-screens is 77.3%, based on public PR activity from non-core contributors.
software-mansion/react-native-screens currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Native navigation primitives for your React Native app.
Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in software-mansion/react-native-screens.
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/software-mansion/react-native-screens?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 10:00 UTC (10:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~53 hours (96% approval). Large PRs (>500 lines) take ~390 hours (35% approval). Keep your diff compact for rapid review.
Hi! 👋 Thanks for your work on this project! Description On iOS 26, any screen with a custom headerRight shows the right header item stretch out toward the middle of the navigation bar for the duration of the back (pop) transition, pushing the title aside. Once the transition completes the header on the destination screen is correct — the glitch is visible only while the dismissal animates. It reproduces regardless of: how the title is provided (custom React element or plain string) how the options are set (declarative <Stack.Screen options> or imperative navigation.setOptions) whether the header item has an explicit size in its React styles The only requirement is that the screen being popped has a custom headerLeft/headerRight subview. Android is unaffected. Cause I believe this is a mismatch between the iOS 26 wrapper view and the snapshot logic used during dismissal. In -[RNSScreenStackHeaderSubview getUIBarButtonItem] (ios/RNSScreenStackHeaderSubview.mm), on iOS 26 the subvi
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 software-mansion/react-native-screens, 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 software-mansion/react-native-screens acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 77.3% were successfully merged into the primary branch.
software-mansion/react-native-screens has a recorded first-timer success rate of 52.6%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 days+. 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 62.7 places software-mansion/react-native-screens in the Welcoming tier.
The external pull request merge rate is 77.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, software-mansion/react-native-screens 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 software-mansion/react-native-screens 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.