Udisk Inspector
C 62 completed
Other
unknown / rust · tiny
24
Files
4,396
LOC
0
Frameworks
4
Languages
Pipeline State
completedRun ID
#1545241Phase
doneProgress
0%Started
2026-04-16 23:14:15Finished
2026-04-16 23:14:15LLM tokens
0Pipeline Metadata
Stage
CatalogedDecision
proceedNovelty
28.89Framework unique
—Isolation
—Last stage change
2026-05-10 03:34:46Deduplication group #47718
Member of a group with 962 similar repo(s) — canonical #1515287 view group →
Repobility analyzer · published findings · https://repobility.com
🧪 Code Distillation
Browse all specs →AI Prompt
Create a cross-platform command-line tool, similar to UDisk Inspector, written in Rust. This tool should be able to test USB flash drives for quality issues. Key features must include detecting fake capacity by writing and verifying data blocks, benchmarking sequential and random read/write speeds, and scanning for bad blocks. It should also support a thermal stress test and generate a comprehensive 100-point quality score based on capacity, speed, stability, and bad block checks. Finally, it needs to output results both as a standalone HTML report (with ECharts graphs) and as machine-readable JSON output.
rust cli usb hardware-testing quality-assurance benchmark cross-platform command-line
Generated by gemma4:latest
Catalog Information
Create a cross-platform command-line tool, similar to UDisk Inspector, written in Rust. This tool should be able to test USB flash drives for quality issues. Key features must include detecting fake capacity by writing and verifying data blocks, benchmarking sequential and random read/write speeds, and scanning for bad blocks. It should also support a thermal stress test and generate a comprehensive 100-point quality score based on capacity, speed, stability, and bad block checks. Finally, it ne
Tags
rust cli usb hardware-testing quality-assurance benchmark cross-platform command-line
Quality Score
C
61.7/100
Structure
66
Code Quality
57
Documentation
37
Testing
60
Practices
75
Security
84
Dependencies
80
Strengths
- Good test coverage (46% test-to-source ratio)
- Consistent naming conventions (snake_case)
- Good security practices — no major issues detected
Weaknesses
- No LICENSE file — legal ambiguity for contributors
- No CI/CD configuration — manual testing and deployment
- 372 duplicate lines detected — consider DRY refactoring
- 1 'god files' with >500 LOC need decomposition
Recommendations
- Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
- Add a linter configuration to enforce code style consistency
- Add a LICENSE file (MIT recommended for open source)
Languages
Frameworks
None detected
Symbols
function35
struct13
enum5
constant3
extension1
Embed Badge
Add to your README:
