Sample
verify semver.neq in pkg:npm/semver@5.7.2
sha256:eed218858c4d32cae8e2e727e4e163f38dbc8d463d28c42666d2fd5ff5c6eea2
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-27 |
Case
HOW- Goal
- verify semver.neq in pkg:npm/semver@5.7.2
- Packages
- Symbols
-
- semver.neq
- Created
- 2026-08-27T21:45:40Z
Contract
- semver.neq returns true when two version strings represent different semantic versions
- semver.neq returns false when two version strings are semantically identical including with prefixes or whitespace
- semver.neq distinguishes between differing prerelease identifiers and release versions
- semver.neq treats versions differing only by build metadata as semantically equal returning false
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.js
- test/contract.js
Origin Seeder
anonymous