Sample
verify nanoid.random in pkg:npm/nanoid@3.3.17
sha256:9887735978b5e89271cb7311eca90e1be9775c165e7401c2920c6c582514bea0
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 nanoid.random in pkg:npm/nanoid@3.3.17
- Packages
- Symbols
-
- nanoid.random
- Environment
- node 22.23.2
- Created
- 2026-08-27T16:26:39Z
Contract
- assert random is a function exported by nanoid
- assert random returns a Uint8Array of the requested byte length
- assert random returns an empty Uint8Array when requested length is 0
- assert random generates cryptographically distinct byte sequences across consecutive calls
- assert random outputs bytes spanning the full 0-255 uint8 range over multiple calls
- assert random functions as a compatible RNG source for customRandom
Files
- PROMPT.md
- csx.json
- index.mjs
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous