[Bug Report] After modifed the hash values, the software shows that it displays as normal

[DentistCode]

Hello,

Thank you for developing this software; it's incredibly useful. However, there's a small issue I'd like to mention.
I encountered two issues while using the software and would like to provide feedback as follows:

Bug 1:

When modifying 3 hash values in a .hash file with 4 hash values, the software still indicates that the file is normal. It seems the software defaults to checking with SHA-1, without flagging discrepancies in other hash algorithms.

Steps to reproduce:

1. Generate a .hash file for a file. I used MD5, SHA-1, SHA256, and SHA3-256.
2. Modify the MD5, SHA256, and SHA3-256 values. The software still reports the file as normal.
   

Question 1:

When modifying the hash values in the .hash file one by one, the software only begins to show unstable behavior after the third modification.

(I have no idea about whether it is designed to like this)

Steps to reproduce:

Step 0: Initial detection (default state)

Step 1: After modifying the SHA-1 value

Step 2: After modifying the SHA-256 value

Step 3: After modifying the SHA3-256 value

Step 4: After modifying the MD5 value

Wish u have a good day

[namazso]

A checksum file that contains impossible combinations of hashes for a file is invalid, as it cannot possibly have been generated from the same data if the hash algorithms are secure. Flagging invalid sumfiles is not the purpose of this program. In fact it'd be potentially impossible as the user may not have all algorithms enabled that the file contains.

I also don't see the use case here. What scenario is when you trust only some hashes in a sumfile, but not the others in the same file, when the algorithms in question are secure?