1.3.0 — diff review from 1.1.0 only (current)
From google/supply-chain copy of chromium. Audited without comment by Daniel Verkamp.
These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
1.3.0 (current)
From google/supply-chain copy of google/rust-crate-audits. By Manish Goregaokar, Augie Fackler.
1.3.0 — diff review from 1.1.0 only (current)
From mozilla/supply-chain copy of hg. Audited without comment by Max Inden.
1.3.0 (current)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (unstable). Changelog:
- Team upload.
- Package shlex 1.3.0 from crates.io using debcargo 2.6.1
- Fixes https://rustsec.org/advisories/RUSTSEC-2024-0006.html
1.3.0 (current)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
The current version of Shlex is 1.3.0.
1.1.0 (older version)
From google/supply-chain copy of chromium. Audited without comment by George Burgess IV.
1.1.0 (older version)
From bytecodealliance/wasmtime. By Alex Crichton.
Only minor unsafe code blocks which look valid and otherwise does what it says on the tin.
1.0.0 (older version)
From google/supply-chain copy of chromium. Audited without comment by Android Legacy.
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
- 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.- safe-to-run
-
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
- ub-risk-3 (implies ub-risk-4)
-
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
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 shlex. Alternatively, you can download the tarball of shlex v1.3.0 or view the source online.
Reviewed in CL 600742555 This crate appears safe, but it's not clear that the unchecked utf8 stuff is necessary given the use case, and it relies on undocumented invariants from the bytes iterator code. Would be nice to have these properties documented and fuzz tested.