Recordsgolanggithub.com/googleapis/enterprise-certificate-proxyv0.3.11github.com/googleapis/enterprise-certificate-proxy/client/util.GetDefaultConfigFilePath
Change the conditions
Current conditions
github.com/googleapis/enterprise-certificate-proxy/client/util.GetDefaultConfigFilePath @v0.3.11ubuntu glibc · x64 · go 1.26 · go 1
3 of 3 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 3 / 3
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-10-11
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.3.11
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:47a0d2b2ba4d9ffb4e6e4bf9894d74414f7743f110eb66256d73dce0167dadfd
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/crypto | v0.47.0 | CANDIDATE Correlated change; unproven combination | contract passed | 25 project-days |
| golang.org/x/sys | v0.40.0 | CANDIDATE Correlated change; unproven combination | contract passed | 24 project-days |
| golang.org/x/sys | v0.47.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| github.com/google/go-pkcs11 | v0.3.0 | UNKNOWN No linked outcome measured | nothing measured | 5 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.
| Library | v0.3.20 | v0.3.17 | v0.3.15 | v0.3.14 | v0.3.11 | v0.3.2 |
|---|---|---|---|---|---|---|
| golang.org/x/crypto | v0.55.0 | v0.55.0 | v0.52.0 | v0.47.0 | v0.47.0 | v0.22.0 |
| golang.org/x/sys | v0.47.0 | v0.47.0 | v0.45.0 | v0.40.0 | v0.47.0 | v0.31.0 |
| github.com/google/go-pkcs11 | v0.3.0 | v0.3.0 | — | v0.3.0 | v0.3.0 | — |
Moved: 2 · unchanged at every release: 1
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
-
observed UNKNOWN exit 1 Evidence gap ×1 v0.3.11 os=linux · runtime=go@1.26 sha256:47a0d2b2ba4d…Assertion failed: key.Sign must succeed: gob: name not registered for interface: <str> · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-11 · Last seen: 2026-10-11Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v0.3.11 os=linux · runtime=go@1.26 sha256:d64eea365a80…# sample/test · test/contract.go:<n>:<n>: args.Opts.HashFunc undefined (type crypto.DecrypterOpts has no field or method HashFunc) …go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-11 · Last seen: 2026-10-11Diagnostic re-verification candidate