* (all versions)
From EmbarkStudios/rust-ecosystem. By Embark on 2021-01-01.
This review is from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
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
Implied by other criteria
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
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 ash-molten. Alternatively, you can download the tarball of ash-molten v0.20.0+1.2.11 or view the source online.
Maintained by the Ark team at Embark.
Tiny crate that with sane unsafe usage and no ambient runtime capabilities in the Rust code.
Note it has a complex build setup where it downloads over HTTP a specific a pinned pre-built static binary for the C++ MoltenVK library.
This audit does NOT cover the very large C++ MoltenVK codebase.