Sample
Pass non-zero-offset Uint8Array views safely to Bun hash, SHA-256, gzip, and file-write APIs without processing bytes outside the view
sha256:26d2c82aade11eeecc4816af2b310cb0609b299abb3878c451466acbc2b6db36
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Pass non-zero-offset Uint8Array views safely to Bun hash, SHA-256, gzip, and file-write APIs without processing bytes outside the view HOW
- Packages
- bun 1.3.14
- Environment
- node
- Created
- 2026-08-17T01:47:19Z
Commonly assumed
Bun binary APIs receive a typed array's entire backing ArrayBuffer, so passing a subarray with a non-zero offset hashes, compresses, or writes bytes outside the view.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Bun.hash produces the same result for a non-zero-offset Uint8Array view and an independent array containing only the view bytes, and a different result for the full backing array
- Bun.SHA256.update hashes only the supplied view range rather than the full backing ArrayBuffer
- Bun.gzipSync followed by Bun.gunzipSync preserves exactly the view bytes
- Bun.write persists exactly the view bytes and excludes the prefix and suffix in the backing array
Files
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9