Rust advisories / crate
Security history · unsafe-libyaml · data from Oct 24, 2026
Is unsafe-libyaml safe to use? Its security history
VerdictUnmaintained. RustSec marked unsafe-libyaml unmaintained (RUSTSEC-2024-0449), so new security bugs will not be fixed.
2advisories on record
0vulnerabilities
1unmaintained notices
0.2.10newest fixed version
Every advisory, newest first
- UnmaintainedRUSTSEC-2024-0449 · 2024-03-25unsafe-libyaml is unmaintained
- UnsoundRUSTSEC-2023-0075 · 2023-12-20Unaligned write of u64 on 32-bit and 16-bit platforms
Check your version
Run cargo tree -i unsafe-libyaml to see which version you build and why, or paste your Cargo.lock into the Cargo.toml checker to match every advisory against your exact versions.
Download trends, dependents and alternatives: unsafe-libyaml crate data.
RustSec advisories (CC0-1.0) and GitHub-reviewed advisories via OSV's crates.io export, downloaded Oct 24, 2026.
Up next
Before you depend on itunsafe-libyaml crate dataReal downloads, dependents and alternatives.Read it next →Did this answer your question?