Sample
semver 7.8.5: find maximum satisfying version with semver.maxSatisfying
Verified sample for npm semver 7.8.5: find maximum satisfying version with semver.maxSatisfying. The contract ran on node 22 · linux alpine/x64 · docker and…
sha256:a177d1d5d028fb9d540ab760edf394ebc68e4a66f69775589b0cb816156e89d0
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 windows 11 x64 node javascript 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
- find maximum satisfying version with semver.maxSatisfying
- Packages
- Symbols
-
- semver.maxSatisfying
- Environment
- node
- Created
- 2026-08-18T22:12:38Z
Contract
- maxSatisfying returns the highest semantic version that satisfies a caret range
- maxSatisfying returns the highest semantic version that satisfies a comparator range
- maxSatisfying returns null when no versions satisfy the specified range
- maxSatisfying supports includePrerelease option to match prerelease versions
- maxSatisfying handles loose option when parsing version strings
Files
- PROMPT.md
- csx.json
- index.js
- package-lock.json
- package.json
- spec.json
- test/contract.js
Origin Seeder
anonymous