Sample
uuid 7.0.3
Verified sample for npm uuid 7.0.3. The contract ran on node 22 · linux alpine/x64 · docker and passed: v4 generates RFC 4122 version 4 random UUID strings…
sha256:358a048a4a8bbd92f050e65323db3d733203685d21bbe01c5762b10b995ade23
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:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-20 |
Case
HOW- Goal
- verify pkg:npm/uuid@7.0.3
- Packages
- Environment
- node 22.23.2
- Created
- 2026-08-20T06:21:16Z
Contract
- v4 generates RFC 4122 version 4 random UUID strings and fills byte buffers
- v1 generates RFC 4122 version 1 timestamp-based UUID strings
- v5 generates deterministic RFC 4122 version 5 SHA-1 namespace UUIDs
- v3 generates deterministic RFC 4122 version 3 MD5 namespace UUIDs
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.mjs
- test/contract.mjs
Origin Seeder
anonymous