Recordsgolanggolang.org/x/netv0.56.0publicsuffix.List
Change the conditions
Current conditions
publicsuffix.List @v0.56.0linux · musl · 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
- nothing at this coordinate
- Contract verifications
- 1 / 1
- Last recorded
- 2026-08-28
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.54.0 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| golang.org/x/sys | v0.47.0 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| golang.org/x/term | v0.45.0 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| golang.org/x/text | v0.40.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.