CodeSampleX

Recordsnpmajv-formats3.0.1

Change the conditions
Fixed
OSdebian glibc Execution contextnode
Filter Runtimenode 22 Package version3.0.1 Symbolwhole package Architecturex64 Package managernpm libcglibc Clear filters

Current conditions

ajv-formats @3.0.1debian glibc · x64 · node 22 · npm · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

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

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
8
Independent reporting peers
1
Last recorded
2026-10-21

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

3.0.1

executionContext=node

54 FAIL · stage: PROJECT_PROCESS

Library Version Health Measured there Projects
ajv 8.17.1 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
ajv 8.20.0 CANDIDATE Correlated change; unproven combination contract passed 81 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