Sample
verify pkg:npm/isbinaryfile@4.0.10
sha256:b102ec45b8d12e0911dc695f9bea236dabe2a2f67f18b9a625e7d0da97468ad1
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@1 |
2026-08-21 |
Case
HOW- Goal
- verify pkg:npm/isbinaryfile@4.0.10
- Packages
- Created
- 2026-08-21T14:32:43Z
Contract
- isBinaryFileSync returns false for plain text buffer and true for binary buffer
- isBinaryFile asynchronously returns false for plain text buffer and true for binary buffer
- isBinaryFile and isBinaryFileSync correctly detect binary status for file paths
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.js
- test/contract.js
Origin Seeder
anonymous