Sample
verify pathKey in pkg:npm/path-key@3.1.1
sha256:6c7c88e41f1b2bb476199c0a2559af7673c7cc933d89203b3b7bd76219ffe4e9
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:d91480838ac982c9 | 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 pathKey in pkg:npm/path-key@3.1.1
- Packages
- Symbols
-
- pathKey
- Environment
- node 22.23.2
- Created
- 2026-08-27T02:19:52Z
Contract
- assert pathKey returns PATH on POSIX platforms like linux and darwin
- assert pathKey returns PATH by default on current POSIX environment
- assert pathKey returns Path on Windows when no PATH environment variable exists
- assert pathKey returns the specific PATH casing present in Windows environment options
- assert pathKey returns the last matching key in reverse order when multiple PATH casings exist on Windows
- assert pathKey accepts custom environment and platform options
Files
- PROMPT.md
- csx.json
- index.js
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous