1.0.7 (current)
From google/supply-chain copy of chromium. Audited without comment by Ying Hsu.
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)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
The current version of scratch is 1.0.7.
1.0.3 (older version)
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.
- safe-to-run
-
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
- 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 impliescrypto-safe, but does not require expert review in order to audit for.- 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 scratch is 1.0.7.
1.0.1 (older version) 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) 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.
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 scratch. Alternatively, you can download the tarball of scratch v1.0.7 or view the source online.
Packaged for Guix (crates-io)