CodeSampleX

Recordsnpmparse57.3.0

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

Current conditions

parse5 @7.3.0ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 8 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
16 / 17
Contract verifications
0 / 8
Usage records
1
Independent reporting peers
2
Failures with a captured fingerprint
0 / 1
Last recorded
2026-09-12
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

7.3.0

windows · node@24.13 · moduleSystem=cjs · executionContext=node

8 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2

View exact conditions View failure cluster
Library Version Health Measured there Projects
entities 6.0.1 CANDIDATE Correlated change; unproven combination contract passed 9 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.

Library8.0.18.0.07.3.0
entities 8.0.0 6.0.1 6.0.1

Moved: 1 · 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