Sample
graceful-fs readFile and writeFile with gracefulify patch
sha256:dea138b032ca0d50f5ebd6b5aca220ecadacb25a419c828368ec32e4566b7343
This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 1
- Signing keys that built it
- 1
Declared environment
node 22.23 linux 24 · ubuntu · glibc 2.39 x64 node 22.23 javascript npm 10
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:c1973797be207ac4 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1node:22-alpine@sha256:c610fcdfb1d5… |
2026-08-27 |
Case
HOW- Goal
- graceful-fs readFile and writeFile with gracefulify patch
- Packages
- Symbols
-
- gracefulify
- readFile
- writeFile
- Environment
- node 22.23.2
- Created
- 2026-08-27T15:06:45Z
Contract
- gracefulify patches a standard file system module with retry queue capabilities
- readFile asynchronously reads file contents from disk with string and buffer encodings
- writeFile asynchronously creates and writes data to disk
- readFile returns ENOENT error when target file does not exist
- readFileSync synchronously reads file contents created by writeFileSync
- writeFile and readFile safely handle concurrent file system operations
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.js
- test/contract.js
Origin Seeder
anonymous