A libre lightweight streaming front-end for Android.
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 52%
Response Time: -
First Timer Success: 41%
TeamNewPipe/NewPipe has a recorded first-timer success rate of 40.9%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in TeamNewPipe/NewPipe 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 62.7 places TeamNewPipe/NewPipe in the A tier.
The external contributor pull request merge rate for TeamNewPipe/NewPipe is 52.0%, based on public PR activity from non-core contributors.
TeamNewPipe/NewPipe currently has 8 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in TeamNewPipe/NewPipe. 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/TeamNewPipe/NewPipe?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (65% approval). Large PRs (>500 lines) take ~115 hours (23% approval). Keep your diff compact for rapid review.
Checklist I am able to reproduce the bug with the latest version given here: CLICK THIS LINK. I made sure that there are no existing issues - open or closed - which I could contribute my information to. I have read the FAQ and my problem isn't listed. I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise. This issue contains only one bug. I have read and understood the contribution guidelines. I have read and understood the AI policy. The content of this bug report is not generated by AI. Affected version 0.29.1 (F-Droid) Steps to reproduce the bug Install NewPipe 0.29.1 on a device running Android 6.0.1 Open the app Expected behavior The app opens normally Actual behavior The app crashes immediately on startup, before showing any content. Clearing app data does not help. Screenshots/Screen recordings No response Logs E ACRA: java.lang.RuntimeException: Unable to start activity ComponentInfo{org.schabi.newpipe
Checklist I am able to reproduce the bug with the latest version given here: CLICK THIS LINK. I made sure that there are no existing issues - open or closed - which I could contribute my information to. I have read the FAQ and my problem isn't listed. I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise. This issue contains only one bug. I have read and understood the contribution guidelines. I have read and understood the AI policy. The content of this bug report is not generated by AI. Affected version 0.29.0 Steps to reproduce the bug Close the app with a video slowly loading in. Reopen the app. Expected behavior No crash Actual behavior Crash Screenshots/Screen recordings No response Logs Exception User Action: ui error Request: ACRA report Content Country: NL Content Language: en-NL App Language: en_NL Service: <unknown_service> Timestamp: 2026-08-16T11:52:10.943+03:00 Package: org.schabi.newpipe Servic
Checklist I am able to reproduce the bug with the latest version given here: CLICK THIS LINK. I made sure that there are no existing issues - open or closed - which I could contribute my information to. I have read the FAQ and my problem isn't listed. I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise. This issue contains only one bug. I have read and understood the contribution guidelines. I have read and understood the AI policy. The content of this bug report is not generated by AI. Affected version 0.28.6 and all release versions Description On the history page, when the list of entries is long, and the user scrolls up to see more entries, the control buttons at the top (Sort button + action buttons: Background | Play All | Popup) scroll together with the list and disappear from view. This can make it inconvenient for users to quickly sort or perform actions, as they have to scroll back to the top to acce
Checklist I made sure that there are no existing issues - open or closed - which I could contribute my information to. I have read the FAQ and my problem isn't listed. I'm aware that this is a request for NewPipe itself and that requests for adding a new service need to be made at NewPipeExtractor. I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise. This issue contains only one feature request. I have read and understood the contribution guidelines. I have read and understood the AI policy. The content of this request is not generated by AI. Feature description Toggle switch somewhere in settings (maybe a new Network category even, if that would be appropriate) to switch off the use of IPv6 for fetching content. Why do you want this feature? YouTube is particularly bad about forcing "sign in to confirm you're not a bot" on IPv6 networks (and Google in general tends to apply draconian levels of CAPTCHA to
Discussed in #13323 Originally posted by Minus46 March 8, 2026 Checklist I made sure that there are no existing issues or discussions - open or closed - which I could contribute my information to. I have read the FAQ and my question isn't listed. I have taken the time to fill in all the required details. I understand that the question will be dismissed otherwise. I have read and understood the contribution guidelines. What is/are your question(s)? Hello everybody. I love newpipe. I was wondering if the Newpipe Team feel like adding a always repeat on? Everytime i restart the App the repeat button is off. I hope in the future The NewPipe Team adds an option to always have the repeat on. Thank you kindly sirs. Additional information No response
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 TeamNewPipe/NewPipe, 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 TeamNewPipe/NewPipe acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 52.0% were successfully merged into the primary branch.
TeamNewPipe/NewPipe has a recorded first-timer success rate of 40.9%. 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 62.7 places TeamNewPipe/NewPipe in the Welcoming tier.
The external pull request merge rate is 52.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, TeamNewPipe/NewPipe currently has 8 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for TeamNewPipe/NewPipe 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.