Sample
cookie-signature 1.2.2
Verified sample for npm cookie-signature 1.2.2. The contract ran on node 22 · linux alpine/x64 · docker and passed: assert cookieSignature.sign signs cookie…
sha256:5a9400f0796dc83957921d83e1eea8f6054d4c32a6d9d991342d1fd71dd76b1b
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@1 |
2026-08-20 |
Case
HOW- Goal
- verify pkg:npm/cookie-signature@1.2.2
- Packages
- Created
- 2026-08-20T13:43:52Z
Contract
- assert cookieSignature.sign signs cookie string value with HMAC SHA256 base64 digest stripped of padding
- assert cookieSignature.unsign recovers the original cookie value when secret matches
- assert cookieSignature.unsign returns false for tampered payload or mismatched secret
- assert cookieSignature.sign and cookieSignature.unsign throw TypeError when argument types are invalid or secret is null
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous