CodeSampleX

Recordsnpm@vitest/mocker3.2.7@vitest/mocker.AutospiedModule

Change the conditions
Fixed
OSalpine musl Symbol@vitest/mocker.AutospiedModule Execution contextnode
Filter Runtimenode 22 Package version3.2.7 Architecturex64 Package managernpm libcmusl Clear filters

Current conditions

@vitest/mocker.AutospiedModule @3.2.7alpine 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-23
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 2

First observed break

3.2.7

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

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
@vitest/spy 3.2.7 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
estree-walker 3.0.3 PASS All observations passed contract passed 8 project-days
magic-string 0.30.21 PASS All observations passed contract passed 8 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.

Library4.1.114.1.104.0.184.0.164.0.03.2.73.2.43.0.02.1.9
@vitest/spy 4.1.11 4.1.10 4.0.18 4.0.16 4.0.0 3.2.7 3.2.4 3.0.0 2.1.9
estree-walker 3.0.3 3.0.3 3.0.3 3.0.3 3.0.3 3.0.3 3.0.3 3.0.3 3.0.3
magic-string 0.30.21 0.30.21 0.30.21 0.30.21 0.30.21 0.30.21 0.30.21 0.30.21 0.30.21

Moved: 1 · 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