CodeSampleX

Recordsgolanggithub.com/spf13/cobrav1.10.2Command.MarkFlagsOneRequired

Change the conditions
Fixed
Package versionv1.10.2 SymbolCommand.MarkFlagsOneRequired
Filter OSalpine musl Runtimego 1.26 Architecturex64 Package managergo Execution contextgo libcmusl Clear filters

Current conditions

Command.MarkFlagsOneRequired @v1.10.2alpine musl · x64 · go 1.26 · go · go

2 of 2 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
2 / 2
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-08-18

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 1

First observed break

v1.10.2

go@1.26

76 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
github.com/cpuguy83/go-md2man/v2 v2.0.7 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
github.com/spf13/pflag v1.0.10 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
go.yaml.in/yaml/v3 v3.0.4 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: 2 · unchanged at every release: 5

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