4.5.4 (older version)
From google/supply-chain copy of chromium. Audited without comment by Ying Hsu.
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 clap_derive is 4.5.24.
4.5.4 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
4.1.14 — diff review from 4.0.21 only (older version)
From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.
4.0.18 — diff review from 3.2.18 only (older version)
From google/supply-chain copy of chromium. Audited without comment by Dennis Kempin.
3.2.18 (older version)
From google/supply-chain copy of chromium. Audited without comment by ChromeOS.
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.- 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 clap_derive is 4.5.24.
4.5.0 (older version) Thoroughness: High Understanding: High
by weiznich on 2024-02-29
Update from 4.4.7 to 4.5.0 Minor dependency bump
Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories. There is absolutely no guarantee that the repository URL declared by the crate belongs to the crate, or that the code in the repository is the code inside the published tarball.
To review the actual code of the crate, it's best to use cargo crev open clap_derive. Alternatively, you can download the tarball of clap_derive v4.5.24 or view the source online.
Packaged for Guix (crates-io)