Weekly hash checks: compare against a trusted baseline

For a recurring file-integrity check, store the expected digest, algorithm, file identity, and date in a trusted location separate from the file being checked. Each week, hash the current file and compare the full value with that baseline. If the file is expected to change, create a new approved baseline and keep the previous record. Do not paste credentials or confidential text into a web tool merely to hash them; use a trusted local method for sensitive inputs.