| Crates.io | hashsum |
| lib.rs | hashsum |
| version | 0.1.0 |
| created_at | 2025-10-29 07:07:55.288308+00 |
| updated_at | 2025-10-29 07:07:55.288308+00 |
| description | CLI to print or verify cryptographic checksums (md5, sha1, sha2, belt-hash). |
| homepage | |
| repository | https://github.com/makavity/hashsum/tree/main |
| max_upload_size | |
| id | 1906156 |
| size | 35,923 |
CLI to print or verify cryptographic checksums (md5, sha1, sha2 family, belt-hash).
From local path:
cargo install --path /path/to/repository
From Git repository:
cargo install --git <git-url> hashsum
From crates.io (after publishing):
cargo install hashsum
hashsum [OPTIONS] [FILE]...
FILE is given, or when - is used, input is read from stdin.md5.-a, --algorithm <ALG>: Hash algorithm (md5, sha1, sha224, sha256, sha384, sha512, belt-hash)-c, --check: Read checksums from the given files and verify them--ignore-missing (with --check): Do not fail on missing files-q, --quiet (with --check): Do not print OK for each successfully verified file--status (with --check): Do not print anything; use exit status only--strict (with --check): Treat malformed lines as fatal errors-w, --warn (with --check): Warn about malformed linesWhen computing hashes:
<hex-digest> <filename>
When verifying with --check, the input format supported is compatible with common tools:
<hex-digest> <filename>
<hex-digest> *<filename>
On success (unless --quiet or --status):
<filename>: OK
On mismatch:
<filename>: FAILED
Compute SHA-256 of a file:
hashsum -a sha256 path/to/file
Verify checksums listed in checksums.txt:
hashsum --check checksums.txt
Read from stdin:
cat file | hashsum -a sha1 -
0: success (all requested operations succeeded)
1: at least one file failed, IO error, or malformed line in strict mode