libredirect/browser_extension - Open Source PR Review Scorecard

A browser extension that redirects popular sites to alternative privacy friendly frontends

C-Rank Grade: D (Risky) - 21/100

External PR Merge Rate: -

Response Time: 10d

First Timer Success: -

Frequently Asked Questions

Is libredirect/browser_extension welcoming to first-time open-source contributors?

libredirect/browser_extension 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.

How fast can I expect code review feedback on my pull request?

Maintainers in libredirect/browser_extension respond to incoming external pull requests in approximately 235.2 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 21.4 C-Rank™ score (D Tier) represent?

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 21.4 places libredirect/browser_extension in the D tier.

What is the external contributor pull request merge rate for libredirect/browser_extension?

The external contributor pull request merge rate for libredirect/browser_extension is 0.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in libredirect/browser_extension?

libredirect/browser_extension currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

libredirect
libredirect/browser_extensionD•Risky4.1k
GitHub
Back to Explorer
libredirect

libredirect/browser_extension

4,069
InactiveD•Risky(21/100)Low Sample (<20 PRs)JavaScript

A browser extension that redirects popular sites to alternative privacy friendly frontends

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
20%

Active maintainer team in libredirect/browser_extension welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • •Ensure code complies with repository style conventions
  • •Keep PRs focused and well-documented

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
Response Velocity
9 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
0.0%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
0.0%
No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
4 core
Small core review team
Diagnostic Health HUD
0.0%
Merge Gauge
0.0%
1st-Timer
Community Vibe0/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for libredirect/browser_extension
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/libredirect/browser_extension)](https://getmerged.abhishekco.de/libredirect/browser_extension?utm_source=github&utm_medium=badge)

Active Good First Issues (3)

View on GitHub

Currently certain features with respect to frontends are done in a manual basis when a new frontend is added. Creating additional work. The proposal is, we create a template For example, Copy raw - The function will be available for every frontend by default. The template is copy original link. It writes the original link to the clipboard and the template contains instructions to fetch original link from the frotnend-{name}.js . Now, the extensions, checks the active frontend. If in a redlib instance. It finds the reddit redirection service file and undo the redirect logic that was done by extension and copy link to clipboard. This way, a generic service file will be available. It just needs to be linked to the frontend serivce file where the logic is already there. So, no need to manually create these buttons everytime there is a new frontend. There is already a lot of frontends that doesn't have these features that are available in libredirect. They would benefit too. This requires

📅 Opened Sep 25, 2026💬 0 comments
Quality: 90/100Contribute

Create a scripting file, that checks if all URLs are properly redirected with different combination of settings along with features such as redirect to original, preferred instance, copy Raw & their keyboard settings, sync settings - both file & accounts, etc across browsers and Operating systems. This helps to release the extension quickly without manually checking everything by hand and saves a lot of time. This can be a script first to check locally on the developer machine first. Expand to Github CI pipeline down the road to utilize and check in other operating systems and browser to cater to multitude of users.

📅 Opened Sep 23, 2026💬 0 comments
Quality: 90/100Contribute

So originally I wanted to ask about grayjay support, however that's already been asked for and doesn't seem to have much traction (at least at a glance, I haven't looked at anything outside this feature request). I am aware grayjays licensing makes a lot of open source focused developers uncomfortable, since it's not an open source license but rather a source available license, at least based off some interactions I've had. So I was thinking, instead of requesting support for grayjay specifically, maybe adding a feature to "redirect to an external application" and the user could just select an application installed on their system?

📅 Opened Jun 8, 2026💬 4 comments
Quality: 55/100Contribute
Looking for more JavaScript beginner tasks?Explore JavaScript GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for libredirect/browser_extension

When evaluating whether to contribute to libredirect/browser_extension, 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 libredirect/browser_extension acknowledge new external contributions in approximately 9 days+. 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.

Frequently Asked Questions - Contributing to libredirect/browser_extension

01

Is libredirect/browser_extension welcoming to first-time open-source contributors?

libredirect/browser_extension 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.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~9 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 21.4 C-Rank™ score represent?

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 21.4 places libredirect/browser_extension in the Risky tier.

04

What is the external contributor pull request merge rate for libredirect/browser_extension?

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.

05

Are there beginner Good First Issues open in libredirect/browser_extension?

Yes, libredirect/browser_extension currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for libredirect/browser_extension 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.