CodeSampleX

Recordsnpmajv-formats2.1.1addFormats

Change the conditions
Fixed
SymboladdFormats Package managernpm
Filter OSalpine musl Runtimenode 22 Package version2.1.1 Architecturex64 Execution contextnode libcmusl Clear filters

Current conditions

addFormats @2.1.1alpine 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
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-08

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

2.1.1

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

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

Library Version Health Measured there Projects
ajv 8.17.1 CANDIDATE Correlated change; unproven combination contract passed 13 project-days
ajv 8.20.0 CANDIDATE Correlated change; unproven combination contract passed 3 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.0.12.1.1
ajv 8.17.1 8.20.0

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

Showing the 12 most-reported of 25 recorded failure clusters. The rest are single reports.