File Fingerprint
A cryptographic hash value computed over file contents, such as SHA-256, used to uniquely identify a specific file version. Any byte-level change produces a completely different digest, making it a core verification mechanism in code evidence chains.
Timeline (last 90 days)
A file fingerprint usually refers to a cryptographic hash computed over the file contents (such as SHA-256), and any byte-level change produces a completely different digest.
A fingerprint only covers the files explicitly included in the computation; untracked dependencies, generated artifacts, or external resources are not automatically included.
A source file fingerprint cannot prove everything about the code's runtime environment; environment dependencies, system library versions, and configuration differences are not covered by the source file fingerprint.
All Facts (3)
A file fingerprint usually refers to a cryptographic hash computed over the file contents (such as SHA-256), and any byte-level change produces a completely different digest.
50%UnverifiedA fingerprint only covers the files explicitly included in the computation; untracked dependencies, generated artifacts, or external resources are not automatically included.
50%UnverifiedA source file fingerprint cannot prove everything about the code's runtime environment; environment dependencies, system library versions, and configuration differences are not covered by the source file fingerprint.
50%