Sample
imurmurhash 0.1.4
Verified sample for npm imurmurhash 0.1.4. The contract ran on node 22 · linux alpine/x64 · docker and passed: assert MurmurHash3 creates a hash instance and…
sha256:7de2781e33dd2bf3cfedbaada2e49afd8d792ec2f05bcd09b9ec8f44f1cc8a65
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
node 22.23 linux 24 · ubuntu · glibc 2.39 x64 node 22.23 javascript npm 10
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-20 |
Case
HOW- Goal
- verify pkg:npm/imurmurhash@0.1.4
- Packages
- Environment
- node 22.23.2
- Created
- 2026-08-20T14:46:21Z
Contract
- assert MurmurHash3 creates a hash instance and calculates 32-bit unsigned integer hash
- assert MurmurHash3 supports incremental string hashing matching single-pass calculation
- assert MurmurHash3 accepts custom seed affecting hash output
- assert MurmurHash3 supports reset method for reusing instance with optional new seed
- assert MurmurHash3 without new uses cached instance and resets on each call
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous