Records/npm/nanoid/failure issue

Where it was measured

PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• 3.3.19 not measured
• 3.3.18 not measured
• 3.3.17 not measured
• 3.3.16 FAIL
• 3.3.15 not measured
• 3.3.11 not measured

Where it reproduced

• executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×1 2026-09-06 → 2026-09-06

Nearest known PASS/FAIL boundaries

No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.

Evidence gaps

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• The captured output could not establish: stage-unknown.
• No release in this window recorded a passing observation at UNKNOWN.
• Releases in this window never measured at UNKNOWN: 5
• No failure domain was inferred for this failure.

Published answers for the affected releases

• nanoid 3.3.16: nanoid 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. HOWnanoid.nanoidnode 22.23.2 MIT-0 · 2026-09-06
• nanoid 3.3.16: customRandom 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. HOWnanoid.customRandomnode 22.23.2 MIT-0 · 2026-09-06
• nanoid 3.3.16: customAlphabet 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. HOWnanoid.customAlphabetnode 22.23.2 MIT-0 · 2026-09-06