Sample
execute child process with cross-spawn and cross-spawn.sync
sha256:c92afed6c986dbf6e1d569c08eeaed85fa755d53fe3f8e0ec3cf5981e9aa5dd7
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
linux 24 · ubuntu · glibc 2.39 x64 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-26 |
Case
HOW- Goal
- execute child process with cross-spawn and cross-spawn.sync
- Packages
- Symbols
-
- spawn
- sync
- Created
- 2026-08-26T08:56:04Z
Contract
- spawn.sync executes command and captures stdout and exit status synchronously
- spawn.sync returns non-zero status when child process exits with non-zero code
- spawn.sync returns ENOENT error in result when command executable does not exist
- spawn.sync passes input option to child process stdin
- spawn executes command asynchronously and streams stdout data
- spawn emits error event with ENOENT when command executable does not exist
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.js
- test/contract.js
Origin Seeder
anonymous