LORIS is a web-accessible database solution for longitudinal multi-site studies.
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 66%
Response Time: 3d
First Timer Success: 75%
aces/Loris has a recorded first-timer success rate of 75.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in aces/Loris respond to incoming external pull requests in approximately 61.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 64.9 places aces/Loris in the A tier.
The external contributor pull request merge rate for aces/Loris is 66.1%, based on public PR activity from non-core contributors.
aces/Loris currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in aces/Loris. Maintains strict focus on technical quality and test standards.
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/aces/Loris?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~40 hours (83% approval). Large PRs (>500 lines) take ~296 hours (30% approval). Keep your diff compact for rapid review.
Is your feature request related to an existing module? The Candidate Parameter's Family tab allows a user to select the type of relationship between 2 candidates but the source of truth of the possible relationship types is defined in both SQL (family table) AND in the JavaScript code https://github.com/aces/Loris/blob/main/modules/candidate_parameters/jsx/FamilyInfo.js#L135 making project flexibility very limited without an override. Describe the solution you'd like There is no reason the options can not be loaded directly from the SQL, if it is done for proper labeling, we can use either an automatic underscore-to-space conversion or a name-label in SQL to manually define labels for each. Additional context The Candidate parameters module is reachable by going to access profile (candidate_list) --> click on a candidate --> click on candidate info. In some cases the Family tab is unaccessible if the study configuration does not have it enables (check config module)
We need the possibility of filtering dates using a range filter. It would be nice to be able to filter for >= or <= A JSX element should be created and can be added as a filter in Form.js. An existing UI element exists in the dashboard under the Statistics module. The filter should be added to the candidate_list module to filter DoB, as well as to replace the existing date range in dashboard.
On a fresh LORIS install without data, the dashboard pages has all the boxes and widgets but they are mostly empty. They should probably replaced with a message saying "No data collected yet" or something along those lines. To reproduce: Install a fresh copy of LORIS (without raisinbread) Login as the user created as part of the install process.
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 aces/Loris, 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 aces/Loris acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.1% were successfully merged into the primary branch.
aces/Loris has a recorded first-timer success rate of 75.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 64.9 places aces/Loris in the Welcoming tier.
The external pull request merge rate is 66.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, aces/Loris 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 aces/Loris 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.