Recordsnpmajv8.20.0ajv.compileSerializer
Change the conditions
Current conditions
ajv.compileSerializer @8.20.0alpine 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-18
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| 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.
| Library | 8.20.0 | 8.17.1 | 6.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
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×4 6.15.0 → 8.20.0 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-14 · Last seen: 2026-08-29Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×3 6.15.0 → 8.20.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:986d98189e70…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 8.20.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:0d62cac8c07a…AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: · + actual - expected · + <str> · - <str>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 8.20.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:e1d65fc7c136…<path>:<n> · throw new Error(`Unsupported arch ${name}`) · ^ · Error: Unsupported arch 1node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 8.20.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:9be950af9140…Traceback (most recent call last): · File <str>, line 1, in <module> · ModuleNotFoundError: No module named <str>python3 · unclassified-diagnostic · outer python3 · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate