CodeSampleX

Recordsgolanggithub.com/Microsoft/go-winiov0.6.2

Change the conditions
Fixed
Runtimego (version not recorded) Symbolwhole package Package managergo 1
Filter OSwindows 11 Package versionv0.6.2 Architecturex64 Clear filters

Current conditions

github.com/Microsoft/go-winio @v0.6.2windows 11 · x64 · go (version not recorded) · go 1

package-level total, not an API

1 of 1 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (3)

Project observations
1 / 1
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-15
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 1

First observed break

v0.6.2

windows · go@1.26

298 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
golang.org/x/sys v0.10.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
golang.org/x/sys v0.26.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
golang.org/x/tools v0.11.0 CANDIDATE Correlated change; unproven combination nothing measured 3 project-days
github.com/sirupsen/logrus v1.9.3 PASS All observations passed builds observed 3 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.

Libraryv0.6.2v0.6.0
golang.org/x/sys v0.26.0 v0.0.0-20220722155257-8c9f86f7a55f
golang.org/x/tools v0.11.0 v0.1.12
github.com/sirupsen/logrus v1.9.3 —

Moved: 2 · 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