These reviews are from cargo-vet. To add your review, set up cargo-vet
and submit your URL to its registry.
0.4.5 (current)
From EmbarkStudios/rust-ecosystem. By Embark.
No unsafe usage or ambient capabilities
0.4.5 (current)
From kornelski/crev-proofs copy of salsa.debian.org.
Packaged for Debian (stable). Changelog:
- Team upload.
- Package yaml-rust 0.4.5 from crates.io using debcargo 2.4.4-alpha.0
0.4.5 (current)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
- safe-to-deploy (implies safe-to-run)
-
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
- safe-to-run
-
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
- unknown
-
May have been packaged automatically without a review
This review is from Crev, a distributed system for code reviews. To add your review, set up cargo-crev
.
The current version of yaml-rust is 0.4.5.
0.4.1 (older version) Thoroughness: None Understanding: None
by dpc on 2019-07-02
-
Issue: Medium (RUSTSEC-2018-0006)
Lib.rs has been able to verify that all files in the crate's tarball, except Cargo.lock
,
are in the crate's repository with a git tag matching the version. 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 yaml-rust
. Alternatively, you can download the tarball of yaml-rust v0.4.5 or view the source online.
The maintainer seems unreachable.
Many issues and pull requests have been submitted over the years without any response.
Alternatives
Consider switching to the actively maintained
yaml-rust2
fork of the original project: