SHA-256 / normalized UTF-8 text
Does the receipt core produce the declared digest?
We run the exact browser-facing core against two published SHA-256 vectors, line-ending normalization, Unicode text, and a separate node:crypto reference implementation.
Observed verdictPASS
All four cases produced a 64-character lowercase SHA-256 digest. The empty and abc vectors matched their fixed expected values; every case matched Node's separate crypto implementation after the declared normalization.
One core, two crypto paths.
The runner imports the same small module used by the browser tool. It compares Web Crypto output with Node's createHash implementation and checks fixed standard vectors before any receipt is presented as reproducible.
corepack pnpm field-test:receiptCases4
Nodev24.15.0
Platformwin32 / x64
AlgorithmSHA-256
- empty / 0 bytes / e3b0c44298fc…PASS
- abc / 3 bytes / ba7816bf8f01…PASS
- line endings / 16 bytes / f3220283d05d…PASS
- unicode / 24 bytes / 6aafa92c63db…PASS
A digest is not a rights certificate.
- The test covers normalized text encoded as UTF-8, not arbitrary binary files.
- A matching digest supports content-equivalence checking but does not establish authorship, ownership, rights clearance, identity, or trusted time.
- The browser tool requires a secure context with Web Crypto support.
The runner reads the public core and writes only the dated result when capture mode is requested.
corepack pnpm field-test:receipt:capture