CodeSampleX

Recordsnpmsource-map-support0.5.21

Change the conditions
Fixed
Runtimenode 22 Package managerpnpm 10
Filter OSwindows 11 Package version0.5.21 Symbolwhole package Architecturex64 Execution contextnode Clear filters

Current conditions

source-map-support @0.5.21windows 11 · x64 · node 22 · pnpm 10 · 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 (3)

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 2

First observed break

0.5.21

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

32 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

View exact conditions View failure cluster
Library Version Health Measured there Projects
buffer-from 1.1.2 PASS All observations passed contract passed 38 project-days
source-map 0.6.1 PASS All observations passed contract passed 35 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