Recordsnpmajv8.20.0
Change the conditions
Current conditions
ajv @8.20.0windows 11 · x64 · node (version not recorded) · 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 (5)
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-13
Dependency Health
Observed combinations and failure evidence for this release
First observed break
8.20.0
executionContext=node
96 FAIL · stage: PROJECT_PROCESS
| 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 | 20 project-days |
| fast-uri | 3.1.9 | CANDIDATE Correlated change; unproven combination | contract passed | 43 project-days |
| json-schema-traverse | 1.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 86 project-days |
| fast-deep-equal | 3.1.3 | PASS All observations passed | contract passed | 87 project-days |
| require-from-string | 2.0.2 | PASS All observations passed | contract passed | 84 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 | 6.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
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×96 6.15.0 → 8.20.0 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 4 · First recorded: 2026-08-14 · Last seen: 2026-11-20Diagnostic re-verification candidate
-
observed PROJECT_TEST EFTYPE Evidence gap ×52 6.12.6 → 6.15.0 → 8.17.1 → 8.20.0 executionContext=node · os=windowsEvidence quality: legacy-evidence-incomplete · Environment variants: 4 · First recorded: 2026-08-21 · Last seen: 2026-11-20Diagnostic re-verification candidate
-
observed PROCESS_START process start failed Evidence gap ×8 6.15.0 → 8.17.1 → 8.20.0 executionContext=node sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 2 · First recorded: 2026-09-02 · Last seen: 2026-09-16Diagnostic re-verification candidate
-
observed PROJECT_TYPECHECK Evidence gap ×7 6.12.6 → 6.15.0 → 8.17.1 → 8.20.0 executionContext=node · moduleSystem=cjs · os=windowsEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-19 · Last seen: 2026-11-20Diagnostic re-verification candidate