CodeSampleX

Recordsgolanghonnef.co/go/toolsv0.0.1-2020.1.4

Change the conditions
Fixed
Package versionv0.0.1-2020.1.4 Package managergo 1
Filter OSubuntu glibc Runtimego 1.26 Symbolwhole package Architecturex64 libcglibc Clear filters

Current conditions

honnef.co/go/tools @v0.0.1-2020.1.4ubuntu glibc · x64 · go 1.26 · go 1

package-level total, not an API

0 of 3 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
30 / 32
Contract verifications
0 / 3
Usage records
12
Independent reporting peers
1
Last recorded
2026-10-09

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Unknown 2 · Steady 2

First observed break

v0.0.1-2020.1.4

linux · go@1.26

2 FAIL · stage: PROJECT_RESOLVE · fingerprint: sha256:960c448010d338b23e4225acf905c3ba5fc46c4e38004ca42dccb0ec225d0a82

Library Version Health Measured there Projects
golang.org/x/mod v0.3.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
golang.org/x/tools v0.0.0-20200618134242-20370b0cb4b2 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
golang.org/x/tools v0.0.0-20200804011535-6c149bb5ef0d CANDIDATE Correlated change; unproven combination builds observed 2 project-days
github.com/google/renameio v0.1.0 UNKNOWN No linked outcome measured nothing measured 3 project-days
github.com/kisielk/gotool v1.0.0 UNKNOWN No linked outcome measured nothing measured 3 project-days
github.com/BurntSushi/toml v0.3.1 PASS All observations passed contract passed 3 project-days
github.com/rogpeppe/go-internal v1.3.0 PASS All observations passed contract passed 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.

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