Lib.rs

› SmallVec › Reviews

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.5.

1.11.2 (older version) unknown

From kornelski/crev-proofs copy of salsa.debian.org.

Only in debcargo (unstable). Changelog:

  • Team upload.
  • Package smallvec 1.11.2 from crates.io using debcargo 2.6.1
  • Add patch to fix tests on 32-bit.

1.11.0 — diff review from 1.8.0 only (older version) safe-to-deploy

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_uncheckeds look ok.

Most of the rest of the changes are adding some new unstable features which aren't enabled by default.

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…

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

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 implies crypto-safe, but does not require expert review in order to audit for.

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

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.5.

0.6.10 (older version) Rating: Negative 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) Rating: Neutral Thoroughness: Low Understanding: Low

by dpc on 2018-12-20

Show review…

Quite a bit of unsafe. It seems to me this crate could use some fuzzing.

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 smallvec. Alternatively, you can download the tarball of smallvec v2.0.0-alpha.5 or view the source online.