CodeSampleX

Recordsgolanggolang.org/x/lintv0.0.0-20190227174305-5b3e6a55c961

Change the conditions
Fixed
Package versionv0.0.0-20190227174305-5b3e6a55c961 libcglibc
Filter OSdebian glibc Runtimego 1.26 Symbolwhole package Architecturex64 Package managergo Execution contextgo Clear filters

Current conditions

golang.org/x/lint @v0.0.0-20190227174305-5b3e6a55c961debian glibc · x64 · go 1.26 · go · go

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
2
Independent reporting peers
1
Last recorded
2026-09-07

Dependency Health

Observed combinations and failure evidence for this release

Changed 2 · Steady 0

Dependency changes observed: 2. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
golang.org/x/tools v0.0.0-20190226205152-f727befe758c CHANGED Version changed, no linked failure builds observed 7 project-days
golang.org/x/tools v0.31.0 CHANGED Version changed, no linked failure contract passed 1 project-day

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.0.0-20200302205851-738671d3881bv0.0.0-20190930215403-16217165b5dev0.0.0-20190227174305-5b3e6a55c961
golang.org/x/tools v0.1.12 v0.0.0-20191029041327-9cc4af7d6b2c v0.31.0

Moved: 1 · unchanged at every release: 0

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.