Wipe files and drives securely with random ASCII dicks
C-Rank Grade: C (Moderate) - 37/100
External PR Merge Rate: 17%
Response Time: 7d
First Timer Success: -
vxfemboy/wipedicks has a recorded first-timer success rate of 0.0%. Repositories ranked C typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in vxfemboy/wipedicks respond to incoming external pull requests in approximately 159.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 37.2 places vxfemboy/wipedicks in the C tier.
The external contributor pull request merge rate for vxfemboy/wipedicks is 16.7%, based on public PR activity from non-core contributors.
vxfemboy/wipedicks currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Rust project in vxfemboy/wipedicks welcoming community pull requests and bug fixes.
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/vxfemboy/wipedicks?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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~104 hours (21% approval). Large PRs (>500 lines) take ~767 hours (15% approval). Keep your diff compact for rapid review.
why Windows users keep killing their SSDs On Linux and macOS, wipedicks actually knows what it's plowing into. Linux reads /sys/class/block/<dev>/queue/rotational; macOS shells out to diskutil info -plist and parses the SolidState key. Both refuse to multi-pass overwrite SSDs/NVMes — because flash storage doesn't enjoy repeat performances. The Flash Translation Layer remaps your writes to fresh NAND, your "secure overwrite" leaves the original data sitting smug in over-provisioned cells, and every pass burns program/erase cycles off the drive's lifespan. On Windows it's the bad old days. drive::classify returns DriveKind::Unknown for everything, drive::resolve_block_device returns None, and the tool happily blasts an NVMe like a $5 hooker. No refusal. No warning. No mercy. Some poor Windows user is out there grinding their Samsung 990 Pro into dust thinking they're being safe. What Needs Penetrating Two functions in src/drive.rs need real Windows implementations. They currently live
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 vxfemboy/wipedicks, 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 vxfemboy/wipedicks acknowledge new external contributions in approximately 6 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 16.7% were successfully merged into the primary branch.
vxfemboy/wipedicks has a recorded first-timer success rate of 0.0%. Repositories ranked Moderate typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~6 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 37.2 places vxfemboy/wipedicks in the Moderate tier.
The external pull request merge rate is 16.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, vxfemboy/wipedicks 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 vxfemboy/wipedicks 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.