1.2.0 (current)
From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.
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 extend is 1.2.0.
1.1.2 (older version)
From mozilla/supply-chain copy of hg. By bendk.
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…
This review is from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.
The current version of extend is 1.2.0.
0.1.1 (older version) Thoroughness: Low Understanding: Low
Approved without comment by kornelski on 2020-05-01
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 extend. Alternatively, you can download the tarball of extend v1.2.0 or view the source online.
Inspected the crate and noted that the impl block comes directly from the proc-macro input. If no new code can be added by this crate, I don't think there can be any issues.