Sample
verify pkg:npm/path-key@3.1.1
sha256:7d96cea5b7beafdadd83bf6fb4d524c517576ab0c48993ca2fb7a03013546334
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-26 |
Case
HOW- Goal
- verify pkg:npm/path-key@3.1.1
- Packages
- Created
- 2026-08-26T09:38:40Z
Contract
- pathKey is a callable function with default export compatibility
- pathKey returns 'PATH' by default on POSIX platform
- pathKey returns 'PATH' when explicit POSIX platform is passed regardless of env
- pathKey returns the exact matching key name from env on win32
- pathKey returns the last defined PATH key when multiple case variants exist on win32
- pathKey defaults to 'Path' on win32 when no PATH variable exists in env
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous