loxilb-io/loxilb - Open Source PR Review Scorecard

eBPF based cloud-native load-balancer for Kubernetes|Edge|Telco|IoT|XaaS.

C-Rank Grade: B (Solid) - 65/100

External PR Merge Rate: 93%

Response Time: 2d

First Timer Success: 50%

Frequently Asked Questions

Is loxilb-io/loxilb welcoming to first-time open-source contributors?

loxilb-io/loxilb has a recorded first-timer success rate of 50.0%. Repositories ranked B 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 loxilb-io/loxilb respond to incoming external pull requests in approximately 47.6 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 65.2 C-Rank™ score (B 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 65.2 places loxilb-io/loxilb in the B tier.

What is the external contributor pull request merge rate for loxilb-io/loxilb?

The external contributor pull request merge rate for loxilb-io/loxilb is 93.2%, based on public PR activity from non-core contributors.

Are there Good First Issues available in loxilb-io/loxilb?

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

loxilb-io
loxilb-io/loxilbBSolid1.9k
GitHub
Back to Explorer
loxilb-io

loxilb-io/loxilb

1,870
BSolid(65/100)Go

eBPF based cloud-native load-balancer for Kubernetes|Edge|Telco|IoT|XaaS.

Compare
Jump to:
Response Velocity
1 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
93.2%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
50.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
93.2%
Merge Gauge
50.0%
1st-Timer
Community Vibe52/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

Describe the bug Lets say i configure firewall rule as shown below. Then i restart the loxilb pod .. After that , the below rule is not found. loxicmd create firewall --firewallRule="sourceIP:200.0.0.101/32" --snat=100.0.0.10 To Reproduce Lets say i configure firewall rule as shown below. Then i restart the loxilb pod .. After that , the below rule is not found. loxicmd create firewall --firewallRule="sourceIP:200.0.0.101/32" --snat=100.0.0.10 Expected behavior Firewall should persist across loxilb pod restarts. Screenshots Environment (please complete the following information): OS: Ubuntu 20.04 Kernel Version: 6.8.0-101-generic LoxiLB Version: 0.9.8.5 Cloud Environment: On-prem K8s cluster K8s Version - 1.33.7 Additional context Add any other context or topology about the problem here.

📅 Opened Jun 9, 2026💬 3 comments
Quality: 80/100Contribute
Looking for more Go beginner tasks?Explore Go 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 loxilb-io/loxilb

When evaluating whether to contribute to loxilb-io/loxilb, 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 loxilb-io/loxilb acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 93.2% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to loxilb-io/loxilb

01

Is loxilb-io/loxilb welcoming to first-time open-source contributors?

loxilb-io/loxilb has a recorded first-timer success rate of 50.0%. Repositories ranked Solid 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 ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 65.2 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 65.2 places loxilb-io/loxilb in the Solid tier.

04

What is the external contributor pull request merge rate for loxilb-io/loxilb?

The external pull request merge rate is 93.2%. 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 loxilb-io/loxilb?

Yes, loxilb-io/loxilb currently has 1 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 loxilb-io/loxilb 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.