CodeSampleX

Compatibilitynpmwhatwg-url16.0.1

Change the conditions
Fixed
OSalpine musl Symbolwhole package
Filter Runtimenode 22 Package version16.0.1 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

whatwg-url @16.0.1alpine musl · 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
2 / 2
Contract verifications
1 / 1
Usage records
1
Independent reporting peers
1
Last recorded
2026-08-30

Dependencies

LibraryVersionMeasured thereProjects
@exodus/bytes 1.15.1 contract passed 2 project-days
tr46 6.0.0 contract passed 2 project-days
webidl-conversions 8.0.1 contract passed 2 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.

Library16.0.114.2.0
tr46 6.0.0 5.1.1
webidl-conversions 8.0.1 7.0.0
@exodus/bytes 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