01
Know what is actually hashed
The generator reads the selected file bytes without adding a wrapper. A version-control object identifier may hash a structured object containing a header as well as content, so it need not match a direct SHA-1 of a working file. A mismatch can reflect different input construction rather than a broken hashing implementation.
02
Check a known three-byte input
The file abc, without a newline or byte-order mark, gives a9993e364706816aba3e25717850c26c9cd0d89d. Verify that your sample is three bytes long. A text editor's automatic final newline is enough to change the result even though the same letters remain visible on screen.
03
Use the expected reference carefully
Compare all 40 hexadecimal characters with the reference for the same version and file. Obtaining a matching digest from an untrusted page does not establish who produced the file. If you control a new distribution process, use a contemporary verification design and authenticated reference instead of perpetuating SHA-1 solely for familiarity.