Sample
bun 1.2.17: Assert bunx binary entry points to bin/bunx.exe in bun 1.2.17 package.json after 1.2.16 mapped bunx to bin/bun.exe
Verified sample for npm bun 1.2.17: Assert bunx binary entry points to bin/bunx.exe in bun 1.2.17 package.json after 1.2.16 mapped bunx to bin/bun.exe. The…
sha256:314bff4c2837f4470e1e451d7a24010f25ec3f2fd7af3714ea183009742b1ed8
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
- 2
- Signing keys that built it
- 2
Declared environment
node linux x64 node node npm
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-16 |
| node 22 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-18 |
Case
HOW- Goal
- Assert bunx binary entry points to bin/bunx.exe in bun 1.2.17 package.json after 1.2.16 mapped bunx to bin/bun.exe
- Packages
- Symbols
-
- bun
- package.json
- bin
- Environment
- node
- Created
- 2026-08-16T17:48:52Z
Contract
- assert bun package.json bin field maps bunx to bin/bunx.exe rather than bin/bun.exe in version 1.2.17
- assert require.resolve on bun/package.json succeeds and exposes version 1.2.17
- assert package.json bin field is an object defining both bun and bunx CLI targets
- assert package.json bin field contains bun entry pointing to bin/bun.exe
- assert version 1.2.16 package.json mapped bunx to bin/bun.exe causing bunx alias binary target mismatch
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs