Nimbus: an Ethereum Execution Client for Resource-Restricted Devices
C-Rank Grade: S (Elite) - 74/100
External PR Merge Rate: 83%
Response Time: 7h
First Timer Success: 64%
status-im/nimbus-eth1 has a recorded first-timer success rate of 63.6%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in status-im/nimbus-eth1 respond to incoming external pull requests in approximately 6.9 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 74.3 places status-im/nimbus-eth1 in the S tier.
The external contributor pull request merge rate for status-im/nimbus-eth1 is 82.7%, based on public PR activity from non-core contributors.
status-im/nimbus-eth1 currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in status-im/nimbus-eth1. Reviews community pull requests with focus on project quality.
Discussions in status-im/nimbus-eth1 focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/status-im/nimbus-eth1?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 10:00 UTC (10:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~5 hours (96% approval). Large PRs (>500 lines) take ~33 hours (37% approval). Keep your diff compact for rapid review.
Tracker issue for all execution-api JSON RPC issues. Most of these are visible / discovered via hive tests, but some are additional ones discovered (and more are likely to be discovered as these get worked on). Some are also just spec / test vector / hive PITAs For latest hive results on rpc-compat: https://hive.ethpandaops.io/#/test/generic/1769753159-b9b9d40703a67f0737e0eb880873ff13 Recurring issues over several methods: block tag not parsing hash Some calls are named "...ByNumber" or "...ByHash" These will parse either: latest/safe/finalized and number block hash Other calls without this specific naming however are often supposed parse latest/safe/finalized + number + hash. Several failures are due to nimbus not implementing the hash part. #3981 null vs omit vs error vs [ ] null vs omitting the fields: Our current JSON flavor is set to NOT omit null fields (= Opt.none(T)). This is because this behavior is actually expected/specified in engine_api (see status-im/nim-json-rpc#238
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 status-im/nimbus-eth1, 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 status-im/nimbus-eth1 acknowledge new external contributions in approximately 6 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 82.7% were successfully merged into the primary branch.
status-im/nimbus-eth1 has a recorded first-timer success rate of 63.6%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~6 hours. 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 74.3 places status-im/nimbus-eth1 in the Elite tier.
The external pull request merge rate is 82.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, status-im/nimbus-eth1 currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for status-im/nimbus-eth1 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.