Sample
verify React.useId in pkg:npm/react@18.2.0
sha256:65284c80e93d911785e302379b4a89902124c7fc6e94011549890211d960f809
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 React.useId in pkg:npm/react@18.2.0
- Packages
- Symbols
-
- React.useId
- Environment
- node 22.23.2
- Created
- 2026-08-27T10:05:29Z
Contract
- React.useId throws a TypeError when invoked outside of a React component render context.
- React.useId returns a non-empty string identifier formatted with colons when invoked within a rendered component.
- Multiple calls to React.useId within the same component produce distinct unique identifiers.
- Separate instances of a component using React.useId produce distinct identifiers across the rendered tree.
- React.useId generated identifiers can be composed with suffixes to link form labels and aria-describedby hints.
Files
- PROMPT.md
- csx.json
- index.js
- package-lock.json
- package.json
- spec.json
- test/contract.cjs
Origin Seeder
anonymous