CodeSampleX

Recordsnpmsource-map-support0.5.21source-map-support.getErrorSource

Change the conditions
Fixed
OSalpine musl Symbolsource-map-support.getErrorSource
Filter Runtimenode 22 Package version0.5.21 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

source-map-support.getErrorSource @0.5.21alpine musl · 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
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-28
Evidence you can open

Dependencies

LibraryVersionMeasured thereProjects
buffer-from 1.1.2 contract passed 7 project-days
source-map 0.6.1 contract passed 7 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.

Library0.5.210.5.13
buffer-from 1.1.2 1.1.2
source-map 0.6.1 0.6.1

Moved: 0 · unchanged at every release: 2

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