01
Keep the algorithm name in your records
A spreadsheet column labeled only hash is ambiguous. Store Whirlpool alongside the digest and the exact filename or artifact version so a later reviewer knows how to reproduce it. Two algorithms can produce strings of the same length without producing the same value or being interchangeable.
02
Test a rename and a byte change
Hash a small sample, rename it without editing, and hash it again. The digest should stay the same because the filename is not part of the input. Next, alter a single byte and compare the results. These checks help distinguish file-content hashing from tools that also hash paths or package metadata.
03
Verify support before adopting it
A tool producing a digest does not ensure that your recipient has a matching verifier. If you are creating a new manifest, first choose an algorithm supported by the entire verification workflow. Whirlpool is most useful here when matching an existing requirement. The download is an ordinary text record, not a signature, encrypted file, or proof of who authored the source.