4.5.32 — diff review from 4.5.31 only (current)
From google/supply-chain copy of chromium. By Lukasz Anforowicz.
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_builder is 4.5.32.
4.5.31 — diff review from 4.5.29 only (older version)
From google/supply-chain copy of chromium. By Daniel Cheng.
No unsafe uses added or changed. Delta consists of miscellaneous fixes and cleanups (e.g. improvements for ValueRange) and a new parser for Saturating.
4.5.29 — diff review from 4.5.27 only (older version)
From google/supply-chain copy of chromium. By Jonathan Hao.
Only changed args_present method a bit and added a value method to flat_map.
4.5.21 — diff review from 4.5.20 only (older version)
From google/supply-chain copy of chromium. Audited without comment by Adrian Taylor.
4.5.20 — diff review from 4.5.18 only (older version)
From google/supply-chain copy of chromium. By Dana Jansens.
No new unsafe
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.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.
- 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-0 (implies ub-risk-1)
-
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
- ub-risk-1 (implies ub-risk-2)
Implied by other criteria
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
- ub-risk-2 (implies ub-risk-3)
Implied by other criteria
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
- ub-risk-3 (implies ub-risk-4)
Implied by other criteria
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
- ub-risk-4
Implied by other criteria
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
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.32.
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
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_builder. Alternatively, you can download the tarball of clap_builder v4.5.32 or view the source online.
Just a new
fn removemethod insrc/error/mod.rs.