Recordsgolanggopkg.in/yaml.v2v2.4.0
Change the conditions
Current conditions
gopkg.in/yaml.v2 @v2.4.0alpine 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-07
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 1 ·
Changed 3 ·
Steady 0
First observed break
v2.4.0
linux · node@22.23 · moduleSystem=cjs · executionContext=node
6 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| gopkg.in/check.v1 | v0.0.0-20161208181325-20d25e280405 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| gopkg.in/check.v1 | v1.0.0-20190902080502-41f04d3bba15 | CANDIDATE Correlated change; unproven combination | nothing measured | 2 project-days |
| gopkg.in/check.v1 | v1.0.0-20201130134442-10cb98267c6c | CANDIDATE Correlated change; unproven combination | contract passed | 3 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 | v2.4.0 | v2.3.0 | v2.2.2 | v2.2.1 |
|---|---|---|---|---|
| gopkg.in/check.v1 | v1.0.0-20190902080502-41f04d3bba15 | v0.0.0-20161208181325-20d25e280405 | v1.0.0-20190902080502-41f04d3bba15 | 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 UNKNOWN exit 1 Evidence gap ×3 v2.3.0 → v2.4.0 os=linux sha256:9922ca80f240…go: <path> already existsgo · unclassified-diagnostic · outer go mod · gap stage-unknownEvidence quality: complete · Environment variants: 2 · First recorded: 2026-08-29 · Last seen: 2026-09-05Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 1 ×1 v2.4.0 os=linux · runtime=go@1.26 sha256:bed685930873…<path> undefined: config.RoundTripperFromConfig · <path> undefined: config.RoundTripperFromConfiggo/compiler · compiler-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31
-
observed PROJECT_TEST exit 1 ×1 v2.4.0 os=linux · runtime=go@1.26 sha256:93a9cf8f2e92…--- FAIL: TestSecretSerializationMasking (0.00s) · FAIL example.com/csx-prometheus-common-config-test 0.012sgo/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31
-
observed PROJECT_COMPILE exit 1 ×1 v2.4.0 os=linux · runtime=go@1.26 sha256:0a43185f3587…<path> undefined: config.NewConfiggo/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31
-
observed UNKNOWN exit 1 Evidence gap ×1 v2.4.0 os=linux · runtime=go@1.26 sha256:77e59c8edcd8…panic: runtime error: slice bounds out of range [:<n>] with capacity 0 · goroutine 1 [running]: · github.com/slackhq/nebula/header.Encode(...) · <path>:<n>go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-02 · Last seen: 2026-09-02Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v2.4.0 os=linux · runtime=go@1.26 sha256:58785aaebb01…FAIL: field mismatch after encode/parse: parsed=ver=1 type=message subtype=none reserved=0x0 <token> <token>, orig=ver=1 type=message subtype=none …go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-03 · Last seen: 2026-09-03Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v2.4.0 os=linux · runtime=go@1.26 sha256:b415c4f731aa…FAIL: Test SubTypeName mismatch: got <str>, expected <str> · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-03 · Last seen: 2026-09-03Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v2.4.0 os=linux · runtime=go@1.26 sha256:c3643b16b6fb…FAIL: Handshake SubTypeName mismatch: got <str>, expected <str> · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-03 · Last seen: 2026-09-03Diagnostic re-verification candidate
-
observed PROJECT_RESOLVE exit 1 ×1 v2.4.0 os=linux · runtime=go@1.26 sha256:fec6afe05e5c…<path>:<n>:<n>: missing go.sum entry for module providing package github.com/mwitkow/go-conntrack (imported by github.com/prometheus/common/config); to add: …go/module · resolve-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-04 · Last seen: 2026-09-04
-
observed UNKNOWN exit 1 Evidence gap ×1 v2.4.0 os=linux · runtime=go@1.26 sha256:0cc5633d6f9a…Contract test failed: expected JSON output to mask secret with <str>, got <str> · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-04 · Last seen: 2026-09-04Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v2.4.0 os=linux · runtime=go@1.26 sha256:8429622b4944…package example.com/mergoerrdifferentargumentstypes/test is not a main packagego · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-06 · Last seen: 2026-09-06Diagnostic re-verification candidate