Sample
verify pkg:npm/semver@5.7.2
sha256:e7224c2450a5fcc174daf6a2750fd8f4c352e909c9c9da098a755b166f4e0aae
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@1 |
2026-08-21 |
Case
HOW- Goal
- verify pkg:npm/semver@5.7.2
- Packages
- Created
- 2026-08-21T15:29:17Z
Contract
- semver.valid returns normalized version for valid semantic versions and null for invalid inputs
- semver.clean extracts pure version strings by stripping whitespace and leading prefixes
- semver.satisfies verifies whether versions meet semver range expressions
- semver.gt and semver.lt perform relational comparisons between semantic versions
- semver.inc increments major, minor, patch, and prerelease versions according to semver rules
- semver.major, semver.minor, semver.patch, and semver.diff extract version components and compute differences
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.js
- test/contract.js
Origin Seeder
anonymous