CodeSampleX

Recordsgolanggithub.com/cpuguy83/go-md2man/v2v2.0.2md2man.Render

Change the conditions
Fixed
Symbolmd2man.Render
Filter OSalpine musl Runtimego 1.26 Package versionv2.0.2 Architecturex64 Package managergo Execution contextgo libcmusl Clear filters

Current conditions

md2man.Render @v2.0.2alpine musl · x64 · go 1.26 · go · go

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
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-28

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 1

First observed break

v2.0.2

linux · go@1.26

2 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
github.com/russross/blackfriday/v2 v2.1.0 PASS All observations passed contract passed 2 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: 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