CodeSampleX

Recordsgolanggithub.com/caddyserver/certmagicv0.25.3github.com/caddyserver/certmagic.Cache

Change the conditions
Fixed
OSdebian glibc Symbolgithub.com/caddyserver/certmagic.Cache
Filter Runtimego 1.26 Package versionv0.25.3 Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

github.com/caddyserver/certmagic.Cache @v0.25.3debian glibc · 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
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 6 · Steady 7

First observed break

v0.25.3

linux

3 FAIL · stage: UNKNOWN · fingerprint: sha256:91ad26545eb1f3df29e3d9731c4244f3cf919942db2aa314b6b8d67ca84b47ef

View exact conditions View failure cluster
Library Version Health Measured there Projects
go.uber.org/zap v1.27.1 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
go.uber.org/zap v1.28.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
golang.org/x/crypto v0.50.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
golang.org/x/crypto v0.52.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
golang.org/x/net v0.53.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
golang.org/x/net v0.55.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
github.com/caddyserver/zerossl v0.1.5 PASS All observations passed contract passed 4 project-days
github.com/klauspost/cpuid/v2 v2.3.0 PASS All observations passed contract passed 4 project-days
github.com/libdns/libdns v1.1.1 PASS All observations passed contract passed 4 project-days
github.com/mholt/acmez/v3 v3.1.6 PASS All observations passed contract passed 4 project-days
github.com/miekg/dns v1.1.72 PASS All observations passed contract passed 4 project-days
github.com/zeebo/blake3 v0.2.4 PASS All observations passed contract passed 4 project-days
go.uber.org/zap/exp v0.3.0 PASS All observations passed 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.

Libraryv0.25.3v0.23.0
go.uber.org/zap v1.28.0 v1.27.1
golang.org/x/crypto v0.52.0 v0.50.0
golang.org/x/net v0.55.0 v0.53.0
github.com/caddyserver/zerossl v0.1.5 v0.1.5
github.com/klauspost/cpuid/v2 v2.3.0 v2.3.0
github.com/libdns/libdns v1.1.1 v1.1.1
github.com/mholt/acmez/v3 v3.1.6 v3.1.6
github.com/miekg/dns v1.1.72 v1.1.72
github.com/zeebo/blake3 v0.2.4 v0.2.4
go.uber.org/zap/exp v0.3.0 v0.3.0

Moved: 3 · unchanged at every release: 7

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