Code reviews of the scratch crate // Lib.rs

These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.

1.0.7 (current) unknown

From kornelski/crev-proofs copy of git.savannah.gnu.org.

Packaged for Guix (crates-io)

The current version of scratch is 1.0.7.

1.0.3 (older version) safe-to-run

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

Packaged for Debian (stable). Changelog:

Package scratch 1.0.3 from crates.io using debcargo 2.6.0

cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.

unknown

May have been packaged automatically without a review

safe-to-run

This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…

These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.

The current version of scratch is 1.0.7.

1.0.1 (older version) Rating: Strong Positive Thoroughness: High Understanding: High

by Minoru on 2022-03-23

There were no material changes since 1.0.0, the main code wasn't even touched.

1.0.0 (older version) Rating: Strong Positive Thoroughness: High Understanding: High

by Minoru on 2021-03-11

Show review…

Trivial (but useful!) crate that creates a temporary directory which can be seen by any crate that depends on this one.

There are just 6 lines of actual code here. They read OUT_DIR from environment, and create/remove some directories.

A rogue crate could include this one and use it to stomp on some other crate's scratch space. It's hard for me to see this as a vulnerability, since the user is supposed to trust the code they're running during the build.

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 scratch. Alternatively, you can download the tarball of scratch v1.0.7 or view the source online.