Sample
nanoid 3.3.16
Verified sample for npm nanoid 3.3.16. The contract ran on node 22 · linux alpine/x64 · docker and passed: nanoid generates 21-character URL-safe string…
sha256:442f866e05adfa8cc7477de2e0d98b754447b3fdba39d1aa04cdc569f47e5f12
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
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/nanoid@3.3.16
- Packages
- Environment
- node 22.23.2
- Created
- 2026-08-20T23:10:27Z
Contract
- nanoid generates 21-character URL-safe string identifiers by default
- nanoid generates strings with the specified length when size argument is provided
- customAlphabet generates identifiers using only characters from the specified alphabet
- customRandom generates identifiers using custom byte generator function
- urlAlphabet contains 64 URL-safe characters
- random returns Uint8Array of requested byte length
- repeated generations produce unique non-colliding identifiers
Files
- PROMPT.md
- csx.json
- index.js
- package-lock.json
- package.json
- spec.json
- test/contract.cjs
Origin Seeder
anonymous