CodeSampleX

Recordsnpmprosemirror-model1.25.11

Change the conditions
Fixed
Package managernpm 10
Filter OSubuntu glibc Runtimenode 22 Package version1.25.11 Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

prosemirror-model @1.25.11ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 10 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed

Project observations
79 / 79
Contract verifications
0 / 10
Usage records
37
Independent reporting peers
3
Last recorded
2026-09-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 1

First observed break

1.25.11

linux · node@22.23 · executionContext=node

3 FAIL · stage: UNKNOWN · fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc

View exact conditions View failure cluster
Library Version Health Measured there Projects
orderedmap 2.1.1 PASS All observations passed contract passed 97 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.

Library1.25.111.25.4
orderedmap 2.1.1 2.1.1

Moved: 0 · unchanged at every release: 1

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