Sample
verify cross-spawn in pkg:npm/cross-spawn@7.0.6
sha256:16485ebfe716dd75c9e7351ada1212ac6dff8035da0898f4479e291a67474c32
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
- verify cross-spawn in pkg:npm/cross-spawn@7.0.6
- Packages
- Symbols
-
- cross-spawn
- Created
- 2026-08-26T10:41:56Z
Contract
- crossSpawn.sync executes command synchronously and returns status 0 with valid pid
- crossSpawn.sync decodes stdout and stderr as strings when encoding option is provided
- crossSpawn.sync passes arguments and custom environment variables to child process
- crossSpawn.sync captures non-zero exit code and standard error on failure
- crossSpawn.sync reports ENOENT error when binary does not exist
- crossSpawn executes command asynchronously and streams stdout
- crossSpawn pipes stdin to child process
- crossSpawn emits error event with ENOENT for non-existent command
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous