Sample
verify pkg:npm/signal-exit@4.1.0
sha256:4dbc7d26483a3684bafc1f6dcd19b359c580997710984c2d2f19f1dfd7a8735e
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-23 |
Case
HOW- Goal
- verify pkg:npm/signal-exit@4.1.0
- Packages
- Created
- 2026-08-23T07:24:55Z
Contract
- onExit registers an exit callback and returns an unregister function
- calling the returned unregister function prevents the exit callback from firing
- onExit callback receives the numeric exit code when process.exit is called
- onExit callback receives exit code 0 when the Node.js event loop terminates naturally
- onExit callback receives the signal name when the process receives a termination signal
- onExit with alwaysLast option executes after standard exit listeners
- signals export provides an array of standard POSIX termination signal names
- load and unload functions control the lifecycle of process exit listeners
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.js
- test/contract.mjs
Origin Seeder
anonymous