CodeSampleX

Recordsnpmnpm-package-arg12.0.2Result

Change the conditions
Fixed
SymbolResult
Filter OSdebian glibc Runtimenode 22 Package version12.0.2 Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

Result @12.0.2debian glibc · x64 · node 22 · npm · node

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
2 / 2
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-10-19

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 0

First observed break

12.0.2

linux · node@22.23 · executionContext=node

3 FAIL · stage: UNKNOWN · fingerprint: sha256:43caf7a060e79da9ba87e7d4fd8dfc44202f7f80ad5048d34829569f87387124

Library Version Health Measured there Projects
hosted-git-info 8.1.0 CANDIDATE Correlated change; unproven combination contract passed 116 project-days
proc-log 5.0.0 CANDIDATE Correlated change; unproven combination contract passed 116 project-days
semver 7.7.4 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
semver 7.8.5 CANDIDATE Correlated change; unproven combination contract passed 104 project-days
validate-npm-package-name 6.0.2 CANDIDATE Correlated change; unproven combination contract passed 114 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.

Moved: 4 · unchanged at every release: 0

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

Showing the 12 most-reported of 13 recorded failure clusters. The rest are single reports.