Sample
verify bare-stream.PassThrough in pkg:npm/bare-stream@2.13.3
sha256:689dc33496248f851d229e99fa24177182a0284611449a4172f3cdd19b11db4b
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-27 |
Case
HOW- Goal
- verify bare-stream.PassThrough in pkg:npm/bare-stream@2.13.3
- Packages
- Symbols
-
- bare-stream.PassThrough
- Environment
- node 22.23.2
- Created
- 2026-08-27T13:22:07Z
Contract
- PassThrough forwards written string chunks unmodified to readable stream listeners
- PassThrough supports streaming piping between readable and writable streams
- PassThrough supports backpressure and pause/resume stream flow control
- PassThrough integrates with pipeline utility for multi-stream chaining
- PassThrough emits finish event when writing ends and end event when reading completes
- PassThrough emits error and close events when destroyed with an error
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous