Code reviews of the Dirs crate // Lib.rs

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

5.0.1 (current) Rating: Positive Thoroughness: Medium Understanding: High

Approved without comment by kpcyrd on 2023-12-31

The current version of Dirs is 5.0.1.

2.0.2 (older version) Rating: Neutral Thoroughness: None Understanding: None

by Minoru on 2020-06-27

Overwriting my earlier review: this crate is maintained, development moved to https://github.com/dirs-dev

1.0.5 (older version) Rating: Positive Thoroughness: Low Understanding: Medium

Approved without comment by kornelski on 2019-10-11

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

5.0.1 (current) unknown

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

Packaged for Guix (crates-io)

5.0.1 (current) unknown

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

Only in debcargo (unstable). Changelog:

Package dirs 5.0.1 from crates.io using debcargo 2.6.0

The current version of Dirs is 5.0.1.

4.0.0 — diff review from 2.0.2 only (older version) safe-to-deploy

From zcash/rust-ecosystem copy of zcash/zcash. By Jack Grigg.

Some paths change across this upgrade (AFAICT they were bugfixes).

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…

unknown

May have been packaged automatically without a review

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 dirs. Alternatively, you can download the tarball of dirs v5.0.1 or view the source online.