CodeSampleX

Recordsnpmqs6.13.0qs.parse

Change the conditions
Fixed
OSdebian glibc Package version6.13.0 Symbolqs.parse
Filter Runtimenode 22 Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

qs.parse @6.13.0debian glibc · 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
2 / 2
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-10-09

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 1

First observed break

6.13.0

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

2 FAIL · stage: UNKNOWN · fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc

Library Version Health Measured there Projects
side-channel 1.1.1 PASS All observations passed contract passed 11 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.

Library6.16.06.15.36.13.06.11.0
es-define-property 1.0.1 1.0.1 — —
side-channel 1.1.1 1.1.1 1.1.1 1.1.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