0.2.1 (current) Thoroughness: High Understanding: Medium
by fishi0x01 on 2020-03-20
This review is from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.
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 docker_extract. Alternatively, you can download the tarball of docker_extract v0.2.1 or view the source online.
I am the maintainer of docker_extract. docker_extract is a rather simple crate which heavily relies on the safety of the tar crate dependency.
It looks to me like the tar crate is very conscious about security. By design, they do not allow '..' sequences in paths in order to avoid path traversals issues. I do not consider myself an expert on source code auditing, so I give this review only a medium understanding.