CodeSampleX

Recordsgolanggithub.com/caddyserver/certmagicv0.23.0

Change the conditions
Fixed
Runtimenode 22 Package versionv0.23.0
Filter OSubuntu glibc Symbolwhole package Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

github.com/caddyserver/certmagic @v0.23.0ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 15 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (22)

Project observations
8 / 8
Contract verifications
0 / 15
Usage records
36
Independent reporting peers
2
Last recorded
2026-08-31
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 11

First observed break

v0.23.0

linux · node@22.23 · moduleSystem=cjs · executionContext=node

3 FAIL · stage: UNKNOWN · fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868

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

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