An Android app that uses your phone's sensors to assist with wilderness treks or survival situations.
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 95%
Response Time: -
First Timer Success: 71%
kylecorry31/Trail-Sense has a recorded first-timer success rate of 71.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kylecorry31/Trail-Sense respond to incoming external pull requests in approximately 0.0 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 67.7 places kylecorry31/Trail-Sense in the A tier.
The external contributor pull request merge rate for kylecorry31/Trail-Sense is 95.4%, based on public PR activity from non-core contributors.
kylecorry31/Trail-Sense does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Highly welcoming maintainers in kylecorry31/Trail-Sense. Prompt code reviews with positive guidance for new contributors.
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/kylecorry31/Trail-Sense?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (43% approval). Keep your diff compact for rapid review.
If the user's GPS is accurate enough, they may want to disable the snap to path feature on augmented reality. Add a setting for "Snap to path", default true. When off, the snapping logic is disabled.
I don't think I'm going to add that since it may interfere with some of my other planned map features. I might reconsider once it is fully built out. This would allow the user to upload their own render theme and render that in the UI. It may cause several features to stop working which are dependent on the custom theme (ex. #3711). And I'm not sure I want to support users having issues with their custom renderthemes. Keeping this here in case someone can throw together a quick proof of concept (ex. using AI) so I can see how it would feel in the app. Needs to support the icons that come with the theme and have a way for users to manage that.
Display the time the weather was last updated on the page (the time of the last reading), as one of the list items (at the bottom). It should display both the date and time of the last reading using the format service.
Reported by one user with Fairphone on Android 16. Unable to reproduce on my devices. They say they have 4G service but Trail Sense always shows it as 0%. When they enable 5G service, it properly shows the 5G strength. Looking for someone with a Fairphone to confirm this issue and either fix it or provide more detailed steps. If there's no workaround or progress made on this one (or someone with a Fairphone can't reproduce this issue), I'm going to assume it is an upstream issue and close this ticket. I'm not sure it is a bug or if that's what the system is reporting.
Per page default show on map setting on the edit page fragment (default to true) Changing the per page default show on map setting should show a dialog to let the user choose to update all existing sightings for that page Useful if you want to document a species without it appearing on the map by default.
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 kylecorry31/Trail-Sense, 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 kylecorry31/Trail-Sense acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 95.4% were successfully merged into the primary branch.
kylecorry31/Trail-Sense has a recorded first-timer success rate of 71.4%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 67.7 places kylecorry31/Trail-Sense in the Welcoming tier.
The external pull request merge rate is 95.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
kylecorry31/Trail-Sense 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 kylecorry31/Trail-Sense 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.