CodeSampleX

Recordsnpm@npmcli/fs2.1.2

Change the conditions
Fixed
OSwindows 11 Runtimenode 24 Package version2.1.2
Filter Symbolwhole package Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

@npmcli/fs @2.1.2windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

0 of 11 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
25 / 28
Contract verifications
0 / 11
Usage records
46
Independent reporting peers
1
Failures with a captured fingerprint
1 / 3
Last recorded
2026-09-16
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 1

First observed break

2.1.2

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

15 FAIL · stage: UNKNOWN · fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868

View exact conditions View failure cluster
Library Version Health Measured there Projects
semver 7.8.5 CANDIDATE Correlated change; unproven combination contract passed 19 project-days
@gar/promisify 1.1.3 PASS All observations passed contract passed 19 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.

Library5.0.04.0.02.1.2
semver 7.7.3 7.7.4 7.8.5
@gar/promisify — — 1.1.3

Moved: 1 · unchanged at every release: 1

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