F´ - A flight software and embedded systems framework
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 67%
Response Time: -
First Timer Success: 63%
nasa/fprime has a recorded first-timer success rate of 63.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in nasa/fprime respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
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 64.8 places nasa/fprime in the A tier.
The external contributor pull request merge rate for nasa/fprime is 66.8%, based on public PR activity from non-core contributors.
nasa/fprime does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Highly welcoming maintainers in nasa/fprime. Prompt code reviews with positive guidance for new contributors.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/nasa/fprime?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (83% approval). Large PRs (>500 lines) take ~115 hours (30% approval). Keep your diff compact for rapid review.
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
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
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 -. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.8% were successfully merged into the primary branch.
nasa/fprime has a recorded first-timer success rate of 63.4%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
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 64.8 places nasa/fprime in the Welcoming tier.
The external pull request merge rate is 66.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
nasa/fprime does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
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.