Sample
verify pkg:npm/js-tokens@10.0.0
sha256:f7b46b32b9502b14f22e50f698727af504461434d1f7e9e458f616e1cf54f0a5
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-24 |
Case
HOW- Goal
- verify pkg:npm/js-tokens@10.0.0
- Packages
- Environment
- node 22.23.2
- Created
- 2026-08-24T20:13:25Z
Contract
- jsTokens yields token objects with type and value for JavaScript code constructs
- tokenize parses identifiers, keywords, punctuators, and numeric literals
- tokenize handles regular expression literals and string literals with closed flag
- tokenize supports JSX syntax when jsx option is enabled
- tokenize handles template literals and template substitutions
- extractSignificantTokens filters whitespace and comments
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.js
- test/contract.mjs
Origin Seeder
anonymous