Recordsgolanggolang.org/x/netv0.56.0publicsuffix.EffectiveTLDPlusOne
Change the conditions
Current conditions
publicsuffix.EffectiveTLDPlusOne @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
First observed break
v0.56.0
linux · go@1.26
4 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:964ddac6b19a356d0ae3f5727559d1fc36ac1222ed1964d18326e8a89565fde3
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/crypto | v0.54.0 | CANDIDATE Correlated change; unproven combination | contract passed | 10 project-days |
| golang.org/x/sys | v0.47.0 | CANDIDATE Correlated change; unproven combination | contract passed | 10 project-days |
| golang.org/x/term | v0.45.0 | CANDIDATE Correlated change; unproven combination | contract passed | 10 project-days |
| golang.org/x/text | v0.40.0 | CANDIDATE Correlated change; unproven combination | contract passed | 10 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.
Recent failure clusters
-
observed PROJECT_COMPILE exit 1 ×4 v0.12.0 → v0.52.0 → v0.56.0 os=linux · runtime=go@1.26 sha256:964ddac6b19a…<path> <str> imported and not usedgo/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-09-05