Sample
verify pkg:npm/import-fresh@3.3.1
sha256:b9ed95eeb82afdc30a82de96ec34c7acd2bb94eb18bd39a50db5575dd4ba8e1a
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/import-fresh@3.3.1
- Packages
- Created
- 2026-08-23T14:08:52Z
Contract
- importFresh throws TypeError when moduleId argument is not a string
- importFresh imports a module and returns its exported value
- importFresh returns a new module instance on each call bypassing require cache
- importFresh resolves relative module paths relative to the caller file directory in CommonJS
- importFresh loads fresh parsed objects for JSON files bypassing cache
- importFresh throws MODULE_NOT_FOUND error when the module cannot be resolved
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
- test/fixtures/data.json
- test/fixtures/stateful.cjs
- test/fixtures/sub/caller.cjs
- test/fixtures/sub/target.cjs
Origin Seeder
anonymous