Lib.rs

› Adler32 › Reviews

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

1.2.0 (current) Rating: Strong Positive Thoroughness: High Understanding: High

by remram44 on 2021-11-14

I wrote this. No unsafe code, no dependencies.

1.2.0 (current) Rating: Positive Thoroughness: None Understanding: None

Approved without comment by inflation on 2021-11-08

The current version of Adler32 is 1.2.0.

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

by remram44 on 2021-11-14

Show review…

I wrote this. No unsafe code, no dependencies.

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

Approved without comment by kornelski on 2019-10-11

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

Approved without comment by dpc on 2019-10-14

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

1.2.0 (current) safe-to-run

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

Packaged for Debian (stable). Changelog:

  • Team upload.
  • Package adler32 1.2.0 from crates.io using debcargo 2.4.3
  • temporarily drop rustc-dep-of-std feature to avoid the NEW queue
  • drop criterion-based benchmarking code

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…

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