1.13.2 — diff review from 1.11.0 only (older version)
From bytecodealliance/wasmtime. By Alex Crichton.
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 SmallVec is 2.0.0-alpha.7.
1.13.2 — diff review from 1.11.0 only (older version)
From bytecodealliance/wasmtime. By Alex Crichton.
1.13.2 — diff review from 1.11.1 only (older version)
From zcash/rust-ecosystem copy of zcash/librustzcash. Audited without comment by Daira Emma Hopwood.
1.13.2 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (unstable). Changelog:
1.13.1 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
1.11.0 (older version)
From google/supply-chain copy of google/rust-crate-audits. By Manish Goregaokar.
Reviewed in CL 552492992
1.11.0 — diff review from 1.8.0 only (older version)
From bytecodealliance/wasmtime. By Dan Gohman.
The main change is the switch to use NonNull<T>
internally instead of
*mut T
. This seems reasonable, as Vec
also never stores a null pointer,
and in particular the new NonNull::new_unchecked
s look ok.
Most of the rest of the changes are adding some new unstable features which aren't enabled by default.
1.10.0 — diff review from 1.9.0 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.
1.6.1 (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.
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
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
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.
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
These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev
.
The current version of SmallVec is 2.0.0-alpha.7.
0.6.10 (older version) Thoroughness: Low Understanding: Low
by dpc on 2019-11-04
Quite a bit of unsafe, but I've implemented fuzzing for it https://github.com/servo/rust-smallvec/pull/168, so hopefully unsoundness issues won't be a problem anymore.
Issue: High (RUSTSEC-2019-0009)
Issue: High (RUSTSEC-2019-0012)
0.6.10 (older version) Thoroughness: None Understanding: None
by MaulingMonkey on 2019-07-23
Lots of unsafe code, long standing open 'maybe UB' issues that proved to be correct, 3 previous rustsec advisories, no obvious fuzz tests. Use only under duress.
0.6.7 (older version) Thoroughness: Low Understanding: Low
by dpc on 2018-12-20
Quite a bit of unsafe. It seems to me this crate could use some fuzzing.
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 smallvec
. Alternatively, you can download the tarball of smallvec v2.0.0-alpha.7 or view the source online.
Mostly minor updates, the one semi-substantial update looks good.