Records/npm/b4a/failure issue

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.

• 1.9.0 PASS 5 passing observations
• 1.8.1 FAIL

Where it reproduced

• executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×22 2026-08-26 → 2026-08-27
• executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×4 2026-08-18 → 2026-08-18
• executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×2 2026-08-26 → 2026-08-26

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 failing release 1.8.1 → first passing release 1.9.0

  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.9.0 or for 1.8.1, 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

• b4a 1.8.1: isBuffer Built ? 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. HOWb4a.isBuffer MIT-0 · 2026-08-27
• b4a 1.8.1: b4a buffer allocation, encoding conversion, and slicing Built ? 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. HOWb4a.allocb4a.concatb4a.fromb4a.toString MIT-0 · 2026-08-23