Recordsnpmbunfailure issue
Failure signature
PROJECT_PROCESS ERR_ASSERTION Evidence gap ×11
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-16 · Last seen: 2026-08-18
Where it was measured
PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×6 2026-08-16 → 2026-08-16
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×4 2026-08-16 → 2026-08-18
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-08-16 → 2026-08-16
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release 1.2.17 → first failing release 1.3.14
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- No resolved dependency tree for 1.2.17 or for 1.3.14, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- bun 1.3.14 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. HOWnode 22.23.2 MIT-0 · 2026-08-21
- bun 1.3.14: CryptoHasher, CryptoHasher.update, CryptoHasher.digest 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. HOWBun.CryptoHasherBun.CryptoHasher.updateBun.CryptoHasher.digestbun 1 MIT-0 · 2026-08-18
- bun 1.3.14: Demonstrate that FileSink.write() silently drops data without throwing when called after end() 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. HOWBun.filenode MIT-0 · 2026-08-17