4.5.20 — diff review from 4.5.18 only (current)
From google/supply-chain copy of chromium. By Dana Jansens.
These reviews are from cargo-vet. To add your review, set up cargo-vet
and submit your URL to its registry.
4.5.20 — diff review from 4.5.18 only (current)
From google/supply-chain copy of chromium. By Dana Jansens.
The current version of clap_builder is 4.5.20.
4.5.18 (older version)
From google/supply-chain copy of chromium. Audited without comment by Lukasz Anforowicz.
4.5.9 — diff review from 4.5.8 only (older version)
From google/supply-chain copy of chromium. Audited without comment by Dustin J. Mitchell.
4.5.8 — diff review from 4.5.7 only (older version)
From google/supply-chain copy of chromium. Audited without comment by Adrian Taylor.
4.5.2 (older version)
From google/supply-chain copy of chromium. Audited without comment by Ying Hsu.
4.5.2 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
4.4.8 (older version)
From google/supply-chain copy of chromium. By Dana Jansens.
Reviewed in https://crrev.com/c/5171063
Previously reviewed during security review and the audit is grandparented in.
4.3.0 — diff review from 4.1.14 only (older version)
From divviup/libprio-rs. Audited without comment by Brandon Pitman.
4.1.14 (older version)
From google/supply-chain copy of chromium. By George Burgess IV.
This was a diff audit between clap 4.0.32 sources, and sources in clap_builder
4.1.14. clap_builder is primarily stuff refactored out of clap
.
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
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.
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 implies crypto-safe
, but does not require expert review in order to
audit for.
No unsafe code.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-0
Excellent soundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-1
Negligible unsoundness or average soundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-2
Mild unsoundness or suboptimal soundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-3
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
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
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_builder is 4.5.20.
4.5.1 (older version) Thoroughness: Low Understanding: Medium
by weiznich on 2024-02-29
Update from 4.4.7 to 4.5.1
Dependency updates
More options
New documentation
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 clap_builder
. Alternatively, you can download the tarball of clap_builder v4.5.20 or view the source online.
No new unsafe