CodeSampleX

Recordsnpmread-pkg10.1.0

Change the conditions
Fixed
OSubuntu glibc Package version10.1.0 Architecturex64
Filter Runtimenode 22 Symbolwhole package Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

read-pkg @10.1.0ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 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 failed

Project observations
1 / 1
Contract verifications
0 / 1
Independent reporting peers
1
Last recorded
2026-09-14
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 1

First observed break

10.1.0

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

2 FAIL · stage: UNKNOWN · fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc

View exact conditions View failure cluster
Library Version Health Measured there Projects
@types/normalize-package-data 2.4.4 PASS All observations passed contract passed 1 project-day

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.

Library10.1.09.0.1
@types/normalize-package-data 2.4.4 2.4.4
normalize-package-data — 6.0.2
parse-json — 8.3.0
type-fest — 4.41.0

Moved: 0 · unchanged at every release: 4

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