Recordsgolanggithub.com/spiffe/go-spiffe/v2v2.6.0
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
Showing the environments with the most evidence.
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Environment detail
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| go 1.26 · Go · go · linux glibc · docker
Observations: PROJECT_LOAD 1✓ · PROJECT_TEST 1✓ — Usage: USED 2✓ — Verified: CONTRACT 5✓
|
LOW | 2 +2 | 5 | 100% | 1 · 1✓ | 2026-10-14 |
| go 1.26 · Go · go · linux glibc
Observations: PROJECT_PROCESS 6✓ — Usage: USED 10✓ — Verified: UNKNOWN 0✓ 1✕
|
LOW | 6 +10 | 1 | 86% | 1 | 2026-10-14 |
Recent failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×1 v2.6.0 os=linux · runtime=go@1.26 github.com/spiffe/go-spiffe/v2/bundle/x509bundle.FromX509Authorities sha256:96affe4e5cc0…expected 2 unique authorities, got 3 · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-14 · Last seen: 2026-10-14Diagnostic re-verification candidate
Symbols
- github.com/spiffe/go-spiffe/v2/spiffeid.FromSegments 1 1 of 1 runs passed
- github.com/spiffe/go-spiffe/v2/bundle/x509bundle.FromX509Authorities 1 1 of 2 runs passed
- github.com/spiffe/go-spiffe/v2/spiffeid.MatchID
- github.com/spiffe/go-spiffe/v2/spiffeid.MatchMemberOf
- github.com/spiffe/go-spiffe/v2/bundle/x509bundle.NewSet 1 1 of 1 runs passed
- github.com/spiffe/go-spiffe/v2/svid/x509svid.ParseRaw
- github.com/spiffe/go-spiffe/v2/spiffeid.RequireTrustDomainFromString
- github.com/spiffe/go-spiffe/v2/spiffeid.TrustDomain
- github.com/spiffe/go-spiffe/v2/spiffeid.TrustDomainFromString 1 1 of 2 runs passed
- github.com/spiffe/go-spiffe/v2/svid/x509svid.Verify
- github.com/spiffe/go-spiffe/v2/svid/x509svid.WithTime
Published samples
- github.com/spiffe/go-spiffe/v2 v2.6.0 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-10-14