CodeSampleX

Recordsgolanggolang.org/x/cryptov0.48.0

Change the conditions
Fixed
OSdebian glibc Package versionv0.48.0
Filter Runtimego 1.26 Symbolwhole package Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

golang.org/x/crypto @v0.48.0debian glibc · x64 · go 1.26 · go · go

package-level total, not an API

4 of 4 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 (5)

Project observations
4 / 4
Contract verifications
4 / 4
Usage records
5
Independent reporting peers
1
Last recorded
2026-09-03

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 4 · Steady 0

First observed break

v0.48.0 golang.org/x/net@v0.49.0

windows · go@1.26

3 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
golang.org/x/net v0.49.0 FAIL Linked failure observed; version changed across releases nothing measured 4 project-days
golang.org/x/net v0.50.0 FAIL Linked failure observed; version changed across releases contract passed 1 project-day
golang.org/x/sys v0.41.0 FAIL Linked failure observed; version changed across releases contract passed 5 project-days
golang.org/x/term v0.40.0 FAIL Linked failure observed; version changed across releases nothing measured 5 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.

Libraryv0.55.0v0.54.0v0.52.0v0.50.0v0.48.0v0.36.0v0.20.0v0.19.0v0.0.0-20210921155107-089bfa567519v0.0.0-20200622213623-75b288015ac9
golang.org/x/net v0.57.0 v0.57.0 v0.55.0 v0.53.0 v0.50.0 v0.21.0 v0.21.0 v0.21.0 v0.4.0 v0.0.0-20210525063256-abc453219eb5
golang.org/x/sys v0.47.0 v0.47.0 v0.45.0 v0.43.0 v0.41.0 v0.31.0 v0.17.0 v0.17.0 v0.47.0 v0.47.0
golang.org/x/term v0.45.0 v0.45.0 v0.43.0 v0.42.0 v0.40.0 v0.30.0 v0.17.0 v0.17.0

Moved: 3 · 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