pytorch/executorch - Open Source PR Review Scorecard

On-device AI across mobile, embedded and edge for PyTorch

C-Rank Grade: A (Welcoming) - 61/100

External PR Merge Rate: 71%

Response Time: 20h

First Timer Success: 63%

Frequently Asked Questions

Is pytorch/executorch welcoming to first-time open-source contributors?

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

What does the 61.0 C-Rank™ score (A 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 61.0 places pytorch/executorch in the A tier.

What is the external contributor pull request merge rate for pytorch/executorch?

The external contributor pull request merge rate for pytorch/executorch is 71.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in pytorch/executorch?

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

pytorch
pytorch/executorchAWelcoming5.0k
GitHub
Back to Explorer
pytorch

pytorch/executorch

4,966
AWelcoming(61/100)Python

On-device AI across mobile, embedded and edge for PyTorch

Compare
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Quality Architect

Warmth Score
7.2/10
Patience Score
7.7/10
Nitpick Rate
35%

Active Python repository in pytorch/executorch with ongoing community development and issue triage.

Top PR Submission Do's

  • Ensure code complies with Python style conventions
  • Keep PRs scoped and well-documented
  • Include relevant test coverage for changes

Top PR Friction Pitfalls (Don'ts)

  • Do not submit unlinked PRs without context
  • Do not break existing automated test suites
  • Do not mix unrelated refactors with feature work
Response Velocity
20 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
71.0%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
62.7%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
71 core
Highly collaborative maintainer core
Diagnostic Health HUD
71.0%
Merge Gauge
62.7%
1st-Timer
Community Vibe62/100

Embed C-Rank Badge

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

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

Active Good First Issues (2)

View on GitHub

This repository currently has 2 open good first issue tickets available for newcomers.

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 pytorch/executorch

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

Frequently Asked Questions - Contributing to pytorch/executorch

01

Is pytorch/executorch welcoming to first-time open-source contributors?

pytorch/executorch has a recorded first-timer success rate of 62.7%. Repositories ranked Welcoming 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 ~20 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 61.0 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 61.0 places pytorch/executorch in the Welcoming tier.

04

What is the external contributor pull request merge rate for pytorch/executorch?

The external pull request merge rate is 71.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 pytorch/executorch?

Yes, pytorch/executorch currently has 2 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 pytorch/executorch 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.