CodeSampleX

Recordsnpmprosemirror-tables1.8.5

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

Current conditions

prosemirror-tables @1.8.5ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 7 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
68 / 68
Contract verifications
0 / 7
Usage records
36
Independent reporting peers
3
Last recorded
2026-09-17

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 2

First observed break

1.8.5

linux · node@22.23 · moduleSystem=cjs · executionContext=node

2 FAIL · stage: UNKNOWN · fingerprint: sha256:a4c16095efc09c0e3ff544250e938719346bc9b2cb85e02e7db0a48f7c91962a

Library Version Health Measured there Projects
prosemirror-model 1.25.11 CANDIDATE Correlated change; unproven combination contract passed 87 project-days
prosemirror-transform 1.12.1 CANDIDATE Correlated change; unproven combination contract passed 87 project-days
prosemirror-view 1.42.3 CANDIDATE Correlated change; unproven combination contract passed 87 project-days
prosemirror-keymap 1.2.3 PASS All observations passed contract passed 87 project-days
prosemirror-state 1.4.4 PASS All observations passed contract passed 87 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.

Moved: 3 · unchanged at every release: 2

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