Undetected version of the Playwright testing and automation library.
C-Rank Grade: B (Solid) - 50/100
External PR Merge Rate: 55%
Response Time: 3d
First Timer Success: 100%
Kaliiiiiiiiii-Vinyzu/patchright 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 Kaliiiiiiiiii-Vinyzu/patchright respond to incoming external pull requests in approximately 78.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 50.3 places Kaliiiiiiiiii-Vinyzu/patchright in the B tier.
The external contributor pull request merge rate for Kaliiiiiiiiii-Vinyzu/patchright is 54.5%, based on public PR activity from non-core contributors.
Kaliiiiiiiiii-Vinyzu/patchright currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Undetected version of the Playwright testing and automation library.
Active maintainer team in Kaliiiiiiiiii-Vinyzu/patchright 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/Kaliiiiiiiiii-Vinyzu/patchright?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 Monday - Wednesday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~51 hours (68% approval). Large PRs (>500 lines) take ~378 hours (25% approval). Keep your diff compact for rapid review.
patchright 1.61.2, Chrome 151.0.7922.76, macOS. A headed launch_persistent_context with channel="chrome" opens with Chrome's bad-flags bar under the address bar: "You are using an unsupported command-line flag: --disable-blink-features=AutomationControlled. Stability and security will suffer." import time from patchright.sync_api import sync_playwright with sync_playwright() as p: ctx = p.chromium.launch_persistent_context( "/tmp/patchright-repro-profile", channel="chrome", headless=False, no_viewport=True, chromium_sandbox=True) ctx.pages[0].goto("https://example.com") time.sleep(60) ctx.close() Dropping the flag with ignore_default_args gets rid of the bar, but then navigator.webdriver is back to true, so that's not really an option. Pages can't see the infobar so it's not a detection issue, but our users are asked to log in in that window and it's not a great first impression. Is there a way to keep webdriver false without the bar? --test-type hides
I’m using PatchRight Node.js for my scrapers and it works well on all my targets. However, when I run the Docker container on a Windows PC with an x86_64 architecture it successfully retrieves the page. However, using my M3 Mac triggers the bot protections. I suspect this is due to the architecture. Has anyone else experienced this issue? Is there a solution? I’d like to run my scraper in a Docker container on an ARM64 architecture device.
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 Kaliiiiiiiiii-Vinyzu/patchright, 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 Kaliiiiiiiiii-Vinyzu/patchright acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 54.5% were successfully merged into the primary branch.
Kaliiiiiiiiii-Vinyzu/patchright 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 ~3 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 50.3 places Kaliiiiiiiiii-Vinyzu/patchright in the Solid tier.
The external pull request merge rate is 54.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Kaliiiiiiiiii-Vinyzu/patchright currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for Kaliiiiiiiiii-Vinyzu/patchright 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.