Sample
verify AdmZip.writeZip in pkg:npm/adm-zip@0.6.0
sha256:9a832ea64a7eff9c7f586e366a5c195d88fa5223604c34f6cd2fa949fdad31c0
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@1 |
2026-08-21 |
Case
HOW- Goal
- verify AdmZip.writeZip in pkg:npm/adm-zip@0.6.0
- Packages
- Symbols
-
- AdmZip.writeZip
- Environment
- node 22.23.2
- Created
- 2026-08-21T10:47:27Z
Contract
- AdmZip instance exposes writeZip method for persisting zip archives to disk
- writeZip synchronously writes archive to specified target file path
- writeZip creates target directories recursively if they do not exist
- writeZip supports optional callback for write completion notification
- writeZip overwrites original file when called without target path on an opened archive
- generated zip file on disk is readable by a new AdmZip instance and preserves entry contents
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.js
- test/contract.js
Origin Seeder
anonymous