Recordsgolanggo.yaml.in/yaml/v3v3.0.4
Change the conditions
Current conditions
go.yaml.in/yaml/v3 @v3.0.4alpine musl · 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
- 2 / 2
- Contract verifications
- 1 / 1
- Usage records
- 3
- Independent reporting peers
- 1
- Last recorded
- 2026-09-08
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v3.0.4
linux · go@1.26
1 FAIL
· stage: PROJECT_TEST
· fingerprint: sha256:dda800f87ad336ceb3470d5a3d62662cd8dbf7f91f2b28e427be0c6fc592b4b7
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| gopkg.in/check.v1 | v1.0.0-20190902080502-41f04d3bba15 | CANDIDATE Correlated change; unproven combination | nothing measured | 4 project-days |
| gopkg.in/check.v1 | v1.0.0-20201130134442-10cb98267c6c | 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.
| Library | v3.0.4 | v3.0.3 |
|---|---|---|
| gopkg.in/check.v1 | v1.0.0-20201130134442-10cb98267c6c | v0.0.0-20161208181325-20d25e280405 |
Moved: 1 · 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
-
observed PROJECT_TEST exit 1 ×1 v3.0.4 os=linux · runtime=go@1.26 sha256:dda800f87ad3…--- FAIL: TestPathAndMethodMatchers (0.00s) · panic: interface conversion: interface {} is nil, not *caddy.Replacer [recovered, repanicked] …go/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29
-
observed UNKNOWN exit 1 Evidence gap ×1 v3.0.4 os=linux · runtime=go@1.26 sha256:f3a5a3011077…panic: interface conversion: interface {} is nil, not *caddy.Replacer · goroutine 1 [running]: …go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29Diagnostic re-verification candidate
-
observed PROJECT_RESOLVE exit 1 ×1 v3.0.4 os=linux · runtime=go@1.26 sha256:5008c43f49e4…<path>:<n>:<n>: missing go.sum entry for module providing package github.com/skip2/go-qrcode (imported by github.com/slackhq/nebula/cmd/nebula-cert); to add: …go/module · resolve-diagnostic · outer go listEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31
-
observed UNKNOWN exit 1 Evidence gap ×1 v3.0.4 os=linux · runtime=go@1.26 sha256:0ab0b4fa727d…FAIL: Sign should reject subnet outside CA scope · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v3.0.4 os=linux · runtime=go@1.26 sha256:b922aed4721c…VerifyPrivateKey failed: invalid private key · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate