Sample
verify pkg:npm/bare-module-resolve@1.12.4
sha256:fbf384c14256eb5d992d14cde6fc44d99714aea20cb8013c91270eef2d2d1638
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-27 |
Case
HOW- Goal
- verify pkg:npm/bare-module-resolve@1.12.4
- Packages
- Symbols
-
- resolve
- Created
- 2026-08-27T13:12:58Z
Contract
- resolve yields candidate URLs for relative paths and appends configured file extensions and directory index files
- resolve queries package.json via readPackage and resolves package main entry point
- resolve handles package exports conditions and subpath patterns
- resolve supports async iteration when readPackage returns a promise
- resolve throws ModuleResolveError with INVALID_MODULE_SPECIFIER for invalid package specifiers
- resolve throws ModuleResolveError with PACKAGE_PATH_NOT_EXPORTED when subpath is not in exports
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous