Sample
atomic-sleep 1.0.0
Verified sample for npm atomic-sleep 1.0.0. The contract ran on node 22 · linux alpine/x64 · docker and passed: sleep is exported as a function
sha256:1d7acdbf2e434986fcfae92e8837f25e47fc815d7567b95f61ff2d239d5543fc
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
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@1 |
2026-08-20 |
Case
HOW- Goal
- verify pkg:npm/atomic-sleep@1.0.0
- Packages
- Environment
- node 22.23.2
- Created
- 2026-08-20T21:42:35Z
Contract
- sleep is exported as a function
- sleep synchronously pauses execution for positive integer milliseconds
- sleep supports BigInt durations
- sleep blocks the event loop so pending asynchronous timers do not run until after sleep returns
- sleep throws TypeError for non-numeric and non-bigint arguments
- sleep throws RangeError for non-positive or non-finite numbers
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.js
- test/contract.mjs
Origin Seeder
anonymous