Recordsgolanggolang.org/x/toolsv0.0.0-20200825202427-b303f430e36d
Change the conditions
Current conditions
golang.org/x/tools @v0.0.0-20200825202427-b303f430e36ddebian 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
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-03
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 5. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/yuin/goldmark | v1.1.32 | CHANGED Version changed, no linked failure | nothing measured | 1 project-day |
| golang.org/x/mod | v0.3.0 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| golang.org/x/net | v0.0.0-20210525063256-abc453219eb5 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| golang.org/x/sync | v0.21.0 | CHANGED Version changed, no linked failure | nothing measured | 1 project-day |
| golang.org/x/xerrors | v0.0.0-20200804184101-5ec99f83aff1 | 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.
| Library | v0.49.0 | v0.44.0 | v0.6.0 | v0.1.12 | v0.0.0-20200825202427-b303f430e36d | v0.0.0-20200130002326-2f3ba24bd6e7 |
|---|---|---|---|---|---|---|
| github.com/yuin/goldmark | v1.4.13 | v1.8.2 | v1.4.13 | v1.4.13 | v1.1.32 | — |
| golang.org/x/mod | v0.39.0 | v0.35.0 | v0.8.0 | v0.6.0-dev.0.20220419223038-86c51ed26bb4 | v0.3.0 | v0.1.1-0.20191105210325-c90efee705ee |
| golang.org/x/net | v0.58.0 | v0.53.0 | v0.21.0 | v0.4.0 | v0.0.0-20210525063256-abc453219eb5 | v0.0.0-20190620200207-3b0461eec859 |
| golang.org/x/sync | v0.22.0 | v0.20.0 | v0.1.0 | v0.21.0 | v0.21.0 | v0.0.0-20190423024810-112230192c58 |
| golang.org/x/sys | — | — | v0.17.0 | v0.47.0 | — | — |
| golang.org/x/telemetry | v0.0.0-20260811182544-a038080d80e5 | v0.0.0-20260409153401-be6f6cb8b1fa | — | — | — | — |
| golang.org/x/xerrors | — | — | — | — | v0.0.0-20200804184101-5ec99f83aff1 | v0.0.0-20191011141410-1b5146add898 |
| github.com/google/go-cmp | v0.6.0 | v0.6.0 | — | — | — | — |
| golang.org/x/text | — | — | — | v0.5.0 | — | — |
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.