Rust implementation of findutils
C-Rank Grade: A (Welcoming) - 70/100
External PR Merge Rate: 64%
Response Time: 1d
First Timer Success: 75%
uutils/findutils has a recorded first-timer success rate of 75.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in uutils/findutils respond to incoming external pull requests in approximately 24.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 69.7 places uutils/findutils in the A tier.
The external contributor pull request merge rate for uutils/findutils is 64.3%, based on public PR activity from non-core contributors.
uutils/findutils currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in uutils/findutils. 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/uutils/findutils?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~15 hours (80% approval). Large PRs (>500 lines) take ~111 hours (29% approval). Keep your diff compact for rapid review.
A -printf format string that is not valid UTF-8 panics during argument collection, before the format parser is ever reached. $ find d -printf $'%\xff|\n' thread 'main' panicked at ...: called `Result::unwrap()` on an `Err` value $ echo $? 101 The panic is in std::env::args, which panics on non-UTF-8 arguments. Collecting via std::env::args_os and handling the invalid-UTF-8 case explicitly would let this produce a normal error (or match GNU, which accepts arbitrary bytes in the format string and passes them through).
uutils findutils: $ cargo run --bin find -- -amin 1 Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.05s Running `target/debug/find -amin 1` GNU findutils: $ find -amin 1 ./target/debug/find.d
Hi, findutils mainteners we confirmed the find utility, silences errors, while the gnu correctly output them relunsec@relunsec:~/software/findutils/target/debug$ sudo /bin/find -files0-from /dev/vhost-vsock /bin/find: ‘/dev/vhost-vsock’: read error: File descriptor in bad state relunsec@relunsec:~/software/findutils/target/debug$ sudo /bin/find -files0-from /dev/vhost-net /bin/find: ‘/dev/vhost-net’: read error: File descriptor in bad state relunsec@relunsec:~/software/findutils/target/debug$ sudo ./find -files0-from /dev/vhost-net relunsec@relunsec:~/software/findutils/target/debug$ sudo ./find -files0-from /dev/vhost-vsock relunsec@relunsec:~/software/findutils/target/debug$ sudo ./find -files0-from /dev/vhost-vsock relunsec@relunsec:~/software/findutils/target/debug$ echo $? 0 relunsec@relunsec:~/software/findutils/target/debug$
Hi, findutils mainteners that was a logic issue with find. as we confirmed relunsec@relunsec:~/software/findutils/target/debug$ /bin/find -mindepth 2 -maxdepth 1 relunsec@relunsec:~/software/findutils/target/debug$ ./find -mindepth 2 -maxdepth 1 ./.cargo-lock ./build ./incremental ./xargs.d ./--help ./testing-commandline ./xargs ./-lah . ./-lah ./libfindutils.d ./find ./a.bin ./testing-commandline.d ./-quit ./.cargo-artifact-lock ./deps ./locate ./updatedb ./ ./locate.d ./.cargo-build-lock ./.fingerprint ./libfindutils.rlib ./updatedb.d ./--helpg ./examples ./find.d ./z relunsec@relunsec:~/software/findutils/target/debug$
Hi, findutils mainteners we confirmed a corruption when passing the same file to -fprintf and -fprint0, as we confirmed, you will see like that, note the second command output truncated because of github char limits relunsec@relunsec:~/software/findutils/target/debug$ /bin/find -fprint a.txt -fprint0 a.txt relunsec@relunsec:~/software/findutils/target/debug$ cat a.txt | tail -n 23 ./.fingerprint/unicode-width-4643a6e756166721/invoked.timestamp./.fingerprint/unicode-width-4643a6e756166721/dep-lib-unicode_width ./.fingerprint/unicode-width-4643a6e756166721/dep-lib-unicode_width./.fingerprint/unicode-width-4643a6e756166721/lib-unicode_width ./.fingerprint/unicode-width-4643a6e756166721/lib-unicode_width./.fingerprint/unicode-width-4643a6e756166721/lib-unicode_width.json ./.fingerprint/unicode-width-4643a6e756166721/lib-unicode_width.json./.fingerprint/onig_sys-e6a8dcd4958cc99a ./.fingerprint/onig_sys-e6a8dcd4958cc99a./.fingerprint/onig_sys-e6a8dcd4958cc99a/run-build-script-build-script-bu
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 uutils/findutils, 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 uutils/findutils acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 64.3% were successfully merged into the primary branch.
uutils/findutils has a recorded first-timer success rate of 75.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 69.7 places uutils/findutils in the Welcoming tier.
The external pull request merge rate is 64.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, uutils/findutils currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for uutils/findutils 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.