Sample
verify fs-extra.remove in pkg:npm/fs-extra@8.1.0
sha256:59d0c4c6e383bdc4814ee7b5bfae6da9300f24dadf3c33e87c18c14238b869a7
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@1node:22-alpine@sha256:c610fcdfb1d5… |
2026-08-23 |
Case
HOW- Goal
- verify fs-extra.remove in pkg:npm/fs-extra@8.1.0
- Packages
- Symbols
-
- fs-extra.remove
- Environment
- node 22.23.2
- Created
- 2026-08-23T04:46:28Z
Contract
- fs.remove asynchronously deletes a single file
- fs.remove asynchronously deletes a non-empty nested directory hierarchy recursively
- fs.remove resolves without error when the target path does not exist
- fs.remove removes a symbolic link without deleting the underlying target
- fs.removeSync synchronously removes files and directories without throwing on non-existent paths
Files
- PROMPT.md
- csx.json
- index.js
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous