1.2.7 (older version)
From mozilla/supply-chain copy of mozilla/cargo-vet. By Alex Franchuk.
This review is from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.
The current version of base64-stream is 4.0.0.
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
- safe-to-deploy (implies safe-to-run)
-
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
- safe-to-run
Implied by other criteria
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
Lib.rs has been able to verify that all files in the crate's tarball are in the crate's repository. 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 base64-stream. Alternatively, you can download the tarball of base64-stream v4.0.0 or view the source online.
The crate is fairly straightforward. There are a few unsafe blocks to elide bounds-checking when copying data, but I have manually verified that the unsafe blocks will always have lengths within bounds of source and destination pointers. Some
debug_assert!s document and check these invariants as well (though there could be more).