Recordsgolanggolang.org/x/cryptov0.36.0chacha20poly1305.New
Change the conditions
Current conditions
chacha20poly1305.New @v0.36.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-26
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 1 ·
Changed 3 ·
Steady 0
First observed break
v0.36.0
linux
13 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/net | v0.21.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| golang.org/x/sys | v0.31.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| golang.org/x/term | v0.30.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
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 PROJECT_PROCESS ERR_ASSERTION Evidence gap ×13 v0.0.0-20220331220935-ae2d96664a29 → v0.19.0 → v0.20.0 → v0.26.0 → v0.27.0 → v0.36.0 → v0.54.0 os=linuxEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-21 · Last seen: 2026-08-27Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×8 v0.0.0-20220331220935-ae2d96664a29 → v0.27.0 → v0.36.0 → v0.50.0 os=linux sha256:91ad26545eb1…node:internal/modules/cjs/loader:<n> · throw err; · ^ · Error: Cannot find module <str>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 2 · First recorded: 2026-08-30 · Last seen: 2026-09-04Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×2 v0.36.0 os=linux · runtime=go@1.26 sha256:e148632e8429…panic: runtime error: invalid memory address or nil pointer dereference · [signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x783bfc] …go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed PROJECT_PROCESS exit 1 ×1 v0.36.0 os=linux · runtime=go@1.26 sha256:d722967cb243…<path>:<n>:<n>: missing go.sum entry for module providing package golang.org/x/sys/cpu (imported by golang.org/x/crypto/argon2); to add: …Evidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30
-
observed PROJECT_TEST exit 1 ×1 v0.36.0 os=linux · runtime=go@1.26 sha256:a0832edd0b66…# sample · <path>:<n>:<n>: missing go.sum entry for module providing package golang.org/x/sys/cpu (imported by golang.<token>); to add: …Evidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30
-
observed PROJECT_TEST exit 1 ×1 v0.36.0 os=linux · runtime=go@1.26 sha256:cc163319b3eb…# sample/test_test · # [sample/test_test] · test/contract_test.go:<n>:<n>: suspect or: got != chacha20poly1305.NonceSizeX || got != 24 …Evidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30
-
observed UNKNOWN exit 1 Evidence gap ×1 v0.36.0 os=linux · runtime=go@1.26 sha256:23ccd0c7b557…FAIL: expected 168h for 1w, got 0s (err: time: unknown unit <str> in duration <str>) · 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.36.0 os=linux · runtime=go@1.26 sha256:2470d64a481a…# example.com/sample/test · test/contract.go:<n>:<n>: dur.UnmarshalText undefined (type caddy.Duration has no field or method UnmarshalText)go · 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.36.0 os=linux · runtime=go@1.26 sha256:31bc65941ca5…# example.com/sample/test · test/contract.go:<n>:<n>: dur.String undefined (type caddy.Duration has no field or method String) …go · 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 PROJECT_COMPILE exit 1 ×1 v0.36.0 os=linux · runtime=go@1.26 sha256:558314b686cc…<path> undefined: certmagic.ACMETLS1Protocolgo/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31
-
observed PROJECT_COMPILE exit 1 ECDSA256 ×1 v0.36.0 os=linux · runtime=go@1.26 sha256:de7c2e92122a…<path> undefined: certmagic.ECDSA256 · <path> undefined: certmagic.ECDSA384go/compiler · compiler-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31
-
observed PROJECT_TEST exit 1 ×1 v0.36.0 os=linux · runtime=go@1.26 sha256:7e9d088c5c85…--- FAIL: TestNew_DefaultFields (0.00s) · contract_test.go:<n>: expected default CertSelection to be non-nil …go/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31
Showing the 12 most-reported of 17 recorded failure clusters. The rest are single reports.