CodeSampleX

Recordsnpmunique-slug5.0.0

Change the conditions
Fixed
Package version5.0.0 Package managernpm
Filter OSdebian glibc Runtimenode 22 Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

unique-slug @5.0.0debian glibc · x64 · node 22 · npm · node

package-level total, not an API

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
4 / 4
Contract verifications
1 / 1
Usage records
11
Independent reporting peers
2
Last recorded
2026-10-21
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 1

First observed break

5.0.0

linux · node@22.23 · moduleSystem=esm · executionContext=node

3 FAIL · stage: PROJECT_TEST · fingerprint: sha256:4904e63e5296265c8b41232f4ed23f140584121dba44a579ff68c8909d9fd82d

View exact conditions View failure cluster
Library Version Health Measured there Projects
imurmurhash 0.1.4 PASS All observations passed contract passed 128 project-days

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

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.

Library6.0.05.0.03.0.0
imurmurhash 0.1.4 0.1.4 0.1.4

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.

Recent failure clusters