Open-source AI browser agent for Chrome and Firefox (monorepo) 🧠
C-Rank Grade: S (Elite) - 73/100
External PR Merge Rate: 89%
Response Time: -
First Timer Success: 85%
webbrain-one/webbrain has a recorded first-timer success rate of 84.6%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in webbrain-one/webbrain 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 72.9 places webbrain-one/webbrain in the S tier.
The external contributor pull request merge rate for webbrain-one/webbrain is 88.8%, based on public PR activity from non-core contributors.
webbrain-one/webbrain currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Open-source AI browser agent for Chrome and Firefox (monorepo) 🧠
Strict review standards in webbrain-one/webbrain. Ensure PR scope matches issue requirements closely before requesting review.
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/webbrain-one/webbrain?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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (40% approval). Keep your diff compact for rapid review.
We need help testing the nine CMS content workflows added in #3114 against real installations and real model runs. Automated coverage exercises packaged skills, permissions, synthetic HTTP fixtures and local browser modules; it does not establish that authentication, custom editors and publishing work on every live CMS. Testing just one CMS, one browser and one workflow is useful. Please report both successes and failures, including cases where WebBrain correctly falls back to the editor because the API is unavailable. Use a build from the latest main containing #3114, following the local installation instructions. Use a site/environment you control and disposable test content. See CMS API-first scope and limitations for supported APIs, authentication and fallback behavior. You do not need to buy a plan, install integrations or change account permissions to participate. We are looking for reports on: CMS Areas to check Ghost Posts versus pages, Lexical/cards, tags/authors, draft
Right now you can't attach file to the plugin by drag'n drop, you have to click the attachment icon.
Summary Propose adding a dedicated, structured intent field to LLM responses when operating in Ask mode. When a user request requires action/mutation capabilities, the model signals that Act mode is needed, allowing WebBrain to deterministically render a one-click mode switch button in the UI. Problem Attempting to detect mode-switch requirements by parsing natural language output is fragile, error-prone, and not language-agnostic. Heuristic text matching or regex parsing across different languages and prompt variations leads to inconsistent UI behavior. Proposed Solution Structured Intent Field: Extend the response payload in Ask mode to include an explicit field (e.g., requires_mode: "act" or intent: "switch_to_act") indicating when an action cannot be completed within Ask mode. Deterministic Client UI: When this field is present, WebBrain immediately renders a dedicated button in the UI, enabling the user to switch to Act mode in a single click. Language Agnostic: Decouples intent
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 webbrain-one/webbrain, 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 webbrain-one/webbrain acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 88.8% were successfully merged into the primary branch.
webbrain-one/webbrain has a recorded first-timer success rate of 84.6%. Repositories ranked Elite 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 72.9 places webbrain-one/webbrain in the Elite tier.
The external pull request merge rate is 88.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, webbrain-one/webbrain currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for webbrain-one/webbrain 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.