Sample
verify pkg:npm/%40jest/globals@29.7.0
sha256:be45e69db31e6f1db5deb834e6e3b12265a7abdacf3f7939fd0fb2382201886c
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-23 |
Case
HOW- Goal
- verify pkg:npm/%40jest/globals@29.7.0
- Packages
- Environment
- node 22.23.2
- Created
- 2026-08-23T16:22:04Z
Contract
- requiring @jest/globals outside Jest runtime throws an error stating it cannot be imported outside the Jest test environment
- @jest/globals/package.json exports package metadata and dependencies including @jest/environment, @jest/expect, @jest/types, and jest-mock
- loadJestGlobals safely attempts requiring @jest/globals and captures outside-Jest error
- isJestEnvironment detects whether running in a Jest test environment
- assertOutsideJestError validates that caught errors match canonical Jest environment restriction message
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.js
- test/contract.js
Origin Seeder
anonymous