Sample
verify which.sync in pkg:npm/which@2.0.2
sha256:e900d51b6145e11f69e755489fbfb845057b7db355a3628b87929a5ff8021425
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-23 |
Case
HOW- Goal
- verify which.sync in pkg:npm/which@2.0.2
- Packages
- Symbols
-
- which.sync
- Created
- 2026-08-23T04:23:24Z
Contract
- which.sync resolves the path to an executable from a custom search path
- which.sync throws an ENOENT error when the executable is not found
- which.sync with nothrow option returns null when the executable is not found
- which.sync with all option returns an array of all matching executable paths
- which.sync respects custom path delimiter with colon option
- which.sync directly resolves executable paths containing directory slashes
- findExecutableSync and tryFindExecutableSync helper functions correctly wrap which.sync behavior
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.mjs
- test/contract.mjs
Origin Seeder
anonymous