CodeSampleX

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

Change the conditions
Fixed
Package versionv0.3.15 libcmusl
Filter OSalpine musl Runtimego 1.26 Symbolwhole package Architecturex64 Package managergo Execution contextgo Clear filters

Current conditions

github.com/googleapis/enterprise-certificate-proxy @v0.3.15alpine musl · x64 · go 1.26 · go · go

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-08-31

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

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.

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