0.38.0+1.3.281 (current)
From google/supply-chain copy of chromium. By Chia-I Wu.
These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
0.38.0+1.3.281 — diff review from 0.37.3+1.3.251 only (current)
From mozilla/supply-chain copy of hg. By Erich Gubler.
There are many sweeping changes to code generation that make this review intimidating, at first. However, I have audited all hand-written code, and vetted changes to the code generator (with some auditing of generated output to ensure correspondence to my mental model). Vulkan is an inherently unsafe API, but this crate makes many of the preparatory steps for calling Vulkan APIs safer and easier to use.
The current version of Ash is 0.38.0+1.3.281.
0.37.3+1.3.251 — diff review from 0.37.2+1.3.238 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Teodor Tanasoaia.
0.37.3+1.3.251 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-graphics)
0.37.2+1.3.238 — diff review from 0.37.1+1.3.235 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Nicolas Silva.
0.37.1+1.3.235 — diff review from 0.37.0+1.3.209 only (older version)
From mozilla/supply-chain copy of hg. By Jim Blandy.
Nicolas Silva, Jim Blandy, and Teodor Tanasoaia audited ash master branch commits from e43e9c0c to 6bd82768 inclusive.
0.37.0+1.3.209 (older version)
From google/supply-chain copy of fuchsia. By David Koloski.
Reviewed on https://fxrev.dev/694269
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
- safe-to-run
-
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
- does-not-implement-crypto (implies crypto-safe)
-
Inspection reveals that the crate in question does not attempt to implement any cryptographic algorithms on its own.
Note that certification of this does not require an expert on all forms of cryptography: it's expected for crates we import to be "good enough" citizens, so they'll at least be forthcoming if they try to implement something cryptographic. When in doubt, please ask an expert.
- crypto-safe
Implied by other criteria
All crypto algorithms in this crate have been reviewed by a relevant expert.
Note: If a crate does not implement crypto, use
does-not-implement-crypto, which impliescrypto-safe, but does not require expert review in order to audit for.- ub-risk-4
-
Extreme unsoundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-4
- safe-to-deploy (implies safe-to-run)
-
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
- unknown
-
May have been packaged automatically without a review
Lib.rs has been able to verify that all files in the crate's tarball 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 ash. Alternatively, you can download the tarball of ash v0.38.0+1.3.281 or view the source online.
Vulkan binding mostly generated from vk.xml