CodeSampleX

Recordsnpmschema-utils4.3.3validate

Change the conditions
Fixed
OSalpine musl Symbolvalidate
Filter Runtimenode 22 Package version4.3.3 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

validate @4.3.3alpine 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
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-26
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 5

First observed break

4.3.3

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

4 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2

View exact conditions View failure cluster
Library Version Health Measured there Projects
@types/json-schema 7.0.15 PASS All observations passed contract passed 3 project-days
ajv 8.17.1 PASS All observations passed contract passed 2 project-days
ajv 8.20.0 PASS All observations passed contract passed 1 project-day
ajv-formats 2.1.1 PASS All observations passed contract passed 3 project-days
ajv-keywords 5.1.0 PASS All observations passed 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.