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 such as serde_yaml_ng.
Alternatives
Consider a YAML parser written in safe Rust, for example:
> unsafe-libyaml is unmaintained
| Details | |
| ------------------- | ---------------------------------------------- |
| Status | unmaintained |
| Package | `unsafe-libyaml` |
| Version | `0.2.11` |
| URL | [https://github.com/dtolnay/unsafe-libyaml](https://github.com/dtolnay/unsafe-libyaml) |
| Date | 2024-03-25 |
The [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)
See [advisory page](https://rustsec.org/advisories/RUSTSEC-2024-0449.html) for additional details.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
unsafe-libyaml0.2.11The repository was archived by
its owner on 2024-03-25 and is read-only. The last release is 0.2.11
(March 2024).
unsafe-libyamlis a machine translation of libyaml's C code into unsafeRust (c2rust). Bugs found in it will not be fixed upstream. It is used by
serde_yaml(itself deprecated) and by forks such asserde_yaml_ng.Alternatives
Consider a YAML parser written in safe Rust, for example:
See advisory page for additional details.