juananzzz/resonus - Open Source PR Review Scorecard

A clean Android music player for your self-hosted server, and your local files.

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

External PR Merge Rate: 59%

Response Time: 1d

First Timer Success: 75%

Frequently Asked Questions

Is juananzzz/resonus welcoming to first-time open-source contributors?

juananzzz/resonus 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.

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

Maintainers in juananzzz/resonus respond to incoming external pull requests in approximately 24.7 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 65.7 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 65.7 places juananzzz/resonus in the A tier.

What is the external contributor pull request merge rate for juananzzz/resonus?

The external contributor pull request merge rate for juananzzz/resonus is 59.1%, based on public PR activity from non-core contributors.

Are there Good First Issues available in juananzzz/resonus?

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

juananzzz
juananzzz/resonusA•Welcoming182
GitHub
Back to Explorer
juananzzz

juananzzz/resonus

182
InactiveA•Welcoming(66/100)TypeScript

A clean Android music player for your self-hosted server, and your local files.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Architecture Gatekeeper

Warmth Score
7.0/10
Patience Score
7.6/10
Nitpick Rate
55%

Strict review standards in juananzzz/resonus. Ensure PR scope matches issue requirements closely before requesting review.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
1 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
59.1%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
8 core
Highly collaborative maintainer core
Diagnostic Health HUD
59.1%
Merge Gauge
75.0%
1st-Timer
Community Vibe58/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

Description I would like to propose a new feature for Resonus that implements a smart, self-managing offline cache for music streaming. This would significantly improve the user experience in areas with poor connectivity, reduce mobile data usage, and provide seamless playback without manual intervention. Proposed solution Add a new section in the Downloads / Storage settings menu with the following options: Enable Smart Cache – Toggle ON/OFF Cache Size Limit – User-selectable dropdown (e.g., 2GB, 4GB, 8GB, 16GB, Unlimited) When enabled, the app would: Automatically cache every track the user streams (both full plays and partial listens) to internal device storage. Serve cached files locally on subsequent plays – if the track exists in the cache, play it from storage instead of re-downloading from the server, saving bandwidth and ensuring offline playback. Evict files intelligently when the cache reaches the defined size limit, using a Least Recently Used (LRU) + oldest-first

📅 Opened Aug 25, 2026💬 1 comment
Quality: 50/100Contribute

Description Requested by @ztx-lyghters. The idea is to share a reference to an object on a server so that another user of the same instance, also using Resonus, can open it in their own app and look at it. Albums, artists and public playlists all have a permanent id, so a link can point at one. This is not what the existing Share does. That one asks the server for a public link anybody can open in a browser. This is for pointing somebody who already has an account on that server at something inside their own library. Power Ampache 2 does this for the Ampache backend. There is no standard for it on the Subsonic side, and the hopes of one are not high: navidrome/navidrome#2378 (comment) Proposed solution Two halves. Creating. From the ⋯ of an album, an artist or a playlist, with a choice between sharing to another app and copying to the clipboard. Shared to another app it would carry a line of text and the link below it, something like: Check out <name> by <artist> on <server domain> r

📅 Opened Aug 23, 2026💬 2 comments
Quality: 90/100Contribute

Description i want u to add support for TTML lyrics, for example took feishin navidrome already got ttml lyrics support ttml.txt - example of ttml lyrics (file was called 01 - Usseewa - Ado.ttml on server) Proposed solution as i seen there is karaoke style lyrics support (idk which lyrics format tho. it doesnt work with apple ttml/or any other generated ttml's for me). so its just adding another parser for lyrics / improving current one

📅 Opened Aug 21, 2026💬 0 comments
Quality: 50/100Contribute

Description To me this looks like holding a map per server config that can be optionally set before login and at the settings page, and those headers would just be sent with http requests to that server My use-case is gating all requests to navidrome through custom http header secrets, that way I can serve navidrome publicly over the internet and my family can use my instance without installing tailscale. So nothing can even hit the login page without having a secret, which doesnt require frequent updates or user instruction to work. Proposed solution No response

📅 Opened Aug 19, 2026💬 1 comment
Quality: 50/100Contribute

Description The app only works in portrait. Proposed solution Let the screen rotate and lay the screens out for the wider space, so it works in landscape and on tablets.

📅 Opened Aug 7, 2026💬 3 comments
Quality: 65/100Contribute
Looking for more TypeScript beginner tasks?Explore TypeScript 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 juananzzz/resonus

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

Frequently Asked Questions - Contributing to juananzzz/resonus

01

Is juananzzz/resonus welcoming to first-time open-source contributors?

juananzzz/resonus 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.

02

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

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

03

What does the 65.7 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 65.7 places juananzzz/resonus in the Welcoming tier.

04

What is the external contributor pull request merge rate for juananzzz/resonus?

The external pull request merge rate is 59.1%. 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 juananzzz/resonus?

Yes, juananzzz/resonus currently has 3 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 juananzzz/resonus 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.