Browser Harness | Self-healing harness that enables LLMs to complete any task.
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 39%
Response Time: -
First Timer Success: 28%
browser-use/browser-harness has a recorded first-timer success rate of 28.2%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in browser-use/browser-harness 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.0 places browser-use/browser-harness in the A tier.
The external contributor pull request merge rate for browser-use/browser-harness is 39.1%, based on public PR activity from non-core contributors.
browser-use/browser-harness currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in browser-use/browser-harness. 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/browser-use/browser-harness?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 23:00 to 03:00 UTC (23:00 - 03:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (49% approval). Large PRs (>500 lines) take ~115 hours (18% approval). Keep your diff compact for rapid review.
Environment-specific setup challenges (Lubuntu / Snap / Minimal Python) Description: Attempted to set up browser-harness on a Lubuntu environment and encountered several blockers related to Snap confinement, portable binary stability, and environment assumptions. Key Issues Found: Snap Confinement: Default browsers (chromium, firefox) on Ubuntu/Lubuntu are Snaps. These run in a restricted mount namespace that prevents binding to the CDP port (9222) even with --no-sandbox. The harness's automatic discovery fails silently or with "Connection Refused." Portable Binary Instability: Attempted to bypass Snap using Playwright's Chromium binaries. Encountered fatal GPU and Zygote initialization errors (FATAL:gpu_data_manager_impl_private.cc:416). Even with --disable-gpu and --no-sandbox, the browser failed to maintain a stable connection in this restricted environment. Missing pip Dependency: The setup assumes python3 -m pip is available for uv or manual installs. On minimal Lubuntu installs,
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 browser-use/browser-harness, 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 browser-use/browser-harness acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 39.1% were successfully merged into the primary branch.
browser-use/browser-harness has a recorded first-timer success rate of 28.2%. 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.0 places browser-use/browser-harness in the Welcoming tier.
The external pull request merge rate is 39.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, browser-use/browser-harness 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 browser-use/browser-harness 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.