Recordsgolanggolang.org/x/netv0.59.0golang.org/x/net/html/atom.Head
Change the conditions
Current conditions
golang.org/x/net/html/atom.Head @v0.59.0ubuntu glibc · x64 · go 1.26 · go 1
3 of 3 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 3 / 3
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-09-14
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 4. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/crypto | v0.57.0 | CHANGED Version changed, no linked failure | nothing measured | 2 project-days |
| golang.org/x/sys | v0.48.0 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| golang.org/x/term | v0.46.0 | CHANGED Version changed, no linked failure | nothing measured | 2 project-days |
| golang.org/x/text | v0.42.0 | CHANGED Version changed, no linked failure | contract passed | 2 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.