nasa/fprime - Open Source PR Review Scorecard

F´ - A flight software and embedded systems framework

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

External PR Merge Rate: 72%

Response Time: 2d

First Timer Success: 77%

Frequently Asked Questions

Is nasa/fprime welcoming to first-time open-source contributors?

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

What does the 56.8 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 56.8 places nasa/fprime in the A tier.

What is the external contributor pull request merge rate for nasa/fprime?

The external contributor pull request merge rate for nasa/fprime is 72.2%, based on public PR activity from non-core contributors.

Are there Good First Issues available in nasa/fprime?

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

nasa
nasa/fprimeAWelcoming11.7k
GitHub
Back to Explorer
nasa

nasa/fprime

11,680
AWelcoming(57/100)C++

F´ - A flight software and embedded systems framework

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
72.2%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
35 core
Highly collaborative maintainer core
Diagnostic Health HUD
72.2%
Merge Gauge
76.9%
1st-Timer
Community Vibe55/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

F´ Version Affected Component Feature Description An F´ library isn't a project, yet it still should be able to be formattable. The issue is that there's no easy way to go find the default F´ .clang-format file. Either libraries should provide their own, or maybe we could add in the behavior to go fetch that file and put it in the root of the library. Many possible solutions. Expected behavior: clone an F´ library (such as https://github.com/fprime-community/fprime-zephyr) outside of a project run cd fprime-zephyr && fprime-util format --dirs ./Svc should work

📅 Opened Mar 31, 2026💬 1 comment
Quality: 70/100Contribute
Looking for more C++ beginner tasks?Explore C++ 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 nasa/fprime

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

Frequently Asked Questions - Contributing to nasa/fprime

01

Is nasa/fprime welcoming to first-time open-source contributors?

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

03

What does the 56.8 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 56.8 places nasa/fprime in the Welcoming tier.

04

What is the external contributor pull request merge rate for nasa/fprime?

The external pull request merge rate is 72.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 nasa/fprime?

Yes, nasa/fprime 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 nasa/fprime 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.