Sample
semver 7.8.5: validate semantic versions and check range satisfaction with semver
Verified sample for npm semver 7.8.5: validate semantic versions and check range satisfaction with semver. The contract ran on node 22 · linux alpine/x64 …
sha256:09ceefaa6191fbac99f32be645a6fa93f149913d6049cd2daba69a739203d64a
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 windows 11 x64 node 22 javascript npm 10
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-19 |
Case
HOW- Goal
- validate semantic versions and check range satisfaction with semver
- Packages
- Symbols
-
- satisfies
- valid
- Environment
- node 22
- Created
- 2026-08-19T12:00:04Z
Contract
- semver.valid parses and normalizes valid version strings and returns null for invalid strings
- semver.satisfies returns true when a valid version matches a range specification
- semver.satisfies returns false when a version does not meet range constraints
Files
- PROMPT.md
- csx.json
- index.js
- package-lock.json
- package.json
- spec.json
- test/contract.js
Origin Seeder
anonymous