Recordsgolanggolang.org/x/lintv0.0.0-20190313153728-d0100b6bd8b3golang.org/x/lint.Linter
Change the conditions
Current conditions
golang.org/x/lint.Linter @v0.0.0-20190313153728-d0100b6bd8b3debian glibc · x64 · go 1.26 · go · go
1 of 1 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 (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-10-14
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 3. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/tools | v0.0.0-20190311212946-11955173bddd | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| golang.org/x/tools | v0.0.0-20190524140312-2c0ae7006135 | CHANGED Version changed, no linked failure | contract passed | 20 project-days |
| golang.org/x/tools | v0.44.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.
| Library | v0.0.0-20200302205851-738671d3881b | v0.0.0-20190930215403-16217165b5de | v0.0.0-20190313153728-d0100b6bd8b3 | v0.0.0-20190227174305-5b3e6a55c961 |
|---|---|---|---|---|
| golang.org/x/tools | v0.1.12 | v0.0.0-20191029041327-9cc4af7d6b2c | v0.44.0 | 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.