Recordsgolanggopkg.in/yaml.v2v2.4.0
Change the conditions
Current conditions
gopkg.in/yaml.v2 @v2.4.0ubuntu glibc · x64 · node 22 · go 1 · node
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.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-29
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 · executionContext=node · moduleSystem=cjs
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 PROJECT_PROCESS ERR_ASSERTION Evidence gap ×6 v2.4.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-26 · Last seen: 2026-08-29Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_MODULE_NOT_FOUND Evidence gap ×4 v2.4.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:88af852f99a8…node:internal/modules/package_json_reader:<n> · throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null); · ^ …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-30Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×4 v2.4.0 executionContext=node · os=linux · runtime=node@22.23 sha256:9be950af9140…Traceback (most recent call last): · File <str>, line 1, in <module> · ModuleNotFoundError: No module named <str>python3 · unclassified-diagnostic · outer python3 · gap stage-unknownEvidence quality: complete · Environment variants: 2 · First recorded: 2026-08-30 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×4 v2.4.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:91ad26545eb1…node:internal/modules/cjs/loader:<n> · throw err; · ^ · Error: Cannot find module <str>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30Diagnostic re-verification candidate
-
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 UNKNOWN exit 2 Evidence gap ×3 v2.4.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:fddf8ea09045…Using CPython 3.12.3 interpreter at: <path> · Creating virtual environment at: .venv · error: Failed to create virtual environment …· unclassified-diagnostic · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-30Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×2 v2.4.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:8310a83be884…node:internal/modules/cjs/loader:<n> · const err = new Error(message); · ^ · Error: Cannot find module <str>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-30Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×2 v2.4.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:cc724e2e6a32…<path>:<n> · module.exports = require.addon() · ^ · TypeError: require.addon is not a functionnode · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed PROJECT_PROCESS exit 1 ERR_ASSERTION ×1 v2.4.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:0e3b7c489c9f…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:Evidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29
-
observed PROJECT_PROCESS exit 1 ERR_ASSERTION ×1 v2.4.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:c209875bcbeb…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ …Evidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29
-
observed PROJECT_PROCESS exit 1 ERR_MODULE_NOT_FOUND ×1 v2.4.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:c33691aec18d…node:internal/modules/package_json_reader:<n> · throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null); · ^ …Evidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29
-
observed UNKNOWN exit 1 Evidence gap ×1 v2.4.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:3226ba56e07f…Traceback (most recent call last): · File <str>, line 45, in <module> · File <str>, line 856, in from_path · with open(path, <str>) as fp:· unclassified-diagnostic · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29Diagnostic re-verification candidate
Showing the 12 most-reported of 30 recorded failure clusters. The rest are single reports.