Recordsgolanggithub.com/caddyserver/certmagic
Change the conditions
Current conditions
github.com/caddyserver/certmagic.Cache @v0.23.0x64 · go 1.26 · 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
- 7 / 9
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 2
- Last recorded
- 2026-08-28
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
ubuntu glibc · x64 · go 1.26 · go 1
7 of 9 passed
Observed — real project builds reported from this coordinate.
-
alpine musl · x64 · go 1.26 · go · go
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.23.0
linux · node@22.23 · moduleSystem=cjs · executionContext=node
3 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868
| 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.
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.