Recordsgolanggolang.org/x/cryptov0.55.0golang.org/x/crypto/argon2.Key
Change the conditions
Current conditions
golang.org/x/crypto/argon2.Key @v0.55.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
First observed break
v0.55.0
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:c95b7b9d7dca9480a46b3c516ddd1a806ca10fc2608ffb2121b59911aaa07f53
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/net | v0.57.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| golang.org/x/net | v0.58.0 | CANDIDATE Correlated change; unproven combination | contract passed | 20 project-days |
| golang.org/x/sys | v0.47.0 | CANDIDATE Correlated change; unproven combination | contract passed | 23 project-days |
| golang.org/x/term | v0.45.0 | CANDIDATE Correlated change; unproven combination | contract passed | 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.
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
-
observed UNKNOWN exit 1 Evidence gap ×1 v0.55.0 os=linux · runtime=go@1.26 sha256:c95b7b9d7dca…sha3.Sum512 <str> mismatch: got <token>, want <token> · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v0.55.0 os=linux · runtime=go@1.26 sha256:cbb95d5b5eb1…sha3.NewShake256 <str> 64-byte mismatch: got <token>, want <token> · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v0.55.0 os=linux · runtime=go@1.26 sha256:3a88fde6a8c9…go: finding module for package golang.org/x/crypto/secretbox · go: example.com/sample imports …go · unclassified-diagnostic · outer go mod · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-02 · Last seen: 2026-09-02Diagnostic re-verification candidate