Recordsgolanggolang.org/x/cryptov0.0.0-20220525230936-793ad666bf5egolang.org/x/crypto/bcrypt.ErrMismatchedHashAndPassword
Change the conditions
Current conditions
golang.org/x/crypto/bcrypt.ErrMismatchedHashAndPassword @v0.0.0-20220525230936-793ad666bf5eubuntu glibc · x64 · go 1.26 · go 1
10 of 10 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
- 10 / 10
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-10-23
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.0.0-20220525230936-793ad666bf5e
linux · go@1.26
7 FAIL
· stage: UNKNOWN
· fingerprint: sha256:3b3190f2cd44c327e0d62d5fcac6e314a022dc126a98b5c1b38661e44ab6a020
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/net | v0.0.0-20211112202133-69e39bad7dc2 | CANDIDATE Correlated change; unproven combination | nothing measured | 31 project-days |
| golang.org/x/sys | v0.0.0-20210615035016-665e8c7367d1 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| golang.org/x/sys | v0.0.0-20220608164250-635b8c9b7f68 | CANDIDATE Correlated change; unproven combination | nothing measured | 1 project-day |
| golang.org/x/sys | v0.8.0 | CANDIDATE Correlated change; unproven combination | contract passed | 8 project-days |
| golang.org/x/sys | v0.9.0 | CANDIDATE Correlated change; unproven combination | contract passed | 15 project-days |
| golang.org/x/term | v0.0.0-20201126162022-7de9c90e9dd1 | CANDIDATE Correlated change; unproven combination | contract passed | 19 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 ×7 v0.0.0-20190701094942-4def268fd1a4 → v0.0.0-20210711020723-a769d52b0f97 → v0.0.0-20220525230936-793ad666bf5e → v0.43.0 → v0.48.0 → v0.49.0 os=linux · runtime=go@1.26 sha256:3b3190f2cd44…doc: cannot find package <str> in any of: · ($GOROOT not set) · <path> (from $GOPATH)go · unclassified-diagnostic · outer go · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-04 · Last seen: 2026-10-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×6 v0.0.0-20181029021203-45a5f77698d3 → v0.0.0-20190308221718-c2843e01d9a2 → v0.0.0-20190820162420-60c769a6c586 → v0.0.0-20201002170205-7f63de1d35b0 → v0.0.0-20220525230936-793ad666bf5e → v0.43.0 os=linux · runtime=go@1.26 sha256:0882784d80c2…go: build output <str> already exists and is a directorygo · unclassified-diagnostic · outer go build · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-20 · Last seen: 2026-10-27Diagnostic re-verification candidate