Records/npm/unique-slug/failure issue

Where it was measured

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

• 6.0.0 PASS 2 passing observations
• 5.0.0 FAIL
• 3.0.0 PASS 15 passing observations

Where it reproduced

• executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×2 2026-10-17 → 2026-10-18

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 3.0.0 → first failing release 5.0.0

  Both trees resolved every dependency to the same version. Nothing here moved.

• Last failing release 5.0.0 → first passing release 6.0.0

  Both trees resolved every dependency to the same version. Nothing here moved.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Moved: 0 · unchanged at every release: 1

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.

Evidence gaps

• No failure domain was inferred for this failure.

Published answers for the affected releases

• unique-slug 5.0.0 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. HOW MIT-0 · 2026-10-17