Lib.rs

› percent-encoding › Reviews

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

The current version of percent-encoding is 2.3.1.

2.2.0 (older version) safe-to-deploy

From bytecodealliance/wasmtime. By Alex Crichton.

This crate is a single-file crate that does what it says on the tin. There are a few unsafe blocks related to utf-8 validation which are locally verifiable as correct and otherwise this crate is good to go.

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

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 implies crypto-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 percent-encoding is 2.3.1.

2.1.0 (older version) Rating: Positive Thoroughness: Medium Understanding: High

by gitlab.com/chrysn on 2020-01-31

The crate is compact and straight-forward. It is refreshingly unopinionated in that it leaves it up to the user to pick what to escape; consequently, there was little to check against RFC3986 other than that the default uppercasing rule is followed. A minor issue about unsafe code was found and reported (https://github.com/servo/rust-url/pull/583), but it's more theoretical then likely to cause practical trouble.

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

Approved without comment by gitlab.com/KonradBorowski on 2019-07-31

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

Approved without comment by kornelski on 2019-07-22

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 percent-encoding. Alternatively, you can download the tarball of percent-encoding v2.3.1 or view the source online.