Sample
compare semantic version strings
sha256:c00b05cf59160c8944b28c956972cc5e6ea024456542e58a5a5ceba79ac792c1
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
linux 24 · ubuntu · glibc 2.39 x64 npm
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:c1973797be207ac4 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1node:22-alpine@sha256:c610fcdfb1d5… |
2026-08-28 |
Case
HOW- Goal
- compare semantic version strings
- Packages
- Symbols
-
- semver-compare
- Created
- 2026-08-28T02:37:16Z
Contract
- semver-compare exports a comparison function
- returns 0 when two semantic versions are identical
- returns 1 when the first version is greater than the second version
- returns -1 when the first version is less than the second version
- can be used as a comparator callback for Array.prototype.sort to sort semantic versions in ascending order
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.js
- test/contract.mjs
Origin Seeder
anonymous