A libp2p implementation for .NET in C#.
C-Rank Grade: B (Solid) - 53/100
External PR Merge Rate: 26%
Response Time: <1h
First Timer Success: -
NethermindEth/dotnet-libp2p has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in NethermindEth/dotnet-libp2p respond to incoming external pull requests in approximately 0.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 53.3 places NethermindEth/dotnet-libp2p in the B tier.
The external contributor pull request merge rate for NethermindEth/dotnet-libp2p is 26.3%, based on public PR activity from non-core contributors.
NethermindEth/dotnet-libp2p currently has 20 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in NethermindEth/dotnet-libp2p. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in NethermindEth/dotnet-libp2p 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/NethermindEth/dotnet-libp2p?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (33% approval). Large PRs (>500 lines) take ~4 hours (15% approval). Keep your diff compact for rapid review.
Gossipsub v1.1 permits PX entries without a signed peer record, but HandlePrune unconditionally passes the optional record bytes to PeerStore.Discover. Empty records fail parsing and can abort the enclosing RPC instead of using ambient discovery information. Specification: https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/gossipsub-v1.1.md#peer-exchange Acceptance criteria Honor the advertised peer ID while safely skipping omitted signed records. Do not abort the whole RPC because one PX record is absent or malformed. Use existing ambient discovery only when available, and test recordless/malformed/mixed PX lists.
Graylisting is checked only while handling new messages. A graylisted non-direct peer can still mutate subscriptions, mesh state, control messages, and extensions through OnRpc, contrary to the specified all-RPC gate. Specification: https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/gossipsub-v1.1.md#score-thresholds Acceptance criteria Gate every RPC handler before state mutation for peers below GraylistThreshold. Preserve the intended direct-peer exemption explicitly. Add regression tests for messages, subscriptions, GRAFT/PRUNE, IHAVE/IWANT, and extensions.
The IP-colocation scoring mechanism cannot activate because SetPeerIPAddress has no production caller. Every peer score therefore lacks an address even though the settings expose colocation thresholds and weights. Gossipsub v1.1 peer scoring includes IP colocation: https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/gossipsub-v1.1.md#peer-scoring Acceptance criteria Derive a normalized, trustworthy address from the secure session or multiaddress at connection time. Define safe behavior for DNS, relay, private, and changing addresses. Test threshold penalties and ensure unrelated peers do not share accidental buckets.
Several mesh, fanout, and gossip paths use ordered .Take(...) selection from peer collections. That makes peer choice dependent on collection order and can permanently starve otherwise eligible peers. Gossipsub requires random initial mesh/gossip selection and random gossip-factor sampling: https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/gossipsub-v1.1.md Acceptance criteria Use bounded, unbiased sampling for mesh growth, fanout, and gossip recipients. Preserve score/direct-peer/degree filtering before sampling. Add deterministic injectable-randomness tests that show eligible peers are not fixed by insertion order.
The router keeps up to DOut locally initiated peers while pruning an oversized mesh, but it rejects all GRAFTs at D_hi and never fills missing outbound quota when the mesh already meets D_lo. This leaves the v1.1 outbound-quota mechanism incomplete. Specification: https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/gossipsub-v1.1.md#outbound-mesh-quotas Acceptance criteria Accept eligible outbound GRAFTs at the high-degree boundary according to the v1.1 rules. Proactively fill a missing D_out quota during heartbeat. Test inbound/outbound combinations at D_lo/D_hi and pruning behavior.
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 NethermindEth/dotnet-libp2p, 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 NethermindEth/dotnet-libp2p acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 26.3% were successfully merged into the primary branch.
NethermindEth/dotnet-libp2p has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 53.3 places NethermindEth/dotnet-libp2p in the Solid tier.
The external pull request merge rate is 26.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, NethermindEth/dotnet-libp2p currently has 20 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for NethermindEth/dotnet-libp2p 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.