CodeSampleX

Recordsgolanggithub.com/googleapis/enterprise-certificate-proxyv0.3.15

Change the conditions
Fixed
Package versionv0.3.15 libcglibc
Filter OSubuntu glibc Runtimego 1.26 Symbolwhole package Architecturex64 Package managergo 1 Clear filters

Current conditions

github.com/googleapis/enterprise-certificate-proxy @v0.3.15ubuntu glibc · x64 · go 1.26 · go 1

package-level total, not an API

0 of 2 passed

Verified — this network ran a contract at this coordinate.

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

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

v0.3.15

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:f3a5a30110770e510159fdb2eda104f320d4f31f36251c1770da6e4ec58af6d8

View exact conditions View failure cluster
Library Version Health Measured there Projects
golang.org/x/crypto v0.52.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
golang.org/x/sys v0.45.0 CANDIDATE Correlated change; unproven combination 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.

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.3.15v0.3.2
golang.org/x/crypto v0.52.0 v0.22.0
golang.org/x/sys v0.45.0 v0.31.0

Moved: 2 · unchanged at every release: 0

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