Sample
verify pkg:npm/resolve-from@4.0.0
sha256:79ed2be4d403a02cf7f1980e76ed964a76533064e1df32c36ccc8b89c0686361
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 pkg:npm/resolve-from@4.0.0
- Packages
- Created
- 2026-08-23T13:48:35Z
Contract
- resolveFrom resolves a relative file path from a specified directory
- resolveFrom resolves an installed npm package from a specified directory
- resolveFrom throws MODULE_NOT_FOUND error when the target module does not exist
- resolveFrom throws TypeError when fromDirectory or moduleId is not a string
- resolveFrom.silent returns null instead of throwing when the target module does not exist
- resolveFrom.silent returns resolved absolute path when target exists
- resolveModuleFrom and tryResolveModuleFrom helper functions wrap resolveFrom and resolveFrom.silent
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.mjs
- test/contract.mjs
Origin Seeder
anonymous