GHSA-GFXP-F68G-8X78 LibYML: `libyml::string::yaml_string_extend` is unsound and unmaintained

In version 0.0.4, libyml::string::yamlstringextend 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. Recommende...

LibYML: `libyml::string::yaml_string_extend` is unsound and unmaintained

In version 0.0.4, libyml::string::yamlstringextend 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. Recommende...

RUSTSEC-2025-0067 `libyml::string::yaml_string_extend` is unsound and unmaintained

In version 0.0.4, libyml::string::yamlstringextend 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. Recommende...

`libyml::string::yaml_string_extend` is unsound and unmaintained

In version 0.0.4, libyml::string::yamlstringextend 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. Recommende...

RUSTSEC-2024-0449 unsafe-libyaml is unmaintained

The repository 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 serdeyaml itself deprecated and by forks...

a0 (>=0.0.1, <=0.0.4), a3s-use-core (>=0.2.2, <=0.2.10) +1769 more potentially affected by unknown CVE via unsafe-libyaml (0.2.11)

unsafe-libyaml CARGO version 0.2.11 is affected by a known vulnerability. The following packages have a transitive dependency on unsafe-libyaml and may be impacted: - a0 =0.0.1, =0.2.2, =0.0.1-alpha.4, =0.0.1-beta.4, =0.1.0, =0.10.0-dev0, =0.1.0, =0.1.0, =0.0.6, =0.0.1, =0.0.2, =0.0.2, =0.1.0,...

unsafe-libyaml is unmaintained

The repository 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 serdeyaml itself deprecated and by forks...

PT-2024-42043

The repository 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...

GHSA-R24F-HG58-VFRW unsafe-libyaml unaligned write of u64 on 32-bit and 16-bit platforms

Affected versions allocate memory using the alignment of usize and write data to it of type u64, without using core::ptr::writeunaligned. In platforms with sub-64bit alignment for usize including wasm32 and x86 these writes are insufficiently aligned some of the time. If using an ordinary optimiz...

unsafe-libyaml unaligned write of u64 on 32-bit and 16-bit platforms

Affected versions allocate memory using the alignment of usize and write data to it of type u64, without using core::ptr::writeunaligned. In platforms with sub-64bit alignment for usize including wasm32 and x86 these writes are insufficiently aligned some of the time. If using an ordinary optimiz...