CodeSampleX

Recordsgolanggithub.com/letsencrypt/pebble/v2v2.10.0

Change the conditions
Fixed
OSdebian glibc
Filter Runtimego 1.26 Package versionv2.10.0 Symbolwhole package Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

github.com/letsencrypt/pebble/v2 @v2.10.0debian glibc · x64 · go 1.26 · go · go

package-level total, not an API

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
4 / 4
Contract verifications
1 / 1
Usage records
4
Independent reporting peers
1
Last recorded
2026-10-19

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Unknown 2 · Steady 2

First observed break

v2.10.0

linux · go@1.26

1 FAIL · stage: PROJECT_RESOLVE · fingerprint: sha256:0abf71f153e54969e6f7ffedab0df5bdba986c13e8ff60a85ea0f66eed2742fa

Library Version Health Measured there Projects
github.com/go-jose/go-jose/v4 v4.1.3 UNKNOWN No linked outcome measured nothing measured 3 project-days
github.com/miekg/dns v1.1.62 UNKNOWN No linked outcome measured nothing measured 1 project-day
github.com/letsencrypt/challtestsrv v1.4.2 PASS All observations passed builds observed 3 project-days
github.com/miekg/dns v1.1.72 PASS All observations passed contract passed 2 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.

Recent failure clusters