Recordsnpmajv8.17.1
Change the conditions
Current conditions
ajv @8.17.1ubuntu glibc · x64 · node 22 · npm 10 · node
package-level total, not an API
0 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 failed (1)
- Project observations
- 1 / 1
- Contract verifications
- 0 / 1
- Usage records
- 4
- Independent reporting peers
- 3
- Last recorded
- 2026-08-31
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| fast-deep-equal | 3.1.3 | contract passed | 5 project-days |
| fast-uri | 3.1.6 | contract passed | 5 project-days |
| json-schema-traverse | 1.0.0 | contract passed | 5 project-days |
| require-from-string | 2.0.2 | contract passed | 5 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 UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 8.17.1 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:a19dc4247bc4…unknown format <str> ignored in schema at path <str> · unknown format <str> ignored in schema at path <str> · node:internal/modules/run_main:<n> …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