CodeSampleX

Recordsnpm@vitest/spy3.2.4

Change the conditions
Fixed
OSubuntu glibc Package version3.2.4 Package managernpm 10
Filter Runtimenode 22 Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

@vitest/spy @3.2.4ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 3 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed

Project observations
11 / 12
Contract verifications
0 / 3
Usage records
8
Independent reporting peers
2
Last recorded
2026-09-08
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

3.2.4

executionContext=node

10 FAIL · stage: PROCESS_START · fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32

View exact conditions View failure cluster
Library Version Health Measured there Projects
tinyspy 4.0.6 CANDIDATE Correlated change; unproven combination 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.

Library3.2.73.2.43.0.02.1.9
tinyspy 4.0.4 4.0.6 3.0.2 3.0.2

Moved: 1 · unchanged at every release: 0

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