CodeSampleX

Recordsnpmajv6.15.0ajv.Ajv

Change the conditions
Fixed
Symbolajv.Ajv
Filter OSwindows 11 Runtimenode 24 Package version6.15.0 Architecturex64 Package managerpnpm 10 Execution contextnode Clear filters

Current conditions

ajv.Ajv @6.15.0windows 11 · x64 · node 24 · pnpm 10 · node

0 of 6 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
12 / 21
Contract verifications
0 / 6
Independent reporting peers
1
Last recorded
2026-09-16

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 3

First observed break

6.15.0

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

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

Library Version Health Measured there Projects
json-schema-traverse 0.4.1 CANDIDATE Correlated change; unproven combination contract passed 90 project-days
fast-deep-equal 3.1.3 PASS All observations passed contract passed 91 project-days
fast-json-stable-stringify 2.1.0 PASS All observations passed contract passed 90 project-days
uri-js 4.4.1 PASS All observations passed contract passed 91 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.

Moved: 2 · unchanged at every release: 4

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 207 recorded failure clusters. The rest are single reports.