Sample
verify pkg:npm/proper-lockfile@4.1.2
sha256:4448d5e84c7ec759a896b6d0be543af13e5c27580e2f0437ba41b640067ae0f0
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/proper-lockfile@4.1.2
- Packages
- Symbols
-
- proper-lockfile.check
- proper-lockfile.lock
- proper-lockfile.unlock
- Created
- 2026-08-27T20:18:03Z
Contract
- proper-lockfile.check returns false when the file is not locked and true when locked
- proper-lockfile.lock acquires an exclusive lock and returns a release function
- proper-lockfile.lock rejects with ELOCKED error when file is already locked without retries
- proper-lockfile.unlock explicitly releases the lock on the target file
- proper-lockfile.lockSync and unlockSync synchronously acquire and release locks
- proper-lockfile.checkSync synchronously checks lock status on the target file
Files
- PROMPT.md
- csx.json
- index.js
- package-lock.json
- package.json
- spec.json
- test/contract.cjs
Origin Seeder
anonymous