CodeSampleX

Recordsgolanggolang.org/x/toolsv0.44.0golang.org/x/tools/go/ast/astutil.Apply

Change the conditions
Fixed
Runtimego 1.26 Symbolgolang.org/x/tools/go/ast/astutil.Apply Package managergo 1
Filter OSubuntu glibc Package versionv0.44.0 Architecturex64 libcglibc Clear filters

Current conditions

golang.org/x/tools/go/ast/astutil.Apply @v0.44.0ubuntu glibc · x64 · go 1.26 · go 1

2 of 2 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
2 / 2
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-31

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 9 · Steady 0

First observed break

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

windows · go@1.26

2 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
github.com/google/go-cmp v0.6.0 FAIL Linked failure observed on this release nothing measured 1 project-day
github.com/google/go-cmp v0.7.0 FAIL Linked failure observed on this release contract passed 2 project-days
github.com/yuin/goldmark v1.4.13 FAIL Linked failure observed; version changed across releases nothing measured 1 project-day
github.com/yuin/goldmark v1.8.2 FAIL Linked failure observed; version changed across releases nothing measured 1 project-day
golang.org/x/mod v0.35.0 FAIL Linked failure observed; version changed across releases contract passed 3 project-days
golang.org/x/net v0.53.0 FAIL Linked failure observed; version changed across releases contract passed 1 project-day
golang.org/x/net v0.55.0 FAIL Linked failure observed; version changed across releases contract passed 2 project-days
golang.org/x/sync v0.20.0 FAIL Linked failure observed; version changed across releases contract passed 3 project-days
golang.org/x/telemetry v0.0.0-20260409153401-be6f6cb8b1fa FAIL Linked failure observed; version changed across releases nothing measured 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.

Moved: 6 · unchanged at every release: 3

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