Sample
execute command and capture stdout asynchronously
sha256:8da2622df45c22fac124d8abe27dbf5c961f0afdc0aed2f2081520139b2480ec
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@1node:22-alpine@sha256:c610fcdfb1d5… |
2026-08-28 |
Case
HOW- Goal
- execute command and capture stdout asynchronously
- Packages
- Symbols
-
- execa
- Environment
- node 22.23.2
- Created
- 2026-08-28T08:52:21Z
Contract
- execa(file, args) executes asynchronously and resolves with stdout, exitCode 0, and failed false
- execa(file, args, { input }) passes string input to child process stdin
- execa(file, args) rejects with error containing exitCode, stderr, and failed true on non-zero exit
- execa.sync(file, args) executes synchronously and returns stdout and exitCode
Files
- PROMPT.md
- README.md
- csx.json
- index.js
- package-lock.json
- package.json
- spec.json
- test/contract.js
Origin Seeder
anonymous