Lib.rs

› pulldown-cmark › 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 pulldown-cmark is 0.10.3.

0.9.3 (older version) safe-to-deploy

From bytecodealliance/wasmtime. By Alex Crichton.

This is a large change to the pulldown-cmark crate but it tightens restrictions on unsafe code to forbid it in non-SIMD mode and additionally many changes look to be related to refactoring, improving, and restructuring. This crate is not fundamentally different from before, which was trusted, but looks to be receiving new assistance for maintainership as well.

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

ub-risk-2 (implies ub-risk-3)

Negligible unsoundness or average soundness.

Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-2

ub-risk-3 (implies ub-risk-4)
Implied by other criteria

Mild unsoundness or suboptimal soundness.

Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-3

ub-risk-4
Implied by other criteria

Extreme unsoundness.

Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-4

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…

unknown

May have been packaged automatically without a review

Lib.rs has been able to verify that all files in the crate's tarball, except Cargo.lock, 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 pulldown-cmark. Alternatively, you can download the tarball of pulldown-cmark v0.10.3 or view the source online.