CodeSampleX

Recordsgolanggolang.org/x/lintv0.0.0-20190930215403-16217165b5de

Change the conditions
Fixed
OSalpine musl Package managergo
Filter Runtimego 1.26 Package versionv0.0.0-20190930215403-16217165b5de Symbolwhole package Architecturex64 Execution contextgo libcmusl Clear filters

Current conditions

golang.org/x/lint @v0.0.0-20190930215403-16217165b5dealpine musl · 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.

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

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 0

First observed break

v0.0.0-20190930215403-16217165b5de

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:cc6da42c69d5a8040f6a9dbda27d7d8e0daef42f5c34d1da8e73713061384c8d

View exact conditions View failure cluster
Library Version Health Measured there Projects
golang.org/x/tools v0.0.0-20190311212946-11955173bddd CANDIDATE Correlated change; unproven combination contract passed 2 project-days
golang.org/x/tools v0.0.0-20191029041327-9cc4af7d6b2c CANDIDATE Correlated change; unproven combination builds observed 1 project-day
golang.org/x/tools v0.0.0-20191029190741-b9c20aec41a5 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
golang.org/x/tools v0.0.0-20200103221440-774c71fcf114 CANDIDATE Correlated change; unproven combination builds observed 6 project-days
golang.org/x/tools v0.6.0 CANDIDATE Correlated change; unproven combination contract passed 10 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.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.

Recent failure clusters