A libre Android browser built from scratch on Gecko. Privacy by default, powerful tab containers, and a local-first search engine.
C-Rank Grade: D (Risky) - 19/100
External PR Merge Rate: -
Response Time: 19h
First Timer Success: -
FaFre/WebLibre has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in FaFre/WebLibre respond to incoming external pull requests in approximately 18.6 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 19.0 places FaFre/WebLibre in the D tier.
The external contributor pull request merge rate for FaFre/WebLibre is 0.0%, based on public PR activity from non-core contributors.
FaFre/WebLibre does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Balanced & professional review environment in FaFre/WebLibre. 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/FaFre/WebLibre?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
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~12 hours (81% approval). Large PRs (>500 lines) take ~89 hours (29% approval). Keep your diff compact for rapid review.
Describe the bug After setting a custom user agent and removing it, the desktop toggle no longer works until the browser profile is fully reset or when creating a new profile To Reproduce Steps to reproduce the behavior: Go to Settings Go to Advanced Set any Custom User Agent Remove Custom User Agent Try the Desktop mode toggle Expected behavior User Agent changes to a desktop user agent for sites to detect after using a Custom User Agent Videos https://files.muppie.xyz/Shares/8dnfjshit9gd/screen-20260914-081244-1789344666446.mp4 Device / App (please complete the following information): Device: Xiaomi Redmi Note 13 Pro 5G OS: Android 16 QPR2 (LineageOS 23.2) App Version: v0.30.0 Exists in the latest alpha release Additional context Here is my WebLibre config json, if needed weblibre-settings_2026-09-14_083547.json
Describe the bug When opening external links, the prompt to select what container to open and whether to open it in a custom tab does not show up upon loading WebLibre when fully stopped. The prompt will only open once WebLibre is already running To Reproduce Steps to reproduce the behavior: Have external link handling set to prompt Quit/Force stop WebLibre Open an external link Expected behavior The prompt should show even when the app has fully stopped Videos https://github.com/user-attachments/assets/f44bb58b-c602-4020-a4e0-79b8eace93f8 Device / App (please complete the following information): Device: Xiaomi Redmi Note 13 Pro 5G OS: Android 16 QPR2 (LineageOS 23.2) App Version: v0.30.0-alpha-6-alpha Exists in the latest alpha release: [/] Additional context WebLibre v0.30.0 Alpha 6 introduces this bug and is not present on Alpha 5
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 FaFre/WebLibre, 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 FaFre/WebLibre acknowledge new external contributions in approximately 18 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
FaFre/WebLibre has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~18 hours. 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 19.0 places FaFre/WebLibre in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
FaFre/WebLibre does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for FaFre/WebLibre 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.