Recordsgolanggolang.org/x/netv0.56.0golang.org/x/net/publicsuffix.PublicSuffix
Change the conditions
Current conditions
golang.org/x/net/publicsuffix.PublicSuffix @v0.56.0ubuntu glibc · x64 · go 1.26 · go 1
2 of 4 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- Project observations
- 2 / 4
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-31
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.56.0
linux · go@1.26
7 FAIL
· stage: UNKNOWN
· fingerprint: sha256:5782351ae918be51270d9cef1bb673332e715560dfddd80edfbf5b54ef128219
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/crypto | v0.53.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| golang.org/x/crypto | v0.54.0 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| golang.org/x/sys | v0.46.0 | CANDIDATE Correlated change; unproven combination | contract passed | 8 project-days |
| golang.org/x/sys | v0.47.0 | CANDIDATE Correlated change; unproven combination | contract passed | 12 project-days |
| golang.org/x/term | v0.44.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 9 project-days |
| golang.org/x/term | v0.45.0 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| golang.org/x/text | v0.38.0 | CANDIDATE Correlated change; unproven combination | contract passed | 8 project-days |
| golang.org/x/text | v0.40.0 | CANDIDATE Correlated change; unproven combination | contract passed | 12 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 UNKNOWN signal KILLED Evidence gap ×7 v0.52.0 → v0.56.0 → v0.58.0 os=linux · runtime=go@1.26 sha256:5782351ae918…go · unclassified-diagnostic · outer go run, go test · gap diagnostic-missingEvidence quality: partial · Environment variants: 1 · First recorded: 2026-09-07 · Last seen: 2026-10-12Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 1 ×5 v0.0.0-20180826012351-8a410e7b638d → 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-19