Code review of the LibYML crate // Lib.rs

RUSTSEC-2025-0067 (unsound) on 2025-09-11: libyml::string::yaml_string_extend is unsound and unmaintained

In version 0.0.4, libyml::string::yaml_string_extend was revised resulting in undefined behaviour, which is unsound.

The GitHub project for libyml was archived after unsoundness issues were raised.

If you rely on this crate, it is highly recommended switching to a maintained alternative.

Recommended alternatives

libyaml-safer
unsafe-libyaml-norway - Maintained fork of unsafe-libyaml

GHSA-gfxp-f68g-8x78

This review is from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.

0.0.5 (current) unknown

From kornelski/crev-proofs copy of salsa.debian.org.

Only in debcargo (unstable). Changelog:

Team upload.
Disable tests using unpublished internal crate
Package libyml 0.0.5 from crates.io using debcargo 2.7.5

cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.

unknown

May have been packaged automatically without a review

Lib.rs has been able to verify that all files in the crate's tarball, except Cargo.lock, are in the crate's repository. Please note that this check is still in beta, and absence of this confirmation does not mean that the files don't match.

Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories, so there is a possibility that published crates have a misleading repository URL, or contain different code from the code in the repository.

To review the actual code of the crate, it's best to use cargo crev open libyml. Alternatively, you can download the tarball of libyml v0.0.5 or view the source online.