CodeSampleX

Recordsgolanggolang.org/x/toolsv0.49.0

Change the conditions
Fixed
Package versionv0.49.0 Symbolwhole package Package managergo
Filter OSdebian glibc Runtimego 1.26 Architecturex64 Execution contextgo libcglibc Clear filters

Current conditions

golang.org/x/tools @v0.49.0debian glibc · x64 · go 1.26 · go · go

package-level total, not an API

5 of 5 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 (5)

Project observations
4 / 4
Contract verifications
5 / 5
Usage records
2
Independent reporting peers
1
Last recorded
2026-09-04

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 6 · Steady 0

First observed break

v0.49.0 github.com/yuin/goldmark@v1.4.13

linux · go@1.26

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:d5fae02e8604b6955b8f1c65a8d5cc795aaceed9651a9f67da2c34536a6764a1

Library Version Health Measured there Projects
github.com/google/go-cmp v0.6.0 FAIL Linked failure observed on this release nothing measured 5 project-days
github.com/yuin/goldmark v1.4.13 FAIL Linked failure observed; version changed across releases nothing measured 5 project-days
golang.org/x/mod v0.39.0 FAIL Linked failure observed; version changed across releases builds observed 5 project-days
golang.org/x/net v0.58.0 FAIL Linked failure observed; version changed across releases builds observed 5 project-days
golang.org/x/sync v0.22.0 FAIL Linked failure observed; version changed across releases contract passed 5 project-days
golang.org/x/telemetry v0.0.0-20260811182544-a038080d80e5 FAIL Linked failure observed; version changed across releases nothing measured 5 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: 7 · unchanged at every release: 2

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