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

Dependencies

LibraryVersionMeasured thereProjects
fast-deep-equal 3.1.3 contract passed 10 project-days
fast-uri 3.1.5 contract passed 1 project-day
fast-uri 3.1.6 contract passed 9 project-days
json-schema-traverse 1.0.0 contract passed 10 project-days
require-from-string 2.0.2 contract passed 10 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.0
fast-uri 3.1.5 3.1.6 —
json-schema-traverse 1.0.0 1.0.0 0.4.1
fast-deep-equal 3.1.3 3.1.3 3.1.3
fast-json-stable-stringify — — 2.1.0
require-from-string 2.0.2 2.0.2 —
uri-js — — 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