CodeSampleX

Recordsnpmajv8.20.0

Change the conditions
Fixed
Runtimenode 22 Package managernpm 11
Filter OSwindows 11 Package version8.20.0 Symbolwhole package Architecturex64 Execution contextnode Clear filters

Current conditions

ajv @8.20.0windows 11 · x64 · node 22 · npm 11 · node

package-level total, not an API

15 of 16 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (5)

Project observations
15 / 16
Contract verifications
nothing at this coordinate
Usage records
5
Independent reporting peers
1
Failures with a captured fingerprint
0 / 1
Last recorded
2026-08-24
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 2

First observed break

8.20.0

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

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
fast-uri 3.1.4 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
fast-uri 3.1.5 CANDIDATE Correlated change; unproven combination contract passed 13 project-days
fast-uri 3.1.6 CANDIDATE Correlated change; unproven combination contract passed 10 project-days
fast-uri 3.1.8 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
json-schema-traverse 1.0.0 CANDIDATE Correlated change; unproven combination contract passed 27 project-days
fast-deep-equal 3.1.3 PASS All observations passed contract passed 28 project-days
require-from-string 2.0.2 PASS All observations passed contract passed 25 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.

Library8.20.08.17.16.15.06.12.6
fast-uri 3.1.4 3.1.0 — —
json-schema-traverse 1.0.0 1.0.0 0.4.1 0.4.1
fast-deep-equal 3.1.3 3.1.3 3.1.3 3.1.3
fast-json-stable-stringify — — 2.1.0 2.1.0
require-from-string 2.0.2 2.0.2 — —
uri-js — — 4.4.1 4.4.1

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