Sample
verify pkg:npm/tar-stream@3.2.0
sha256:8f8e18ec9f170ae96807d573c8dbcc41ca12062c0d11cdb153c8ea2305c35478
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/tar-stream@3.2.0
- Packages
- Created
- 2026-08-23T15:15:57Z
Contract
- pack.entry appends a file entry with header metadata and content buffer, emitting valid tar chunks until finalize
- extract parses entries from a tar stream emitting entry events with header info and readable content stream
- pack and extract roundtrip preserves multiple files with custom modes, sizes, and binary payloads
- extract supports async iteration over entries yielding readable entry streams with headers
- pack.entry throws an error when called on a finalized pack stream
- extract emits an error when supplied with invalid or corrupted tar stream data
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous