CodeSampleX

Recordsnpmmarkdown-it14.3.1markdownit

Change the conditions
Fixed
Symbolmarkdownit
Filter OSdebian glibc Runtimenode 22 Package version14.3.1 Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

markdownit @14.3.1debian glibc · 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
2 / 2
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-10-13
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 4

First observed break

14.3.1

linux · node@22.23 · executionContext=node

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
linkify-it 5.0.2 CANDIDATE Correlated change; unproven combination contract passed 12 project-days
mdurl 2.1.0 CANDIDATE Correlated change; unproven combination contract passed 12 project-days
argparse 2.0.1 PASS All observations passed contract passed 12 project-days
entities 4.5.0 PASS All observations passed contract passed 12 project-days
punycode.js 2.3.1 PASS All observations passed contract passed 12 project-days
uc.micro 2.1.0 PASS All observations passed contract passed 12 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.

Library14.3.214.3.114.1.0
linkify-it 5.0.2 5.0.2 5.0.0
mdurl 2.1.0 2.1.0 2.0.0
argparse 2.0.1 2.0.1 2.0.1
entities 4.5.0 4.5.0 4.5.0
punycode.js 2.3.1 2.3.1 2.3.1
uc.micro 2.1.0 2.1.0 2.1.0

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