A simple, fast and user-friendly alternative to 'find'
C-Rank Grade: B (Solid) - 51/100
External PR Merge Rate: 22%
Response Time: 22h
First Timer Success: 29%
sharkdp/fd has a recorded first-timer success rate of 28.6%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in sharkdp/fd respond to incoming external pull requests in approximately 22.1 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 50.5 places sharkdp/fd in the B tier.
The external contributor pull request merge rate for sharkdp/fd is 21.6%, based on public PR activity from non-core contributors.
sharkdp/fd currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in sharkdp/fd. Maintains strict focus on technical quality and test standards.
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/sharkdp/fd?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 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~14 hours (28% approval). Large PRs (>500 lines) take ~106 hours (15% approval). Keep your diff compact for rapid review.
Checks I have read the troubleshooting section and still think this is a bug. Describe the bug you encountered: One of the nice features of GNU find and many other GNU programs is that they avoid arbitrary limits whenever possible. As a result, GNU mkdir can create arbitrarily deep directories which find can then visit: $ mkdir -p $(yes a/ | head -n 32768 | tr -d '\n') $ find a | wc -l 32768 This is not the case with fd: $ ./target/release/fd a | wc -l 2062 Using strace, we can see that fd constructs the file names in full each time and calls statx(2) instead of operating on file descriptors. This means fd reaches PATH_MAX limitations: $ strace -ff -e trace=statx ./target/release/fd -j 1 '' a 2>&1 | grep '= -1' [...] [pid 344540] statx(AT_FDCWD, "[long file name trimmed]"..., AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7fdb3c3fbcf0) = -1 ENAMETOOLONG (File name too long) [...] It also gives a misleading non-zero exit status after failing to list all of the file names: $ ./target/releas
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 sharkdp/fd, 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 sharkdp/fd acknowledge new external contributions in approximately 22 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 21.6% were successfully merged into the primary branch.
sharkdp/fd has a recorded first-timer success rate of 28.6%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~22 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 50.5 places sharkdp/fd in the Solid tier.
The external pull request merge rate is 21.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, sharkdp/fd 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 sharkdp/fd 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.