Stremio and Nuvio addon for movie and series recommendation
C-Rank Grade: B (Solid) - 66/100
External PR Merge Rate: 67%
Response Time: <1h
First Timer Success: 100%
TimilsinaBimal/Watchly has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in TimilsinaBimal/Watchly respond to incoming external pull requests in approximately 0.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 66.0 places TimilsinaBimal/Watchly in the B tier.
The external contributor pull request merge rate for TimilsinaBimal/Watchly is 66.7%, based on public PR activity from non-core contributors.
TimilsinaBimal/Watchly currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in TimilsinaBimal/Watchly welcoming community pull requests and bug fixes.
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/TimilsinaBimal/Watchly?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (83% approval). Large PRs (>500 lines) take ~3 hours (30% approval). Keep your diff compact for rapid review.
Problem statement Watchly generates personalized movie and series recommendations, but they are currently mainly available through its Stremio catalogs. Users who also use Trakt-compatible applications cannot easily reuse these recommendations outside Stremio. They would need to manually find and add each recommended title to a Trakt list. Proposed solution Add an optional feature to export a selected Watchly recommendation catalog to a custom Trakt list. Users should be able to choose which catalog to export and whether the Trakt list should be replaced or updated during synchronization. Movies and series could either be exported to separate lists or combined when supported. Alternatives considered One alternative is to create an external script that reads the Watchly catalog endpoints and updates a Trakt list separately. This is possible, but it requires users to deploy and configure another service. It would also duplicate Watchly's authentication, scheduling, identifier matching, a
As title says, make a template for Unraid to install and update it there easier
Problem statement Stremio Supporters accounts now support multiple profiles, allowing each profile to maintain its own library, watch history, and recommendations. Watchly currently does not support Stremio profiles. When a user signs in to Watchly with a Stremio account, Watchly only accesses the library and watch history associated with the account’s primary profile. As a result, all Watchly recommendation catalogs are generated from the primary profile’s activity, even when the addon is installed or used under another Stremio profile. Proposed solution After the user signs in with Stremio, Watchly should retrieve the available profiles and prompt the user to select one. Watchly could then create a separate addon configuration or addon instance tied to the selected profile. Each instance should use only that profile’s library and watch history when generating recommendation catalogs. The selected profile should also be identifiable in the addon name or configuration URL so that
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 TimilsinaBimal/Watchly, 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 TimilsinaBimal/Watchly acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.7% were successfully merged into the primary branch.
TimilsinaBimal/Watchly has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 66.0 places TimilsinaBimal/Watchly in the Solid tier.
The external pull request merge rate is 66.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, TimilsinaBimal/Watchly 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 TimilsinaBimal/Watchly 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.