A full-featured implementation of the Network Time Protocol, including NTS support.
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 94%
Response Time: 24h
First Timer Success: 100%
pendulum-project/ntpd-rs has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in pendulum-project/ntpd-rs respond to incoming external pull requests in approximately 23.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 68.4 places pendulum-project/ntpd-rs in the A tier.
The external contributor pull request merge rate for pendulum-project/ntpd-rs is 94.1%, based on public PR activity from non-core contributors.
pendulum-project/ntpd-rs currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in pendulum-project/ntpd-rs. Reviews community pull requests with focus on project quality.
Discussions in pendulum-project/ntpd-rs 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/pendulum-project/ntpd-rs?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 08:00 UTC (08: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 ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (42% approval). Keep your diff compact for rapid review.
Observation In Server::handle_inner at ntp-proto/src/server.rs:228, NtpPacket::deserialize(message, self.keyset.as_ref()) is invoked for inbound messages that have already been classified as ServerResponse::Deny by the denylist policy gate above it. For NTS-shaped packets from denylisted clients, this performs cookie decryption work whose result is then discarded by the existing branch: Err(PacketParsingError::DecryptError(packet)) => { // Don't care about decryption errors when denying anyway if action != ServerResponse::Deny { action = ServerResponse::NTSNak; reason = ServerReason::InvalidCrypto; } (packet, None) } The comment shows you already know about this; I wanted to ask whether the asymmetry is intentional (i.e., the small wasted work is the better tradeoff vs. complicating the parse path) or whether it would be welcome to skip parsing entirely on the deny branch. The asymmetry would be relevant to denial-of-service amplification only at high ra
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 pendulum-project/ntpd-rs, 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 pendulum-project/ntpd-rs acknowledge new external contributions in approximately 23 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 94.1% were successfully merged into the primary branch.
pendulum-project/ntpd-rs has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~23 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 68.4 places pendulum-project/ntpd-rs in the Welcoming tier.
The external pull request merge rate is 94.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, pendulum-project/ntpd-rs 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 pendulum-project/ntpd-rs 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.