An open source and lightweight music client for Subsonic, designed and built natively for Android.
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 81%
Response Time: -
First Timer Success: 90%
eddyizm/tempus has a recorded first-timer success rate of 90.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in eddyizm/tempus 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.
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.4 places eddyizm/tempus in the A tier.
The external contributor pull request merge rate for eddyizm/tempus is 81.5%, based on public PR activity from non-core contributors.
eddyizm/tempus currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in eddyizm/tempus. Prompt code reviews with positive guidance for new contributors.
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/eddyizm/tempus?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (37% approval). Keep your diff compact for rapid review.
Summary Hi, love the new icon compared to the previous Tempo app. It would be nice if you could submit your own themed icon to the arcticons team. Description I use a launcher (Nova Launcher) that supports theming app icons. Most of my app icons are provided by Arcticons icons library. I recently moved from Tempo to Tempus ❤ and I would love to have the same experience with Tempus. Could it be possible create an Arcticons icon and submit it to the Arcticons team please? Use Case I think a lot of efforts went into developing this app, and it would be great to have the same integrated experience as it was with Tempo. Additional context I see Tempus in on their request dashboard https://arcticons.com/dashboard/requests/ already. Thank you for considering this request.
Describe the bug Tempus stops playback when attempting to start the next song in a playlist containing more than one song. Once a song has started playing, playback completes without any issues. The problem occurs specifically at the moment when Tempus attempts to start a new song. Clicking the play button works after the issue happens, and the issue happens again after a few songs. Sometimes it occurs after playing 1 song, and other times it occurs after playing multiple songs (e.g., 5 songs). Tempus was in the background and never got closed (battery optimizations are off), tried multiple settings too, like switching between AAC and OPUS, toggling EQ on and off, disabling scrobbling, etc, none of these fixed the issue. Expected behavior When playing a more than one song, Tempus should automatically and consistently start playback of the next song after the current song finishes, without requiring user interaction. To Reproduce Start playing a playlist with many songs Press the Home
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 eddyizm/tempus, 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 eddyizm/tempus acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 81.5% were successfully merged into the primary branch.
eddyizm/tempus has a recorded first-timer success rate of 90.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 65.4 places eddyizm/tempus in the Welcoming tier.
The external pull request merge rate is 81.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, eddyizm/tempus currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for eddyizm/tempus 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.