rapido-fs Claudio Abierto
winget install --id=ClaudioAbierto.RapidoFS -e rapido-fs provides the rao command for ranking folders and files by size, searching filesystem metadata, and exporting reports without modifying the scanned tree.
winget install --id=ClaudioAbierto.RapidoFS -e rapido-fs provides the rao command for ranking folders and files by size, searching filesystem metadata, and exporting reports without modifying the scanned tree.
Fast, non-destructive filesystem inventory and search. rapido (rao)
shows where your files and bytes are without changing the scanned tree.
The current implementation is a native Rust CLI. The original Python code
remains in superquick/ for comparison while the Rust interface stabilizes.
--out report path--force is suppliedSee SAFETY.md for the non-destructive contract.
brew install elclaudioabierto/tap/rapido-fs
curl -fsSL https://raw.githubusercontent.com/elclaudioabierto/rapido-fs/main/install.sh | sh
The script verifies the release checksum and installs to ~/.local/bin by
default. Override the directory with RAO_INSTALL_DIR.
Install the Rust toolchain, then build an optimized executable:
cargo build --release
The executable is target/release/rao (target/release/rao.exe on Windows).
# Which folders contain the most data?
rao folders ~/Documents --top 30
# Largest files
rao files ~/Documents --top 50
# Search using familiar filters
rao find ~/Documents --ext xlsx --min-size 10MB
# Machine-pure output
rao folders . --format json
rao files . --format csv
# Create a report; existing files are protected by default
rao folders . --format json --out report.json
rao folders . --format json --out report.json --force
Run rao help, rao help folders, or rao help find for all options.
cargo fmt -- --check
cargo test
cargo build --release
The Release GitHub Actions workflow builds these native archives:
Running the workflow manually builds temporary GitHub Actions artifacts but
does not publish a release. Publishing happens only when a v* tag is pushed,
and the tag must exactly match the Cargo package version. For version 0.2.0:
git tag v0.2.0
git push origin v0.2.0
The published release includes all five archives, generated release notes, and
a SHA256SUMS file. Do not push the tag until the release is ready to publish.