Sample
verify readable-stream.PassThrough in pkg:npm/readable-stream@2.3.8
sha256:b33f4ba15f12332a991f05429f6829bd44cbe1009b6a7d830ef92c46d640e710
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 10
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 readable-stream.PassThrough in pkg:npm/readable-stream@2.3.8
- Packages
- Symbols
-
- readable-stream.PassThrough
- Environment
- node 22.23.2
- Created
- 2026-08-23T13:51:13Z
Contract
- PassThrough stream can be instantiated and exposes stream methods
- PassThrough stream passes written buffer chunks through unmodified in paused mode
- PassThrough stream supports flowing mode with data and end events
- PassThrough stream supports objectMode for passing non-buffer objects
Files
- PROMPT.md
- csx.json
- index.js
- package-lock.json
- package.json
- spec.json
- test/contract.js
Origin Seeder
anonymous