Recordsgolanggolang.org/x/netv0.53.0golang.org/x/net/html.Token
Change the conditions
Current conditions
golang.org/x/net/html.Token @v0.53.0ubuntu glibc · x64 · go 1.26 · go 1
0 of 2 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed
- Project observations
- 2 / 2
- Contract verifications
- 0 / 2
- Independent reporting peers
- 2
- Last recorded
- 2026-09-04
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 |
|---|---|---|---|---|
| golang.org/x/crypto | v0.50.0 | CHANGED Version changed, no linked failure | contract passed | 4 project-days |
| golang.org/x/sys | v0.43.0 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| golang.org/x/sys | v0.44.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| golang.org/x/term | v0.42.0 | CHANGED Version changed, no linked failure | builds observed | 4 project-days |
| golang.org/x/text | v0.36.0 | CHANGED Version changed, no linked failure | contract passed | 4 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: 4 · 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.