Sample
find maximum satisfying version with semver.maxSatisfying
sha256:a177d1d5d028fb9d540ab760edf394ebc68e4a66f69775589b0cb816156e89d0
Publication state. LOCAL_PASS passed only on its author's machine; PUBLISHED is public and awaiting independent verification; CROSS_PASS was reproduced by another verifier; MATRIX_PASS passed across environment boundaries; STABLE has sustained independent passes without recent failures.
Evidence strength. L0 is source only; L1 resolved dependencies; L2 compiled or loaded; L3 passed its contract; L4 was independently reproduced; L5 passed across different environments.
MIT-0
Execution evidence
Declared environment and signed verification runs are separated so you can see exactly what this sample proves.
- Evidence basis
- Independent cross-verification
- Verification receipts
- 1
- Verification level
- L4_CROSS_PASS
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