23.0.1 (current)
From mozilla/supply-chain copy of hg. Audited without comment by Erich Gubler.
These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
The current version of wgpu-hal is 23.0.1.
22.0.0 (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Jim Blandy.
0.20.0 (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Jim Blandy, Nicolas Silva, Erich Gubler, Teodor Tanasoaia.
0.18.0 (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Nicolas Silva.
0.13.0 (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Jim Blandy.
0.12.0 (older version)
From mozilla/supply-chain copy of hg. By Dzmitry Malyshau.
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 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 wgpu-hal. Alternatively, you can download the tarball of wgpu-hal v23.0.1 or view the source online.
This crate, up through the indicated version, was written or reviewed by Dzmitry Malyshau while he was a Mozilla employee. Dzmitry left Mozilla at the beginning of February 2022. This audit statement was collected by Jim Blandy, a Mozilla employee, over email in July 2022: Dzmitry was shown, and agreed to, the 'safe-to-deploy' text.