CodeSampleX

Recordsnpmwhatwg-url16.0.1

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

Current conditions

whatwg-url @16.0.1debian glibc · x64 · node 22 · npm · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-06
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 1

First observed break

16.0.1

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

2 FAIL · stage: UNKNOWN · fingerprint: sha256:529aac3b1da710068c9dcfe93d0864269e86bebfbe110ca5beeed398860460e7

View exact conditions View failure cluster
Library Version Health Measured there Projects
tr46 6.0.0 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
webidl-conversions 8.0.1 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
@exodus/bytes 1.15.1 PASS All observations passed contract passed 6 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.

Library17.1.016.0.115.1.014.2.05.0.0
tr46 6.0.0 6.0.0 6.0.0 5.1.1 0.0.3
webidl-conversions 8.0.1 8.0.1 8.0.0 7.0.0 3.0.1
@exodus/bytes 1.15.1 1.15.1 — — —

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