Recordsgolanggithub.com/caddyserver/certmagicfailure issue
Failure signature
PROJECT_PROCESS Evidence gap ×2
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-26 · Last seen: 2026-08-26
github.com/caddyserver/certmagic.Cache github.com/caddyserver/certmagic.CacheOptions github.com/caddyserver/certmagic.Certificate github.com/caddyserver/certmagic.Config github.com/caddyserver/certmagic.DefaultRenewCheckInterval github.com/caddyserver/certmagic.ED25519 github.com/caddyserver/certmagic.LooksLikeHTTPChallenge github.com/caddyserver/certmagic.MatchWildcard github.com/caddyserver/certmagic.New github.com/caddyserver/certmagic.NewCache github.com/caddyserver/certmagic.NewDefault github.com/caddyserver/certmagic.PEMDecodePrivateKey github.com/caddyserver/certmagic.PEMEncodePrivateKey github.com/caddyserver/certmagic.StandardKeyGenerator github.com/caddyserver/certmagic.StorageKeys github.com/caddyserver/certmagic.SubjectIsIP github.com/caddyserver/certmagic.SubjectIsInternal github.com/caddyserver/certmagic.SubjectQualifiesForCert github.com/caddyserver/certmagic.SubjectQualifiesForPublicCert
Where it was measured
PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- os=linux · runtime=go@1.26 ×2 2026-08-26 → 2026-08-26
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last failing release v0.23.0 → first passing release v0.25.3
What differs across the boundary
- github.com/caddyserver/zerossl v0.1.5 → v0.1.3, v0.1.5 hypothesis
- github.com/klauspost/cpuid/v2 v2.3.0 → v2.2.10, v2.3.0 hypothesis
- github.com/libdns/libdns v1.1.1 → v1.0.0-beta.1, v1.1.1 hypothesis
- github.com/mholt/acmez/v3 v3.1.6 → v3.1.2, v3.1.6 hypothesis
- go.uber.org/zap v1.27.1, v1.28.0 → v1.27.0, v1.27.1 hypothesis
- golang.org/x/crypto v0.50.0, v0.52.0 → v0.50.0 hypothesis
- golang.org/x/net v0.53.0, v0.55.0 → v0.38.0, v0.53.0 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
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: 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.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/caddyserver/certmagic v0.23.0: FileStorage This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWcertmagic.FileStorage MIT-0 · 2026-09-01
- github.com/caddyserver/certmagic v0.23.0: SubjectQualifiesForPublicCert This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgithub.com/caddyserver/certmagic.SubjectQualifiesForPublicCert MIT-0 · 2026-08-28
- github.com/caddyserver/certmagic v0.23.0: SubjectQualifiesForCert This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgithub.com/caddyserver/certmagic.SubjectQualifiesForCert MIT-0 · 2026-08-28