Listenarr automates audiobook collection management similar to Sonarr or Radarr, but for audiobooks. It can search, download, and organize your library automatically using metadata from Audible and other sources.
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 32%
Response Time: 4d
First Timer Success: 27%
Listenarrs/Listenarr has a recorded first-timer success rate of 26.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Listenarrs/Listenarr respond to incoming external pull requests in approximately 86.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 56.7 places Listenarrs/Listenarr in the A tier.
The external contributor pull request merge rate for Listenarrs/Listenarr is 32.4%, based on public PR activity from non-core contributors.
Listenarrs/Listenarr currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in Listenarrs/Listenarr. 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/Listenarrs/Listenarr?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 20:00 UTC (20: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 ~56 hours (41% approval). Large PRs (>500 lines) take ~416 hours (15% approval). Keep your diff compact for rapid review.
Context When importing files from downloads for audiobooks with already imported files, we try to determine the following informations: Best quality of existing files Quality of the current file being processed If the audio book has a quality profile set: We use those to skip file when the quality is not better than the one we already have Effectively, I could not write tests for that behavior nor could I determine precisely which use case it covers. Suggestion I suggest that, when we import a download, the following should be done: Determine the quality of the existing audiobook Determine the quality of the download Check the defined profile strategy Skip the whole import if the quality is not better Remove all existing files if the quality is better I'm not sure what heuristic we should use to determine the quality of those though, a first approach could be to compare to take the best or worst (this is already what's implemented) Regarding the quality determination algorithm,
Another issue related to naming structure. If I set single file or multipart file naming with {Title} is is also adding {Subtitle} afterwards. For example, If in a audiobook's metadata I have this: Title: Example Subtitle: Yup It is naming the file --> Example - Yup.ext instead of just Example.ext Is this intended or a bug? Originally posted by @lamb0985 in #504 Sounds like we should either make it explicit (change the configured naming pattern and notify the user) or apply given naming patterns exactly Either way, it's worth investigating
When importing/matching existing audiobooks into Listenarr, it would be great if search results could show the narrator. Some audiobooks have multiple recordings with different narrators and this would really help get the correct match. Compare with the equivalent screen in Audiobookshelf which provides extra data, including the narrator and publication year: Thank you for your consideration.
I noticed the total size of the audiobook given in the summary is not the sum of all the MP3 files that are part of that audiobook. I also noticed that not every audiobook gives the total size in the summary, and I haven't been able to figure out why some have it and some don't. Happy to provide any extra info that would help with debugging.
Description While adding remote path mapping for a download client, if one enters the local path manually instead of using the file browser modal, that value will not be used to query the backend Expected behavior Either: If the value has not been set through the modal, retrieve it to query the backend with the input value Disable manual input on the field
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 Listenarrs/Listenarr, 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 Listenarrs/Listenarr acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 32.4% were successfully merged into the primary branch.
Listenarrs/Listenarr has a recorded first-timer success rate of 26.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 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.7 places Listenarrs/Listenarr in the Welcoming tier.
The external pull request merge rate is 32.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Listenarrs/Listenarr currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for Listenarrs/Listenarr 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.