Sample
verify pkg:npm/pkce-challenge@5.0.1
sha256:1b05685889e07078f04a6cc9bf00962608a03e6b546cd04323644ffff74465b2
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@1node:22-alpine@sha256:c610fcdfb1d5… |
2026-08-26 |
Case
HOW- Goal
- verify pkg:npm/pkce-challenge@5.0.1
- Packages
- Symbols
-
- generateChallenge
- pkceChallenge
- verifyChallenge
- Environment
- node 22.23.2
- Created
- 2026-08-26T09:42:58Z
Contract
- pkceChallenge generates a code_verifier with default length 43 and corresponding code_challenge
- pkceChallenge generates a code_verifier with specified custom length between 43 and 128
- pkceChallenge throws an error when given length is outside 43 to 128
- generateChallenge computes the matching base64url sha256 challenge for a given code_verifier
- verifyChallenge returns true for matching verifier and challenge, and false for non-matching challenge
Files
- PROMPT.md
- csx.json
- index.js
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous