Is yaml/go-yaml the successor of go-yaml/yaml?
go-yaml-maintained · status observed
Data verified at: 2026-11-11T22:01:34.776Z (UTC)
Conclusion status
No confirmed conclusion exists for this pair. The evidence below is presented for
transparency; a relationship conclusion requires a human review that has not happened,
or a previous decision no longer matches the current evidence.
No directional succession or fork claim was found; the current evidence does not establish the researched relationship.
Seed context: 2026-09-16 curated succession candidate; NOT APPROVED. Original explicitly unmaintained; YAML organization states it took over ongoing maintenance after discussion with author. Evidence: https://github.com/yaml/go-yaml
Observed repository facts
As of the last verified collection. These are facts about the snapshots, not
activity verdicts — a low number is not a claim that a project is inactive.
Versions & deployment facts
Official release and package declarations, compared independently of the relationship verdict.
These are not installation tests or a migration guarantee. Missing declarations mean unknown.
yaml/go-yaml
Release-pinned deployment declarations
Release commit · v4.0.0 · complete
Commit: f2f9563503f11b7a60da0c532175dcc693ce8d5a
Collection endpoint (may change) · Observed 2026-11-04T23:01:23.202Z
Response SHA-256: 3f56fc7925a86d4100d8a590fac91301703d2982a187f4e33370924b5788a8f8
Release tree · v4.0.0 · complete
Commit: f2f9563503f11b7a60da0c532175dcc693ce8d5a
Collection endpoint (may change) · Observed 2026-11-04T23:01:23.202Z
File search coverage: selected_manifest_names. Only selected manifest filenames were searched; fixtures and vendored dependency directories are excluded. Unlisted declarations remain unknown.
Response SHA-256: 88fb286f68deee4802fe9331cc9885c4b79e7a1150e013a6c23a1a3af3deec5a
GitHub release · v4.0.0 · not_modified
Official source
GitHub latest published non-prerelease (not a semantic-version ranking). Verified: 2026-11-15T04:01:13.931Z (UTC).
Listed release assets only. Asset names do not prove platform support or successful execution.
- Runtime declarations
Not declared / unknown
- Operating systems
Not declared / unknown
- CPU architectures
Not declared / unknown
- C libraries
Not declared / unknown
Direct dependency declarations
Not declared / unknown
Published artifacts (0)
Provenance
Parser: software-1
First observed: 2026-11-04T22:01:41.641Z (UTC)
Last checked: 2026-11-15T04:01:13.931Z (UTC)
Source response SHA-256: 059a36459a4e446b8e5d10eb0316e0f2bb88f7f5c30090e87bdbb29fa6fd8194
go-yaml/yaml
Release-pinned deployment declarations
Unknown: no release-pinned files have been collected. The default branch is not substituted.
GitHub release · Unknown version · stale evidence
Latest collection: unavailable. No verified release declaration is available. This does not mean the project has no releases or platform support.
Official source
Timeline
“Event time” is an upstream timestamp when the source provides one; “first observed” is when
this project saw it. They are deliberately separate columns.
Decision and dispute history
Review decisions are recorded privately with reasons that stay internal; this
public history shows what happened and when, not why.
To question this report, use the feedback form,
select “data error”, and include pair ID go-yaml-maintained.
Feedback is reviewed privately and does not change a report automatically.
Snapshot taken at 2026-11-15T10:01:58.857Z (UTC).