A cli tool to browse and play anime
C-Rank Grade: B (Solid) - 49/100
External PR Merge Rate: 42%
Response Time: 2d
First Timer Success: 42%
pystardust/ani-cli has a recorded first-timer success rate of 41.7%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in pystardust/ani-cli respond to incoming external pull requests in approximately 54.8 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 48.8 places pystardust/ani-cli in the B tier.
The external contributor pull request merge rate for pystardust/ani-cli is 41.9%, based on public PR activity from non-core contributors.
pystardust/ani-cli does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Rigorous architecture standards (75% critical review signals). Ensure PRs strictly follow guidelines before requesting review in pystardust/ani-cli.
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/pystardust/ani-cli?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~36 hours (52% approval). Large PRs (>500 lines) take ~267 hours (19% approval). Keep your diff compact for rapid review.
Is your feature request related to a problem? Please describe. Neither my file manager nor my old SSD like the countless small files appearing and vanishing in quick succession (it crashes). Also makes it hard to find the video to watch while the other episodes are still downloading. Which is why i would like to move the path of the temporary fragments to XDG_RUNTIME_DIR or /tmp. Describe the solution you'd like A cli parameter or environment variable or config option Describe alternatives you've considered Creating a wrapper that first moves there, then the done downloads here. But that's a hack. Additional context Looks like the script uses yt-dlp, so there it would be the -P/--paths option i think? If so, you can just pass that through.
Is your feature request related to a problem? Please describe. This is related to my problem for #1850. I used a wrapper script which calls ani-cli to play a specific episode from a specific show, but since only one result appeared for the show I searched and it was the wrong show, it was auto selected and started playing without any warning that it wasn't an exact match. Describe the solution you'd like For scripting it would be nice to have some flag to force an exact match against the titles of the search results (--exact or --exact-match).
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 pystardust/ani-cli, 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 pystardust/ani-cli acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 41.9% were successfully merged into the primary branch.
pystardust/ani-cli has a recorded first-timer success rate of 41.7%. Repositories ranked Solid 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 48.8 places pystardust/ani-cli in the Solid tier.
The external pull request merge rate is 41.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
pystardust/ani-cli does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for pystardust/ani-cli 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.