Sample
get augmented PATH string with npm-run-path
sha256:71ca203a926ef41260215877bf89b1f82bc2e1c82bcba4e7daacb20f6c721bd4
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@1node:22-alpine@sha256:c610fcdfb1d5… |
2026-08-27 |
Case
HOW- Goal
- get augmented PATH string with npm-run-path
- Packages
- Symbols
-
- npmRunPath
- npmRunPath.env
- Environment
- node 22.23.2
- Created
- 2026-08-27T16:17:44Z
Contract
- npmRunPath returns a string containing local node_modules/.bin directories and node binary path
- npmRunPath with custom cwd and path prepends parent node_modules/.bin directories to custom path
- npmRunPath with custom execPath includes directory of specified executable
- npmRunPath.env returns copy of environment with augmented PATH key
- npmRunPath.env with custom env object augments custom PATH without mutating original input
- npmRunPath.default export provides interop compatibility
Files
- PROMPT.md
- csx.json
- index.js
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous