Wild Me's first product, Wildbook supports researchers by allowing collaboration across the globe and automation of photo ID matching
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 73%
Response Time: 5d
First Timer Success: 20%
WildMeOrg/Wildbook has a recorded first-timer success rate of 20.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in WildMeOrg/Wildbook respond to incoming external pull requests in approximately 126.4 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 56.8 places WildMeOrg/Wildbook in the A tier.
The external contributor pull request merge rate for WildMeOrg/Wildbook is 73.2%, based on public PR activity from non-core contributors.
WildMeOrg/Wildbook currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly encouraging & supportive maintainers (100% positive review sentiment). Active code reviews with constructive guidance for new contributors in WildMeOrg/Wildbook.
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/WildMeOrg/Wildbook?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 Tuesday - Thursday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~82 hours (91% approval). Large PRs (>500 lines) take ~607 hours (33% approval). Keep your diff compact for rapid review.
Expected behavior Users can delete the default "12" from the Number of results field on the match page (/react/match-results) and enter their own value. Current behavior If a user tries to delete the "12" from the field before typing a new value, the 1 still remains. Workaround is to highlight the number and then type over the highlighted text. QA notes Replicated in Edge, Firefox, Chrome, Brave, and Safari.
Expected behavior When you click the Edit button on an Individual page (individuals.jsp) one of the available fields to edit is the taxonomy. Current behavior Taxonomy is the only metadata field on the Individual page that can't be edited. Even if the associated encounters have been updated with the correct taxonomy, the individual page will only display the original one. Examples: https://giraffespotter.org/individuals.jsp?id=98fefafb-2fd7-4cf4-895f-52a7b6e0657e https://giraffespotter.org/individuals.jsp?id=a1b900a1-c9d1-4f6b-8a3f-8c86a7dfa15b QA notes This does not appear to be a new bug, just a design flaw. Older versions of Wildbook (like Seadragon) behave the same way. May need to be rolled up as part of Individual page redesign. Community link Reported by ZCP via email to @goddesswarship 8/11/26
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 WildMeOrg/Wildbook, 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 WildMeOrg/Wildbook acknowledge new external contributions in approximately 5 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 73.2% were successfully merged into the primary branch.
WildMeOrg/Wildbook has a recorded first-timer success rate of 20.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 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 56.8 places WildMeOrg/Wildbook in the Welcoming tier.
The external pull request merge rate is 73.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, WildMeOrg/Wildbook currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for WildMeOrg/Wildbook 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.