e2b-dev/E2B - Open Source PR Review Scorecard

Open-source, secure environment with real-world tools for enterprise-grade agents.

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

External PR Merge Rate: 58%

Response Time: 6d

First Timer Success: 28%

Frequently Asked Questions

Is e2b-dev/E2B welcoming to first-time open-source contributors?

e2b-dev/E2B has a recorded first-timer success rate of 27.6%. 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 e2b-dev/E2B respond to incoming external pull requests in approximately 135.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 45.7 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 45.7 places e2b-dev/E2B in the B tier.

What is the external contributor pull request merge rate for e2b-dev/E2B?

The external contributor pull request merge rate for e2b-dev/E2B is 58.4%, based on public PR activity from non-core contributors.

Are there Good First Issues available in e2b-dev/E2B?

e2b-dev/E2B does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

e2b-dev
e2b-dev/E2BBSolid13.5k
GitHub
Back to Explorer
e2b-dev

e2b-dev/E2B

13,480
BSolid(46/100)Python

Open-source, secure environment with real-world tools for enterprise-grade agents.

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%

Established Python ecosystem in e2b-dev/E2B. Maintains structured code review standards for external contributors.

Top PR Submission Do's

  • Ensure code complies with Python style conventions
  • Keep PRs scoped 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
5 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
58.4%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
27.6%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
14 core
Highly collaborative maintainer core
Diagnostic Health HUD
58.4%
Merge Gauge
27.6%
1st-Timer
Community Vibe32/100

Embed C-Rank Badge

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

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

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for e2b-dev/E2B.

View all good first issues directly on GitHub

Looking for more Python beginner tasks?Explore Python 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 e2b-dev/E2B

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

Frequently Asked Questions - Contributing to e2b-dev/E2B

01

Is e2b-dev/E2B welcoming to first-time open-source contributors?

e2b-dev/E2B has a recorded first-timer success rate of 27.6%. 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 ~5 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 45.7 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 45.7 places e2b-dev/E2B in the Solid tier.

04

What is the external contributor pull request merge rate for e2b-dev/E2B?

The external pull request merge rate is 58.4%. 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 e2b-dev/E2B?

e2b-dev/E2B does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for e2b-dev/E2B 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.