Sample
semver 7.8.5: check version range subset containment with semver.subset
Verified sample for npm semver 7.8.5: check version range subset containment with semver.subset. The contract ran on node 22 · linux alpine/x64 · docker and…
sha256:39ae9f6e450848b0334a7f2e2bac65ef7908c6b83176b3ef8dc0c314dbae03df
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
windows 11 x64 npm
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
- check version range subset containment with semver.subset
- Packages
- Symbols
-
- semver.subset
- Created
- 2026-08-18T22:31:51Z
Contract
- semver.subset verifies whether an exact version or narrower range is a subset of a broader range
- semver.subset correctly evaluates caret (^) and tilde (~) range subset containment
- semver.subset correctly evaluates bounded comparator ranges and partial overlap
- semver.subset supports includePrerelease option for prerelease ranges
- semver.subset returns false for disjoint ranges and throws TypeError for invalid range strings
Files
- PROMPT.md
- csx.json
- index.mjs
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous