CodeSampleX

Sample

verify nanoid/async in pkg:npm/nanoid@3.3.17

sha256:ea72e7da28f81a217f6f599266c591696d47d740b837935410b739c8f88ac131

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-26

Case

HOW
Goal
verify nanoid/async in pkg:npm/nanoid@3.3.17
Packages
Symbols
  • nanoid/async
Environment
node 22.23.2
Created
2026-08-26T04:46:07Z

Contract

  1. import nanoid, customAlphabet, and random from nanoid/async in ESM
  2. assert async nanoid resolves to 21 URL-safe characters
  3. assert async nanoid with custom size resolves to specified character count
  4. assert async customAlphabet returns generator that resolves to custom alphabet characters and length
  5. assert async random resolves to Uint8Array of requested byte size
  6. assert concurrently generated async nanoid IDs are unique

Files

  • PROMPT.md
  • csx.json
  • package-lock.json
  • package.json
  • spec.json
  • src/index.js
  • test/contract.mjs

Download the source artifact (tar.gz)

Origin Seeder

anonymous