An open-source platform for managing biological and geological collections.
C-Rank Grade: D (Risky) - 30/100
External PR Merge Rate: -
Response Time: 3h
First Timer Success: -
specify/specify7 has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in specify/specify7 respond to incoming external pull requests in approximately 3.1 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 29.9 places specify/specify7 in the D tier.
The external contributor pull request merge rate for specify/specify7 is 0.0%, based on public PR activity from non-core contributors.
specify/specify7 currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
An open-source platform for managing biological and geological collections.
Collaborative maintainer environment in specify/specify7. Reviews community pull requests with focus on project quality.
Discussions in specify/specify7 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/specify/specify7?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (81% approval). Large PRs (>500 lines) take ~15 hours (29% approval). Keep your diff compact for rapid review.
Is your feature request related to a problem? Please describe. Reported by Nate Shoobs, OSU Mollusks sorts determinations by date descending, with the current determination and most recent determinations first. This is done using the following form XML: <row> <cell type="subview" viewname="Determination" id="66" name="determinations" colspan="14" rows="5" initialize="sortfield=-DeterminedDate"/> </row> A problem arises when determinations do not have a known determinedDate. The null value sorts at the beginning of the set of determinations, even in front of the one marked "Current". OSU frequently adds prior determinations from old labels that don't have dates associated, and each addition without a date jumps to the top ahead of the current determination. Describe the solution you'd like We could add an explicit null check at the top of both sortFunction and multiSortFunction in specifyweb/frontend/js_src/lib/utils/utils.ts so that empty values always sort to the end of the list (SQL'
Is your feature request related to a problem? Please describe. If your database does not currently include a remote user prefs app resource, it cannot be created on the front-end. Describe the solution you'd like There should be an option to create a remote user prefs app resource from the default when adding a resource at the global level. Describe alternatives you've considered Currently, you can create this by running the following: docker exec -it specify7 bash -c "ve/bin/python manage.py shell -c 'from specifyweb.backend.setup_tool.app_resource_defaults import create_app_resource_defaults; create_app_resource_defaults()'"
If a user is marked as an 'Institution Admin', their user will not appear under the collection view in Security and Accounts unless they had been given collection access prior to being assigned as an institution admin. To alleviate the confusion users have, we should show all institution admin users under each collection so it is very clear they have power there.
Describe the bug On a record with no attachments, if you open the attachment gallery, the download all button is enabled, in 7.11.4 the button was disabled. To Reproduce Steps to reproduce the behavior: Create a new record on any table that supports attachments Save without adding an attachment Click the attachment icon in the top right See error Expected behavior The button should be disabled to match the behavior in 7.11.4 Screenshots 7.12: 7.11.4: Please fill out the following information manually: OS: Windows 11 Browser: Chrome Specify 7 Version: 7.12 Database Name: ojsmnh Collection name: fossil invertebrates User Name: spadmin URL: https://ojsmnh20260326-v7120-prerelease.test.specifysystems.org/specify/
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 specify/specify7, 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 specify/specify7 acknowledge new external contributions in approximately 3 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
specify/specify7 has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 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 29.9 places specify/specify7 in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, specify/specify7 currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for specify/specify7 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.