CodeSampleX

Recordsgolanggolang.org/x/cryptov0.54.0blake2b.New256

Change the conditions
Fixed
Runtimego 1.26 Symbolblake2b.New256
Filter OSalpine musl Package versionv0.54.0 Architecturex64 Package managergo Execution contextgo libcmusl Clear filters

Current conditions

blake2b.New256 @v0.54.0alpine 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-30

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 3 · Steady 0

First observed break

v0.54.0 golang.org/x/net@v0.57.0

linux

13 FAIL · stage: PROJECT_PROCESS

Library Version Health Measured there Projects
golang.org/x/net v0.57.0 FAIL Linked failure observed; version changed across releases contract passed 4 project-days
golang.org/x/sys v0.47.0 FAIL Linked failure observed; version changed across releases contract passed 4 project-days
golang.org/x/term v0.45.0 FAIL Linked failure observed; version changed across releases contract passed 4 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: 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