hash-file-full-sha256
IN premise
`hash_file` returns a full 64-character hex SHA-256 digest (per the fix in PR #40 that removed the earlier `[:16]` truncation).
Summary
The hash_file function now produces complete SHA-256 hashes instead of truncated ones. This matters because full 64-character digests virtually eliminate collision risk, which was a real concern when hashes were being cut down to just 16 characters — that earlier truncation could have caused different files to appear identical in the system.
Dependents
These beliefs depend on this one:
- source-tracking-is-collision-resistant-and-safe — Source integrity tracking uses full 64-character SHA-256 digests with exact string comparison for collision resistance, and backfills hashes additively without overwriting existing values — ensuring high-fidelity drift detection with no accidental data loss
Details
| Source | entries/2026/04/24/reasons_lib-check_stale.md |