grimmory-tools/grimmory - Open Source PR Review Scorecard

A self-hosted library for your ebooks, comics, and audiobooks

C-Rank Grade: A (Welcoming) - 67/100

External PR Merge Rate: 71%

Response Time: -

First Timer Success: 55%

Frequently Asked Questions

Is grimmory-tools/grimmory welcoming to first-time open-source contributors?

grimmory-tools/grimmory has a recorded first-timer success rate of 54.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in grimmory-tools/grimmory 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.

What does the 67.0 C-Rank™ score (A Tier) represent?

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.0 places grimmory-tools/grimmory in the A tier.

What is the external contributor pull request merge rate for grimmory-tools/grimmory?

The external contributor pull request merge rate for grimmory-tools/grimmory is 71.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in grimmory-tools/grimmory?

grimmory-tools/grimmory currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

grimmory-tools
grimmory-tools/grimmoryA•Welcoming4.5k
GitHub
Back to Explorer
grimmory-tools

grimmory-tools/grimmory

4,496
Active (30d)A•Welcoming(67/100)Java

A self-hosted library for your ebooks, comics, and audiobooks

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Quality Architect

Warmth Score
7.1/10
Patience Score
7.6/10
Nitpick Rate
36%

Balanced & professional review environment in grimmory-tools/grimmory. Maintains strict focus on technical quality and test standards.

Top PR Submission Do's

  • •Add unit tests with >80% coverage for modified code paths
  • •Run repository linter and code formatters locally before pushing
  • •Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without referencing an existing issue
  • •Do not mix refactoring and feature logic into a single commit
  • •Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
-
No reviewer activity recorded

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
71.0%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
54.5%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
32 core
Highly collaborative maintainer core
Diagnostic Health HUD
71.0%
Merge Gauge
54.5%
1st-Timer
Community Vibe45/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for grimmory-tools/grimmory
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/grimmory-tools/grimmory)](https://getmerged.abhishekco.de/grimmory-tools/grimmory?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

Discussed in https://github.com/orgs/grimmory-tools/discussions/1738 Originally posted by jeypawlik June 13, 2026 What went wrong? I've re-made my Audiobook library several times now, trying to get the files to read correctly. When I tried "per folder" many files were out of order, sometimes not added to the root book at all, or added as it's own separate book. Merging books didn't seem to solve this issue. I re-made the library to be "per file" while still keeping my audiobook files within a folder per book. This seemed to work better and the files are in order and playing correctly. However, the "duration" on the main page for the audiobook is set to only read the first audio file (it doesn't seem to grab chapters in per file for some reason?). So if I have Example Book, and Example Book has 3 audio files in the folder: The correct file size is showing up (and wasn't showing up in the per folder option) The first audio file is 7h 26m, but the whole book is 14h 15m The "Duration" re

📅 Opened Sep 17, 2026💬 0 comments
Quality: 75/100Contribute

Description When a user is promoted to an admin, they should not have any library assignments, or content restrictions visible on their profile, and it should not appear as if they can be limited w/ their libraries or content restrictions. This should be consistent between the user creation flow, and the user editing flow. Acceptance Criteria When a user becomes an admin, either hide or clear all content restrictions for that user Similarly, ensure the library is cleared/hidden consistently (just double check- it should be as is) Ensure that the create user and edit user flows' UIs are consistent and effectively communicate that making a user an admin means they cannot have any library or content restrictions applied to them

📅 Opened Jun 10, 2026💬 6 comments
Quality: 70/100Contribute

Discussed in https://github.com/orgs/grimmory-tools/discussions/835 Originally posted by sabrina553 April 24, 2026 What would you like Grimmory to do? Provide options for notifications to mute to tray or reduce real estate as below with mobile use in mind What problem does this solve for you? Mobile versions become invisible once an excess of notifications are shown. furthermore, on mobile there is no access to the "notification-tray" Anything else? alternatively, Want to help out? I'm happy to help test and give feedback Before submitting I've searched existing discussions and this hasn't been suggested yet I've reviewed this report and have completed it as fully as I can

📅 Opened Apr 24, 2026💬 1 comment
Quality: 30/100Contribute

What Went Wrong? When attempting to update an audiobook cover using the "generate covers" or "generate custom covers" mass-metadata actions from the book view, the cover does not update. The action appears to run, but the original cover remains unchanged. Expected Behavior: The audiobook cover should visually update to the newly generated cover. Actual Behavior: The cover stays the same. How Can We Reproduce This? Go to the book view. Select an audiobook and a "normal" book, see here: on the pop-up click on "generate custom cover" See that normal cover updated, audiobook cover is not. What Should Have Happened? It should updated booth. Screenshots or Error Messages (Optional) No response Any Ideas on How to Fix This? (Optional) No response Your Setup Grimmory, nightly. Though it is inherited bug. What Build of Grimmory are you on? Nightly Before Submitting I've searched existing issues and confirmed this bug hasn't been reported yet

📅 Opened Apr 16, 2026💬 4 comments
Quality: 45/100Contribute

What documentation needs attention? If Bookdrop doesn't react when you add files: Use a local folder instead Adjust mount options to enable notification support What mount options would improve Bookdrop's ability to detect new files? This sounds like an LLM hallucination. Where did you run into this? (Optional) https://grimmory.org/docs/bookdrop What would improve it? Explain which mount options, if they exists, are relevant for NFS/SMB etc. to improve performance. Anything else? (Optional) No response Before Submitting I've searched existing issues and confirmed this documentation request hasn't been filed yet

📅 Opened Apr 12, 2026💬 1 comment
Quality: 30/100Contribute
Looking for more Java beginner tasks?Explore Java GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for grimmory-tools/grimmory

When evaluating whether to contribute to grimmory-tools/grimmory, 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 grimmory-tools/grimmory acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 71.0% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to grimmory-tools/grimmory

01

Is grimmory-tools/grimmory welcoming to first-time open-source contributors?

grimmory-tools/grimmory has a recorded first-timer success rate of 54.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 67.0 C-Rank™ score represent?

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.0 places grimmory-tools/grimmory in the Welcoming tier.

04

What is the external contributor pull request merge rate for grimmory-tools/grimmory?

The external pull request merge rate is 71.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in grimmory-tools/grimmory?

Yes, grimmory-tools/grimmory currently has 6 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for grimmory-tools/grimmory 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.