Sample
path-exists 4.0.0
Verified sample for npm path-exists 4.0.0. The contract ran on node 22 · linux alpine/x64 · docker and passed: pathExists asynchronously returns a Promise…
sha256:da8fe3c9208914bd1bc31fc04d906e71d0594afc592bc20a4156d48829e0898a
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/path-exists@4.0.0
- Packages
- Environment
- node 22.23.2
- Created
- 2026-08-20T17:55:49Z
Contract
- pathExists asynchronously returns a Promise resolving to true for an existing file or directory and false for a non-existent path
- pathExists.sync synchronously returns true for an existing file or directory and false for a non-existent path
- pathExists handles non-existent paths gracefully returning false without throwing exceptions
Files
- PROMPT.md
- csx.json
- index.js
- package-lock.json
- package.json
- spec.json
- test/contract.cjs
Origin Seeder
anonymous