Sample
semver 7.8.5: compare versions including build metadata with semver.compareBuild
Verified sample for npm semver 7.8.5: compare versions including build metadata with semver.compareBuild. The contract ran on node 22 · linux alpine/x64 …
sha256:89761a13ea0a6acf75bfb216aacb98301ac7af23a5cc0a17da684ecf7bc97d11
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
- compare versions including build metadata with semver.compareBuild
- Packages
- Symbols
-
- compareBuild
- Created
- 2026-08-19T11:10:44Z
Contract
- semver.compareBuild('1.0.0+1', '1.0.0+2') === -1
- semver.compareBuild('1.0.0+2', '1.0.0+1') === 1
- semver.compareBuild('1.0.0+build', '1.0.0+build') === 0
- semver.compareBuild('1.0.0', '1.0.0+build') === -1
- semver.compareBuild('1.0.0+build', '1.0.0') === 1
- semver.compareBuild('1.0.0', '2.0.0') === -1
- semver.compareBuild('1.0.0-alpha', '1.0.0-beta') === -1
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.mjs
- test/contract.mjs
Origin Seeder
anonymous