unsafe-libyaml is unmaintained
Collected exploitation and prediction evidence
Risk source coverageCISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.
No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.
osv · RUSTSEC-2024-0449
PublishedThe [repository](https://github.com/dtolnay/unsafe-libyaml) was archived by its owner on 2024-03-25 and is read-only. The last release is 0.2.11 (March 2024). `unsafe-libyaml` is a machine translation of libyaml's C code into unsafe Rust (c2rust). Bugs found in it will not be fixed upstream. It is used by `serde_yaml` (itself deprecated) and by forks such as `serde_yaml_ng`. ## Alternatives Consider a YAML parser written in safe Rust, for example: - [saphyr](https://crates.io/crates/saphyr) ([serde-saphyr](https://crates.io/crates/serde-saphyr) for serde users) - [noyalib](https://crates.io/crates/noyalib)
- Source published
- 25 Mar 2024 12:00:00 UTC
- Source modified
- 12 Oct 2026 11:45:02 UTC
- Observed here
- 24 Oct 2026 13:19:54 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.