Sample
Prove that embedded files must be opened with fs.ValidPath-style names, not os/filepath-style paths.
sha256:e0ab881bb6e03a1d68177d32a6688b85505ae28037acb54405bac8d34cdf554c
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Prove that embedded files must be opened with fs.ValidPath-style names, not os/filepath-style paths. HOW
- Packages
- embed 1.26.5
- Environment
- go
- Created
- 2026-08-16T12:04:35Z
Commonly assumed
Passing "/assets/hello.txt" to embed.FS.Open should open the same embedded file as "assets/hello.txt".
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- assert embed.FS.Open("/assets/hello.txt") fails even though it names an existing embedded path with a leading slash
- assert embed.FS.Open("./assets/hello.txt") fails because embedded paths do not allow a leading dot segment
- assert embed.FS.Open("assets/../hello.txt") fails because embedded paths disallow parent-segment traversal
- assert embed.FS.Open("assets/hello.txt") succeeds for the same file using a clean relative path
Files
- NOTES.md
- assets/hello.txt
- csx.json
- embed_test.go
- go.mod
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- go 1.26 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-16 · ed25519:d91480838ac982c9